Issue reaching device on VPN(Ixon)

[ham1hel]

Hello
We are using the ixon app on a coreX3 to connect to a machine.
Internet connection goes in on XF10 and the machine network is connected on XF51.

We have now discovered that one of the devices (PR4) is not reachable from the PC when connecting through IXON but other devices (CML)are the subnet is configured on the ixon as 192.168.142.0 with subnet 255.255.255.0 and gateway to the XF10 adress of the core.

We are also able to ping the PR4 from the core but not from the PC and we are able to ping the CML from the PC so the subnet is reachable.

does anyone have an idea what might be the issue? We have tried to disable the firewall thinking that was the issue but it seems thats not the case

Regards
Marcus

[CodeShepherd]

Could you add a topology drawing with all set IP Adresses and subnet masks, for a better understanding? Further more the settings of the cloud adapter and firewall could be helpful.

I will also forward your request to the ixon support directly support@ixon.cloud. 

[ham1hel]

Network topology:

I also attached an image of the configured subnets in ixon and images how the ping looks like from the core and from the PC connected through IXON. It could be something with the IPC firewall but i would expect that when the core receives a ping reply we would also be able to get one through the VPN.

[CodeShepherd · Accepted solution]

Here the reply of the IXON support team, please get in direct conact with them for further questions support@ixon.cloud:

The IXagent, or Cloud Connector, provides remote access to the device on which you install the IXagent, not to any of the devices locally connected to it. Whether it's possible to remotely access any of the connected devices depends mainly on the device on which the IXagent is installed, because thát device needs to route the traffic properly. This is not not managed by the Cloud Connector for 2 reasons: (1) It doesn't have this much control over the local device and (2) it's outside of scope of the IXagent. The purpose of the IXagent is to access a single device remotely. If someone wishes to access multiple devices, they can either choose for the IXrouter or see if they can manage the routing themselves on that device. We do not provide any support on the latter.

This is also mentioned in our public IXagent article (https://support.ixon.cloud/s/article/What-is-the-IXagent😞
"The IXagent and IXrouter share a lot of functionalities, but both have their benefits.

If you're looking to only remotely access one particular part of the machine, e.g. the PLC, and nothing more, then the IXagent may be a perfect fit for you. In most other situations the IXrouter would instead be your best choice."

Reading the forum post, it seems they wish to remotely access devices that are locally connected to the device that is running the IXagent. Apparently this does work for some (CML?) and not for others (PR4?), though I don't know either abbreviation. Being able to remotely access the CML can be considered a positive gain, and not an expected functionality as per the reasons explained above.

I hope this information helps. If you have any questions, please let me know.