From owner-freebsd-current@FreeBSD.ORG Fri Jul 15 13:04:24 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 64ED516A41C for ; Fri, 15 Jul 2005 13:04:24 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: from mailserv1.neuroflux.com (ns2.neuroflux.com [204.228.228.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0200D43D46 for ; Fri, 15 Jul 2005 13:04:23 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 29721 invoked by uid 1003); 15 Jul 2005 13:04:12 -0000 Received: from ryans@gamersimpact.com by mailserv1.neuroflux.com by uid 89 with qmail-scanner-1.22 (clamscan: 0.65. spamassassin: 2.60. Clear:RC:1(63.224.20.10):. Processed in 1.310031 secs); 15 Jul 2005 13:04:12 -0000 Received: from unknown (HELO ?192.168.0.5?) (63.224.20.10) by mailserv1.neuroflux.com with SMTP; 15 Jul 2005 13:04:10 -0000 Message-ID: <42D7B45D.9080807@gamersimpact.com> Date: Fri, 15 Jul 2005 08:04:29 -0500 From: Ryan Sommers User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <20050714182136.071B35D07@ptavv.es.net> <42D70C0B.9090802@errno.com> In-Reply-To: <42D70C0B.9090802@errno.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 13:04:24 -0000 Sam Leffler wrote: > > Something is busted; I'll need to investigate. If you want to help you > can run ieee80211watch (from tools/tools/ath) while things happen and > note the events that get sent by the kernel. > > Sam I've been having very similar problems with wireless and DHCP. My case is somewhat different though. Instead of DHCP not only not setting the default route, it doesn't even seem to be setting up a routing socket. For the past few weeks my sequence while on the road using APs where I don't know them before hand has been: 1) dstumbler to find AP name 2) add entry to /etc/dhclient.conf 3) Run dhclient to see IP address assignment 4) Manually take the interface down and bring it back up setting media as in dhclient.conf entry 5) Assign IP address and create the default route. Lately dhclient hasn't even been setting the IP address all the time. And for a slightly longer time if I simply tried to create/change the default route to the new gateway I would get a no routing socket error. Manually taking the interface down and up solved this. Note though, this only applies to wireless, wired dhclient plays very nicely. Let me know if there is anything I can do to help diagnose. -- Ryan Sommers ryans@gamersimpact.com