Announcements

For the latest on our response to Coronavirus (COVID-19), click here.

New Member

 • 

2 Messages

Thu, Jan 30, 2020 2:24 PM

BGW210 Connecting to LAN device using public IP and port forwarding

Hey,

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:

  1. I'm missing something. If so, please tell me what

  2. 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.)

Responses

Accepted Solution

Brand User
ATTHelp

Administrator

 • 

111.9K Messages

2 months ago

We're here to help clarify this for you, @ricardovdbroek!

 

Our gateways were designed for a basic internet setup, and what you're detailing is called NAT loopback, which may not be supported. 

 

You can still access the devices on a LAN from the private network and external on a separate WAN, as you have already been able to do. If you do wish to access the LAN using the WAN address, you may need to look into going with a router behind router setup and using a router that supports it.

 

We hope this was able to assist you- let us know!

 

Donovan, AT&T Community Specialist

Still need help? Ask a question! Our 1.4 million members typically respond within 1 hour.

*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.

New Member

 • 

2 Messages

Thank you! I was pleasantly surprised to see using IP Passthrough work to solve this issue! I did already have a second router setup behind your gateway, so configuring the setup outlined in the article you sent was pretty easy. I hadn't tried it before since it seemed overkill for what I'm trying to do, but it does actually simplify things greatly since I may have other ports to forward.

Thank you so much and I hope it helps out other folks who are running into the same thing!

Brand User
ATTHelp

Administrator

 • 

111.9K Messages

Hello @ricardovdbroek,

Glad you were able to get your problem resolved. Please feel free to contact us if you have any questions or concerns. Thank you for choosing AT&T.

Charles, AT&T Community Specialist

Still need help? Ask a question! Our 1.4 million members typically respond within 1 hour.

*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.
AT&T TV – All Your Entertainment In One Spot.  Learn more…