Connect network camera ctrlx COREvirtual

[EchoHarm0ny]

Hi,
i´m using ctrlX WORKS Version: 3.2.0.
I trying to connect a network camera (https://thinklucid.com/de/product/helios2-time-of-flight-imx556/) to a ctrlX COREvirtual.

I followed this guide to connect a network device to the ctrlX COREvirtual: Guide
I can ping the network camera after finishing this setup: "ctrlX COREvirtual in port forwarding mode communicating to a device on the network"
But my app can´t find the camera in the network and also the camera utilities of the Manufacturer can´t find the camera when i´m using the ctrlX COREvirtual.

I tested it also on a real hardware (ctrlX CORE x7) without any problems, my app can find the camera.
It would be very helpful if i can use the camera also in the ctrlX COREvirtual.

i´m guessing that the configuration of my port forwarding and firewall of my host is not yet completed.
The camera Manufacturer provides some information about their default ports, but i´m not sure how to configure my windows host and the ctrlX COREvirtual to fullfilll these requirements:
https://support.thinklucid.com/knowledgebase/default-network-ports-for-lucid-cameras/

Someone has an idea?

[Sgilk]

@EchoHarm0ny ,

On your windows machine, you need to create inbound firewall rules for udp access on ports (3956, 49152:65534) and tcp access on port 58243. 

You can enable tcp port forwarding from your Windows host to the virtualCORE in the extended device settings within ctrlX WORKS. For your device, it will use 58243.

This setting does not handle udp, so you will need to manually update the launch.bat file for your virtualCORE to forward these ports. See this thread for similar discussion. If you can select which udp port to use rather than random allocation within the range, it would make this easier. I am not finding any easy way to forward a range. You may need to write a script that generates the hostfwd syntax for all of the udp ports and copy that into the launch.bat