From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 22:17:09 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7616F234; Mon, 8 Sep 2014 22:17:09 +0000 (UTC) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 249EB14F2; Mon, 8 Sep 2014 22:17:09 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id i8so16388257qcq.22 for ; Mon, 08 Sep 2014 15:17:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=juI0Z7ZZy5sJ3+xCJGhP5fAhYRMnmVgy4AyEIV1nPM8=; b=EMLVw3I+sorVTMWkBeFOVoWrhIuzb9SYBS7bY7sTpHpE2bxNbGSyX+071kz0IBofu9 WKRp8pOI538Yf23SAha7yGscJ3HMl/gRQMkzEjpQCVR0uqhHx7Tk20DB07qdesZ6jZc5 DX7OV2Ngd/4LVF2bZ6g3PRkiumUBXRT5yKxAug2zjtp+mKgJnk/oZ0b5GeUBsF1scadR csg350BZOGa2akBMzGMk3kDKAK7BLDb0/b95S7Dyw2mUkXPNgbbPOo9HfkqSpEbD9K8F Jinn6NthgIwmGuAAp4jJEm67mhZvV5yxtxVlpExH4nH5D38VFqMWSIae2sAVhqCgZPta cSNg== MIME-Version: 1.0 X-Received: by 10.229.38.3 with SMTP id z3mr45577797qcd.17.1410214628254; Mon, 08 Sep 2014 15:17:08 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Mon, 8 Sep 2014 15:17:08 -0700 (PDT) In-Reply-To: <540E2A2D.4090301@freebsd.org> References: <540C751F.6050202@freebsd.org> <540C92D6.4030106@freebsd.org> <540CC53A.90600@freebsd.org> <540E2A2D.4090301@freebsd.org> Date: Mon, 8 Sep 2014 15:17:08 -0700 X-Google-Sender-Auth: cZV32CKqFwTBWfBJuPEoSd-MG5w Message-ID: Subject: Re: Issues with urtwn From: Adrian Chadd To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2014 22:17:09 -0000 Please compile your kernel with IEEE80211_DEBUG, then enable debugging - wlandebug +state +power You can disable powersave with 'ifconfig wlan0 -powersave', but it shouldn't be enabled by default. -a On 8 September 2014 15:14, Nathan Whitehorn wrote: > So it's definitely to do with powersave. Here's a bunch of iterations of > ifconfig list sta on my laptop: > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 54:78:1a:a0:91:22 149 1 54M 37.0 0 4385 37104 EPS A HTCAP > RSN WME > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 54:78:1a:a0:91:22 149 1 54M 37.5 0 4412 39360 EPS A HTCAP > RSN WME > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 54:78:1a:a0:91:22 149 1 54M 37.5 0 4417 39360 EPS AP HTCAP > RSN WME > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 54:78:1a:a0:91:22 149 1 54M 37.5 0 4417 39360 EPS AP HTCAP > RSN WME > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 54:78:1a:a0:91:22 149 1 54M 37.5 0 4417 39360 EPS AP HTCAP > RSN WME > > You can see the connection die on the third line, when the txseq and rxseq > counters stop incrementing and 'P' gets added to the FLAG field. Does this > mean the AP has turned on powersave on its end? > -Nathan > > > On 09/07/14 14:07, Adrian Chadd wrote: >> >> Hi, >> >> The way it's supposed to work in the legacy 802.11 powersave world is >> that you send a/any data frame with the powermgt bit in the 802.11 >> header set to 0 and the AP goes "oh they're awake!" and sends you your >> buffered frames. >> >> By default powersave isn't enabled, so we should never be _telling_ >> the AP that we're going to sleep and the stack always sends data >> frames with pwrmgt=0. >> >> You can ensure it's disabled by ifconfig wlan0 -powersave >> >> The code in -HEAD that manages that is in ieee80211_power.c. I added >> an explicit powersave support mode for NICs that need it done for them >> - and the only one it's enabled for right now is ath(4). >> >> The only reason net80211 sends pwrmgt changes outside of having >> net80211 power save enabled is the background scan code. >> >> I'd compile in IEEE80211_DEBUG in your kernel, then I'd use wlandebug >> +scan to see if somehow there's some scanning going on; and wlandebug >> +power to see if any power save transitions occur. >> >> Are you absolutely sure it's a receive side buffering problem, rather >> than a send side problem? >> >> It's also possible that the NIC stops receiving and the AP treats that >> as "oh ok, they've gone to sleep for a while." ath(4) now does this in >> hostap mode. >> >> >> -a >> >