Sonic.net

After switching to the new Pace 5168N modem from my old Pace 4111N as part of a recent upgrade to Fusion X2, I am no longer able to access my locally hosted website from the local network using the DNS record or external IP (I can't access http://www.[mydomain] from a local computer) even though the firewall is set up to allow external access and external computers can connect just fine.

With the 4111N this worked fine, and, as much as possible, I have attempted to replicate the configuration between the two modems.

Additional details on setup and the failing cases:
* The 'LocalWebServer' is assigned IP 192.168.42.100, and the router has a firewall rule to direct web traffic to this computer
* 'LocalClient' is another computer connected to the same router

LocalWebServer access http://192.168.42.100: works
LocalClient access http://192.168.42.100: works
RemoteClient access http://192.168.42.100: FAIL (as expected)
LocalWebServer access http://<externalIP>: FAIL
LocalClient access http://<externalIP>: FAIL
RemoteClient access http://<externalIP>: works
LocalWebServer access http://www.[mydomain] FAIL
LocalClient access http://www.[mydomain] FAIL
RemoteClient access http://www.[mydomain] works

Does anyone else have a similar setup that works? Any tips on key configuration settings? What could be different between the 5168N and the 4111N that is causing this to fail?

cherian wrote:After switching to the new Pace 5168N modem from my old Pace 4111N as part of a recent upgrade to Fusion X2, I am no longer able to access my locally hosted website from the local network using the DNS record or external IP (I can't access http://www.[mydomain] from a local computer) even though the firewall is set up to allow external access and external computers can connect just fine.

If you do a search for pace 5168n "nat loopback" you'll find a couple of threads in the AT&T forums where people suggest the only way for NAT loopback to work is to use DMZplus or IP Passthrough. https://www.google.com/search?q=pace+51 ... oopback%22

You should be able to connect the Pace 4111N in the 5168N's DMZ and it should work. Just make sure both routers don't use the same subnet.

I no longer have the 4111N, since I had to return in to Sonic. DMZ is a good suggestion though it seems like a step down in terms of security. Thanks!

Thanks for finding this. Going forward, we'll ask Pace to build in hairpin routing into their port forwarding functionality going forward.

adame wrote:Thanks for finding this. Going forward, we'll ask Pace to build in hairpin routing into their port forwarding functionality going forward.

Could you ask them to provide SNMP capabilities? I'm also finding http/https monitoring every 5 minutes makes the web pages 404 after around 3.5 days. Apparently those who had other Pace models found their standard MIBs don't provide DSL metrics. I can ping the device and internet still works but the web server crashes. Each time the 5031 reboots a new certificate is created, too. I guess this is why the device takes so long to re/start.

Guest wrote:Could you ask them to provide SNMP capabilities?

Is this for the Pace 5031 on your FTTN service? If so, this device is resold and managed by AT&T, and they control what software is loaded on and off the device. Unfortunately, we don't have any input in what they choose to load onto their gateway. Sorry about that!

adame wrote:

Guest wrote:Could you ask them to provide SNMP capabilities?

Is this for the Pace 5031 on your FTTN service? If so, this device is resold and managed by AT&T, and they control what software is loaded on and off the device. Unfortunately, we don't have any input in what they choose to load onto their gateway. Sorry about that!

I was referring to the 5031 from AT&T but it would also be nice if Sonic considers offering SNMP for Sonic-owned hardware. AT&T's 5031 http/https is just not as robust as my old Cayman 3546's telnet/SNMP. I used SNMP to get as much info as possible but DSL statistics aren't available so I used the telnet interface--I never used the 3546's web interface to scrape statistics.