Ask a question
Search in Internet Forums

Internet Forum

Reply
Posted Jan 15, 2013
4:47:10 PM
View profile
Static IP Setup 3600/3800/3801

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.

  • Example: 99.18.100.200/29 which is a block of 8 IPs six usable 5 being able to be assigned to device.
  • 99.18.100.207 is the broadcast and will not be usable
  • Gateway/Router Address will be 99.18.100.206
  • Usable for hosts are 99.18.100.201 - 99.18.100.205
  • Subnet Mask is 255.255.255.248

(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;

  • 255.255.255.248 block of 8
  • 255.255.255.240 block of 16
  • 255.255.255.224 block of 32
  • 255.255.255.192 block of 64
  • 255.255.255.128 block of 128

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.

  • Example: 99.18.100.200/29 which is a block of 8 IPs six usable 5 being able to be assigned to device.
  • 99.18.100.207 is the broadcast and will not be usable
  • Gateway/Router Address will be 99.18.100.206
  • Usable for hosts are 99.18.100.201 - 99.18.100.205
  • Subnet Mask is 255.255.255.248

(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;

  • 255.255.255.248 block of 8
  • 255.255.255.240 block of 16
  • 255.255.255.224 block of 32
  • 255.255.255.192 block of 64
  • 255.255.255.128 block of 128
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Static IP Setup 3600/3800/3801

44,718 views
21 replies
(0) Me too
(0) Me too
Reply
View all replies
(21)
0
(0)
  • Rate this reply
View profile
Nov 20, 2013 2:42:58 PM
0
(0)
Tutor

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.

 

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.

 

Re: Static IP Setup 3600/3800/3801

2 of 22 (43,824 Views)
0
(0)
  • Rate this reply
View profile
Nov 22, 2013 12:21:14 PM
0
(0)
Community Support

Hi THX_1138,

 

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:

  1. Login to you the 2wire at http://192.168.1.254
  2. Select the tab Settings
  3. Select the sub-tab Broadband
  4. Select the sub-tab Link Configuration
  5. Check the enable box next to Add Additional Network
  6. In the field Router Address, you want to put in what you want to be the default gateway for your block of IPs. This IP will be assigned to the 2wire router.
  7. In the field Subnet Mask, put in the appropriate subnet mask
  8. I personally like to check the box that says Auto Firewall Open
  9. Select Save

Hopefully, this resolves your issue. Let us know how it goes.

 

-David T

If you encounter any issues with your service or equipment, I recommend checking out our Troubleshoot & Resolve solutions to help diagnose the issue.

Hi THX_1138,

 

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:

  1. Login to you the 2wire at http://192.168.1.254
  2. Select the tab Settings
  3. Select the sub-tab Broadband
  4. Select the sub-tab Link Configuration
  5. Check the enable box next to Add Additional Network
  6. In the field Router Address, you want to put in what you want to be the default gateway for your block of IPs. This IP will be assigned to the 2wire router.
  7. In the field Subnet Mask, put in the appropriate subnet mask
  8. I personally like to check the box that says Auto Firewall Open
  9. Select Save

Hopefully, this resolves your issue. Let us know how it goes.

 

-David T

If you encounter any issues with your service or equipment, I recommend checking out our Troubleshoot & Resolve solutions to help diagnose the issue.
I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Static IP Setup 3600/3800/3801

3 of 22 (43,764 Views)
Highlighted
0
(0)
  • Rate this reply
View profile
Nov 22, 2013 1:27:00 PM
0
(0)
Tutor

I have done all that, although:

 

  1. [step 1] I used the network I set up instead of the default 192.168.1.0 one.
  2. [step 6] I gave the router address I was told to use, which was the last one in my address block (.126 from a x.x.x.96/27 block).
  • The appropriate NICs on the hosts on the LAN have been set (on their hosts)  to the static IP addresses.
  • Most of the NICs can ping the 2wire at the x.x.x.126 address.
  • None of the NICs can reach beyond the 2wire.
  • None of the static addresses are accessible (via ping) from the Internet, not even the x.x.x.126 gateway address.

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.

 

I have done all that, although:

 

  1. [step 1] I used the network I set up instead of the default 192.168.1.0 one.
  2. [step 6] I gave the router address I was told to use, which was the last one in my address block (.126 from a x.x.x.96/27 block).
  • The appropriate NICs on the hosts on the LAN have been set (on their hosts)  to the static IP addresses.
  • Most of the NICs can ping the 2wire at the x.x.x.126 address.
  • None of the NICs can reach beyond the 2wire.
  • None of the static addresses are accessible (via ping) from the Internet, not even the x.x.x.126 gateway address.

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.

 

Re: Static IP Setup 3600/3800/3801

4 of 22 (43,760 Views)
0
(0)
  • Rate this reply
View profile
Nov 22, 2013 1:48:16 PM
0
(0)
Community Support

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.

 

-David T

If you encounter any issues with your service or equipment, I recommend checking out our Troubleshoot & Resolve solutions to help diagnose the issue.

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.

 

-David T

If you encounter any issues with your service or equipment, I recommend checking out our Troubleshoot & Resolve solutions to help diagnose the issue.
I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Static IP Setup 3600/3800/3801

5 of 22 (43,757 Views)
0
(0)
  • Rate this reply
View profile
Nov 30, 2013 2:17:58 AM
0
(0)
Contributor
Edited by SadathCS on Dec 1, 2013 at 11:31:36 AM

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.

 

Setup:

 

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:

x.x.x.49/255.255.255.248

Gateway: x.x.x.54 (router's public IP address)

 

Computer B, on the private subnet:

x.x.x.2/255.255.255.0

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:

 

C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
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  12.83.43.29
  5     8 ms     8 ms     9 ms  ggr3.cgcil.ip.att.net [12.122.133.9]
  6     *        *        *     Request timed out.
  7    10 ms     9 ms     9 ms  209.85.254.128
  8    11 ms    10 ms     9 ms  209.85.254.240
  9    23 ms    22 ms    23 ms  209.85.248.228
 10    31 ms    23 ms    23 ms  216.239.46.191
 11     *        *        *     Request timed out.
 12   171 ms   131 ms    20 ms  google-public-dns-a.google.com [8.8.8.8]

----

 

The problem is that the same request from Computer A, on the static IP address, fails:

 

C:\>tracert 8.8.8.8

Tracing route to 8.8.8.8 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)

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.

 

Setup:

 

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:

x.x.x.49/255.255.255.248

Gateway: x.x.x.54 (router's public IP address)

 

Computer B, on the private subnet:

x.x.x.2/255.255.255.0

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:

 

C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
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  12.83.43.29
  5     8 ms     8 ms     9 ms  ggr3.cgcil.ip.att.net [12.122.133.9]
  6     *        *        *     Request timed out.
  7    10 ms     9 ms     9 ms  209.85.254.128
  8    11 ms    10 ms     9 ms  209.85.254.240
  9    23 ms    22 ms    23 ms  209.85.248.228
 10    31 ms    23 ms    23 ms  216.239.46.191
 11     *        *        *     Request timed out.
 12   171 ms   131 ms    20 ms  google-public-dns-a.google.com [8.8.8.8]

----

 

The problem is that the same request from Computer A, on the static IP address, fails:

 

C:\>tracert 8.8.8.8

Tracing route to 8.8.8.8 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)

Re: Static IP Setup 3600/3800/3801

[ Edited ]
6 of 22 (43,572 Views)
0
(0)
  • Rate this reply
View profile
Nov 30, 2013 9:40:00 AM
0
(0)
Expert

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. List Private Messages

 

 

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. List Private Messages

 

 

Re: Static IP Setup 3600/3800/3801

7 of 22 (43,556 Views)
0
(0)
  • Rate this reply
View profile
Nov 30, 2013 10:21:05 AM
0
(0)
Contributor

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.

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.

Re: Static IP Setup 3600/3800/3801

8 of 22 (43,550 Views)
0
(0)
  • Rate this reply
View profile
Dec 1, 2013 11:35:58 AM
0
(0)
Community Support

Hello cmcguigan,

 

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.

SadathCS
ATTU-verseCare

Need more help?

Download the myAT&T App and click Fix It Now! Support Tools to get U-verse help. Have additional questions, post below or search our forums using the search bar above. Our community members post a lot of great answers!

For more assistance, send a brief message to ATTU-verseCare . Be sure to include your account number, name, and contact number.

Hello cmcguigan,

 

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.

SadathCS
ATTU-verseCare

Need more help?

Download the myAT&T App and click Fix It Now! Support Tools to get U-verse help. Have additional questions, post below or search our forums using the search bar above. Our community members post a lot of great answers!

For more assistance, send a brief message to ATTU-verseCare . Be sure to include your account number, name, and contact number.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Static IP Setup 3600/3800/3801

9 of 22 (43,501 Views)
0
(0)
  • Rate this reply
View profile
Dec 5, 2013 11:27:37 AM
0
(0)
Contributor

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.

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.

Re: Static IP Setup 3600/3800/3801

10 of 22 (43,322 Views)
0
(0)
  • Rate this reply
View profile
Dec 19, 2013 10:22:16 AM
0
(0)
Tutor

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.

 

  1. The LAN->IP Assignment page says that you can configure NICs on LAN devices to use static IP addresses and it will pick them up and honour them -- but that only worked for my Vonage modem.  None of the other 8 NICs I need to set up would work this way.
  2. The 2Wire keeps confusing two of my NICs, assigning the static IPA for one to the other's MAC.
  3. The 2Wire claims a bunch of my NICs have 'Static IP - no DHCP', even though that's false and the 2Wire assigned them the addresses they have.
  4. 'Clear device list' is unreliable; the 2Wire may -- or may not -- remember names previously given to MAC addresses, so who knows what else it's failing to forget?
  5. The 2Wire arbitrarily forgets explicit IP assignments and changes the to 'from the pool'.
  6. Getting rid of all static assignments and trying to port-forward/pinhole SSH to an IP on my LAN didn't work -- external systems showed the port as filtered.  The LAN IPA (IP Address) was originally outside of the 2Wire's DHCP range, but it behaved the same way when I made it a DHCP-assigned IPA.
  7. The 2Wire arbitrarily filters ports that were previously open.

 

Those are highlights, and probably incomplete; I'm so frustrated that I'm sure I've missed some.

 

This morning, I did this:

 

  1. On each of two servers, I a) shut down four NICs; b) configured 'eth1' statically to a LAN IPA outside the 2Wire's DHCP range; c) configured 'eth2' through 'eth4' to get their IPAs from the 2Wire with DHCP.  Note that all 8 NICs are down at this point.
  2. I did a 'clear device list' on the 2Wire.
  3. I turned off all the attack-detection options in Firewall->Advanced.
  4. On the first server, I went through the NICs one by one, and a) brought it up; b) confirmed the 2Wire saw it; c) used the 'IP Address Assignment' page to assign a specific public IPA to it; d) shut down the NIC on the server; e) restarted the NIC on the server; f) confirmed on the server and the 2Wire that the NIC had been assigned the correct IPA; g) moved on to the next NIC.

When I finished with the above merry-go-round,

  • All the NICs showed the correct IPA assignment on their hosts;
  • The 2Wire also showed the correct IPA assignments; and
  • The public IPAs were reachable from the WAN.

However, this didn't last.

  • Port 22 (ssh) on all assigned public IPAs that I tried to use went from 'open' to 'filtered' (as reported by nmap) -- the ones I haven't tried to use still show 'open';
  • server1's eth2 was assigned the IPA originally assigned to server1's eth3;
  • server1's eth3's assignment didn't change, but the 2Wire showed it as 'not connected';
  • most of the devices/NICs explicitly assigned LAN IPAs went from 'DHCP/fixed from <local> pool' to 'Static - no DHCP' (which means they can't really be edited any more at all).

 

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. :-(

 

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.

 

  1. The LAN->IP Assignment page says that you can configure NICs on LAN devices to use static IP addresses and it will pick them up and honour them -- but that only worked for my Vonage modem.  None of the other 8 NICs I need to set up would work this way.
  2. The 2Wire keeps confusing two of my NICs, assigning the static IPA for one to the other's MAC.
  3. The 2Wire claims a bunch of my NICs have 'Static IP - no DHCP', even though that's false and the 2Wire assigned them the addresses they have.
  4. 'Clear device list' is unreliable; the 2Wire may -- or may not -- remember names previously given to MAC addresses, so who knows what else it's failing to forget?
  5. The 2Wire arbitrarily forgets explicit IP assignments and changes the to 'from the pool'.
  6. Getting rid of all static assignments and trying to port-forward/pinhole SSH to an IP on my LAN didn't work -- external systems showed the port as filtered.  The LAN IPA (IP Address) was originally outside of the 2Wire's DHCP range, but it behaved the same way when I made it a DHCP-assigned IPA.
  7. The 2Wire arbitrarily filters ports that were previously open.

 

Those are highlights, and probably incomplete; I'm so frustrated that I'm sure I've missed some.

 

This morning, I did this:

 

  1. On each of two servers, I a) shut down four NICs; b) configured 'eth1' statically to a LAN IPA outside the 2Wire's DHCP range; c) configured 'eth2' through 'eth4' to get their IPAs from the 2Wire with DHCP.  Note that all 8 NICs are down at this point.
  2. I did a 'clear device list' on the 2Wire.
  3. I turned off all the attack-detection options in Firewall->Advanced.
  4. On the first server, I went through the NICs one by one, and a) brought it up; b) confirmed the 2Wire saw it; c) used the 'IP Address Assignment' page to assign a specific public IPA to it; d) shut down the NIC on the server; e) restarted the NIC on the server; f) confirmed on the server and the 2Wire that the NIC had been assigned the correct IPA; g) moved on to the next NIC.

When I finished with the above merry-go-round,

  • All the NICs showed the correct IPA assignment on their hosts;
  • The 2Wire also showed the correct IPA assignments; and
  • The public IPAs were reachable from the WAN.

However, this didn't last.

  • Port 22 (ssh) on all assigned public IPAs that I tried to use went from 'open' to 'filtered' (as reported by nmap) -- the ones I haven't tried to use still show 'open';
  • server1's eth2 was assigned the IPA originally assigned to server1's eth3;
  • server1's eth3's assignment didn't change, but the 2Wire showed it as 'not connected';
  • most of the devices/NICs explicitly assigned LAN IPAs went from 'DHCP/fixed from <local> pool' to 'Static - no DHCP' (which means they can't really be edited any more at all).

 

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. :-(

 

Re: Static IP Setup 3600/3800/3801

11 of 22 (42,850 Views)
0
(0)
  • Rate this reply
View profile
Dec 19, 2013 3:33:28 PM
0
(0)
Community Support

Hi THX_1138,

 

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.

 

-David T

If you encounter any issues with your service or equipment, I recommend checking out our Troubleshoot & Resolve solutions to help diagnose the issue.

Hi THX_1138,

 

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.

 

-David T

If you encounter any issues with your service or equipment, I recommend checking out our Troubleshoot & Resolve solutions to help diagnose the issue.
I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Static IP Setup 3600/3800/3801

12 of 22 (42,824 Views)
0
(0)
  • Rate this reply
View profile
Dec 19, 2013 6:07:01 PM
0
(0)
Tutor

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.

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.

Re: Static IP Setup 3600/3800/3801

13 of 22 (42,812 Views)
0
(0)
  • Rate this reply
View profile
Dec 20, 2013 10:30:45 AM
0
(0)
Community Support

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!

-David T

If you encounter any issues with your service or equipment, I recommend checking out our Troubleshoot & Resolve solutions to help diagnose the issue.

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!

-David T

If you encounter any issues with your service or equipment, I recommend checking out our Troubleshoot & Resolve solutions to help diagnose the issue.
I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Static IP Setup 3600/3800/3801

14 of 22 (42,756 Views)
0
(0)
  • Rate this reply
View profile
Mar 21, 2014 10:47:12 AM
0
(0)
Contributor
Edited by Geronimo321 on Mar 21, 2014 at 1:58:29 PM

I'm also having a similar issue. Smiley Sad

 

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! Smiley Happy

 

 

 

 I have Googled around about U-verse, static IP's, and the RG I'm using. Sad, but hopeful.  

I'm also having a similar issue. Smiley Sad

 

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! Smiley Happy

 

 

 

 I have Googled around about U-verse, static IP's, and the RG I'm using. Sad, but hopeful.  

Re: Static IP Setup 3600/3800/3801

[ Edited ]
15 of 22 (39,031 Views)
0
(0)
  • Rate this reply
View profile
Mar 30, 2015 3:42:19 PM
0
(0)
Tutor

I ride along with above posts.

I see similar behavior on my router, however it is a 5031NV.

Perhaps the same Firmware programmer did the other ones too.

Sometimes at first ping I get a message saying that it would be rerouted to 192.168.1.1

and then stops in its tracks. The 192.168.1.1 is my router with static private on the WAN port.

Seems this router/modem is a fine piece of ship....

Absolutely nothing, except the LAN works!

I ride along with above posts.

I see similar behavior on my router, however it is a 5031NV.

Perhaps the same Firmware programmer did the other ones too.

Sometimes at first ping I get a message saying that it would be rerouted to 192.168.1.1

and then stops in its tracks. The 192.168.1.1 is my router with static private on the WAN port.

Seems this router/modem is a fine piece of ship....

Absolutely nothing, except the LAN works!

Re: Static IP Setup 3600/3800/3801

16 of 22 (19,756 Views)
0
(0)
  • Rate this reply
View profile
Jun 24, 2015 6:47:33 PM
0
(0)
Contributor

Hi,

 

I'm using the 3801 router. I understand everything up until selecting the router address. Where do we find that and the subnet mask? Is it just the 192.168.1.254?

Hi,

 

I'm using the 3801 router. I understand everything up until selecting the router address. Where do we find that and the subnet mask? Is it just the 192.168.1.254?

Re: Static IP Setup 3600/3800/3801

17 of 22 (16,542 Views)
0
(0)
  • Rate this reply
View profile
Aug 29, 2015 11:26:45 AM
0
(0)
Teacher

calvin.jarrod wrote:

Hi,

 

I'm using the 3801 router. I understand everything up until selecting the router address. Where do we find that and the subnet mask? Is it just the 192.168.1.254?


I wish these did not get moved to private messaging so we could follow threads through to the end.

 

I am ignorant of router and modem settings (not as much today as 4 days ago). I would like to take a huge hunk of space to go over the past 4 days.

 

I want to add some cameras and a lighting control system to having access over the internet, I was told having a static IP is optimum. I ordered a static IP and an upgrade to bandwidth....I will just stick with the IP stuff.

 

AT&T sends a tech out to configure the 3801. He plainly states he doe snot know what he is doing and accomplishes the setup via a chat over his IPAD. I could have done that. HE leaves. I look at the router settings and the AT&T devices have taken 4 of the five configurable addresses. So begins my story...nightmare?

 

I chat several times with techs, then finally call. One moves a hardwired DVR to a DMZ zone (no longer as ignorant about that), but says she cannot move the others. She sends me to connectech. They want $50 to fox it....ok....paid....."you can call uis back if it is not corrected"...no way, cut my losses.

 

Posted in here and got into this thread via being directed to it by tech, AFTER about 9 emails going over everything, including two factory resets. No one knows why the ATT devices still take static IPs. I followed the directions in here step-by-step...first:

 

1) I disconnected all but my PC connected directly to the gateway, then did a factory reset.

2) Followed all of the steps

3) Connected the ASUS router

4) Set it up to receive addressing dynamically

5) Went into the gateway and assigned the address as static

6) Plugged in the first ATT device - it took  a static, not the public IP it was supposed to

 

blah blah blah

 

hours later:

1) cancelled static IP addressing

2) dropped bandwidth from 24 to 18

etc

 

Back to dynamic...it has been horrendous - 23 hours in four days. I admit I am ignorant, too bad ATT seesm to have a few that are perhpas as ignorant as me,. I am very well qualified ot go step-by-step through a process (and this one was easy to follow), but if it does not work, what does that mean? I did it wrong (three times)?? Maybe.

 

 

 

 


calvin.jarrod wrote:

Hi,

 

I'm using the 3801 router. I understand everything up until selecting the router address. Where do we find that and the subnet mask? Is it just the 192.168.1.254?


I wish these did not get moved to private messaging so we could follow threads through to the end.

 

I am ignorant of router and modem settings (not as much today as 4 days ago). I would like to take a huge hunk of space to go over the past 4 days.

 

I want to add some cameras and a lighting control system to having access over the internet, I was told having a static IP is optimum. I ordered a static IP and an upgrade to bandwidth....I will just stick with the IP stuff.

 

AT&T sends a tech out to configure the 3801. He plainly states he doe snot know what he is doing and accomplishes the setup via a chat over his IPAD. I could have done that. HE leaves. I look at the router settings and the AT&T devices have taken 4 of the five configurable addresses. So begins my story...nightmare?

 

I chat several times with techs, then finally call. One moves a hardwired DVR to a DMZ zone (no longer as ignorant about that), but says she cannot move the others. She sends me to connectech. They want $50 to fox it....ok....paid....."you can call uis back if it is not corrected"...no way, cut my losses.

 

Posted in here and got into this thread via being directed to it by tech, AFTER about 9 emails going over everything, including two factory resets. No one knows why the ATT devices still take static IPs. I followed the directions in here step-by-step...first:

 

1) I disconnected all but my PC connected directly to the gateway, then did a factory reset.

2) Followed all of the steps

3) Connected the ASUS router

4) Set it up to receive addressing dynamically

5) Went into the gateway and assigned the address as static

6) Plugged in the first ATT device - it took  a static, not the public IP it was supposed to

 

blah blah blah

 

hours later:

1) cancelled static IP addressing

2) dropped bandwidth from 24 to 18

etc

 

Back to dynamic...it has been horrendous - 23 hours in four days. I admit I am ignorant, too bad ATT seesm to have a few that are perhpas as ignorant as me,. I am very well qualified ot go step-by-step through a process (and this one was easy to follow), but if it does not work, what does that mean? I did it wrong (three times)?? Maybe.

 

 

 

 

Re: Static IP Setup 3600/3800/3801

18 of 22 (13,046 Views)
0
(0)
  • Rate this reply
View profile
Aug 30, 2015 9:01:53 AM
0
(0)
Tutor
Edited by Taylarie on Aug 30, 2015 at 9:29:54 AM

Hi there,
NO, I think you did everything to the letter.

The problem, as far as I am concerned, lies within the router / modem
and AT&T's secret society.
People at AT&T that know how to circumvent situations e.g. make it work
as supposed to, aren't allowed to work customer support, I am convinced.
So you'll wind up with one that has a ten point list, perhaps even a
robot. If it isn't on that list, it doesn't exist.

The router they supply, is tighter than a "you know what". The slightest
mistake or simply a misconfiguration, will throw the router off it's
feet and you'll have to
reset the whole thing to factory default. This can take very long,
because it seems that the router needs to find things that aren't there.
Kind a like Microsoft.
Then you can start over.
One of the mysteries I am still working on, is the fact that AT&T calls
it static IP and not Public. What this means is that your assigned IP's
are actually coming of a server that is hosted by AT&T and are DHCP at
the root. The way AT&T makes them static is by configuration at their
system. At this point you are not public, all you do is cruising around
the AT&T network. None of them Static IP's is registered with Internet
Authority, except one. This way it is cheaper for AT&T and extends their
profit margin. We pay for it, they don't!
To get public, you'll have to use a single IP address which wasn't given
to you at installation and can only be found on the Routers web
interface (192.168.1.254). All you received was the so called Static
IP's. Your static IP's are supposed to be routed to the Internet via
that ONE public address. As for me, I simply can't get all of my static
IP's to the Internet. The router is too stupid to do it or AT&T does it
intentionally, to keep control and restriction over what happens. I am
able to route ONE of my Static IP's to the Internet using a LINUX
computer that I can configure in a certain way so that it will pass
through the router.
This took me several days and support from someone that claims to be a
community support person. However, even this person couldn't solve my
puzzle. His reason was that I am subscribing through DSLEXTREME and not
AT&T. But wait, dslextreme sold me your AT&T crap....
The biggest piece of #$@%# that they supply is this modem. It can't be
run in transparent mode, doesn't work half the time correctly and is all
over a piece of non intuitive crap. Also there is no manual for it, at
least we can't get one!

I had a perfectly good system containing four Web Server with e-mail
server, Two DNS Server and more all hooked into 8 Public IP's. Yes these
were public IP's!
I switched because of the slightly better Upstream, I had 768Kbps and
now have close to 2000Kpbs so that the visitor wouldn't fall asleep.
In the course I had to make handstands to get about 25% back from my old
system. This U-Verse or Fusion was a bad decision I made.
I guess you can tell that I am not too wild to give AT&T even just one
STAR, by the time I realized, it was too late and I was locked in a 1
Year contract.
The bothersome is, I am paying for 100% service but get only 20% and
e-mail ports are blocked by AT&T also. Can't run e-mail server under my
own domain.

I think you made the right decision to get back to dynamic host and the
slightly slower speed. AT&T it seems does not want you to host your own
equipment.
Many times businesses force you to do what they want, not what you
desire. It's called business strategy, the only way to fight this war,
is to tell em to fly a kite.
Unfortunately, there aren't many options left and they steam towards a
monopoly....

Cheers,
Norbert

Hi there,
NO, I think you did everything to the letter.

The problem, as far as I am concerned, lies within the router / modem
and AT&T's secret society.
People at AT&T that know how to circumvent situations e.g. make it work
as supposed to, aren't allowed to work customer support, I am convinced.
So you'll wind up with one that has a ten point list, perhaps even a
robot. If it isn't on that list, it doesn't exist.

The router they supply, is tighter than a "you know what". The slightest
mistake or simply a misconfiguration, will throw the router off it's
feet and you'll have to
reset the whole thing to factory default. This can take very long,
because it seems that the router needs to find things that aren't there.
Kind a like Microsoft.
Then you can start over.
One of the mysteries I am still working on, is the fact that AT&T calls
it static IP and not Public. What this means is that your assigned IP's
are actually coming of a server that is hosted by AT&T and are DHCP at
the root. The way AT&T makes them static is by configuration at their
system. At this point you are not public, all you do is cruising around
the AT&T network. None of them Static IP's is registered with Internet
Authority, except one. This way it is cheaper for AT&T and extends their
profit margin. We pay for it, they don't!
To get public, you'll have to use a single IP address which wasn't given
to you at installation and can only be found on the Routers web
interface (192.168.1.254). All you received was the so called Static
IP's. Your static IP's are supposed to be routed to the Internet via
that ONE public address. As for me, I simply can't get all of my static
IP's to the Internet. The router is too stupid to do it or AT&T does it
intentionally, to keep control and restriction over what happens. I am
able to route ONE of my Static IP's to the Internet using a LINUX
computer that I can configure in a certain way so that it will pass
through the router.
This took me several days and support from someone that claims to be a
community support person. However, even this person couldn't solve my
puzzle. His reason was that I am subscribing through DSLEXTREME and not
AT&T. But wait, dslextreme sold me your AT&T crap....
The biggest piece of #$@%# that they supply is this modem. It can't be
run in transparent mode, doesn't work half the time correctly and is all
over a piece of non intuitive crap. Also there is no manual for it, at
least we can't get one!

I had a perfectly good system containing four Web Server with e-mail
server, Two DNS Server and more all hooked into 8 Public IP's. Yes these
were public IP's!
I switched because of the slightly better Upstream, I had 768Kbps and
now have close to 2000Kpbs so that the visitor wouldn't fall asleep.
In the course I had to make handstands to get about 25% back from my old
system. This U-Verse or Fusion was a bad decision I made.
I guess you can tell that I am not too wild to give AT&T even just one
STAR, by the time I realized, it was too late and I was locked in a 1
Year contract.
The bothersome is, I am paying for 100% service but get only 20% and
e-mail ports are blocked by AT&T also. Can't run e-mail server under my
own domain.

I think you made the right decision to get back to dynamic host and the
slightly slower speed. AT&T it seems does not want you to host your own
equipment.
Many times businesses force you to do what they want, not what you
desire. It's called business strategy, the only way to fight this war,
is to tell em to fly a kite.
Unfortunately, there aren't many options left and they steam towards a
monopoly....

Cheers,
Norbert

Re: Static IP Setup 3600/3800/3801

[ Edited ]
19 of 22 (13,001 Views)
0
(0)
  • Rate this reply
View profile
Apr 20, 2016 10:43:14 PM
0
(0)
Contributor

Thanks for the tip on setting an "Additional Network".

 

When I had U-Verse installed (about 6 months ago), I used the cascade router setup

so that my static IP's were all hosted behind another firewall.

 

The set up was RG (3801) 192.168.1.254 -> router 192.168.1.66 

and DMZ flag set for that IP.

 

Yesterday - after working fine for 6 months, everything stopped working.

The 3801 had magically changed the IP associated with the other router to be the same as the 3801's WAN link.

 

When I tried to configure things back the way they were, it said I could not set the DMZ flag

for a staticly configured IP - it had to be DHCP.  That's a new restriction - how did that happen?

 

Ok.... configure router to use DHCP.

Go to set the DMZ flag - and it says router will get new IP - no problem.

 

BUT, once again it associated its own WAN address with the other router.

 

I've been going round in circles with this piece of trash for 2 days now.

Just now I looked at the web ui on the 3801 - every page I looked at showed a different IP associated with my router!  and it changes everytime I look.

Meanwhile the router still has the same address it first got from DHCP.

 

This would all be soooo bloody simple to fix, if I could just statically configure the 3801 

AND set the DMZ flag for the cascade router.

 

I'm going to call up ATT and ask for a new router because this one simply does not work.

(Oh and yes I've been configuring/programming networks for over 20 years - so I think I know what I'm doing ;-)

Thanks for the tip on setting an "Additional Network".

 

When I had U-Verse installed (about 6 months ago), I used the cascade router setup

so that my static IP's were all hosted behind another firewall.

 

The set up was RG (3801) 192.168.1.254 -> router 192.168.1.66 

and DMZ flag set for that IP.

 

Yesterday - after working fine for 6 months, everything stopped working.

The 3801 had magically changed the IP associated with the other router to be the same as the 3801's WAN link.

 

When I tried to configure things back the way they were, it said I could not set the DMZ flag

for a staticly configured IP - it had to be DHCP.  That's a new restriction - how did that happen?

 

Ok.... configure router to use DHCP.

Go to set the DMZ flag - and it says router will get new IP - no problem.

 

BUT, once again it associated its own WAN address with the other router.

 

I've been going round in circles with this piece of trash for 2 days now.

Just now I looked at the web ui on the 3801 - every page I looked at showed a different IP associated with my router!  and it changes everytime I look.

Meanwhile the router still has the same address it first got from DHCP.

 

This would all be soooo bloody simple to fix, if I could just statically configure the 3801 

AND set the DMZ flag for the cascade router.

 

I'm going to call up ATT and ask for a new router because this one simply does not work.

(Oh and yes I've been configuring/programming networks for over 20 years - so I think I know what I'm doing ;-)

Re: Static IP Setup 3600/3800/3801

20 of 22 (4,861 Views)
0
(0)
  • Rate this reply
View profile
Apr 21, 2016 6:58:30 AM
0
(0)
Community Support

@crufty,

 

We can help get you a new modem. Send us a message by clicking here. Provide your:

 

  • Name
  • 9 digit U-verse account number
  • Phone number

 

Keep an eye on the at the top right corner of your screen for a response. In the meantime, let us know if you have any other questions or concerns!

 

-ATTU-verseCare

Need more help?

Download the myAT&T App and click Fix It Now! Support Tools to get U-verse help. Have additional questions, post below or search our forums using the search bar above. Our community members post a lot of great answers!

For more assistance, send a brief message to ATTU-verseCare . Be sure to include your account number, name, and contact number.

@crufty,

 

We can help get you a new modem. Send us a message by clicking here. Provide your:

 

  • Name
  • 9 digit U-verse account number
  • Phone number

 

Keep an eye on the at the top right corner of your screen for a response. In the meantime, let us know if you have any other questions or concerns!

 

-ATTU-verseCare

Need more help?

Download the myAT&T App and click Fix It Now! Support Tools to get U-verse help. Have additional questions, post below or search our forums using the search bar above. Our community members post a lot of great answers!

For more assistance, send a brief message to ATTU-verseCare . Be sure to include your account number, name, and contact number.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Static IP Setup 3600/3800/3801

21 of 22 (4,834 Views)
0
(0)
  • Rate this reply
View profile
Apr 26, 2016 10:01:18 PM
0
(0)
Contributor

Thanks very much to uverse support, they sent me a replacement box virtually over night.

The swap was simple, and so far everything is working fine.

 

One surprise - the new box would not let me disable firewall for the cascade router (private IP) regardless of DHCP.  That's different - but it didn't matter, as all the expected inbound and outbound services work.

 

Kudos AT&T

 

Thanks very much to uverse support, they sent me a replacement box virtually over night.

The swap was simple, and so far everything is working fine.

 

One surprise - the new box would not let me disable firewall for the cascade router (private IP) regardless of DHCP.  That's different - but it didn't matter, as all the expected inbound and outbound services work.

 

Kudos AT&T

 

Re: Static IP Setup 3600/3800/3801

22 of 22 (4,655 Views)
Share this post
Share this post