pump, AT&T, and dhcp...
DJ
keitaro at attbi.com
Wed Mar 19 12:09:38 EST 2003
At 11:18 AM 19/03/2003 -0500, dsr at tao.merseine.nu wrote:
>On Wed, Mar 19, 2003 at 11:13:31AM -0500, DJ wrote:
> > I saw several messages like it and I tried to figure out what it was or
> why
> > it's doing it. I was completely stumped and I ended up using dhcpcd to
> > retrieve my IP address from the server. So does anyone here happen to
> know
> > what kind of error is this and how to interpret it? It's not a problem
> > but I'd like to see if I can fix it anyway, since it's a preference of
> mine
> > to use a different dhcp client.
>
>I've found only ISC's dhcpcd and the udhcpc in Debian to work
>consistently with ATT. pump works intermittently, and I believe that
>this is ATT's fault.
Well that kinda sucked. I've used pump for... a few years
perhaps? Maybe more than that. And I've never had any problem with it
'till now. So now I do not know what to blame: pump's inability to be
consistent or AT&T's handing of their Internet service over to
Comcast. "Smooth transition" my butt...
> > PS: I'd try a different NIC but I'm unsure what exactly is the situation
> > with NICs and AT&T/Comcast (plus, I'm out of spare NICs that has a
> > DIFFERENT chipset). Previously I've been using the same NIC because AT&T
> > supposedly locks cmodem access via the NIC's MAC address. Recently a
> > friend of mine's NIC died and went out to buy a replacement. So we tried
> > it, did not work, called up AT&T's support line, and was told that it
> > should work since they don't track MAC addresses anymore. So which policy
> > holds true?
>
>They used to, but they don't anymore.
Well that answers my question then. Thanks.
__________________________________________________________________
/ keitaro AT attbi DOT com/IRC Nicks: Junta, Strider on #db/#ssppp \
| IRC Servers: irc.aus.org/irc.anime-chat.com ports 6660-6669/7000 |
| = http://junta.darktech.org/public_key.txt -- GnuPG Public Key = |
+-----[ "One shall stand, one shall fall..." - Optimus Prime ]-----+
More information about the Discuss
mailing list