01-15-2013 4:47 PM
2WIRE/PACE 3600/3800/3801 Static IP Setup
1. Open your browser and browse to 192.168.1.254
2. Click on "Settings" across the top
3. Click on Broadband" under settings
4. Then click on " Link Configuration" under Broadband
5. Under "Supplementary Network" you will have a check mark "Enable" for "Add Additional Network" make sure to check the box
6. The "Router Address" will be the last usable address in your block.
(Note: "Auto Firewall Open" will allow all Static IPs to bypass the firewall)
7 Click Save at the bottom Right and the gateway is not ready to handle your Static IPs
Note: these are the Subnet masks used in the router;
11-20-2013 2:42 PM
I've tried this, and set the NICs on the servers on the LAN to use the static IPAs. They can ping the 2WIRE gateway address for the public IP range, but they cannot reach the Internet. Also, they do not show up in the 2WIRE's list of devices.
I've been fighting with this for months. I hear AT&T U-Verse has a Motorola unit that is less brain-dead than the 2WIRE, but I haven't been able to get one. Yet.
11-22-2013 12:21 PM
I am sorry you are running into this issue, and hopefully, it is a simple step that will fix it. When it comes to setting up the static IP block you are paying for to work through the 2wire router, you need to program it into the router so it will handle that subnet.
To do so:
Hopefully, this resolves your issue. Let us know how it goes.
11-22-2013 1:27 PM
I have done all that, although:
The sole exception is my Vonage modem, which I spent hours trying to get to work with address x.x.x.125. It was still not working when I went to bed, but it started working by itself in the middle of the night. It can now be reached from the Internet, and can itself reach the Internet.
I am not currently where I can report on the 'IP Address Allocation' list -- but only a very few of the static NICs show up in the list, despite attempts to force discovery through ping, nmap, and curl requests to and also through the 2wire. Whether a NIC shows up in the 2wire's device list or not makes no difference to its accessibility.
11-22-2013 1:48 PM
Thank you for that information. It looks like you have set everything up right. It appears that it may be some routing issue, whether it is with the U-verse router, or a router beyond that. I can definitely help with both. I will be sending you a private message to discuss this further, since it will be more account specific information.
11-30-2013 2:17 AM - last edited on 12-01-2013 11:31 AM by SadathCS
I'm now having a similar problem with my 2Wire HGV-B 2701, inasmuch as my static IP addresses simply do not seem to route correctly.
This setup was working fine for ~2 years, but two days ago, no traffic routes to the public IP addresses at all. Traffic from the private subnet would make it just fine. There's been no configuration changes on my end, either to the servers or the router involved.
2Wire HGV-B 2701
Router IP address: x.x.x.174
Static IP block (configured as the supplemental network): x.x.x.48/255.255.255.248; router address here is defined as x.x.x.54
Private network: x.x.x.1/255.255.255.0
Computer A, with the public IP:
Gateway: x.x.x.54 (router's public IP address)
Computer B, on the private subnet:
Gateway: x.x.x.1 (router's private IP address)
My computer on the private network (x.x.x.2) can browse the Internet just fine, so line works, router works, etc. From this computer, doing a tracert to Google's nameservers works fine:
Tracing route to google-public-dns-a.google.com [188.8.131.52]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms homeportal [192.168.0.1] <---- Router's private IP
2 9 ms 9 ms 9 ms x-x-x-2.lightspeed.chcgil.sbcglobal.net [99.
117.56.2] <---- Router's x.x.x.174 gateway
3 * * * Request timed out.
4 38 ms 560 ms 599 ms 184.108.40.206
5 8 ms 8 ms 9 ms ggr3.cgcil.ip.att.net [220.127.116.11]
6 * * * Request timed out.
7 10 ms 9 ms 9 ms 18.104.22.168
8 11 ms 10 ms 9 ms 22.214.171.124
9 23 ms 22 ms 23 ms 126.96.36.199
10 31 ms 23 ms 23 ms 188.8.131.52
11 * * * Request timed out.
12 171 ms 131 ms 20 ms google-public-dns-a.google.com [184.108.40.206]
The problem is that the same request from Computer A, on the static IP address, fails:
Tracing route to 220.127.116.11 over a maximum of 30 hops
1 <1 ms 1 ms 1 ms x-x-x-54.uvs.cicril.sbcglobal.net [x.x.x.54] <---- router's supposedly public IP address
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
Similarly, I allowed the router to respond to pings, and I used the website http://ping.eu/ping to send pings remotely. If I ping x.x.x.174 (the router's IP), it works; however, if I ping x.x.x.54 (which should also be the router's IP), it doesn't work.
As far as I can tell, something upstream of the router is discarding packets that originated from my static IP address block. I don't know if this is due to the subnet difference between x.x.x.x andx.x.x.x or what, and I'm hoping you can help.
(IP address removed for security reasons)
11-30-2013 9:40 AM
Since this is account specific I would recommend that you send a private message to the escalation team at ATT U-Verse Care and someone will get in touch with you. Their normal business hours are from 7am to 10pm Central Time. Please take into account weekends when contacting them.
To check for their reply, click the little blue envelope.
11-30-2013 10:21 AM
Since it sounded like I was having a similar problem to THX1138 (computers with the static IP can reach the router but cannot reach the Internet), I was hoping there'd be some insight.
12-01-2013 11:35 AM
We're sorry about the trouble you are having with your block of Static IP's. We have received your private message and will continue working with you via private message to ensure these Static IP's are routing traffic correctly.
Need more help? Feel free to search the AT&T Community for great answers. You can also get immediate troubleshooting steps from the myAT&T app. Simply login, scroll and click Fix it Now! Support Tools. You can also reach out to our Chat Support 24/7.
12-05-2013 11:27 AM
So to give my resolution to this problem, customer care got in touch with me. After talking back and forth, they assigned me a new set of static IPs -- after updating the gateway with the new set, everything worked correctly and the machines that had static IPs assigned had their traffic routed correctly.
I have no idea why this would be the case, but it worked. So there you go.
12-19-2013 10:22 AM
I'm chewing the rug here. I definitely have first-hand experience supporting the wide-spread opinion in the tech community that the 2Wire boxes are piles of steaming ordure that should never have seen the light of day, much less have been deployed by a company as well-known as AT&T.
Some issues and history follows. I don't have the Web UI in front of me, so I'll have to approximate the tab names.
Those are highlights, and probably incomplete; I'm so frustrated that I'm sure I've missed some.
This morning, I did this:
When I finished with the above merry-go-round,
However, this didn't last.
So, after spending three hours this morning (plus at least ten times that much over the last few weeks), I'm essentially still in the condition of having public IPAs I can't use because the 2Wire is as brain-damaged as a squirrel under a concrete truck.
Happy? I don't think so. :-(
12-19-2013 3:33 PM
There definitely seems to be something unusually happening here, as static assignments should not be changing.
I am pretty sure you already tried this, but I would suggest doing a factory reset from the reset page inside the gateway, and starting from scratch.
Also, if possible, statically assign the IP addresses on your devices.
12-19-2013 6:07 PM
I've tried statically assigning the address on the devices. The 2Wire didn't see them, so didn't create device entries for them, so didn't open the firewall for them.
I tried factory resetting through the Web UI, and it looked like it worked -- but it remembered some device settings though not names. I also tried resetting using the physical switch, but in that case it didn't forget anything. (I tried holding the reset button for 15 seconds while the box was powered up, and also holding it for 15 seconds while powering on. No joy either way.)
The ssh ports randomly being open or filtered is killing me. It's a representative symptom of this entire ghastly experience.
12-20-2013 10:30 AM
I greatly apologize about all the issues. It definitely does not sound to be working correctly. Even the basic functions, such as you assigning a Static IP should not cause it to not be recognized by our router. It may be an issue with the router.
We would be glad to help you get it replaced, Please send us a detailed message by clicking here. Be sure to include your name, account number, phone number, and the best time to reach you.
Keep an eye on the at the top right corner of your screen for a response.
In the meantime, let me know if you have any other questions or concerns!
03-21-2014 10:47 AM - edited 03-21-2014 1:58 PM
I'm also having a similar issue.
I just received 5 useable IP addresses from a block of 8.
Now, when I go to:
Settings > LAN > Status
I see "Private Network" and "Public Networks" information. Everything looks good here. The private network DHCP info appears accurate, and the "User Defined Supplemental Networks" appears to be the CIDR addresses that the technician entered into the gateway.
Now, when I go to Settings > LAN > IP Address Allocation, I see the machine I'd like to set up with a static IP, but its "current address" is an old private address that was given to the device via DHCP. It does not reflect the current private address. I assume this should be straight before I try to assign a static IP from my static IP pool.
Updated device lists appear pretty slow with the RG. Do I need to restart my router?
*Even when* the device list did recognize accurate information (the private address was accurate), when I would select a public IP address from the "WAN IP Mapping" dropdown, I would get an error "For the public routed subinterface only WAN IP mapping is allowed."
Help is needed!
I have Googled around about U-verse, static IP's, and the RG I'm using. Sad, but hopeful.
Welcome to the internet boards! Check out our troubleshooting articles below and don’t forget to search the forums - your question may have been answered already!
Service acting up? Click here to troubleshoot now!
For DSL related issues. We highly recommend chatting with our teams to address this as quickly as possible.