New Member
•
3 Messages
Port Forwarding on BGW210-700 doesn't work. Has never worked.
I have a BGW210-700 as my gateway. I have never been able to get port forwarding for any services to work correctly with it. I've attempted forwarding ports for a Minecraft Server, for a Valheim Server, for an SSH server on my home Linux server. I have done a factory reset multiple times. Port forwarding has worked flawlessly when I do IP passthrough to a different device. If I rely on AT&T's provided gateway for port forwarding, it works 1 out of every 25 or so attempts, and otherwise results in a timeout. I am on firmware 4.22.5.
I've followed this documentation to a tee multiple times. https://www.att.com/support/article/u-verse-high-speed-internet/KM1215101/
Will AT&T replace my gateway with one that works if I call? If I'm forced to rent the gateway, it should work as it's supposed to. My screenshots show that:
- Port forwarding is configured to forward to the device "abyss"
- Abyss has an IP address of 192.168.1.88 permanently assigned to it.
- Verifying that abyss is resolving to 192.168.1.88
- Verification of my public facing ip address.
- ssh failing to connect to my public facing IP address via the WAN.
- ssh connecting correctly when doing it via the LAN.
JefferMC
ACE - Expert
•
33.2K Messages
5 months ago
@tonytoon is that first terminal window inside your network or at an outside host? AT&T's Gateways do not do NAT loopback (sometimes called hairpinning) so you cannot use the public address while in your network. So, if you're trying to test Port Forwarding while in your network, it's going to fail. So, for a test from outside your network:
0
tonytoon
New Member
•
3 Messages
5 months ago
@JefferMC that'd certainly explain it if that's the case. what gets me is that it occasionally works? I'll try tethering a device to my phone and see if I continue to see the issues then check back in.
0
0
JefferMC
ACE - Expert
•
33.2K Messages
5 months ago
Yeah, it occasionally works... poorly... slowly. It works just enough to make you think it works, but do not depend on it. Someone reported that the source port did funny things when they Wiresharked it. It is not supported.
You can get your own router that does do NAT loopback and set it up for IP passthrough from the Gateway.
I should also mention that since you're running SSH out in the open like that, you need to be using a certificate to secure it rather than just depending on username/password. Can't tell if you are from your samples, but thought I'd mention it.
(edited)
0
0
tonytoon
New Member
•
3 Messages
5 months ago
Don't worry - I have passwords disabled for authentication. Key based authentication only.
I have an account on sdf.org and ssh from there seems to be working so I'm hoping that was the issue. I feel silly thinking it's not working that badly, but the fact that it worked *occasionally* rather than never is what threw me for a loop.
0
0