Update:
previously I changed over to X47 (controller ip 192.168.0.1), and configured the LAN of the router to be 192.168.0.100
this worked great as port forwarding worked with this config, but then would prevent the controller from booting on cold boot (i'm not sure why, maybe the controller would see the router as a internal component and sends it messages that the router ignores?)
to solve this, I changed the router to be 192.168.1.1, and have DHCP pool to be 192.168.0.2-254, which allows access from all local clients, but not VPN clients (port forwarding does not work, because router is not on the same subnet as controller? i think)
I've looked into the VPN suggestion, and found that my router does have this option, after setting up openVPN on it, I am able to connect to the router with openVPN.
But I cannot access the controller 192.168.0.1, I can access everything else on that local network tho,
my guess is that 192.168.0.1 is somehow special and not being routed through openVPNmy remote local network uses 14x.x.x.x so it's not an issue of my remote local network intercepting anything
side note: by default VPN clients are given 10.8.0.x ip range, I did test changing local client to 192.168.0~126 and VPN to 192.168.0.128~254 but that didn't work either, so it's not a issue of subnet
my guess is that 192.168.0.1 is somehow special and not being routed through openVPN
would it possible to change the controller ip from 192.168.0.1 to 192.168.1.100 so I can test this theory?I've heard changing the internal ip of the controller often results in them bricking/not booting
Another thing I could try is switch back to KLI, and see if that works with openVPN, but then I lose the ability to remote desktop....
Kuka makes things so complicated...Thanks