From owner-freebsd-net@FreeBSD.ORG  Mon Mar 23 18:50:08 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 3751D1065670
	for <freebsd-net@hub.freebsd.org>; Mon, 23 Mar 2009 18:50:08 +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 24FBE8FC1B
	for <freebsd-net@hub.freebsd.org>; Mon, 23 Mar 2009 18:50:08 +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 n2NIo7pO041693
	for <freebsd-net@freefall.freebsd.org>; Mon, 23 Mar 2009 18:50:07 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2NIo7wG041686;
	Mon, 23 Mar 2009 18:50:07 GMT (envelope-from gnats)
Date: Mon, 23 Mar 2009 18:50:07 GMT
Message-Id: <200903231850.n2NIo7wG041686@freefall.freebsd.org>
To: freebsd-net@FreeBSD.org
From: Bruce M Simpson <bms@incunabulum.net>
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: Bruce M Simpson <bms@incunabulum.net>
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 18:50:08 -0000

The following reply was made to PR kern/132722; it has been noted by GNATS.

From: Bruce M Simpson <bms@incunabulum.net>
To: Matthias Apitz <guru@unixarea.de>
Cc: bug-followup@freebsd.org, Sam Leffler <sam@freebsd.org>, 
 freebsd-net@freebsd.org, "Sean C. Farley" <scf@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 18:44:42 +0000

 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 <ap-ip-address>' running in the background, we don't 
 see this problem.
 
     We have yet to produce a tcpdump to catch it 'in the act' and 
 observe the DLT_IEEE80211 traffic when it actually happens, I have only 
 seen the symptoms. The AP does not show the EeePC units as being 
 associated any more at this point, but ath0 still shows 'status: 
 associated'. The AP involved is a Netgear WG602 V2, and is running the 
 vendor's firmware.
 
 I'll try to get set up with 'tcpdump -y ieee802_11' from initial boot 
 (including dhcp and anything we bump into).
 
 cheers
 BMS