For the latest on our response to Coronavirus (COVID-19), click here.
BGW210 Connecting to LAN device using public IP and port forwarding
I've had the following similar problem for a while in multiple settings, all using AT&T's same BGW210 equipment:
There's a device on the LAN we want external access to, i.e. security camera's and servers we want to access using ssh
We forward the appropriate ports to this device, e.g. 22 for ssh, etc
Connecting to the local device remotely using WAN address: Works
Connecting to the local device when on LAN using LAN address: Works
Connecting to the local device when on LAN using WAN address: DOES NOT WORK. The operations simply time out
This creates these problems:
When you set up the security camera app on one's smart phone and use the public IP (or in fact a domain resolving to this IP) it will ONLY work remotely, not when you're local. (And yes I understand this is ironic given that you might not need to connect to a camera when you're actually in the building.)
Same for the ssh server at my home: I have a domain that resolves to my public IP address, so I can easily ssh home when remote. I also use this to sync my files with a Sparkleshare service running on my local server. This issue means I cannot configure my Sparkleshare client to work from anywhere: when I add the project using the server's LAN IP it won't sync when remote. When I add the project using the public IP it will only work remotely
I have not encountered this problem setting up security camera's for locations using a different ISP and different equipment. Before we moved two weeks ago it used to work flawlessly with a different ISP and equipment. So I know it is possible.
There are only two explanations:
I'm missing something. If so, please tell me what
Whoever produced this router overlooked this very trivial routing scenario
Which one is it?
(Please spare me hypotheses: I just want to hear from someone who actually has this exact scenario working.)