From owner-freebsd-current@FreeBSD.ORG Sun Feb 27 11:22:19 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 B7AFA16A4CE for ; Sun, 27 Feb 2005 11:22:19 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9700343D5F for ; Sun, 27 Feb 2005 11:22:18 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 27 Feb 2005 11:22:17 -0000 Received: from pD9E6EB42.dip.t-dialin.net (EHLO ms.homeip.net) (217.230.235.66) by mail.gmx.net (mp001) with SMTP; 27 Feb 2005 12:22:17 +0100 X-Authenticated: #15946415 Received: from [10.0.0.1] (helo=[10.0.0.140]) by ms.homeip.net with esmtpsa (TLSv1:AES256-SHA:256) id 1D5MXD-000ECI-AE; Sun, 27 Feb 2005 12:24:27 +0100 Message-ID: <4221AD64.7080804@gmx.de> Date: Sun, 27 Feb 2005 12:22:12 +0100 From: Jochen Gensch User-Agent: Mozilla Thunderbird 1.0 (X11/20050101) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler , freebsd-current@freebsd.org References: <42211B4A.6090307@gmx.de> <422158D3.7020603@errno.com> In-Reply-To: <422158D3.7020603@errno.com> X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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 11:22:19 -0000 Sam Leffler wrote: > 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 Restarting the dhclient via /etc/rc.d/dhclient restart works fine, though! I guess I will use a little script, which periodically restarts dhclient this way. However this isn't a fine way... Thanks, Jochen