Date: Fri, 15 Jul 2005 08:23:18 -0700 From: Sam Leffler <sam@errno.com> To: Randy Bush <randy@psg.com> Cc: freebsd-current@freebsd.org Subject: Re: Problems with OpenBSD dhclient Message-ID: <42D7D4E6.3020105@errno.com> In-Reply-To: <17111.42602.38548.316014@roam.psg.com> References: <20050714182136.071B35D07@ptavv.es.net> <42D70C0B.9090802@errno.com> <17111.42602.38548.316014@roam.psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Randy Bush wrote: >>>More serious is that I can't roam. When I move between APs, dhclient >>>exits and I need to manually re-start it. I lose my SSH sessions. Ugh! >> >>This should not be happening; dhclient should get a disassociate event, >>drop the lease, then get an associate when you join the new ap and >>immediately grab a new lease. > > > aiii! this was merely a layer-2 re-association, no change at layer-3. I mis-spoke; dhclient trys to re-acquire the current lease. This is exactly what happened before except it should now happen _immediately_ on being notified of a re-association to the same ap or an association to a new ap. Actually I could check for a re-association and not re-aquire the lease to reduce the overhead but regardless this should be ok (so far as I understand the protocols). The previous code polled for these events. This made it prone to missing fast re-associations (instead falling back to various timeouts) and slow to respond when roaming. The new code had been working correctly; something has clearly changed and I'll fix it asap. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42D7D4E6.3020105>