From owner-freebsd-current@FreeBSD.ORG Sun Feb 27 19:11:36 2005 Return-Path: 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 0354216A4CE for ; Sun, 27 Feb 2005 19:11:36 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDAFE43D58 for ; Sun, 27 Feb 2005 19:11:35 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] (sam@[66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j1RJBYWi045089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Feb 2005 11:11:35 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <42221B96.7060508@errno.com> Date: Sun, 27 Feb 2005 11:12:22 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jochen Gensch References: <42211B4A.6090307@gmx.de> <422158D3.7020603@errno.com> <4221A726.3090707@gmx.de> In-Reply-To: <4221A726.3090707@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Wpa, dhcp and default routes... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sun, 27 Feb 2005 19:11:36 -0000 Jochen Gensch wrote: > Sam Leffler wrote: > >> I think I recall seeing this. I mostly use minipci cards so don't >> experience this. I'll check on it. > > > Thanks! > > >> I've not seen that however I mostly use a port of the openbsd dhclient >> that's been modified to understand 802.11 msgs through the routing >> socket. Unfortunately I've got no time to shepherd this work into the >> tree and noone responded to my request for help in the last status report > > > Is that port available for FreeBSD? No, I've been looking for a committer to shepherd the work into the tree. In particular I am concerned about the potential fallout in changing from a single instance of dhclient to having one per/interface. > Mmh, but why isn't the option -i for > periodical polling working? > >> Yes, this is a pain with the current dhclient. I believe it's >> resolved with the new dhclient hook scripts. > > > Could you geive me a bit more information on that? What hook scripts and > when / where could I test them? But why is setting up a corret route an > dhclient issue? http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/wifi&HIDEDEL=NO Sam