It's all good btw, learned that the runtime doesn't isolate the networks that are involved so changing the ethernet subnets away from the Wi-Fi's subnet was all I needed (maybe some config file changes helped, can't say for certain)
I've also noticed that when I turn off "enp1s0", suddenly the source IP for the ModbusTCP changes to that of "enp2s0", which is what makes sense to me. When I turn it back on, the source IP remains that of "enp2s0".
I have an IPC with 2 ethernet ports and 1 Wi-Fi. I'm using ModbusTCP with the ethernet port named "enp2s0" connected to my remote I/O. This works fine when testing with Python and also works with CODESYS, but CODESYS is only able to scan for the Linux SoftPLC when I turn off the "enp2s0" interface. In other words, I can't get online with the IDE if I want my ModbusTCP comms to run with CODESYS. I'm using a Linux SoftPLC that has the following entry in CODESYSControl.cfg, hoping that this will allow...