Trying to communicate (from Europe) with/to a unit located in china, the communication seems blocked/stopped.

The edge gateway is installed in a linux environment and was possible to link to my Automation server account using the "Automation service tool". However it seems the unit cannot communicate with the Automation server (a Network scan will give the message "Gateway not connected").

(I have tested the eq. setup with units locally which works.)

Anyone having experience situation similar to this and if its possible to make this work? Will a VPN be needed possibly? Other tips?

We have tested this and it had worked at that time with China.
which device is it? Anything special?

Gateway and runtime (Control for linux SL) on a debian linux.

Thanks for your check. Good to know. I will probably travel there in about a months time so that will give me better possibility for further testing.

(on a side note, I dont get mail-updates on forum-subscriptions, need to check the topics manually)

I think I understand my problem. They are most probably related to configuration of the network. When I use DHCP for the unit to my router it all works. However when using static IP I have not managed to reach functioning state.

Trying to replicate the situation on my desk. Having a static IP on the "debian host" and a connection to my computer which then routes traffic on to internet. I have entered settings for gateway and netmask.

I can ping from my "debian plc host" to internet and also do "curl google.com" so traffic seems to find its way through and back, still "Automation server" will not find the gateway.

Any hints how a manual configuration should be done? Is it possibly a "firewall" issue of my "normal router"? Thanks for any help!

Per

Some new test.

Now I cannot connect from Automation server to my gateway in any way also from my office setup with my unit directly connected to my router by dhcp.

I can use the IDE and the tool "Connect Edge Gateway" and successfully connect to my server/link to my Automation server account. However no PLC will respond from Automation server "Network scan".

I guess the traffic should be initiated by the gateway towards automation server? Any tips on how I can diagnose my problem? Ports to be opened etc?

Thing is that this has been working previously but not now (base system has been updated from debian 12 to debian 13, but I dont know at which point it has stopped working).

Setup as before. A "Codesys Control for Linux SL" running on a debian 13 installation.

Any help/tips appreciated!
Per

Update. Found the error. Had a wrong gateway-setting. Which meant the PLC could not reach internet. Checked by "ping google.com" from the PLC.