From: "Brian T. Schmidt" >This isn't so much to offer a solution to your problem, but more of an "I >feel your pain" thing. I use AT&T @Home, though in the Dallas area, and I >also have similar problems you describe. On Wed, 1 Aug 2001, Mike Chambers wrote: > Is anyone by chance using AT&T@Home cable service especially in the >Chicago area? This is an @home problem with the way their DHCP servers communicate. (At least as of a year and a half ago in Louisville) As it was explained to me, the linux client will open negotations with the DHCP server, the server will make the updates and respond, but the response is technically malformed. As the Linux DHCP client is strict, it ignores the response and your computer sits their waiting infinitely for the "OK" signal. I spent four weeks trying to debug my ethernet card thinking it was a bad driver. I was using RH6.1 at the time and the hack I came up with was to cron a dhcp request to maintain my lease and then immediately switch back to static. I've been told there is a hacked DHCP client just for @Home. It might be referred to as a roadrunner-compliant DHCP client since the Roadrunner cable network had the same problems and IIRC, the developer was using Roadrunner. I haven't tried it under either 7.1 or 6 so I can't tell you much else. -James McP _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
