I think I just figured out the solution myself: Start virtual control with ctrlX Works and configure the IP address + gateway in "settings->connectivity" Shutdown virtual control and close ctrlX Works (important!) Go to your Windows network adapter options Bridge your Ethernet connection to the virtual TAP of ctrlX Core virtual (in my case VirtualControl-DE-AD-BE-00-00-01) Remark: ctrlX Works should be closed, as it (imho) tries to create a new TAP every time a virtual machine is started; This does interfere with the bridging mechanism of windows (if not intended -- possible bug?) Since we can not use ctrlX Works to start the virtual machine, we have to do it manually. You find the corresponding .bat file in your ProgramData In my case, the "fobjft4d.user.qcow2.tap.start.bat" (folder: C:\ProgramData\Rexroth\ctrlX WORKS\virtual-controls\images\1.2.3) starts a ctrlX Core Virtual. If started manually, a new virtual TAP is not recreated --> everything works fine If your network settings are entered correctly, you should be able to access the virtual control from another PC/device in the same network and the other way around Further remark: QEMU is used for virtualization; If I'm not mistaken, ICMP/"ping" does not work for testing*. Imho the best test is to use another PC, enter the IP address of the virtual control into a browser, and then check whether the ctrlX Core Virtual login screen appears. *"if you are using the (default) SLiRP user networking, then ping (ICMP) will not work, though TCP and UDP will. Don't try to use ping to test your QEMU network configuration! " Source: https://wiki.qemu.org/Documentation/Networking I'm not very familar with QEMU, therefore, I might be wrong.
... View more
