Someone on IRC brought to my attention that the version of dhclient shipping with RedHat 8.0 (3.0pl1-9) still has the TTL set to 16. In relatively sane networks, this isn't an issue, but when AT&T Broadband restructured their network in June, the DHCP server ended up much further away (something like 21 hops, for me), causing problems for people using dhclient [1]. One solution was to mangle the outgoing DHCP request with iptables so that the TTL was higher [2]. This didn't work for the person asking for help this morning, so I decided to implement the more permanent fix [3]. I've patched and compiled the dhcp source RPM from RH8, changing the TTL to 128. RPMs (& SRPM) can be found at: http://devel.tclug.org/dhclient/RPMS/dhclient-3.0pl1-9.tclug1.i386.rpm http://devel.tclug.org/dhclient/RPMS/dhcp-3.0pl1-9.tclug1.i386.rpm http://devel.tclug.org/dhclient/RPMS/dhcp-devel-3.0pl1-9.tclug1.i386.rpm http://devel.tclug.org/dhclient/SRPMS/dhcp-3.0pl1-9.tclug1.src.rpm The most important one is the dhclient RPM, but I've included the rest since, well, that's what rpmbuild spit out. The patch I used was: http://devel.tclug.org/dhclient/dhclient.patch Bob, feel free to replicate that for the TCLUG apt repository if you want. Many thanks to Scott Dier's co-worker for coming up with the solution, and to Nate Straz for passing it along. Jima 1. http://archives2.real-time.com/pipermail/tclug-list/2002-June/051341.html 2. http://archives2.real-time.com/pipermail/tclug-list/2002-June/051485.html 3. http://archives2.real-time.com/pipermail/tclug-list/2002-June/051477.html