can't reset internal IP to 10.0.0.x on 3801HGV?

rati0nal · ‎04-25-2012

Just landed a brand-new 3801HGV and I'm reading the forums here, gradually finding out that things are a bit different now on the inside.

I have a bunch of devices set up with static IPs in the 10.0 network. NAS, printers, linux servers, home automation stuff. I've moved all of it between three or four different houses and different ISPs, and each time I get a new DSL or cable modem, the first thing I do is hook up the new box and reset its internal IP to 10.0.0.1 and then when I plug it into the rest of my setup, everything else just worked. Until this time.

Now, when I try to change the internal ip on the HGV to 10.0.0.1, it tells me

"ERROR: Router Address should not start with 10."

since when does a box get to have veto power over what IP I decide to use for my private network?

I don't mind allowing the HGV to hand out IP addresses to the DHCP devices on my network, like laptops and handhelds and stuff. But it's going to be a colossal pain in the BUTT if I have to choose between letting it re-assign IPs in the 192.168 to everything, or manually going through all my static devices and the software that uses them and then changing them over from 10.0.0 to 192.168.

Please tell me there is some kind of "god mode" on the 3801HGV that will allow me to overcome this insubordination.

{edited to comply with guidelines}

Computer-Joe · ‎09-19-2008

rati0nal wrote:
Just landed a brand-new 3801HGV and I'm reading the forums here, gradually finding out that things are a bit different now on the inside.

I have a bunch of devices set up with static IPs in the 10.0 network. NAS, printers, linux servers, home automation stuff. I've moved all of it between three or four different houses and different ISPs, and each time I get a new DSL or cable modem, the first thing I do is hook up the new box and reset its internal IP to 10.0.0.1 and then when I plug it into the rest of my setup, everything else just worked. Until this time.

Now, when I try to change the internal ip on the HGV to 10.0.0.1, it tells me

"ERROR: Router Address should not start with 10."

since when does a box get to have veto power over what IP I decide to use for my private network?

I don't mind allowing the HGV to hand out IP addresses to the DHCP devices on my network, like laptops and handhelds and stuff. But it's going to be a colossal pain in the BUTT if I have to choose between letting it re-assign IPs in the 192.168 to everything, or manually going through all my static devices and the software that uses them and then changing them over from 10.0.0 to 192.168.

Please tell me there is some kind of "god mode" on the 3801HGV that will allow me to overcome this insubordination.

{edited to comply with guidelines}

Sorry the only "god mode" here is the one AT&T has over your creditcard. You can always put your old router between the 3801 and the rest of your network.

__________________________________________________________
How can you be in two places at once, when your not anywhere at all?
------------------------------------------------------------------------------------------------------
I really want to become a procrastinator, but I keep putting it off.
------------------------------------------------------------------------------------------------------
There are three kinds of people, those that can count, and those that can't.
------------------------------------------------------------------------------------
“Our great democracies still tend to think that a stupid man is more likely to be honest than a clever man, and our politicians take advantage of this prejudice by pretending to be even more stupid than nature has made them." :Bertrand Russell

rati0nal · ‎04-25-2012

[Per Guidelines: Keep it Relevant and Appropriate].

thanks a bunch, deathstar. So glad that FISA thing got cleared up for you.

SomeJoe7777 · ‎01-30-2008

The speculation is that AT&T is preparing to deploy some type of carrier grade NAT solution where your gateway will be assigned an outside IP address in the 10.x.x.x range. This precludes using the 10.x.x.x range on your LAN since the addresses could not be translated.

As stated, you could use your own router between the AT&T gateway and your LAN to allow 10.x.x.x to still be in use, or you can renumber to one of the other RFC1918 private address ranges of 192.168.x.x/16, or 172.16.x.x/12.

Computer-Joe · ‎09-19-2008

SomeJoe7777 wrote:
The speculation is that AT&T is preparing to deploy some type of carrier grade NAT solution where your gateway will be assigned an outside IP address in the 10.x.x.x range. This precludes using the 10.x.x.x range on your LAN since the addresses could not be translated.

As stated, you could use your own router between the AT&T gateway and your LAN to allow 10.x.x.x to still be in use, or you can renumber to one of the other RFC1918 private address ranges of 192.168.x.x/16, or 172.16.x.x/12.

Is that something they're doing to put off the IPv6 change-over, or to consolidate DNS or static IP assignment?

__________________________________________________________
How can you be in two places at once, when your not anywhere at all?
------------------------------------------------------------------------------------------------------
I really want to become a procrastinator, but I keep putting it off.
------------------------------------------------------------------------------------------------------
There are three kinds of people, those that can count, and those that can't.
------------------------------------------------------------------------------------
“Our great democracies still tend to think that a stupid man is more likely to be honest than a clever man, and our politicians take advantage of this prejudice by pretending to be even more stupid than nature has made them." :Bertrand Russell

SomeJoe7777 · ‎01-30-2008

I think it's because AT&T is behind on IPv6 implementation. Other ISPs like Comcast are already deploying IPv6 to customers, including residential customers (upon request) while AT&T is struggling to even deploy it to enterprise customers.

I think the fact is that they're simply running out of available IPv4 address space and need to buy some time to get ready for IPv6 deployment. The 108.x.x.x/8 block was one of the last ones allocated by IANA, and AT&T has already been using it for several months now. They continue to deploy more U-Verse customers and more smart phones, and I think they're projecting that they will run out of IPv4 address space before IPv6 is really ready.

They don't have IPv6 firmware for the U-Verse gateways yet (except the NVG510, although that thing barely functions), they don't have IPv6 multicast infrastructure for IPTV, the VOIP system isn't IPv6 yet, and there are huge numbers of end consumers who have computers and other devices that don't have IPv6 capability. They're in trouble, and they need an out. CGN is the only viable solution for them because they waited so long to start IPv6 deployment plans.

Computer-Joe · ‎09-19-2008

Hmmmm, AT&T behind the eightball again, imagine that.

__________________________________________________________
How can you be in two places at once, when your not anywhere at all?
------------------------------------------------------------------------------------------------------
I really want to become a procrastinator, but I keep putting it off.
------------------------------------------------------------------------------------------------------
There are three kinds of people, those that can count, and those that can't.
------------------------------------------------------------------------------------
“Our great democracies still tend to think that a stupid man is more likely to be honest than a clever man, and our politicians take advantage of this prejudice by pretending to be even more stupid than nature has made them." :Bertrand Russell

Casper42 · ‎04-30-2012

Got a notice today in the mail from AT&T U-verse that says they need me to reconfigure my entire home network before July 6th because I am using 10.x addresses at home. (as opposed to 192.168.x.x for instance)

Wondering if anyone else got such a letter and WHY they care exactly what I use for my home network?

If they would stick to using public IPs for the stuff outside my RG, then they shouldnt need me to reconfigure anything. This is the nature of NAT and havign a public IP.

If they are going to be essentially doube-NAT'ing all our connections, thats something I would want to know.

SomeJoe7777 · ‎01-30-2008

Two things:

1. The speculation is that AT&T is preparing to deploy carrier-grade NAT (CGN) where the 2Wire routers are going to get an outside IP address in the 10.x.x.x range. This precludes using 10.x.x.x on your LAN, since the addresses could not then be translated.

See the following thread for additional details:

http://forums.att.com/t5/Residential-Gateway/can-t-reset-internal-IP-to-10-0-0-x-on-3801HGV/td-p/320...

2. Can you please scan and post this letter here in the forum? (Use the small icon that looks like a tree to insert a picture).

GeekBoy · ‎11-06-2008

I currently use a 10.0.* address scheme at home, and I have not received an email from AT&T about my address scheme (yet).

equals42 · ‎04-02-2009

This [word filter avoidance] since I pay for a static IP range. Why should I have to change my internal network for their CGN? I have tried talking to techs for hours now and I'm getting nowhere. No I'm going to have to put a router between to RG and my network to avoid changing my subnets? I've had my stuff on 10.x since before Pacbell DSL.

equals42 · ‎04-02-2009

I haven't got an answer from them yet about why. I pay for static. I'd like to know why I should have to change off that internal network.

ajohnson443 · ‎01-09-2012

Has anyone else received a letter/email from AT&T stating that if you are using the 10.X range of IP addresses on you internal lan segment you will be forced to change to another addressing scheme in July?

I can not for the life of me see why AT&T thinks they can control anything my side of the residential gateway. I have two 10.X segments running and both are required due to limitations of my VPN software required to connect to my corportate networks. Once connected to the VPN they only allow acces to local resouces if they are on a 10.232.X.X network, So if AT&T pursues this forced change I will no longer be able to unless I change providers.

This is RIDICULOUS! Now, if they would allow me to run the gateway in bridged mode and utilize my own router, etc then I might be able to work around it, as it is the whole router behind a router is just a royal pain in the rear and not worth my trouble to set it up again. It will be easier to just drop AT&T and go with the competition. They have higher bandwidth anyway

Lwoxen · ‎03-24-2009

Just got a letter from ATT saying that I need to change my network from the current 10. that I am using to something else. Anyone have any ideas what ATT is planning to appropriate a private network ip scheme?

{post merged}

BeeBeeSA · ‎06-26-2009

See Somejoe's answer in this thread: http://forums.att.com/t5/Residential-Gateway/can-t-reset-internal-IP-to-10-0-0-x-on-3801HGV/m-p/3205...

{post merged}

"If you find this post helpful and it solved your issue please mark it as a solution. This will help other forum members locate it and will also let everyone know that it corrected your problem. If they have the same issue they will know how to solve theirs"

Koki4o · ‎04-13-2011

It is ridiculous. I never even got a letter from them to inform me of the change. Also, I paid $100 for the router and they don't even give me control over it. And how can they update the firmware whenever they want without my knowledge? I hate the 192.168 addresses, they are more difficult to type in. It's time to ditch AT&T.

fearlessuser · ‎05-26-2012

Koki4o wrote:
It is ridiculous. I never even got a letter from them to inform me of the change. Also, I paid $100 for the router and they don't even give me control over it. And how can they update the firmware whenever they want without my knowledge? I hate the 192.168 addresses, they are more difficult to type in. It's time to ditch AT&T.

http://www.att.com/u-verse/att-terms-of-service.jsp

NOTICE ABOUT AUTOMATIC SOFTWARE UPGRADES. AT&T, or its applicable third party licensors may provide Software upgrades, updates, or supplements (such as, but not limited to, adding or removing features or updating security components). You understand and agree that AT&T, or the applicable third party licensor, have the unrestricted right, but not the obligation, to upgrade, update, or supplement the Software on the Equipment at any time. Although unlikely, Software upgrades, updates, or supplements could reset your Equipment and erase saved preferences and stored content.

If people are having this big of a deal with 10.0.0.x going away, I would really hate to see what's going to happen when IPv6 comes out and everyone has to type in a few more numbers (and letters) for that to work.

fearlessuser · ‎05-26-2012

equals42 wrote:
This [word filter avoidance] since I pay for a static IP range. Why should I have to change my internal network for their CGN? I have tried talking to techs for hours now and I'm getting nowhere. No I'm going to have to put a router between to RG and my network to avoid changing my subnets? I've had my stuff on 10.x since before Pacbell DSL.

Static IP's are public. This change has to do with private addresses. If you're actually using your public addresses, this will mean nothing to a device with a public static address. Only thing you have to worry about is the internal devices if they are assigned one of the 10.0.0.x addresses.

wswartzendruber · ‎02-02-2011

Hey guys, I used to be an AT&T customer. I see that you are all having problems with them implementing carrier-grade NAT. It seems they require usage of the 10.0.0.0/8 subnet. This is rather odd, since they're supposed to use the 100.64.0.0/10 subnet instead. Perhaps AT&T planned things so poorly that they don't have the time to reconfigure their systems for the new subnet.

I wish you all well. Although I sincerely hope none of you have Xbox LIVE or PlayStation Online. You may find your online gaming options to be...limited.

Anyway, my current ISP has recently enabled native IPv6 access for my DOCSIS 3.0 modem. Cheers!

equals42 · ‎04-02-2009

Just got my DOCSIS 3 modem installed. 100mb/s download and 6 up for less than but close to the amount I was paying for 24 down with Uverse. I love the Uverse TV so I won't be pitching that yet but at least the cable company replaced the bad line in the alley which caused me problems before I moved to Uverse.

Good luck everyone. Oh and IPv6 is rolling out on my cable company but I haven't heard much from Uverse. Not that IPv6 is a game-breaker for me but as a UNIX guy, I'd sure like to be able to play with it at home without funky tunnels, etc.

aforkosh · ‎06-09-2012

I did not receive the letter, but I use my 2Wire device as a gateway only; I have my Airport Extreme router in the DMZ. As it turns out, the default address range for the Airport Extreme is in the 10.0.x.x range, so people doing what I did may be directly affected by this change without notice. (I changed to the 172.16.x.x range, but it a necessitated an hour or so of running around the house to reset various computers and other Internet-connected devices. It is not a trivial process.)

I'm more concerned about the effect of double NATing on some Internet services, in particular those where I remotely connect to a device in my home from outside. Examples include the Back to My Mac service (allows me to view my home computer and screen share from a public Internet connection) and various Sling Player services that allow be to remotely control and view output from my Digital Video Recorder. Can AT&T swear that these services will not be upset by their changes?

When I tried going through Uverse technical support, they claimed to know nothing about this.

IdontlikeU_v_er… · ‎07-13-2012

So I have had my modem replaced now twice from this issue. I was able to actually get a Network Tech that understood the issue and he was baffled as well why private 10.10.0.x addressing was being errored. My 2nd new modem in 6 months is due tomorrow.