Hurry! Find the perfect gift today! Everyone gets our best deals on any smartphone!
Get superfast AT&T Fiber internet
JimDiMcC's profile

Tutor

 • 

6 Messages

Thursday, August 17th, 2017 12:17 AM

AT&T Fiber 1Gig Service = multiple Public IPs

Having a number of service issues with my Gig service so trying to shoot down a few ideas.  Any one know why AT&T started using two different IPs based on protocol.  45.x.x.x WAN address for HTTP(S) and 104.x.x.x and 198.x.x.x  for other protocols (e.g. SSH)?  I understand for traffic mgmt, but it appears it might be impacting a number of inconsistent speed issues (wired and wireless).  Also, certain tools like OpenDNS don't work with these dual IPs.

 

Anyone in AT&T Traffic Mgmt / NOC explain why?  (vs. theories)

 

Jim

ACE - Expert

 • 

33.5K Messages

6 years ago

What do you mean by "using two different IPs"?  Using for what?  Your gateway's external IP?  The next hop in the route after your Gateway?  Can you explain further?

 

Tutor

 • 

6 Messages

6 years ago

On the WAN side of the BHR (Pace).  I connect to a website and it says I have source IP address 45.x.x.x, I connect to a SSH server and it says I have a Source IP address 104.x.x.x (I am not using a proxy or Tor or any special / weird software setup).  OpenDNS can't even handle it for its filtering.

 

Traceroute

 

1  homeportal (192.168.1.254)  6.827 ms  7.648 ms  5.299 ms

2  162-231-212-1.lightspeed.rcsntx.sbcglobal.net (162.231.212.1)  19.769 ms  8.533 ms  6.412 ms

3  71.155.13.226 (71.155.13.226)  9.212 ms  8.143 ms  7.697 ms

4  70.143.193.186 (70.143.193.186)  13.122 ms  11.490 ms  9.174 ms

5  12.83.80.157 (12.83.80.157)  13.154 ms

    12.83.80.153 (12.83.80.153)  12.400 ms

    12.83.80.157 (12.83.80.157)  9.644 ms

6  12.120.51.106 (12.120.51.106)  9.615 ms  10.052 ms  9.294 ms

7  12.120.142.104 (12.120.142.104)  9.065 ms  10.340 ms  10.379 ms

8  a23-221-32-202.deploy.static.akamaitechnologies.com (23.221.32.202)  8.237 ms  9.128 ms  9.118 ms

 

Jim

ACE - Expert

 • 

33.5K Messages

6 years ago

Have you tried this with multiple SSH hosts to confirm that there's not just some mis-configuration at that SSH host?  And/or web sites (I'm assuming you're using something like whatismyip.com)?

 

Also, can you provide at least two octets of these IPs?  104 and 45 are pretty fragmented as to where they're assigned.

 

Not finding what you're looking for?