From owner-freebsd-current@FreeBSD.ORG Fri Jul 15 15:18:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E22516A41C for ; Fri, 15 Jul 2005 15:18:21 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id D439843D49 for ; Fri, 15 Jul 2005 15:18:20 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j6FFIEms099998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Jul 2005 08:18:15 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42D7D4E6.3020105@errno.com> Date: Fri, 15 Jul 2005 08:23:18 -0700 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050327) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Randy Bush References: <20050714182136.071B35D07@ptavv.es.net> <42D70C0B.9090802@errno.com> <17111.42602.38548.316014@roam.psg.com> In-Reply-To: <17111.42602.38548.316014@roam.psg.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Problems with OpenBSD dhclient X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 15:18:21 -0000 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