From owner-freebsd-net@FreeBSD.ORG Mon Mar 23 20:50:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DA211065691 for ; Mon, 23 Mar 2009 20:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5BBF78FC1F for ; Mon, 23 Mar 2009 20:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2NKo3Bu004067 for ; Mon, 23 Mar 2009 20:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2NKo3mi004059; Mon, 23 Mar 2009 20:50:03 GMT (envelope-from gnats) Date: Mon, 23 Mar 2009 20:50:03 GMT Message-Id: <200903232050.n2NKo3mi004059@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: John Hay Cc: Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Hay List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2009 20:50:03 -0000 The following reply was made to PR kern/132722; it has been noted by GNATS. From: John Hay To: Bruce M Simpson Cc: Matthias Apitz , freebsd-net@freebsd.org, Sam Leffler , "Sean C. Farley" , bug-followup@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Mon, 23 Mar 2009 22:40:50 +0200 On Mon, Mar 23, 2009 at 06:44:42PM +0000, Bruce M Simpson wrote: > Matthias Apitz wrote: > >I went today evening with my EeePC and CURRENT on USB key > >to that Greek restaurant; DHCP does not get IP in CURRENT either; > >this is somehow good news, isn't it :-) > > > > This may be orthogonal, but: > A lab colleague and I have been seeing a sporadic problem where the > ath0 exhibits the symptoms of being disassociated from its AP. We are > running RELENG_7 on the EeePC 701 since the open source HAL merge. > In the behaviour we're seeing, we don't see any problem with the > initial dhclient run, the ath0 just seems to get disassociated within > 5-10 minutes of associating. > > If we leave 'ping ' running in the background, we don't > see this problem. > I found doing a -bgscan before it happens, make it not happen. I now have -bgscan in my rc.conf. John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org