chrisdutz commented on issue #1519:
URL: https://github.com/apache/plc4x/issues/1519#issuecomment-3943440771
Ok ... so I purchased a VPN router that works standalone after giving up on
my Ubiqity device.
Here I could perfectly replicate the issue.
Turns out that it's actually not a bug in the driver ... it was a
configuration problem. Most probably 2 separate ones:
First of all, when requests came in from my VPN, the requests were coming
from a subnet my PLC didn't know. So I had to make sure the VPN router is
assigned as default gateway on the PLC.
In my case when dialing in to the VPN router, my client device gets a
dynamic IP address. So if I connect to the PLC, I was connecting from an IP
address the AMS router didn't know about and with an AMS net id that it didn't
know about.
In my case registering an ams net id in the router that matches the "{vpn
client ip}" ip and "{vpn client ip}.1.1" ams net id, I was able to correctly
connect to a remote AMS machine using a VPN.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
