US Telco Support > AT&T > AT&T Southwest > Sticky IP?

Sticky IP?

A static IP is basically a DHCP from the SBC server, no authentication needed from the computer/router/modem, you just statically put the IPs in your TCP/IP/router. A sticky IP is the opposite in a sense, you still receive the same IP everytime but you have to authenticate and the static IP is given through the radius once you authenticate, so you can just set your equipment/OS to obtain the IP automatically.

reply to Brainless
Does each IP address have its own authentication, or is it first come first serve on the 5 ip's?

edit for typo
--
Building a better community
»www.ourrecipebox.com

reply to Brainless
You can only have 1 PPPoE connection. Your static IP block is routed in to you from internet using your PPPoE IP as gateway. It is up to you to route it in from there if not using SBC hardware.

Ok efflandt, your confusing me. For the past three years I have had the expert+s account. All my servers have their own IP addresses (accually it is done through my routers, but the same effect). The 6th ip is the gateway assigned at the SBC router. That is the gateway for all my servers.

I am considering migrating over to the pro-s account. But I need to understand how the sticky ip's work before I decide to switch. So far I dont like the pppoe because of the extra overhead. So which is it, the servers have their own auth to get their own IP, the IP's are assigned by the SBC gateway, or the gateway is on my end? I am not clear on how the servers are assigned their own IP address with sticky IP's.
--
Building a better community »www.ourrecipebox.com

reply to Brainless
Static IP = normal networking stuff. gateway IP is hardcoded into the interface on SBC side. This makes the static IPs routed down that circuit.

Sticky IP's = PPPoE with IP's that always get pushed to the pppoe interface that auths with that user ID. So everytime you connect with that UID you will pull that IP.

What that will mean is you auth once. The device that does the auth gets the Gateway IP. This is tunneled to the SBC router though the PPPoE connection and is in effect applied to the machine that auths and the SBC router at the same time.

This can be just a single computer if you want. However I would suggest a router doing the PPPoE auth so its simpler to pass the other IP's out.

Dont ask me why they went to that model, it makes zero sense to me, only thing I can figure is being able to auto build all possible router interfaces PPPoE and not mess with manual config of IP's to customer interfaces.. but thats never going to outweigh having to deal with all the issues PPPoE statics create compared to straight statics. IMHO but hell, what do I know.. I feel lucky to have my shoes tied most days =)

Thanks DorkLord,

You explained alot. Have there been any real problems with this, or have the problems been mostly the learning curve with a new way of doing things?

I still dont like the pppoe. Had to deal with it before I went with statics. Between the overhead and the extra cycles on the box it is running on (would be on a router now though), it is not a very effecent way of doing things. The way it was done before is much more effecient, and way more stable. I am not at all sure I want to switch over for a little more on the download side.
--
Building a better community »www.ourrecipebox.com

reply to Brainless
Ok so I have this "sticky IP" situation that is confusing. I am using Netgear FVS318 vpn firewalls to configure a VPN tunnel between two locations (both of which have sticky IPs). What I would like to do is configure the VPN firewall to have one of the 5 "sticky IPs" statically assigned to it. This is required for the type of IKE VPN tunnel with static IPs between 2 locations. I cannot seem to find any information about how to get my router to have one of these Public WAN IPs statically assigned to it.
SBC does not offer any explanation besides "sticky IPs and static IPs are identical"

Please help

reply to Brainless
The PPPoE overhead is relatively small. It is dwarfed by the TCP overhead and the ATM overhead, and you have those even without PPPoE.

Whichever device handles the PPPoE needs to handle the block of addresses assigned to you. Normally, your account installation would include a modem/router to handle this. For a good overview, see »AT&T Midwest/Ameritech FAQ »SBC/Ameritech 5 Static IP-Compatible Routers (update 05-19-06)

Sticky Statics are a joke. There just a means by which SBC has more control. Reliability, is the issue, not over head. It is another point of failure if not more. Not only that, SBC has finally found a way to charge their $250 truck role charge. The mandatory charge they forced upon you so that you could train their technicians that came out and did absolutely nothing. Before you were able to by basic and upgrade to avoid the Truck Role Charge. Now, you have to pay for their Router/Modem, which costs 180 dollars now, but will eventually go up in price once we've surrendered to their new business model. It's like their sticking matchbox cars up our ass until we loosen up, then they move to the tonka trucks.

That is how I feel. I have tried two routers, a Netgear and a Linksys and neither would work. I asked SBC and was told I needed something like the Cayman they could sell me or a Cisco. In any case I needed to be prepared to spend at least $200 or more.

I really think they are falsely marketing the Static IP service as they do not clearly state it will only work with specific hardware up front and that what they are doing does not seem to meet standards as both Netgear and Linksys tech support said they did not intend to support the SBC PPPoE Static method because it was not a standard.

So right now I am paying for the Pro S service and can not use my static IPs at all.

quote:

---

So right now I am paying for the Pro S service and can not use my static IPs at all.

---