Topic 'Routing issue on static ip block' in forum 'AT&T U-verse' - dslreports.com

Re: Routing issue on static ip block

Tue, 05 Feb 2013 22:49:17 EDT

David posted : this type of thing happened before when SBC at the time got a 75.x.x.x address and some web admins needed to update their lists and such. Thing is the site is blocking the IP address possibly due to a BOGON list or an old deny list needing updated. removed expects this problem to be a bit more prevalent as of late as the IPv4 shortage is catching up and lots of new IP blocks being turned up.

Give this a shot.... as some sites might be blocking the IP's. This tip is courtesy of removed .

»www2.removed.us/ipguide/
--
If you have a topic in the direct forum please reply to it or a post of mine, I get a notification when you do this.
Koetting Ford, Granite City, illinois... YOU'RE FIRED!!

Re: Routing issue on static ip block

Sat, 02 Feb 2013 10:09:55 EDT

anon posted : You have to allow the gateway to using the static ip to the specific device using DCHP, there is a page in the interface when you see each device and the IP addressed assigned, you need to change the settings there and not on your device.

Re: Routing issue on static ip block

Fri, 01 Feb 2013 01:34:56 EDT

bgreganti posted : Dennis, Thanks for the tip. I didn't exactly understand what the direct forum was when I posted.

wayjac, thanks for the suggestion as well. I'm pretty sure it's not the DMZ+ mode because I turned it off and connected a computer directly to the RG with a static IP and I got the same results.

Re: Routing issue on static ip block

Thu, 31 Jan 2013 15:57:09 EDT

wayjac posted :

said by bgreganti:

I have an ASUS N66U router on one of those public static IPs and configured for DMZ+ mode

Using the dmzplus mode may be the problem......the gateway ip address should be the 3801 public ip address
The 3801 can be configured to allocate the public ip's via dhcp, dhcp reservation and manual static allocation

Re: Routing issue on static ip block

Thu, 31 Jan 2013 15:45:01 EDT

Dennis posted : Without your /29 or BAN it's almost impossible to troubleshoot. I'd recommend posting on the direct forum where you can post information securely.

»AT&T Direct

It's probably a pretty easy fix. I think I know what it is already but like I said can't really see more without details.
--
My Blog. Because I desperately need the acknowledgement of others.

The Judd Family site!

Routing issue on static ip block

Thu, 31 Jan 2013 03:06:14 EDT

bgreganti posted : In hopes that someone will read this who can fix it, I'll try to give as much detail as possible.

Since we've had U-verse I've never been able to reach www.hgvclub.com. Starting just a few days ago I can no longer reach www.unionbank.com either. Since my bank is important, I started investigating the issue and found that it only affects my static IP block.

I have a 3801HGV with DHCP giving out private 192.168.0.x addresses. I also have a public static IP block assigned as a supplemental network. I have an ASUS N66U router on one of those public static IPs and configured for DMZ+ mode. The router provides 192.168.1.x addresses to devices behind it.

After some testing I determined that any device connected to the RG using one of my public IPs can't reach those sites. Using a private IP and NATing through the RG works fine.

I have contacted support two days ago and opened a case with tier 2, who said they would pass it up to the people who can fix it. From what I'm reading here I thought it might be quicker to just ask for help here.

Traceroute from a public IP...


1) 192.168.1.1 (192.168.1.1) 20.259 ms, 8/8 ps, 0.0% loss
2) 172-8-253-62.lightspeed.irvnca.sbcglobal.net (172.8.253.62) 20.249 ms, 7/7 ps, 0.0% loss [AS 7018] United States
3) * * *

and from a private IP with NAT...


1) homeportal (192.168.0.254) 15.170 ms, 2/2 ps, 0.0% loss
2) 108-206-88-3.lightspeed.irvnca.sbcglobal.net (108.206.88.3) 43.682 ms, 2/2 ps, 0.0% loss [AS 7018] United States
3) * * *
4) * * *
5) * * *
6) 12.83.38.133 (12.83.38.133) 58.744 ms, 2/2 ps, 0.0% loss [AS 7018] United States
7) gar4.lsrca.ip.att.net (12.122.129.93) 57.650 ms, 2/2 ps, 0.0% loss [AS 7018] United States
8) cr84.la2ca.ip.att.net (12.122.129.90) 224.504 ms, 2/2 ps, 0.0% loss [AS 7018] United States
9) cr2.la2ca.ip.att.net (12.123.30.250) 174.071 ms, 2/2 ps, 0.0% loss [AS 7018] United States
10) cr1.slkut.ip.att.net (12.122.30.29) 204.757 ms, 2/2 ps, 0.0% loss [AS 7018] United States
11) cr2.dvmco.ip.att.net (12.122.30.26) 175.015 ms, 2/2 ps, 0.0% loss [AS 7018] United States
12) cr1.cgcil.ip.att.net (12.122.31.86) 197.270 ms, 2/2 ps, 0.0% loss [AS 7018] United States
13) cr2.cgcil.ip.att.net (12.122.2.54) 155.297 ms, 2/2 ps, 0.0% loss [AS 7018] United States
14) cr1.n54ny.ip.att.net (12.122.1.1) 147.547 ms, 2/2 ps, 0.0% loss [AS 7018] United States
15) 12.123.250.133 (12.123.250.133) 94.458 ms, 2/2 ps, 0.0% loss [AS 7018] United States
16) * * *

If there is any more info I can provide let me know.

Thanks in advance.