Multiple public IPs with U-verse.

Digital Micro

Well-Known Member
Reaction score
426
Location
Anniston, Alabama
Next week I have to setup two static public ip's at a client. One for the business, and the second for a vendor. The vendor wants their own ip. I've never done this with U-verse and hear it's a pain.

Has anyone set this up before?
 
Not with U-verse. But what are the specs? What about routing? FQDN's? Need some more details about the objective.
I'm sorry. The current network is pretty much a home network in a business. Standard U-verse wireless modem/router with 3 computers. It's a small bar. They have a vendor coming in to setup online gaming systems. I just need a second static IP for them to come in and configure their system on so it's off the business network. No domains. The vendor wants a second IP from U-verse. I've never done this with a U-verse/DSL modem router combo.
 
I'm sorry. The current network is pretty much a home network in a business. Standard U-verse wireless modem/router with 3 computers. It's a small bar. They have a vendor coming in to setup online gaming systems. I just need a second static IP for them to come in and configure their system on so it's off the business network. No domains. The vendor wants a second IP from U-verse. I've never done this with a U-verse/DSL modem router combo.

1. You need to setup to properly setup the account. Not sure about U-verse but many ISP's go from 1 fixed to 5. At any rate you tell them what you want.
2. You need to understand the vendor's setup. Since it's gaming will they have separate workstations?
3. You need to isolate the vendor's network from the business LAN. Most of these companies have guidelines.
4. The U-verse modem you have may or may not handle multiple public IP's. So that may need to be changed.
 
Two possibilities:
  • If it's a single static IP right now but the Uverse modem has its own address (e.g. a /30 or .252 netmask) and the router has its own real-world IP with the gateway being 1-2 IPs away, then you may be able to actually use both the static IP you have and the IP assigned to the modem. To do this you'd basically have any external ports that need access forwarded from the modem through to the internal device or router. If the independent network for the gaming system can work this way, that's best for you because it's a double-NAT situation which isn't good for VPNs etc.
  • If a block of 5 IPs (/29 or a .248 netmask) is available, you can switch to that but you'll need to call and arrange that with AT&T in advance. The existing modem may not handle it, if there's a current static IP it will be changed, etc. In that case the modem will absolutely have an IP address of its own, and there will be a block of 5 IPs that can be assigned to routers "inside" that. Whether the modem will also do DHCP and also be usable with a private subnet is unknown, I think they used to do that with the old Netopia ones but we have nobody using DSL/Uverse as a primary connection these days.
 
You are in for some pain. Assuming the circuit is set up as business class static IP you should get a block of at least 3 addresses. If ATT is still using their NVG589 combo boxes you will have to configure the ATT router to assign the statics via dhcp ( makes perfect sense right?) and then if you haven't killed somebody in frustration - if you want to have a router capable of doing vlans behind the ATT box you have more configuration to do none of which is documented by ATT as their DMZ and passthrough options do not work with external static IP's.

The link below is useful - not currently loading for me but might be a temporary thing.

http://spearfoot.net/uverse-static-ip/
 
Yeah those NV gateways are a pain. Like OlDTech mentioned...there's a couple of spots you have to tickle on the NV gateway (they use the 510 models around here...I think it's nvg510. 5something. Anyways...I recall some area to check off telling it to use the public block..and then you plug those numbers into another DHCP service you'll find on it....you can enter the MAC of your firewalls or devices so it's like a DHCP reservation with the static public IPs...so the correct device gets the correct pub IP. I never trust that so even after entering that...I still manually assign the static pub IP to the WAN interface of my firewalls.

It's ugly. Things like VoIP still don't work optimally through that. I really can't stand U-Verse for business setups. Love it for home (I've had it for over 6 years)...hate it for biz.
 
Thank you for all the help. Unfortunately they do have nvg model. I think I am going to convince them just to get the entry level cable internet package for the vendor.

I did read where this causes issues with the voip phone lines through att. They also have a staff that likes holding in the reset button.
 
I really can't stand U-Verse for business setups.

That's worth knowing, thanks - I have one client that has Uverse connections for failover on the cable modem (vendor-hosted EMR so if there's no Internet they are down), but it's not even configured for full failover of VPNs, etc - just enough to still get to the EMR.
 
That's worth knowing, thanks - I have one client that has Uverse connections for failover on the cable modem (vendor-hosted EMR so if there's no Internet they are down), but it's not even configured for full failover of VPNs, etc - just enough to still get to the EMR.

I have VPN going through them at some clients.....both IPSec and OpenVPN. Those seem to work OK.
I just hate the initial setup of them, each time we go out to set one up...seems the "new" version of the modem has a newer firmware that is juuuuuust different enough to make you go flipping through tabs looking for the sections you need to find. A real time spending onsite.
Versus cable...the straight up Moto modems or SMC/Netgear gateways...wicked quick 'n simple. And no funky MTU on cable to molest traffic.
 
Back
Top