From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 21:37:49 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A22F6106564A; Tue, 10 Feb 2009 21:37:49 +0000 (UTC) (envelope-from nugundam@gmail.com) Received: from fed1rmmtao105.cox.net (fed1rmmtao105.cox.net [68.230.241.41]) by mx1.freebsd.org (Postfix) with ESMTP id 756618FC0A; Tue, 10 Feb 2009 21:37:49 +0000 (UTC) (envelope-from nugundam@gmail.com) Received: from fed1rmimpo01.cox.net ([70.169.32.71]) by fed1rmmtao106.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090210211401.SQQB12540.fed1rmmtao106.cox.net@fed1rmimpo01.cox.net>; Tue, 10 Feb 2009 16:14:01 -0500 Received: from [192.168.4.7] ([68.228.67.116]) by fed1rmimpo01.cox.net with bizsmtp id EME11b00H2WWb6k03ME2xo; Tue, 10 Feb 2009 16:14:02 -0500 X-Authority-Analysis: v=1.0 c=1 a=-CzT27niHhcA:10 a=flI6v7w23cIA:10 a=6I5d2MoRAAAA:8 a=mmMqO3jDGEZO55agLyUA:9 a=ZHkKd2_gbGTIDV2M3lgA:7 a=UZnQ2c5Lp-HCnwLzBK2PuYy4K6MA:4 a=SV7veod9ZcQA:10 a=gi0PWCVxevcA:10 X-CM-Score: 0.00 Message-ID: <4991EE19.5020401@gmail.com> Date: Tue, 10 Feb 2009 13:14:01 -0800 From: Joseph Lee User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Sepherosa Ziehau References: <200806191030.m5JAU36i027140@freefall.freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net , Andrew Thompson Subject: Re: kern/124753: net80211 discards power-save queue packets early X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 21:37:50 -0000 I apologize for following up so late on this. I've only now have time to follow up. Sepherosa Ziehau wrote: > On Thu, Jun 19, 2008 at 6:30 PM, wrote: >> Synopsis: net80211 discards power-save queue packets early >> >> Responsible-Changed-From-To: freebsd-i386->freebsd-net >> Responsible-Changed-By: remko >> Responsible-Changed-When: Thu Jun 19 10:29:47 UTC 2008 >> Responsible-Changed-Why: >> reassign to networking team. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=124753 > > In How-To-Repeat, you said: > "Then associate a recent Windows Mobile 6.1 device to the FreeBSD box > running hostapd ..." > > In Description, you said: > "The WM6.1 device recv ps-poll's for packets every 20 seconds ..." > > AFAIK, STA sends ps-poll to AP; AP does not send ps-poll to STA. Why > did your windows STA receive ps-poll from freebsd AP? Did you capture > it by using 802.11 tap? > > And which freebsd driver were you using? I'm using the ath wifi driver. The upgrade to FreeBSD 7.1 has not changed WiFi behavior. > Your problem looks like: > - Either freebsd AP did not properly configure TIM in beacons, which > could be easily found out by using 802.11 tap. But I highly suspect > if you were using ath(4), TIM would be misconfigured. What is tap? > - Or your windows STA didn't process TIM according to 802.11 standard. Sam Leffler wrote: >The PR states the listen interval sent by the station is 3 (beacons) and the beacon >interval is 100TU. This means the AP is required to buffer unicast frames for only 300TU >which is ~300 ms. But according to the report the Windows device is polling every 20 >seconds so there's no guarantee any packets will be present (even with the net80211 code >arbitrarily using 4x the list interval specified by the sta). I find it really hard to >believe a device would poll every 20 secs so something seems wrong in what's >reported/observed. The device is in its best power-saving mode where it make take time to respond to any packets. I only have this problem with FreeBSD hostap on the switch from FreeBSD 6 -> 7. Other APs such as Netgear/Linkgear have no issues, but can be postulated they don't implement PM as FreeBSD currently does. Also, on this same FreeBSD wifi-ap, no laptops have the same issue. So, it's isolated between FreeBSD and Windows Mobile. >Given that defeating the aging logic just pushed the problem elsewhere it sounds like >there's something else wrong which (as you note) probably requires a packet capture to >understand. I'm pretty sure TIM is handled correctly in RELENG_7 but a packet capture >would help us verify that. What do I need to do get you guys a packet capture to verify the TIM? Thanks, Joseph