Date: Fri, 2 Dec 2005 01:43:57 +0000 From: Joao Barros <joao.barros@gmail.com> To: "Lutt, Paul" <paul.lutt@fluke.com> Cc: freebsd-stable@freebsd.org Subject: Re: dhclient problem with static leases Message-ID: <70e8236f0512011743m67f2dbeck4ad6ee1854f3fc90@mail.gmail.com> In-Reply-To: <20051201075632.P1063@evtpc1390.na.flukecorp.com> References: <dmc4i8$9mt$1@sea.gmane.org> <20051127114252.GG1383@sun.unixguru.nl> <dmc9h8$ktb$1@sea.gmane.org> <20051201075632.P1063@evtpc1390.na.flukecorp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/1/05, Lutt, Paul <paul.lutt@fluke.com> wrote: > > Richard Arends wrote: > >> Removing /var/db/dhclient.leases* fixed the > >> problem not getting a lease for me and several other people over here. > > I had similar issues with my DLINK access point at home. DHCP was > very flakey until I setup a /etc/rc.shutdown.local file to remove > /var/db/dhclient.leases* at shutdown. > After upgrading my "router" machine from 5.4 to 6.0 and when my ISP had DHCP problems, I came home and saw that either the machine had IP but could not connect anywhere or that dhclient had left and it's famous last words were: "Link down, exiting" I started getting flashbacks of dhcpcd on Linux.... I had no link faults on the nic or switch so I started poking on dhclient info and then I saw 2 leases on dhclient.leases After some testing I noticed that if dhclient couldn't get an IP directly from the DHCP it went for the backup lease which was invalid. Now...this on 5.4 was fine, but then again this is another dhclient. Bug? Undocumented feature? I couldn't find a way to disable the "see if we have a lease in file" behavior... -- Joao Barros
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70e8236f0512011743m67f2dbeck4ad6ee1854f3fc90>