From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 01:40:04 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69D61FEE for ; Sun, 7 Sep 2014 01:40:04 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 515391DCA for ; Sun, 7 Sep 2014 01:40:04 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s871e4Qu088253 for ; Sun, 7 Sep 2014 01:40:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 01:40:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 01:40:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #16 from Adrian Chadd --- r270738 fixed some antenna stuff. r270742 fixed AMPDU completion notification to AMRR. This _should_ be better (and it is for me!) but Hiren still reports oddness. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 01:40:19 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B1D5492 for ; Sun, 7 Sep 2014 01:40:19 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9980C1E4B for ; Sun, 7 Sep 2014 01:40:19 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s871eJ80089147 for ; Sun, 7 Sep 2014 01:40:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 01:40:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 01:40:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #17 from Adrian Chadd --- Also, please test out with the latest -HEAD and see if it behaves better for you. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 01:43:30 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 850ACC4 for ; Sun, 7 Sep 2014 01:43:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6C10D1E5D for ; Sun, 7 Sep 2014 01:43:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s871hUrR099166 for ; Sun, 7 Sep 2014 01:43:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 01:43:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 01:43:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #18 from Hiren Panchasara --- Noticing only 400kbps on ssh from laptop to desktop on wifi. root@flymockour-l7:/home/hirenp/head/sys/net80211 # sysctl dev.iwn.0.debug=0xff dev.iwn.0.debug: 0 -> 255 root@flymockour-l7:/home/hirenp/head/sys/net80211 # wlandebug +rate net.wlan.0.debug: 0x0 => 0x20 I see the rate is stuck at 0x0080. Here are logs to send packet no: 1614 to 1616 - just for example. I've added following printf to see if on successful transfer, ratectl code is getting trigger to ++ the rate. It seems to be firing but not doing the right thing. Index: if_iwn.c =================================================================== --- if_iwn.c (revision 270821) +++ if_iwn.c (working copy) @@ -3500,10 +3500,12 @@ */ if (status & IWN_TX_FAIL) { ifp->if_oerrors++; + DPRINTF(sc, IWN_DEBUG_XMIT, "->%s Not updating rate control if_opackets: %lu\n", __func__, ifp->if_opackets); ieee80211_ratectl_tx_complete(vap, ni, IEEE80211_RATECTL_TX_FAILURE, &ackfailcnt, NULL); } else { ifp->if_opackets++; + DPRINTF(sc, IWN_DEBUG_XMIT, "->%s updating rate control if_opackets: %lu\n", __func__, ifp->if_opackets); ieee80211_ratectl_tx_complete(vap, ni, IEEE80211_RATECTL_TX_SUCCESS, &ackfailcnt, NULL); } Logs: 64190 Sep 6 18:27:57 flymockour-l7 kernel: ->iwn_tx_done updating rate control if_opackets: 1613 64191 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=63; qid 6 idx 154 flags 0 type 192(RX_PHY) len 68 64192 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=0; qid 6 idx 155 flags 0 type 193(MPDU_RX_DONE) len 168 64193 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 55 rssi 9766 11051 0 result -56 64194 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=1; qid 6 idx 156 flags 0 type 192(RX_PHY) len 68 64195 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=2; qid 6 idx 157 flags 0 type 193(MPDU_RX_DONE) len 336 64196 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 29 rssi 4884 5399 0 result -50 64197 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=3; qid 6 idx 158 flags 0 type 157(BEACON_STATS) len 528 64198 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 102; cck=48, ofdm=2, ht=0, total=152, thresh=5100 64199 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=4; qid 9 idx 1 flags 0 type 168(IWN_CMD_SET_SENSITIVITY) len 4 64200 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=5; qid 6 idx 159 flags 0 type 192(RX_PHY) len 68 64201 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=6; qid 6 idx 160 flags 0 type 193(MPDU_RX_DONE) len 120 64202 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 56 rssi 10023 11308 0 result -56 64203 Sep 6 18:27:57 flymockour-l7 kernel: iwn_start_locked: called 64204 Sep 6 18:27:57 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 63 len 80 nsegs 2 flags 0x00100018 rate 0x0080 plcp 0x00004100 64205 Sep 6 18:27:57 flymockour-l7 kernel: iwn_start_locked: done 64206 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=7; qid 0 idx 63 flags 0 type 28(TX_DONE) len 44 64207 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 63 retries 0 nkill 0 rate 80004100 duration 296 status 201 64208 Sep 6 18:27:57 flymockour-l7 kernel: ->iwn_tx_done updating rate control if_opackets: 1614 64209 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=8; qid 6 idx 172 flags 0 type 192(RX_PHY) len 68 64210 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=9; qid 6 idx 173 flags 0 type 193(MPDU_RX_DONE) len 336 64211 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 28 rssi 4627 5399 0 result -49 64212 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=10; qid 6 idx 174 flags 0 type 157(BEACON_STATS) len 528 64213 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 102; cck=11, ofdm=0, ht=0, total=113, thresh=5100 64214 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=11; qid 6 idx 183 flags 0 type 192(RX_PHY) len 68 64215 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=12; qid 6 idx 184 flags 0 type 193(MPDU_RX_DONE) len 336 64216 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 30 rssi 3858 5398 0 result -52 64217 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=13; qid 6 idx 185 flags 0 type 157(BEACON_STATS) len 528 64218 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 103; cck=36, ofdm=0, ht=0, total=139, thresh=5150 64219 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=14; qid 6 idx 188 flags 0 type 192(RX_PHY) len 68 64220 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=15; qid 6 idx 189 flags 0 type 193(MPDU_RX_DONE) len 120 64221 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 55 rssi 9765 11051 0 result -56 64222 Sep 6 18:27:57 flymockour-l7 kernel: iwn_start_locked: called 64223 Sep 6 18:27:57 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 64 len 86 nsegs 2 flags 0x00100018 rate 0x0080 plcp 0x00004100 64224 Sep 6 18:27:57 flymockour-l7 kernel: iwn_start_locked: done 64225 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=16; qid 0 idx 64 flags 0 type 28(TX_DONE) len 44 64226 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 64 retries 0 nkill 0 rate 80004100 duration 304 status 201 64227 Sep 6 18:27:57 flymockour-l7 kernel: ->iwn_tx_done updating rate control if_opackets: 1615 64228 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=17; qid 6 idx 200 flags 0 type 192(RX_PHY) len 68 64229 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=18; qid 6 idx 201 flags 0 type 193(MPDU_RX_DONE) len 120 64230 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 55 rssi 9766 11051 0 result -56 64231 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=19; qid 6 idx 206 flags 0 type 192(RX_PHY) len 68 64232 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=20; qid 6 idx 207 flags 0 type 193(MPDU_RX_DONE) len 336 64233 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 29 rssi 4885 5656 0 result -49 64234 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=21; qid 6 idx 208 flags 0 type 157(BEACON_STATS) len 528 64235 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 102; cck=32, ofdm=1, ht=0, total=135, thresh=5100 64236 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=22; qid 6 idx 219 flags 0 type 192(RX_PHY) len 68 64237 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=23; qid 6 idx 220 flags 0 type 193(MPDU_RX_DONE) len 336 64238 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 33 rssi 4884 6169 0 result -52 64239 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=24; qid 6 idx 221 flags 0 type 157(BEACON_STATS) len 528 64240 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 104; cck=50, ofdm=0, ht=0, total=154, thresh=5200 64241 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=25; qid 6 idx 222 flags 0 type 162(BEACON_MISSED) len 20 64242 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: beacons missed 0/0 64243 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=26; qid 6 idx 234 flags 0 type 192(RX_PHY) len 68 64244 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=27; qid 6 idx 235 flags 0 type 193(MPDU_RX_DONE) len 336 64245 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 31 rssi 4114 5399 0 result -52 64246 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=28; qid 6 idx 236 flags 0 type 157(BEACON_STATS) len 528 64247 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 101; cck=16, ofdm=0, ht=0, total=117, thresh=5050 64248 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=29; qid 6 idx 244 flags 0 type 192(RX_PHY) len 68 64249 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=30; qid 6 idx 245 flags 0 type 193(MPDU_RX_DONE) len 336 64250 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 31 rssi 3602 5399 0 result -52 64251 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=31; qid 6 idx 246 flags 0 type 157(BEACON_STATS) len 528 64252 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 102; cck=56, ofdm=0, ht=0, total=158, thresh=5100 64253 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: PLCP error threshold raw (56) comparison (5600) over limit (5100); retune! 64254 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=32; qid 6 idx 255 flags 0 type 192(RX_PHY) len 68 64255 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=33; qid 7 idx 0 flags 0 type 193(MPDU_RX_DONE) len 336 64256 Sep 6 18:27:57 flymockour-l7 kernel: iwn5000_get_rssi: agc 31 rssi 3858 5655 0 result -52 64257 Sep 6 18:27:57 flymockour-l7 kernel: iwn_notif_intr: cur=34; qid 7 idx 1 flags 0 type 157(BEACON_STATS) len 528 64258 Sep 6 18:27:57 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 103; cck=22, ofdm=1, ht=0, total=126, thresh=5150 64259 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=35; qid 7 idx 10 flags 0 type 192(RX_PHY) len 68 64260 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=36; qid 7 idx 11 flags 0 type 193(MPDU_RX_DONE) len 336 64261 Sep 6 18:27:58 flymockour-l7 kernel: iwn5000_get_rssi: agc 31 rssi 4114 5399 0 result -52 64262 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=37; qid 7 idx 12 flags 0 type 157(BEACON_STATS) len 528 64263 Sep 6 18:27:58 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 102; cck=32, ofdm=2, ht=0, total=136, thresh=5100 64264 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=38; qid 7 idx 21 flags 0 type 192(RX_PHY) len 68 64265 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=39; qid 7 idx 22 flags 0 type 193(MPDU_RX_DONE) len 336 64266 Sep 6 18:27:58 flymockour-l7 kernel: iwn5000_get_rssi: agc 32 rssi 4371 5656 0 result -52 64267 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=40; qid 7 idx 23 flags 0 type 157(BEACON_STATS) len 528 64268 Sep 6 18:27:58 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 103; cck=22, ofdm=11, ht=0, total=136, thresh=5150 64269 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=41; qid 7 idx 24 flags 0 type 162(BEACON_MISSED) len 20 64270 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: beacons missed 0/0 64271 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=42; qid 7 idx 32 flags 0 type 192(RX_PHY) len 68 64272 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=43; qid 7 idx 33 flags 0 type 193(MPDU_RX_DONE) len 168 64273 Sep 6 18:27:58 flymockour-l7 kernel: iwn5000_get_rssi: agc 56 rssi 9766 11308 0 result -56 64274 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=44; qid 7 idx 35 flags 0 type 192(RX_PHY) len 68 64275 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=45; qid 7 idx 36 flags 0 type 193(MPDU_RX_DONE) len 336 64276 Sep 6 18:27:58 flymockour-l7 kernel: iwn5000_get_rssi: agc 30 rssi 4115 5142 0 result -52 64277 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=46; qid 7 idx 37 flags 0 type 157(BEACON_STATS) len 528 64278 Sep 6 18:27:58 flymockour-l7 kernel: iwn_check_rx_recovery: time delta: 102; cck=50, ofdm=13, ht=0, total=165, thresh=5100 64279 Sep 6 18:27:58 flymockour-l7 kernel: iwn_check_rx_recovery: PLCP error threshold raw (63) comparison (6300) over limit (5100); retune! 64280 Sep 6 18:27:58 flymockour-l7 kernel: iwn_start_locked: called 64281 Sep 6 18:27:58 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 65 len 80 nsegs 2 flags 0x00100018 rate 0x0080 plcp 0x00004100 64282 Sep 6 18:27:58 flymockour-l7 kernel: iwn_start_locked: done 64283 Sep 6 18:27:58 flymockour-l7 kernel: iwn_notif_intr: cur=47; qid 0 idx 65 flags 0 type 28(TX_DONE) len 44 64284 Sep 6 18:27:58 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 65 retries 0 nkill 0 rate 80004100 duration 296 status 201 64285 Sep 6 18:27:58 flymockour-l7 kernel: ->iwn_tx_done updating rate control if_opackets: 1616 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 01:44:59 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 042C9E7 for ; Sun, 7 Sep 2014 01:44:59 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E00601E62 for ; Sun, 7 Sep 2014 01:44:58 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s871iwKb002213 for ; Sun, 7 Sep 2014 01:44:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 01:44:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 01:44:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #19 from Adrian Chadd --- wlandebug +rate what happens? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 01:58:08 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2EE741D7 for ; Sun, 7 Sep 2014 01:58:08 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 169F51F16 for ; Sun, 7 Sep 2014 01:58:08 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s871w7wP056362 for ; Sun, 7 Sep 2014 01:58:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 01:58:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 01:58:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #20 from Hiren Panchasara --- 18:55 < hiren> Sep 6 18:55:10 flymockour-l7 kernel: wlan0: [dc:9f:db:6a:3e:9e] AMRR: current rate 0, txcnt=11, retrycnt=14 18:55 < hiren> Sep 6 18:55:15 flymockour-l7 kernel: wlan0: [dc:9f:db:6a:3e:9e] AMRR: current rate 0, txcnt=11, retrycnt=20 18:55 < hiren> Sep 6 18:55:20 flymockour-l7 kernel: wlan0: [dc:9f:db:6a:3e:9e] AMRR: current rate 0, txcnt=11, retrycnt=21 I guess because of this much retries rate is not going up. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 02:47:12 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 90147606 for ; Sun, 7 Sep 2014 02:47:12 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 778F3137B for ; Sun, 7 Sep 2014 02:47:12 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s872lCMV059432 for ; Sun, 7 Sep 2014 02:47:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 02:47:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dieterich.joh@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 02:47:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #21 from dieterich.joh@gmail.com --- (In reply to Adrian Chadd from comment #17) > Also, please test out with the latest -HEAD and see if it behaves better for > you. Just installed r271215 and can confirm that the situation is much improved. Without setting -ht, I can get some 3.5 MB/s upload over scp to off-site. I can run more detailed tests if you wish, but I am more than happy with the status as is. Thanks so much for your work on this! :-) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 07:57:29 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 21DE3759 for ; Sun, 7 Sep 2014 07:57:29 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 08DE71F29 for ; Sun, 7 Sep 2014 07:57:29 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s877vSJv081717 for ; Sun, 7 Sep 2014 07:57:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 07:57:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 07:57:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #22 from Hiren Panchasara --- (In reply to dieterich.joh from comment #21) > (In reply to Adrian Chadd from comment #17) > > Also, please test out with the latest -HEAD and see if it behaves better for > > you. > Just installed r271215 and can confirm that the situation is much improved. > Without setting -ht, I can get some 3.5 MB/s upload over scp to off-site. I > can run more detailed tests if you wish, but I am more than happy with the > status as is. Are you connecting at 11g? Can you paste ifconfig o/p? It'd be nice to see what rate does it go up to? (with wlandebug +rate) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 12:08:29 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 DBCEEDCD for ; Sun, 7 Sep 2014 12:08:28 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC7191899 for ; Sun, 7 Sep 2014 12:08:28 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s87C8Sw4053583 for ; Sun, 7 Sep 2014 12:08:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 12:08:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dieterich.joh@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 12:08:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #23 from dieterich.joh@gmail.com --- (In reply to Hiren Panchasara from comment #22) > (In reply to dieterich.joh from comment #21) > > (In reply to Adrian Chadd from comment #17) > > > Also, please test out with the latest -HEAD and see if it behaves better for > > > you. > > Just installed r271215 and can confirm that the situation is much improved. > > Without setting -ht, I can get some 3.5 MB/s upload over scp to off-site. I > > can run more detailed tests if you wish, but I am more than happy with the > > status as is. > > Are you connecting at 11g? Can you paste ifconfig o/p? > It'd be nice to see what rate does it go up to? (with wlandebug +rate) No, this should be 11n (on the 2.4 GHz band and w/ only 20 MHz channel width, though) as I explicitly configured the access point to not support anything but 11n. ifconfig: wlan0: flags=8843 metric 0 mtu 1500 ether XXXXXX inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid XXXXXX channel 10 (2457 MHz 11g ht/20) bssid XXXXXXX country US authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit TKIP 3:128-bit txpower 15 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme roaming MANUAL wlandebug + rate: Sep 7 13:51:54 kernel: wlan0: [] AMRR: current rate 15, txcnt=36, retrycnt=11 Sep 7 13:51:54 kernel: wlan0: [] AMRR: current rate 15, txcnt=37, retrycnt=2 Sep 7 13:51:55 kernel: wlan0: [] AMRR: current rate 15, txcnt=37, retrycnt=6 Sep 7 13:51:55 kernel: wlan0: [] AMRR: current rate 15, txcnt=34, retrycnt=1 Sep 7 13:51:56 kernel: wlan0: [] AMRR: current rate 15, txcnt=38, retrycnt=8 Sep 7 13:51:56 kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=2 Sep 7 13:51:57 kernel: wlan0: [] AMRR: current rate 15, txcnt=39, retrycnt=5 Sep 7 13:51:57 kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=10 Sep 7 13:51:58 kernel: wlan0: [] AMRR: current rate 15, txcnt=38, retrycnt=20 Sep 7 13:51:58 kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=38 retrycnt=20) Sep 7 13:51:58 kernel: wlan0: [] AMRR: current rate 14, txcnt=38, retrycnt=5 Sep 7 13:51:59 kernel: wlan0: [] AMRR: current rate 14, txcnt=35, retrycnt=4 Sep 7 13:51:59 kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=6 Sep 7 13:52:00 kernel: wlan0: [] AMRR: current rate 14, txcnt=32, retrycnt=1 Sep 7 13:52:00 kernel: wlan0: [] AMRR increasing rate 15 (txcnt=32 retrycnt=1) Sep 7 13:52:00 kernel: wlan0: [] AMRR: current rate 15, txcnt=31, retrycnt=12 Sep 7 13:52:00 kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=31 retrycnt=12) Sep 7 13:52:01 kernel: wlan0: [] AMRR: current rate 14, txcnt=36, retrycnt=3 Sep 7 13:52:01 kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=6 Sep 7 13:52:02 kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=5 Sep 7 13:52:02 kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=6 Sep 7 13:52:03 kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=5 Sep 7 13:52:03 kernel: wlan0: [] AMRR: current rate 14, txcnt=35, retrycnt=8 Sep 7 13:52:04 kernel: wlan0: [] AMRR: current rate 14, txcnt=30, retrycnt=6 Sep 7 13:52:04 kernel: wlan0: [] AMRR: current rate 14, txcnt=33, retrycnt=0 Sep 7 13:52:04 kernel: wlan0: [] AMRR increasing rate 15 (txcnt=33 retrycnt=0) Sep 7 13:52:05 kernel: wlan0: [] AMRR: current rate 15, txcnt=26, retrycnt=5 Sep 7 13:52:05 kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=12 Sep 7 13:52:05 kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=33 retrycnt=12) Sep 7 13:52:06 kernel: wlan0: [] AMRR: current rate 14, txcnt=30, retrycnt=8 Sep 7 13:52:06 kernel: wlan0: [] AMRR: current rate 14, txcnt=33, retrycnt=5 Sep 7 13:52:07 kernel: wlan0: [] AMRR: current rate 14, txcnt=27, retrycnt=2 Sep 7 13:52:07 kernel: wlan0: [] AMRR: current rate 14, txcnt=32, retrycnt=9 Sep 7 13:52:08 kernel: wlan0: [] AMRR: current rate 14, txcnt=32, retrycnt=3 Sep 7 13:52:09 kernel: wlan0: [] AMRR: current rate 14, txcnt=27, retrycnt=1 Sep 7 13:52:09 kernel: wlan0: [] AMRR increasing rate 15 (txcnt=27 retrycnt=1) Sep 7 13:52:09 kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=9 Sep 7 13:52:10 kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=8 Sep 7 13:52:10 kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=7 Sep 7 13:52:11 kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=8 Sep 7 13:52:11 kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=11 Sep 7 13:52:12 kernel: wlan0: [] AMRR: current rate 15, txcnt=31, retrycnt=11 Sep 7 13:52:12 kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=31 retrycnt=11) Sep 7 13:52:12 kernel: wlan0: [] AMRR: current rate 14, txcnt=33, retrycnt=8 Sep 7 13:52:13 kernel: wlan0: [] AMRR: current rate 14, txcnt=34, retrycnt=13 Sep 7 13:52:13 kernel: wlan0: [] AMRR decreasing rate 13 (txcnt=34 retrycnt=13) Sep 7 13:52:13 kernel: wlan0: [] AMRR: current rate 13, txcnt=37, retrycnt=13 Sep 7 13:52:13 kernel: wlan0: [] AMRR decreasing rate 12 (txcnt=37 retrycnt=13) Sep 7 13:52:14 kernel: wlan0: [] AMRR: current rate 12, txcnt=39, retrycnt=19 Sep 7 13:52:14 kernel: wlan0: [] AMRR decreasing rate 11 (txcnt=39 retrycnt=19) Sep 7 13:52:14 kernel: wlan0: [] AMRR: current rate 11, txcnt=26, retrycnt=32 Sep 7 13:52:14 kernel: wlan0: [] AMRR decreasing rate 10 (txcnt=26 retrycnt=32) Sep 7 13:52:15 kernel: wlan0: [] AMRR: current rate 10, txcnt=33, retrycnt=6 Sep 7 13:52:15 kernel: wlan0: [] AMRR: current rate 10, txcnt=33, retrycnt=1 Sep 7 13:52:15 kernel: wlan0: [] AMRR increasing rate 11 (txcnt=33 retrycnt=1) Sep 7 13:52:16 kernel: wlan0: [] AMRR: current rate 11, txcnt=34, retrycnt=0 Sep 7 13:52:16 kernel: wlan0: [] AMRR increasing rate 12 (txcnt=34 retrycnt=0) Sep 7 13:52:16 kernel: wlan0: [] AMRR: current rate 12, txcnt=32, retrycnt=7 Sep 7 13:52:17 kernel: wlan0: [] AMRR: current rate 12, txcnt=31, retrycnt=2 Sep 7 13:52:17 kernel: wlan0: [] AMRR increasing rate 13 (txcnt=31 retrycnt=2) Sep 7 13:52:17 kernel: wlan0: [] AMRR: current rate 13, txcnt=32, retrycnt=1 Sep 7 13:52:17 kernel: wlan0: [] AMRR increasing rate 14 (txcnt=32 retrycnt=1) Sep 7 13:52:18 kernel: wlan0: [] AMRR: current rate 14, txcnt=28, retrycnt=2 Sep 7 13:52:18 kernel: wlan0: [] AMRR: current rate 14, txcnt=33, retrycnt=0 Sep 7 13:52:18 kernel: wlan0: [] AMRR increasing rate 15 (txcnt=33 retrycnt=0) Sep 7 13:52:19 kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=5 Sep 7 13:52:19 kernel: wlan0: [] AMRR: current rate 15, txcnt=30, retrycnt=9 Sep 7 13:52:20 kernel: wlan0: [] AMRR: current rate 15, txcnt=30, retrycnt=6 Sep 7 13:52:20 kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=6 Sep 7 13:52:21 kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=3 Sep 7 13:52:21 kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=9 Sep 7 13:52:22 kernel: wlan0: [] AMRR: current rate 15, txcnt=26, retrycnt=6 Sep 7 13:52:22 kernel: wlan0: [] AMRR: current rate 15, txcnt=30, retrycnt=10 Sep 7 13:52:23 kernel: wlan0: [] AMRR: current rate 15, txcnt=32, retrycnt=9 Sep 7 13:52:24 kernel: wlan0: [] AMRR: current rate 15, txcnt=33, retrycnt=10 Sep 7 13:52:24 kernel: wlan0: [] AMRR: current rate 15, txcnt=30, retrycnt=6 Sep 7 13:52:25 kernel: wlan0: [] AMRR: current rate 15, txcnt=31, retrycnt=4 Sep 7 13:52:25 kernel: wlan0: [] AMRR: current rate 15, txcnt=17, retrycnt=15 Sep 7 13:52:25 kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=17 retrycnt=15) Sep 7 13:52:30 kernel: wlan0: [] AMRR: current rate 14, txcnt=11, retrycnt=0 Sep 7 13:52:30 kernel: wlan0: [] AMRR increasing rate 15 (txcnt=11 retrycnt=0) Sep 7 13:52:31 kernel: wlan0: [] AMRR: current rate 15, txcnt=17, retrycnt=6 Sep 7 13:52:31 kernel: wlan0: [] AMRR decreasing rate 14 (txcnt=17 retrycnt=6) Sep 7 13:52:31 kernel: wlan0: [] AMRR: current rate 14, txcnt=56, retrycnt=2 Sep 7 13:52:31 kernel: wlan0: [] AMRR increasing rate 15 (txcnt=56 retrycnt=2) Anything else? :-) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 14:37:05 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A22F11FA for ; Sun, 7 Sep 2014 14:37:05 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 895DD1D65 for ; Sun, 7 Sep 2014 14:37:05 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s87Eb5uj091950 for ; Sun, 7 Sep 2014 14:37:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sun, 07 Sep 2014 14:37:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lme@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 07 Sep 2014 14:37:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 Lars Engels changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lme@FreeBSD.org --- Comment #24 from Lars Engels --- To jump in: I'm not having problems on yesterday's HEAD using an 6205: ubuntu-14.04.1-server-amd64.iso 6.4 MB/s - 195 MB of 572 MB, 59 secs left wlan0: flags=8843 metric 0 mtu 1500 ether 60:67:20:xx:xx:xx inet 192.168.0.11 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid hafenkneipe24GHz channel 1 (2412 MHz 11g ht/20) bssid c4:27:95:xx:xx:xx regdomain ETSI country DE authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 50 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme roaming MANUAL -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 15:20:12 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E978155 for ; Sun, 7 Sep 2014 15:20:12 +0000 (UTC) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EB6AA11DA for ; Sun, 7 Sep 2014 15:20:11 +0000 (UTC) Received: from zeppelin.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by d.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s87F9JnK003757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sun, 7 Sep 2014 08:09:20 -0700 Message-ID: <540C751F.6050202@freebsd.org> Date: Sun, 07 Sep 2014 08:09:19 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Issues with urtwn Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVbLfzY+ylR/gEahe2rSKQk0Dw4LVj4Ichro5CVwGBxZEF5ExuNMWKFuGNfbttur1tQQxoOrktoX1hbJZMPaTFGsYEEh/owAERc= X-Sonic-ID: C;SqgE8aA25BGVQSUo5gupew== M;hraM8aA25BGVQSUo5gupew== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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: Sun, 07 Sep 2014 15:20:12 -0000 I've been having some issues with connection stability in urtwn for several months. The usual symptom is that after some period of time the connection will apparently stall. If I'm running ping continuously, for instance, it will at some point stop receiving replies. Then, sometime later, immediately if I use the "reassociate" command in wpa_cli, the connection will fix itself and all the packets I didn't get earlier get delivered at once: hundreds of ping replies, for instance, some with time stamps minutes in the past. No data is actually lost, though. I think the issue is that the driver does not actually support powersave mode (maybe it should?) but reports to the AP that it does: > ifconfig wlan0 list sta (this is on the AP) ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 80:1f:02:cc:47:a9 1 11 11M 8.5 0 5526 55712 EPS AE RSN I don't know enough about wireless to fix this, but the AP waiting for a powersave poll and never getting one seems consistent with the problem. Is there a simple way just to disable advertising this? -Nathan From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 15:28:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE7C34B3; Sun, 7 Sep 2014 15:28:55 +0000 (UTC) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::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 A14EF12AA; Sun, 7 Sep 2014 15:28:55 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id s7so9019200qap.36 for ; Sun, 07 Sep 2014 08:28:54 -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=RaPHC7F7+uUhTfVM7ZKECSpWPaOau0y7kaA7DCbOEfI=; b=eQpFemoBFBEx/ParTQ4Do3U3197FHxV0J/F7WDMiboaaVOXgmZkRvDQICHmx3XmkxB XHuwbCLYbgVGI/rY7Ditbx5SOlk3LYq3i2bZcy/ai2E5P2QScovgz7477C7TlsXIPlKH 2oIuedmkt5NomDRZE2folOxW1MEDU/qKEQknauhE9GvK4jptn80fokhtWJUYhHucTU4A qNG8Mn1upJ5SmzBzO0HtmyLYDGpUXn1G/qxvoK0owYpaf6Qw7bei07wPt9y87m1gJ14A AZdQ89mhpD6KBkCSoOMz2jaQqtudcG+IP1RcJ8FiovRzTXA+Pc0N/zjuRtVOdaRzhUEz vasA== MIME-Version: 1.0 X-Received: by 10.140.42.17 with SMTP id b17mr22571418qga.52.1410103734851; Sun, 07 Sep 2014 08:28:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 08:28:54 -0700 (PDT) In-Reply-To: <540C751F.6050202@freebsd.org> References: <540C751F.6050202@freebsd.org> Date: Sun, 7 Sep 2014 08:28:54 -0700 X-Google-Sender-Auth: 7stEoiG1mL7pLRA1q3-NIGM5VDw 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: Sun, 07 Sep 2014 15:28:56 -0000 On 7 September 2014 08:09, Nathan Whitehorn wrote: > I've been having some issues with connection stability in urtwn for several > months. The usual symptom is that after some period of time the connection > will apparently stall. If I'm running ping continuously, for instance, it > will at some point stop receiving replies. Then, sometime later, immediately > if I use the "reassociate" command in wpa_cli, the connection will fix > itself and all the packets I didn't get earlier get delivered at once: > hundreds of ping replies, for instance, some with time stamps minutes in the > past. No data is actually lost, though. > > I think the issue is that the driver does not actually support powersave > mode (maybe it should?) but reports to the AP that it does: > >> ifconfig wlan0 list sta (this is on the AP) > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 80:1f:02:cc:47:a9 1 11 11M 8.5 0 5526 55712 EPS AE RSN > > I don't know enough about wireless to fix this, but the AP waiting for a > powersave poll and never getting one seems consistent with the problem. Is > there a simple way just to disable advertising this? When it next stalls, check ifconfig wlan0 and ifconfig urtwn0 - see if OACTIVE is set. I know iwn and ath had problems in the past where OACTIVE handling was plain broken (wasn't behind locks) and in an SMP, preemptive world things got gunked up. -a From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 17:16:14 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 DB41D331; Sun, 7 Sep 2014 17:16:14 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6FB0116D; Sun, 7 Sep 2014 17:16:14 +0000 (UTC) Received: from zeppelin.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s87HG6Cj030525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 7 Sep 2014 10:16:07 -0700 Message-ID: <540C92D6.4030106@freebsd.org> Date: Sun, 07 Sep 2014 10:16:06 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Issues with urtwn References: <540C751F.6050202@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVbof3XfFEh4wib9jDHJ4lHrScKgtqJXM07PddgtDXtJoEXBTn8nRVL8qceWfcE159BNLjsgKp5oxQcvEqerJxqpmDkAxcAYIDk= X-Sonic-ID: C;wjxEp7I25BGsREpcoK8kYw== M;Usyrp7I25BGsREpcoK8kYw== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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: Sun, 07 Sep 2014 17:16:14 -0000 On 09/07/14 08:28, Adrian Chadd wrote: > On 7 September 2014 08:09, Nathan Whitehorn wrote: >> I've been having some issues with connection stability in urtwn for several >> months. The usual symptom is that after some period of time the connection >> will apparently stall. If I'm running ping continuously, for instance, it >> will at some point stop receiving replies. Then, sometime later, immediately >> if I use the "reassociate" command in wpa_cli, the connection will fix >> itself and all the packets I didn't get earlier get delivered at once: >> hundreds of ping replies, for instance, some with time stamps minutes in the >> past. No data is actually lost, though. >> >> I think the issue is that the driver does not actually support powersave >> mode (maybe it should?) but reports to the AP that it does: >> >>> ifconfig wlan0 list sta (this is on the AP) >> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> 80:1f:02:cc:47:a9 1 11 11M 8.5 0 5526 55712 EPS AE RSN >> >> I don't know enough about wireless to fix this, but the AP waiting for a >> powersave poll and never getting one seems consistent with the problem. Is >> there a simple way just to disable advertising this? > When it next stalls, check ifconfig wlan0 and ifconfig urtwn0 - see if > OACTIVE is set. > > I know iwn and ath had problems in the past where OACTIVE handling was > plain broken (wasn't behind locks) and in an SMP, preemptive world > things got gunked up. > OACTIVE is not set when it stalls. It also appears that only the RX path is stalled: transmitted packets make it, at least some of the time, to their destination when this happens. -Nathan From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 18:51:31 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 891D3943; Sun, 7 Sep 2014 18:51:31 +0000 (UTC) Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) (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 39AE31DA3; Sun, 7 Sep 2014 18:51:31 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id x12so12975554qac.20 for ; Sun, 07 Sep 2014 11:51:30 -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=tTCxlJ0v+LrPJc0HEo5cBEP1o1/lXHR8C9w5tjCVjmo=; b=rZyV4y5//zYdMw9XIPrRXFx6SHdL3oUSvRuYNYc+oTymJC1+Hc/2nkIuELFrYHnmhE vh/Vf+xaqxHVZqjvFAirh6MZdN8u0pMSHRKWZWVCTLj93tftD+ZBvW073vPIoUn3NRSy AjeQnaAWFKGNSiLJ9HvIv3kaATRHsjKeBpDudKaIaTbl+8mM8XoQcpIYPn7j/cEi3ViO qgAWLOiY6YBbV2NVRt20ZWJft+Ltxs6+n94EO305pHXfP1uTdIsa7dcI2oDGNfZrOiIs /yOywRYgAkSUxNYnMLGqVk3np+hwm+8SSEo9G8NFTHHSsXsHis1iXqlKSuUDTwV70ouu tMmA== MIME-Version: 1.0 X-Received: by 10.224.75.73 with SMTP id x9mr35944093qaj.63.1410115890241; Sun, 07 Sep 2014 11:51:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 11:51:30 -0700 (PDT) In-Reply-To: <540C92D6.4030106@freebsd.org> References: <540C751F.6050202@freebsd.org> <540C92D6.4030106@freebsd.org> Date: Sun, 7 Sep 2014 11:51:30 -0700 X-Google-Sender-Auth: ax_wsnmM6q1ar0gGhAb-uJRNq10 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: Sun, 07 Sep 2014 18:51:31 -0000 Ok. Try disabling bgscan. ifconfig wlan0 -bgscan -a From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 19:34:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 10BB44FD; Sun, 7 Sep 2014 19:34:30 +0000 (UTC) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (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 BD43711EE; Sun, 7 Sep 2014 19:34:29 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id uy5so10203452obc.32 for ; Sun, 07 Sep 2014 12:34:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Hgut8GQCLF11rwMghkN85WFLcffoqsH2dMrixApVlm4=; b=TUWKADc6nX1YsYO1dfN96+Z68wnVfn+Dxm6jylgYtzdzzDju4i1fSiTTgzmQ9hTB+z AlOyxmtwEIcZ5uNsSjOsBp6N8J+slvLaNZh3a0YSTIoz1LN9tTzKhN4QWe74x/fbwuS5 VeViBD4977Qd79LeAt7b+ATUrEMFil0mfrydiS/LoxkZWH7TMM7jb/94smarO7dWIqHY p8PBbNfCNGdy4s1NhQbbj9sFCsTWVyiJ0ekwCsbVf3R8bwKvQK9kH2/riPs1TorhDa5G ZovSzkqWKnoowK5yGAX0arT9HzfZYzBfixxiVPdsmjBVz9IEnbaeBbFndO0RdrFFaLYJ /bqw== MIME-Version: 1.0 X-Received: by 10.182.60.232 with SMTP id k8mr26539208obr.54.1410118469021; Sun, 07 Sep 2014 12:34:29 -0700 (PDT) Received: by 10.182.28.100 with HTTP; Sun, 7 Sep 2014 12:34:28 -0700 (PDT) In-Reply-To: References: Date: Sun, 7 Sep 2014 21:34:28 +0200 Message-ID: Subject: Re: Intel Centrino Wireless-N 2230 status From: Oliver Pinter To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 07 Sep 2014 19:34:30 -0000 I think no. I'm running with this settings: iwn0: flags=8843 metric 0 mtu 2290 ether 60:6c:66:7b:af:75 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 60:6c:66:7b:af:75 inet 10.0.0.102 netmask 0xffffff00 broadcast 10.0.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g status: associated ssid hellooo channel 3 (2422 MHz 11g) bssid c0:4a:00:ea:5a:ea regdomain ETSI country HU authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme roaming MANUAL And these lines are in rc.conf in working case: wlans_iwn0="wlan0" ifconfig_wlan0="WPA NOSYNCDHCP country HU -powersave -ht" and these in not working case: wlans_iwn0="wlan0" ifconfig_wlan0="WPA NOSYNCDHCP country HU -powersave" On 9/5/14, Adrian Chadd wrote: > Also, do you run this with -bgscan ? > > > -a > > > On 5 September 2014 12:26, Adrian Chadd wrote: >> Hi! >> >> This is just an iwn panic. Did your actual -HEAD kernel panic? >> >> Try doing this with sysctl dev.iwn.0.debug=0xff; let's see what >> happens just before the firmware loses its mind. >> >> Thanks! >> >> >> -a >> >> >> On 5 September 2014 12:22, Oliver Pinter wrote: >>> I got the attached iwn panic, even if running in -ht mode. In between >>> I have a working connection. >>> I set up now a serial console and try to enable the ht mode with >>> debugging. >>> >>> On 9/3/14, Oliver Pinter wrote: >>>> Or not, I forgot the -ht option in rc.conf. >>>> >>>> G STA + G AP = ok >>>> G STA + N AP = ok >>>> N STA + N AP = fail >>>> >>>> On 9/3/14, Oliver Pinter wrote: >>>>> Hi! >>>>> >>>>> Small status update: >>>>> The mode N works too, I mistyped the other AP's passwork. >>>>> So both mode G and mode N working after the backports. >>>>> >>>>> BTW, can you MFC the same changes to 10.1? >>>>> >>>>> On 9/2/14, Adrian Chadd wrote: >>>>>> Hi, >>>>>> >>>>>> Compile it with IWN_DEBUG, then >>>>>> >>>>>> sysctl dev.iwn.0.debug=0x1 >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 2 September 2014 12:41, Oliver Pinter >>>>>> wrote: >>>>>>> I not tried freebsd-head yet, but I'm able today. In mode N seems >>>>>>> like >>>>>>> the NIC sends only one frame, and no more. >>>>>>> >>>>>>> With tcpdump and/or wlandebug I see only rx packets and no tx. >>>>>>> >>>>>>> If you add some pointer what changes must I create to easier debug, >>>>>>> or >>>>>>> what concrete information required, feel free to ping me or send the >>>>>>> details. >>>>>>> >>>>>>> On 9/2/14, Adrian Chadd wrote: >>>>>>>> Cool! Have you tried freebsd-head? Does it work there? >>>>>>>> >>>>>>>> How's it failing in association state? What's it saying? >>>>>>>> >>>>>>>> >>>>>>>> -a >>>>>>>> >>>>>>>> >>>>>>>> On 2 September 2014 12:30, Oliver Pinter >>>>>>>> wrote: >>>>>>>>> Hi All! >>>>>>>>> >>>>>>>>> After I backported all of the net80211 and iwn changes from >>>>>>>>> 11-CURRENT >>>>>>>>> to 10-STABLE the wireless NIC in subject working on mode G. If I >>>>>>>>> try >>>>>>>>> to use with mode N (ht20, ht40) it failed in association state. >>>>>>>>> >>>>>>>>> All of the backports are in this github repo: >>>>>>>>> >>>>>>>>> https://github.com/opntr/opBSD/commits/op/stable/10-iwn-backport >>>>>>>>> >>>>>>>>> Oliver >>>>>>>> >>>>>> >>>>> >>>> > From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 20:51:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14B4C879; Sun, 7 Sep 2014 20:51:10 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EDA841AAB; Sun, 7 Sep 2014 20:51:09 +0000 (UTC) Received: from zeppelin.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s87Kp6x0015392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 7 Sep 2014 13:51:07 -0700 Message-ID: <540CC53A.90600@freebsd.org> Date: Sun, 07 Sep 2014 13:51:06 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Issues with urtwn References: <540C751F.6050202@freebsd.org> <540C92D6.4030106@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVZSmVT986Bj+91UgYNtNGG/P+u7/pIWUcArQmHgNy5NpLtIRP+jODIi/w20MRZ0UDgOUsLN3LxyllLP5b01MGNbJ58vOTlzNQk= X-Sonic-ID: C;rOh8sNA25BGkq0pcoK8kYw== M;4DrYsNA25BGkq0pcoK8kYw== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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: Sun, 07 Sep 2014 20:51:10 -0000 Also does not help. I also tried various other things like forcing 11b or 11g mode, all of which made no difference. -Nathan On 09/07/14 11:51, Adrian Chadd wrote: > Ok. Try disabling bgscan. > > ifconfig wlan0 -bgscan > > > > -a > From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 21:07:47 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16212E20; Sun, 7 Sep 2014 21:07:47 +0000 (UTC) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (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 B9D8C1C52; Sun, 7 Sep 2014 21:07:46 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id dc16so9267044qab.15 for ; Sun, 07 Sep 2014 14:07:45 -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=kki583p8SW1AujYx72p8m2zF0NZhR5sOrsQJmgRwosM=; b=LQEkQpeG5Qzhi2Wm87XyL8uP0txuBZcdFi+3xqxWluo/VB45yeWH1ZcmAKFmmTEEty u1bIX0mUT5bDNPuw6jIVxjv6eWa3sikDkvtY9hZ/NoPNeoT75dVb8YJr16RfAdMKNrsF En/zKEQSHVyBgGroJiWEIPrM18cROYSHLpBGAtZYMEsLqI649dTtdTAVXGQq04R1WyIQ +lrU6WLV2P34Cv6KGB62GhHIzdJ6NREOApJMSy8Mo81Lb+OONBojWw15PVDCMvqjg0SI fesQ3lvijFaPXOwjj1urDpBanfpmLZgaQ6zkCsC3PVifY7zntRtGQT9J4+YBSk/NII2z WEMQ== MIME-Version: 1.0 X-Received: by 10.140.104.69 with SMTP id z63mr34995865qge.81.1410124065847; Sun, 07 Sep 2014 14:07:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 14:07:45 -0700 (PDT) In-Reply-To: <540CC53A.90600@freebsd.org> References: <540C751F.6050202@freebsd.org> <540C92D6.4030106@freebsd.org> <540CC53A.90600@freebsd.org> Date: Sun, 7 Sep 2014 14:07:45 -0700 X-Google-Sender-Auth: PXAvKohbvl5ayc7iaG2bhHox64Q 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: Sun, 07 Sep 2014 21:07:47 -0000 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 From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 02:16:57 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D4AC783; Mon, 8 Sep 2014 02:16:57 +0000 (UTC) Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (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 F32311AB8; Mon, 8 Sep 2014 02:16:56 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id m8so10434177obr.11 for ; Sun, 07 Sep 2014 19:16:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5oqc+c2LPjuCq+MpK0Ck0Tz7bP7kdpmDSAZGc/OAlhQ=; b=Qu+HhBv+SxRaQZn9XlFCDlak5XIZ2cmPP/d0B86N6o0OWictvprEqrRIyRiauf9rxI Tqx9U8kJr1VygtXc9qPHVKz4D5kn4Uf2g727TU6ADmt2zKQ1U/pwYS2Z4RVKqBuZnOl2 d9hsZ1zkheJ+tMa9N0H+cEcntj3ByxNuj0OnFdQCwnv9jD0Ukv5+Q4ioEME8jTxrCWoo 69N3nXK4uq1dEVv0KiJqQBo7do3ReCHGPfbk5/yIvDeLWjWxZJb7QejBuVa0IjSswHpN //crTkegX0nS7FJfZd1BuUThZTBW63U3AYimYxNkUDUS/NPgHkgho25LMvKLfLIGvij7 +GLQ== MIME-Version: 1.0 X-Received: by 10.60.130.170 with SMTP id of10mr29449795oeb.10.1410142616260; Sun, 07 Sep 2014 19:16:56 -0700 (PDT) Received: by 10.202.82.84 with HTTP; Sun, 7 Sep 2014 19:16:56 -0700 (PDT) In-Reply-To: <540C751F.6050202@freebsd.org> References: <540C751F.6050202@freebsd.org> Date: Sun, 7 Sep 2014 23:16:56 -0300 Message-ID: Subject: Re: Issues with urtwn From: Thiago Farina 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 02:16:57 -0000 On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn wrote: > I've been having some issues with connection stability in urtwn for several > months. The usual symptom is that after some period of time the connection > will apparently stall. If I'm running ping continuously, for instance, it > will at some point stop receiving replies. Then, sometime later, immediately > if I use the "reassociate" command in wpa_cli, the connection will fix > itself and all the packets I didn't get earlier get delivered at once: > hundreds of ping replies, for instance, some with time stamps minutes in the > past. No data is actually lost, though. > > I think the issue is that the driver does not actually support powersave > mode (maybe it should?) but reports to the AP that it does: > >> ifconfig wlan0 list sta (this is on the AP) > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 80:1f:02:cc:47:a9 1 11 11M 8.5 0 5526 55712 EPS AE RSN > > I don't know enough about wireless to fix this, but the AP waiting for a > powersave poll and never getting one seems consistent with the problem. I think what you are relating here is what I observed recently too. Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed that after I left it idle (I went to do something for some hours) for some time it lost the connection. Only rebooting makes it connect again to my network. -- Thiago Farina From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 02:36:29 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 1BF5BCF9; Mon, 8 Sep 2014 02:36:29 +0000 (UTC) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (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 C17C61C6D; Mon, 8 Sep 2014 02:36:28 +0000 (UTC) Received: by mail-qg0-f53.google.com with SMTP id z107so14659439qgd.12 for ; Sun, 07 Sep 2014 19:36:27 -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=eZTc6aLBqDVx0RQY9GMPwATxEZKN/1bI8MhT1NXCic0=; b=x7Y12y0IOtsPKyv22vYzuUQxLZ+NUzikcTEDDThBLov7WLCChkF8+jCDrdAbupsE+q Mr87jeV/Mky63vzl63u+fXulLIjoWnqiPllG4AZ2io1KApDja65Ti3CyYkXpXjE4RGfV 8qr7VMPzzUucLbfhebfKcGO1p6kufculFV9rW3Hjksa/v2P42SE8J8l7Gv/e4UL2fm7w G2puiJZxYht9khJi/TufUyavmv+CdXwnZo0wh1lc+h7MaohDxxN9IN7jg7yzj3WyiYAn IAYUWNKwmSuKY92utY+p1Z/rDL6vFIr9oYRY75euEsumX2aV8g4K2rWhk+dnr+1rUae9 uXCQ== MIME-Version: 1.0 X-Received: by 10.140.22.19 with SMTP id 19mr22710566qgm.18.1410143787575; Sun, 07 Sep 2014 19:36:27 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 19:36:27 -0700 (PDT) In-Reply-To: References: <540C751F.6050202@freebsd.org> Date: Sun, 7 Sep 2014 19:36:27 -0700 X-Google-Sender-Auth: ZneARv_stxhZMbKv73KbUwS7ITM Message-ID: Subject: Re: Issues with urtwn From: Adrian Chadd To: Thiago Farina Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , Nathan Whitehorn 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 02:36:29 -0000 Hi, On 7 September 2014 19:16, Thiago Farina wrote: > On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn > wrote: >> I've been having some issues with connection stability in urtwn for several >> months. The usual symptom is that after some period of time the connection >> will apparently stall. If I'm running ping continuously, for instance, it >> will at some point stop receiving replies. Then, sometime later, immediately >> if I use the "reassociate" command in wpa_cli, the connection will fix >> itself and all the packets I didn't get earlier get delivered at once: >> hundreds of ping replies, for instance, some with time stamps minutes in the >> past. No data is actually lost, though. >> >> I think the issue is that the driver does not actually support powersave >> mode (maybe it should?) but reports to the AP that it does: >> >>> ifconfig wlan0 list sta (this is on the AP) >> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> 80:1f:02:cc:47:a9 1 11 11M 8.5 0 5526 55712 EPS AE RSN >> >> I don't know enough about wireless to fix this, but the AP waiting for a >> powersave poll and never getting one seems consistent with the problem. > > I think what you are relating here is what I observed recently too. > Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed > that after I left it idle (I went to do something for some hours) for > some time it lost the connection. Only rebooting makes it connect > again to my network. Which NIC are you seeing this on? I don't have this problem with Intel/Atheros chips on freebsd-head. -a From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 05:47:42 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 43227693; Mon, 8 Sep 2014 05:47:42 +0000 (UTC) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 02E591857; Mon, 8 Sep 2014 05:47:41 +0000 (UTC) Received: from [89.204.138.77] (helo=tiny-r269739) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XQrnc-0001FU-Jd; Mon, 08 Sep 2014 07:47:38 +0200 Date: Mon, 8 Sep 2014 07:47:34 +0200 From: Matthias Apitz To: Adrian Chadd Subject: Re: Issues with urtwn Message-ID: <20140908054658.GA1349@tiny-r269739> Reply-To: Matthias Apitz References: <540C751F.6050202@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.138.77 Cc: "freebsd-wireless@freebsd.org" , Nathan Whitehorn 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 05:47:42 -0000 El día Sunday, September 07, 2014 a las 07:36:27PM -0700, Adrian Chadd escribió: > > I think what you are relating here is what I observed recently too. > > Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed > > that after I left it idle (I went to do something for some hours) for > > some time it lost the connection. Only rebooting makes it connect > > again to my network. > > Which NIC are you seeing this on? Hi, I do not know if this helps. I adquired some weeks ago a small USB adapter which presents itself in HEAD as: ugen4.4: at usbus4 urtwn0: on usbus4 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R wlan0: Ethernet address: 80:1f:02:ee:16:37 I have no problems at all at my home AP (doing WPA PSK). The 'dongle' is very small, only 5-6mm are looking out of the laptop after you plug it in. The 6 euro investment ended all my searches to get the laptop's Broadcom BCM4312 working. I only encountered one problem while traveling through Italy in a hotel: They gave me a piece of paper saying "Password: "N@tur%Wieser" and I could not construct a good /etc/wpa_supplicant.conf to connect correctly. I could figure out the SSID of the AP ("Naturhotel Wieserhof") and tried a lot of network={ ... } settings, nothing worked. Sometimes I could associate and got an IP addr from the AP, but only in places where the hotel said it should not work (im my room). In places where it should work (in the lobby) I could not even associate. I have a lot of wpa_supplicant debug if someone is willing to check for details. At the end I was frustated and gave up, more frustated due to the fact that all the other clients with their stupid smartphones did not have had any problem at all :-( matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 06:21:11 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 D3563CD3; Mon, 8 Sep 2014 06:21:11 +0000 (UTC) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) (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 7EB641B0C; Mon, 8 Sep 2014 06:21:11 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id cm18so13348113qab.37 for ; Sun, 07 Sep 2014 23:21:10 -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=2teQV2OkxzV3td5GDMt5RlrOmGJtezGccEibuNER6Fs=; b=PdYhv/WBu5fTvH6j3MaRcljF6JOfvQP14nUNHKUUdwFaZO2/2MeKAXL/oWq7VCzoDU kbQn7IJTEkNIXmSbamr9WSp3daXeIrD617ZBYOoF405Wc/CeN/Wp+y4YMZbL52mXsp1V qc6FJb8Q8m+YE00hFdxdz9adBJn5/mC23kpPLOCM6gfgsVg5CYjRYzUajB7xvNyjAlkv i9Fmc1ysW2g8sawDINbSBKi7Ti9VRSpvj/7dDTt8OZHIho61ddLeuYWBXevSaWoL7oG+ ePp9m4ZNjzy7LkdYhWqEf7d8DJWX749lzCGn9nbrSdmUV1GKF+TuXV99IY2v0dO3CHXV Q26g== MIME-Version: 1.0 X-Received: by 10.140.42.17 with SMTP id b17mr26522677qga.52.1410157270624; Sun, 07 Sep 2014 23:21:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 23:21:10 -0700 (PDT) Received: by 10.224.39.139 with HTTP; Sun, 7 Sep 2014 23:21:10 -0700 (PDT) In-Reply-To: <20140908054658.GA1349@tiny-r269739> References: <540C751F.6050202@freebsd.org> <20140908054658.GA1349@tiny-r269739> Date: Sun, 7 Sep 2014 23:21:10 -0700 X-Google-Sender-Auth: ZtL_QJW1dLK1kFToNjQ1z5hOYDk Message-ID: Subject: Re: Issues with urtwn From: Adrian Chadd To: Matthias Apitz Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org, Nathan Whitehorn 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 06:21:11 -0000 Please file PR entries for each of the problems you're seeing. I don't use the USB devices and I have my hands full with the atheros and Intel stuff as it is. Thanks! Adriabln On Sep 7, 2014 10:47 PM, "Matthias Apitz" wrote: > El d=C3=ADa Sunday, September 07, 2014 a las 07:36:27PM -0700, Adrian Cha= dd > escribi=C3=B3: > > > > I think what you are relating here is what I observed recently too. > > > Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed > > > that after I left it idle (I went to do something for some hours) for > > > some time it lost the connection. Only rebooting makes it connect > > > again to my network. > > > > Which NIC are you seeing this on? > > Hi, > > I do not know if this helps. I adquired some weeks ago a small USB > adapter which presents itself in HEAD as: > > ugen4.4: at usbus4 > urtwn0: > on usbus4 > urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R > wlan0: Ethernet address: 80:1f:02:ee:16:37 > > I have no problems at all at my home AP (doing WPA PSK). The 'dongle' is > very small, only 5-6mm are looking out of the laptop after you plug it > in. The 6 euro investment ended all my searches to get the laptop's > Broadcom BCM4312 working. > > I only encountered one problem while traveling through Italy in a hotel: > They gave me a piece of paper saying "Password: "N@tur%Wieser" and I > could not construct a good /etc/wpa_supplicant.conf to connect > correctly. I could figure out the SSID of the AP ("Naturhotel Wieserhof") > and tried a lot of network=3D{ ... } settings, nothing worked. Sometimes > I could associate and got an IP addr from the AP, but only in places > where the hotel said it should not work (im my room). In places where it > should work (in the lobby) I could not even associate. I have a lot of > wpa_supplicant debug if someone is willing to check for details. At the > end I was frustated and gave up, more frustated due to the fact that all > the other clients with their stupid smartphones did not have had any > problem at all :-( > > matthias > -- > Matthias Apitz | /"\ ASCII Ribbon Campaign: > E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail > WWW: http://www.unixarea.de/ | X - No proprietary attachments > phone: +49-170-4527211 | / \ - Respect for open standards > | en.wikipedia.org/wiki/ASCII_Ribbon_Campaig= n > From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 06:29:19 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 51FACE53 for ; Mon, 8 Sep 2014 06:29:19 +0000 (UTC) Received: from srv.netng.org (srv.netng.org [185.34.0.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0EB951C00 for ; Mon, 8 Sep 2014 06:29:18 +0000 (UTC) Received: by srv.netng.org (Postfix, from userid 58) id 50B73F1996; Mon, 8 Sep 2014 02:20:11 -0400 (EDT) Received: from planb.g3.netng.org (unknown [188.175.210.2]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by srv.netng.org (Postfix) with ESMTPSA id 26924F1877; Mon, 8 Sep 2014 02:20:09 -0400 (EDT) Date: Mon, 8 Sep 2014 08:19:45 +0200 From: Vladimir Botka To: Matthias Apitz Subject: Re: Issues with urtwn Message-ID: <20140908081945.23015a99@planb.g3.netng.org> In-Reply-To: <20140908054658.GA1349@tiny-r269739> References: <540C751F.6050202@freebsd.org> <20140908054658.GA1349@tiny-r269739> Organization: na X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.23; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/n9/4FgzbxZjUPHowHkCnT+7"; protocol="application/pgp-signature" 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 06:29:19 -0000 --Sig_/n9/4FgzbxZjUPHowHkCnT+7 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Matthias, On Mon, 8 Sep 2014 07:47:34 +0200 Matthias Apitz wrote: > [...] > I only encountered one problem while traveling through Italy in a > hotel: They gave me a piece of paper saying "Password: > "N@tur%Wieser" and I could not construct a > good /etc/wpa_supplicant.conf to connect correctly. I could figure > out the SSID of the AP ("Naturhotel Wieserhof") and tried a lot of > network=3D{ ... } settings, nothing worked. Sometimes I could associate > and got an IP addr from the AP, but only in places where the hotel > said it should not work (im my room). In places where it should work > (in the lobby) I could not even associate. I have a lot of > wpa_supplicant debug if someone is willing to check for details. At > the end I was frustated and gave up, more frustated due to the fact > that all the other clients with their stupid smartphones did not have > had any problem at all :-( >=20 > matthias maybe the wpa_passphrase utility could help you to create the config. In this particular case: $ wpa_passphrase "Naturhotel Wieserhof" "N@tur%Wieser" network=3D{ ssid=3D"Naturhotel Wieserhof" #psk=3D"N@tur%Wieser" psk=3Db853709a9edcd50edf0835f68bf099255cb32fc462e492117fe3c42ab2a38= 7cb } ,or you might want to try wpa_gui. Cheers, -vlado --Sig_/n9/4FgzbxZjUPHowHkCnT+7 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUDUqBAAoJEKzxHYF8kx9kPxEH/3hcjHKOPTqozYuWjpOGBf+t 2s5AOSgFYUInB1gYu5K3sttBxn596pbksPjygYRMKHOgkV1J6RmjKw6GeVfqMneE xq2GttwTxJ3+pPkETof25nP8o01obfK76Gj7+mzbnywvLlzg0GSknDcO+BB2fkVg +f34vydcrubQsu7gMT9bgy4gzdqEDHdEkHoBOrSp/7P9U/ATYBe9giXNLQIPr3cZ B/kvGLKcbONTqp08nBlpesnfT9+7KiVhpjeaZ7/vVF55pgRGXzzKNhZGMsR+jvEQ giQmsV7gXpDeycRbJGQPbKeHBONhxb6LWBlw5Cro2f6HMazquQMLvfUz/x5ihTk= =1IMp -----END PGP SIGNATURE----- --Sig_/n9/4FgzbxZjUPHowHkCnT+7-- From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 06:41:28 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BF52F24 for ; Mon, 8 Sep 2014 06:41:28 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 333E31D47 for ; Mon, 8 Sep 2014 06:41:28 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s886fSRa089367 for ; Mon, 8 Sep 2014 06:41:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Mon, 08 Sep 2014 06:41:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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 06:41:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 --- Comment #25 from Hiren Panchasara --- wow, I so envy you guys :-) I've a similar setting but not getting anything more than 400kbps. So weird. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 07:32:34 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CC31829 for ; Mon, 8 Sep 2014 07:32:34 +0000 (UTC) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5CE1E122E for ; Mon, 8 Sep 2014 07:32:34 +0000 (UTC) Received: from [89.204.138.77] (helo=tiny-r269739) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XQtR8-000259-Vm; Mon, 08 Sep 2014 09:32:31 +0200 Date: Mon, 8 Sep 2014 09:32:29 +0200 From: Matthias Apitz To: Vladimir Botka Subject: Re: Issues with urtwn Message-ID: <20140908073229.GA1766@tiny-r269739> Reply-To: Matthias Apitz References: <540C751F.6050202@freebsd.org> <20140908054658.GA1349@tiny-r269739> <20140908081945.23015a99@planb.g3.netng.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20140908081945.23015a99@planb.g3.netng.org> X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.138.77 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 07:32:34 -0000 El día Monday, September 08, 2014 a las 08:19:45AM +0200, Vladimir Botka escribió: Hi Vladimir, > maybe the wpa_passphrase utility could help you to create the config. > In this particular case: > > $ wpa_passphrase "Naturhotel Wieserhof" "N@tur%Wieser" > network={ > ssid="Naturhotel Wieserhof" > #psk="N@tur%Wieser" > psk=b853709a9edcd50edf0835f68bf099255cb32fc462e492117fe3c42ab2a387cb > } What is the benefit of coding the PSK? I have never used it; the wpa_supplicant.conf file tested was: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel eapol_version=1 ap_scan=1 fast_reauth=1 # Hotel Wieserhof # network={ ssid="Naturhotel Wieserhof" scan_ssid=1 # key_mgmt=WPA-PSK WPA-EAP IEEE8021X key_mgmt=WPA-PSK # key_mgmt=WPA-PSK WPA-EAP psk="N@tur%Wieser" # key_mgmt=NONE # wep_tx_keyidx=0 # wep_key0="N@tur%Wieser" } as you see in the comments, I tested a lot of different key_mgmt= values; the one shown active, gave the best results (but only in my hotel room, not in the lobby); > ,or you might want to try wpa_gui. I have never used it, but will install the port and give it a try next time. Thx matthias PD: To Adrian, I'm willing to file a PR, but the problem is, I will not return to this hotel and can not provide more information or tests. -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 07:59:17 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 313BBF88 for ; Mon, 8 Sep 2014 07:59:17 +0000 (UTC) Received: from srv.netng.org (srv.netng.org [185.34.0.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B35641483 for ; Mon, 8 Sep 2014 07:59:16 +0000 (UTC) Received: by srv.netng.org (Postfix, from userid 58) id E2A98F1998; Mon, 8 Sep 2014 03:59:13 -0400 (EDT) Received: from planb.g3.netng.org (unknown [188.175.210.2]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by srv.netng.org (Postfix) with ESMTPSA id 9BEF4F1993; Mon, 8 Sep 2014 03:59:11 -0400 (EDT) Date: Mon, 8 Sep 2014 09:59:09 +0200 From: Vladimir Botka To: Matthias Apitz Subject: Re: Issues with urtwn Message-ID: <20140908095909.12c56bde@planb.g3.netng.org> In-Reply-To: <20140908073229.GA1766@tiny-r269739> References: <540C751F.6050202@freebsd.org> <20140908054658.GA1349@tiny-r269739> <20140908081945.23015a99@planb.g3.netng.org> <20140908073229.GA1766@tiny-r269739> Organization: na X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.23; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/q+=DhfVCdjQvuPnuuOtC2cH"; protocol="application/pgp-signature" 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 07:59:17 -0000 --Sig_/q+=DhfVCdjQvuPnuuOtC2cH Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Matthias, On Mon, 8 Sep 2014 09:32:29 +0200 Matthias Apitz wrote: > El d=C3=ADa Monday, September 08, 2014 a las 08:19:45AM +0200, Vladimir > Botka escribi=C3=B3: >=20 > Hi Vladimir, >=20 > > maybe the wpa_passphrase utility could help you to create the > > config. In this particular case: > >=20 > > $ wpa_passphrase "Naturhotel Wieserhof" "N@tur%Wieser" > > network=3D{ > > ssid=3D"Naturhotel Wieserhof" > > #psk=3D"N@tur%Wieser" > > psk=3Db853709a9edcd50edf0835f68bf099255cb32fc462e492117fe3c42ab= 2a387cb > > } >=20 > What is the benefit of coding the PSK? I have never used it; the > wpa_supplicant.conf file tested was: >=20 > ctrl_interface=3D/var/run/wpa_supplicant > ctrl_interface_group=3Dwheel > eapol_version=3D1 > ap_scan=3D1 > fast_reauth=3D1 >=20 > # Hotel Wieserhof > # > network=3D{ > ssid=3D"Naturhotel Wieserhof" > scan_ssid=3D1 > # key_mgmt=3DWPA-PSK WPA-EAP IEEE8021X > key_mgmt=3DWPA-PSK > # key_mgmt=3DWPA-PSK WPA-EAP > psk=3D"N@tur%Wieser" > # key_mgmt=3DNONE > # wep_tx_keyidx=3D0 > # wep_key0=3D"N@tur%Wieser" > } >=20 > as you see in the comments, I tested a lot of different key_mgmt=3D > values; the one shown active, gave the best results (but only in my > hotel room, not in the lobby); >=20 > > ,or you might want to try wpa_gui. >=20 > I have never used it, but will install the port and give it a try next > time. >=20 > Thx >=20 > matthias >=20 > PD: To Adrian, I'm willing to file a PR, but the problem is, I will > not return to this hotel and can not provide more information or > tests. psk=3D"N@tur%Wieser" and psk=3Db853709a9edcd50edf0835f68bf099255cb32fc462e492117fe3c42ab2a387cb are equivalent. If you have troubles to configure it manually, I recommend to try wpa_gui as a next step. In the upstream, wpa_gui is maintained together with wpa_supplicant by the same maintainer. Therefor wpa_gui has always been working fine with wpa_supplicant and might help you to create a consistent configuration. If this doesn't work, there might be a problem in the (1) lower layer (driver), (2) AP, or (3) HW in general. If so, to debug it might be a complex issue suitable for a bug entry.=20 Cheers, -vlado --Sig_/q+=DhfVCdjQvuPnuuOtC2cH Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUDWHNAAoJEKzxHYF8kx9kwO8H/3YiY0XsuzXLxIp6Dp2wa12V RxN5o5akFKVBMG550R/CFsZ/fTllt2mYoqo172Tt91HBqarbmj1Mo4zEp9LXDLUg fDDQt1ByR+Wu/UQtgyXVmC2/JRO+2NmF5l4wuQmVaigDtbe8SdTCbUWWh0eDuuOv Hls12w4jlO6f5Df/i8c70ZxAVgU6xOdr3Z85IULfCPBKuFecNzU3c6/hk6SMLl7W q8Ip3giZIhy3VEdqT4xWC8xtRxawGkKJEPUaWpHAoiXA+dQazcXUxwffqrRMu9NM xO+TCrAQA+L+UAZamRfEJCblW82oDkZxg9M1r/3CxvW4p4Vph+Xz33ZyqBxpQRg= =7WtP -----END PGP SIGNATURE----- --Sig_/q+=DhfVCdjQvuPnuuOtC2cH-- From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 08:00:18 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 B5894D1 for ; Mon, 8 Sep 2014 08:00:18 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 961D314C7 for ; Mon, 8 Sep 2014 08:00:18 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8880Iw9069286 for ; Mon, 8 Sep 2014 08:00:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201409080800.s8880Iw9069286@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 08 Sep 2014 08:00:18 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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 08:00:18 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 09:07:57 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 3D2F73BC for ; Mon, 8 Sep 2014 09:07:57 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C8B91D0C for ; Mon, 8 Sep 2014 09:07:57 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8897umM073344 for ; Mon, 8 Sep 2014 09:07:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 193458] New: can not connect reliable to Wifi AP with WPA-PSK / WPA-EAP Date: Mon, 08 Sep 2014 09:07:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: guru@unixarea.de X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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 09:07:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193458 Bug ID: 193458 Summary: can not connect reliable to Wifi AP with WPA-PSK / WPA-EAP Product: Base System Version: 11.0-CURRENT Hardware: i386 OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: guru@unixarea.de $ uname -a FreeBSD tiny-r269739 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r269739M: Fri Aug 15 18:07:41 CEST 2014 guru@vm-tiny-r269739:/usr/obj/usr/src/sys/GENERIC i386 Wifi NIC: urtwn0: on usbus4 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R wlan0: Ethernet address: 80:1f:02:ee:16:37 # cat /etc/wpa_supplicant.conf # ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel eapol_version=1 ap_scan=1 fast_reauth=1 # Hotel Wieserhof # network={ ssid="Naturhotel Wieserhof" scan_ssid=1 # key_mgmt=WPA-PSK WPA-EAP IEEE8021X key_mgmt=WPA-PSK # key_mgmt=WPA-PSK WPA-EAP psk="N@tur%Wieser" # key_mgmt=NONE # wep_tx_keyidx=0 # wep_key0="N@tur%Wieser" } note: credentials have been was by local hotel management staff as: Wi-Fi: Naturhotel Wieserhof Password: N@tur%Wieser i.e. the credentials are correct and the SSID was visible with ifconfig wlan0 list scan WPA started as: # /usr/sbin/wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant.conf -D bsd connection (associating, IP by DHCP) was only sometimes possible far away from the AP (in the hotel room, where the staff said it is not supposed to work), and was never possible near the AP (in the lobby, where it was supposed to work); I tested the various combinations, the best was what is visible above as aktive lines; I will attach log files; -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 11:06:42 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 D9B82125 for ; Mon, 8 Sep 2014 11:06:42 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0A151BCE for ; Mon, 8 Sep 2014 11:06:42 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s88B6g3S017677 for ; Mon, 8 Sep 2014 11:06:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 193458] can not connect reliable to Wifi AP with WPA-PSK / WPA-EAP Date: Mon, 08 Sep 2014 11:06:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: guru@unixarea.de X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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 11:06:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193458 --- Comment #1 from Matthias Apitz --- Created attachment 147057 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147057&action=edit wpa debug log -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 11:07:19 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 969CD210 for ; Mon, 8 Sep 2014 11:07:19 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7D5941BEE for ; Mon, 8 Sep 2014 11:07:19 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s88B7JxY019182 for ; Mon, 8 Sep 2014 11:07:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 193458] can not connect reliable to Wifi AP with WPA-PSK / WPA-EAP Date: Mon, 08 Sep 2014 11:07:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: guru@unixarea.de X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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 11:07:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193458 --- Comment #2 from Matthias Apitz --- Created attachment 147058 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147058&action=edit wpa debug log (2) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 11:30:25 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C6E188C2 for ; Mon, 8 Sep 2014 11:30:25 +0000 (UTC) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4E8E71E9E for ; Mon, 8 Sep 2014 11:30:24 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBEEB8.dip0.t-ipconnect.de [93.203.238.184]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id s88ATu6E022256; Mon, 8 Sep 2014 10:29:56 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id s88AWEsa083622; Mon, 8 Sep 2014 12:32:14 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id s88AVpDs089788; Mon, 8 Sep 2014 12:32:03 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201409081032.s88AVpDs089788@fire.js.berklix.net> To: Vladimir Botka Subject: Re: Issues with urtwn From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 08 Sep 2014 09:59:09 +0200." <20140908095909.12c56bde@planb.g3.netng.org> Date: Mon, 08 Sep 2014 12:31:51 +0200 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 11:30:25 -0000 > wpa_gui as a next step. In the upstream, wpa_gui is maintained together > with wpa_supplicant by the same maintainer. Therefor wpa_gui has always > been working fine with wpa_supplicant and might help you to create a > consistent configuration. I too have found wpa_gui useful to detect syntax errs from my wpa_supplicant.conf (& useful to know same maintainer). Matthias, a word of warning: copy wpa_supplicant.conf before you enable update_config=1 because wpa_gui will discard all lines with comments. Cheers, Julian -- Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com Interleave replies Below, like a play script. From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 15:16:55 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 1DD22F62; Mon, 8 Sep 2014 15:16:55 +0000 (UTC) Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) (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 C2AE01BE8; Mon, 8 Sep 2014 15:16:54 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id n16so10859160oag.10 for ; Mon, 08 Sep 2014 08:16:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9fW8j8o5gWwlKcukmvCZwVPZt5ZyNLtBKW0OsUq3xa0=; b=YKX4aZt10zeYS+GKXPzutu95Cbtl5pNH9fieBkWVBxWjeBqlFNiaAEkpbvbNn1F8Zt eYHTDBW4Zt0Z2g5PNGcWK94S2IpfNkpUX3S4szSmDp3BpZHvEreAysctDaMmYmp5PwSM 3Z9hNijmecNb3GcKr6P9gCbgOnrXCLIm+OhLDFctsDJBjWctNkBEgm0Xyu+3tQprPrYC ONgtb4oJHnyQskWwJDs0wewIgrzRwohlLWoyjx4eLKj4Lt3CHc8Vdw99+8Mos80sMynZ v366S6dnOoO5EIzkQuxhmw8Oaca3fUi1UIh9ZDzfGu68IYSL8epeyQpG4u6aF8qPF2EW EB2A== MIME-Version: 1.0 X-Received: by 10.182.213.7 with SMTP id no7mr32320448obc.39.1410189413906; Mon, 08 Sep 2014 08:16:53 -0700 (PDT) Received: by 10.202.82.84 with HTTP; Mon, 8 Sep 2014 08:16:53 -0700 (PDT) In-Reply-To: References: <540C751F.6050202@freebsd.org> Date: Mon, 8 Sep 2014 12:16:53 -0300 Message-ID: Subject: Re: Issues with urtwn From: Thiago Farina To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" , Nathan Whitehorn 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 15:16:55 -0000 On Sun, Sep 7, 2014 at 11:36 PM, Adrian Chadd wrote: > Hi, > > On 7 September 2014 19:16, Thiago Farina wrote: >> On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn >> wrote: >>> I've been having some issues with connection stability in urtwn for several >>> months. The usual symptom is that after some period of time the connection >>> will apparently stall. If I'm running ping continuously, for instance, it >>> will at some point stop receiving replies. Then, sometime later, immediately >>> if I use the "reassociate" command in wpa_cli, the connection will fix >>> itself and all the packets I didn't get earlier get delivered at once: >>> hundreds of ping replies, for instance, some with time stamps minutes in the >>> past. No data is actually lost, though. >>> >>> I think the issue is that the driver does not actually support powersave >>> mode (maybe it should?) but reports to the AP that it does: >>> >>>> ifconfig wlan0 list sta (this is on the AP) >>> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >>> 80:1f:02:cc:47:a9 1 11 11M 8.5 0 5526 55712 EPS AE RSN >>> >>> I don't know enough about wireless to fix this, but the AP waiting for a >>> powersave poll and never getting one seems consistent with the problem. >> >> I think what you are relating here is what I observed recently too. >> Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed >> that after I left it idle (I went to do something for some hours) for >> some time it lost the connection. Only rebooting makes it connect >> again to my network. > > Which NIC are you seeing this on? > Mine is urtwn0: Realtek RTL8187L from my Gateway laptop. -- Thiago Farina From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 8 22:14:07 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 ABA9E14C; Mon, 8 Sep 2014 22:14:07 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8A33D14CE; Mon, 8 Sep 2014 22:14:07 +0000 (UTC) Received: from zeppelin.tachypleus.net (airbears2-136-152-142-27.AirBears2.Berkeley.EDU [136.152.142.27]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s88ME58X024714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 8 Sep 2014 15:14:06 -0700 Message-ID: <540E2A2D.4090301@freebsd.org> Date: Mon, 08 Sep 2014 15:14:05 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Issues with urtwn References: <540C751F.6050202@freebsd.org> <540C92D6.4030106@freebsd.org> <540CC53A.90600@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVa/HDnxxIDUvkgMkuLbOIsNG23kc3KbQZhHqi9YQfyghNzuChxHQPSG1ZwHIWLSaRLIcA82Tx1J8xHp884LsQqTdUJo7qPzNeU= X-Sonic-ID: C;CiJdcqU35BGbT0pcoK8kYw== M;dDyccqU35BGbT0pcoK8kYw== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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:14:07 -0000 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 > 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 >> > From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 9 01:53:58 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 669B386A for ; Tue, 9 Sep 2014 01:53:58 +0000 (UTC) Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (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 1FC001741 for ; Tue, 9 Sep 2014 01:53:58 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id v10so3172278qac.4 for ; Mon, 08 Sep 2014 18:53:57 -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=zQFn4B+smV0BazTnQ7c5ZyH5Z3DWBineWCFlje6WqXU=; b=Al9lC32NzaPrMymn5h4uhivakTDyqqQ1MAUM/JVAfZJMEuDNDGqzr0NPD+9Ptjqek0 2sryl56ANuQS3hzi+4/0f3Da6t8xlC8NjS9PPUjcHoPiWCDQ+WM2LqjJFHf6aBdfyc1G UDPDtDAS4Pt0h8/rCtokK//a7bO1u14JZXmvZKFW6pJ0GeLG4pem9YyowqcsOP2BlS5H 7pDV1rHeum76eGk5yNESharhL5vrdvc5Rgsb9eWz8Z6CB+2kdt24hNT70fNkdsHu9I/0 PU2G15ywfcbIQa9ig9rkL3z1DXAL7VX0qlmu+vxV4lXHDBrEAqB+LnB3Ju/CmBijmc4q RZtw== MIME-Version: 1.0 X-Received: by 10.224.151.69 with SMTP id b5mr47500834qaw.37.1410227637134; Mon, 08 Sep 2014 18:53:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Mon, 8 Sep 2014 18:53:57 -0700 (PDT) In-Reply-To: References: Date: Mon, 8 Sep 2014 18:53:57 -0700 X-Google-Sender-Auth: tCqU92fAFiRXjwhFRR1JiXzMYd0 Message-ID: Subject: Re: Intel Centrino Wireless-N 2230 status From: Adrian Chadd To: Oliver Pinter 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: Tue, 09 Sep 2014 01:53:58 -0000 I'm not sure why yours is misbehaving. I don't ahve anything channel 3 though, that's for sure. I don't also run it in the HU country/regdomain. :) Can you try updating to the latest -HEAD and retrying? -a From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 9 04:33:55 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 87A635C2 for ; Tue, 9 Sep 2014 04:33:55 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 235E3B02 for ; Tue, 9 Sep 2014 04:33:54 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s894WMgG018634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 9 Sep 2014 12:32:22 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s894WLwP018632; Tue, 9 Sep 2014 12:32:21 +0800 (CST) (envelope-from kevlo) Date: Tue, 9 Sep 2014 12:32:21 +0800 From: Kevin Lo To: Carlos Jacobo Puga Medina Subject: Re: TP-LINK TL-WN821N Message-ID: <20140909043220.GA18621@ns.kevlo.org> References: <20140707211035.5ce0a482fe062bc1ea64ace7@fbsd.es> <20140708022220.GA87876@ns.kevlo.org> <20140708124550.c60683f2c01f3f9aa6a4ff70@fbsd.es> <20140709100229.GA6733@ns.kevlo.org> <20140709154223.9623a93c2d458dc32339b554@fbsd.es> <20140710050524.GA14437@ns.kevlo.org> <20140710112344.86496b02b2d62197a1e467ba@fbsd.es> <20140710100317.GA16286@ns.kevlo.org> <20140824180120.37f6e1018e38dc970585e61e@fbsd.es> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140824180120.37f6e1018e38dc970585e61e@fbsd.es> User-Agent: Mutt/1.5.22 (2013-10-16) 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: Tue, 09 Sep 2014 04:33:55 -0000 On Sun, Aug 24, 2014 at 06:01:20PM +0200, Carlos Jacobo Puga Medina wrote: > > Hi Kevin, Hi, Sorry for the late response. > Sometimes my wireless device fails to connect at boot, and I need to restart the system. Also it states that the device is not configured. > > /boot/loader.conf > if_urtwn_load="YES" > legal.realtek.license_ack=1 You might add the following lines to /boot/loader.conf: urtwn-rtl8192cfwT_load="YES" urtwn-rtl8192cfwU_load="YES" > It shows the following output: > > urtwn0: timeout waiting for checksum report > > Any thoughts? I thought this problem was fixed in r263154, but apparently not. Could you try this patch? Thanks Index: sys/dev/usb/wlan/if_urtwn.c =================================================================== --- sys/dev/usb/wlan/if_urtwn.c (revision 271297) +++ sys/dev/usb/wlan/if_urtwn.c (working copy) @@ -2280,8 +2280,6 @@ urtwn_fw_reset(struct urtwn_softc *sc) return; urtwn_ms_delay(sc); } - /* Force 8051 reset. */ - urtwn_write_2(sc, R92C_SYS_FUNC_EN, reg & ~R92C_SYS_FUNC_EN_CPUEN); } static void From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 9 04:34:19 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6DD155DC; Tue, 9 Sep 2014 04:34:19 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C8C05B05; Tue, 9 Sep 2014 04:34:18 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s894X5J8018667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 9 Sep 2014 12:33:06 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s894X5qE018666; Tue, 9 Sep 2014 12:33:05 +0800 (CST) (envelope-from kevlo) Date: Tue, 9 Sep 2014 12:33:04 +0800 From: Kevin Lo To: Thiago Farina Subject: Re: Issues with urtwn Message-ID: <20140909043304.GA18643@ns.kevlo.org> References: <540C751F.6050202@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-wireless@freebsd.org" , Nathan Whitehorn 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: Tue, 09 Sep 2014 04:34:19 -0000 On Mon, Sep 08, 2014 at 12:16:53PM -0300, Thiago Farina wrote: > > On Sun, Sep 7, 2014 at 11:36 PM, Adrian Chadd wrote: > > Hi, > > > > On 7 September 2014 19:16, Thiago Farina wrote: > >> On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn > >> wrote: > >>> I've been having some issues with connection stability in urtwn for several > >>> months. The usual symptom is that after some period of time the connection > >>> will apparently stall. If I'm running ping continuously, for instance, it > >>> will at some point stop receiving replies. Then, sometime later, immediately > >>> if I use the "reassociate" command in wpa_cli, the connection will fix > >>> itself and all the packets I didn't get earlier get delivered at once: > >>> hundreds of ping replies, for instance, some with time stamps minutes in the > >>> past. No data is actually lost, though. > >>> > >>> I think the issue is that the driver does not actually support powersave > >>> mode (maybe it should?) but reports to the AP that it does: > >>> > >>>> ifconfig wlan0 list sta (this is on the AP) > >>> ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >>> 80:1f:02:cc:47:a9 1 11 11M 8.5 0 5526 55712 EPS AE RSN > >>> > >>> I don't know enough about wireless to fix this, but the AP waiting for a > >>> powersave poll and never getting one seems consistent with the problem. > >> > >> I think what you are relating here is what I observed recently too. > >> Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed > >> that after I left it idle (I went to do something for some hours) for > >> some time it lost the connection. Only rebooting makes it connect > >> again to my network. > > > > Which NIC are you seeing this on? > > > Mine is urtwn0: Realtek RTL8187L from my Gateway laptop. Typo? urtw(4) supports Realtek RTL8187L, not urtwn(4). > -- > Thiago Farina Kevin From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 9 05:54:27 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08AF6100; Tue, 9 Sep 2014 05:54:27 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 472AD206; Tue, 9 Sep 2014 05:54:25 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s895rCAs018951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 9 Sep 2014 13:53:12 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s895rBDC018950; Tue, 9 Sep 2014 13:53:11 +0800 (CST) (envelope-from kevlo) Date: Tue, 9 Sep 2014 13:53:10 +0800 From: Kevin Lo To: Adrian Chadd Subject: Re: TL-WN722N support on FreeBSD. Message-ID: <20140909055310.GA18936@ns.kevlo.org> References: <20140830195721.GA12450@neutralgood.org> <5403AD08.60605@pinyon.org> <20140901105350.GJ57121@e-new.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) 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: Tue, 09 Sep 2014 05:54:27 -0000 On Mon, Sep 01, 2014 at 11:11:20AM -0700, Adrian Chadd wrote: > > The problem -is- the money. The people will come when there's enough > interest and enough money. > > The problem is that people think things like wifi drivers that are > debugged, perform well and get updated as new standards appear is a > few months effort - and I think the herculean efforts done in the past > by people like Sam fuel this myth. > > I've spent almost two years of weekends and evenings hacking on > net80211 and the atheros driver to get it to where it is. The 11n > support for atheros chips appeared when someone (hi Hobnob!) paid me > for six months to get 11n done. I'm still debugging weird corner cases > with rate control and congestion handling even now. And this is _on > top_ of all the work done by the Atheros team to write the HAL in the > first place. > > I've spent almost 18 months of weekends/evenings hacking on the intel > iwn driver to find all the little odd corner cases that make it > unusable by a lot of people. I keep saying I'm not, but since the > laptops I'm using have iwn in them, I end up getting annoyed enough to > fix it. This has all been for free. > > Wireless stuff is a very complicated, very time consuming thing that's > immensely fun if you're into this kind of thing. But please understand > - it's a huge time commitment for each individual device and new > standard. > > So yes, it's the money. I've jokingly said that it's $100k and 2 years > for me in (evenings, weekends) time and equipment to port and debug > one driver for a given NIC. Not just do a "oh look here's an openbsd > driver ported from linux in a month" port - that's just the beginning > (and I tend to quote something like $10k for that) - I mean, something > that ends up implementing the updated standards (11n, 11ac soon); > something that includes powersave, something that includes debugging, > something that handles a multitude of bad environments that people see > every day and complain about. Ie - the level of work that makes it "oh > it just works, I can get on with work now" level of work. > > I don't want to let myself be dragged into another two years of > weekends. I kind of need some sleep here and there. I can't find a reason why I disagree with you. I have almost forgotten that wifi hacking can be fun if it results in something working... > -a Kevin From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 9 06:33:33 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 63DF758E; Tue, 9 Sep 2014 06:33:33 +0000 (UTC) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (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 0DE4A7D5; Tue, 9 Sep 2014 06:33:32 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id w7so16727537qcr.4 for ; Mon, 08 Sep 2014 23:33:32 -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=Z+PUS+ISMhaE9jQEdypPVBUTYmGGpcK2ClCGntTiSwY=; b=LK35B+/7QTF8F6UPqnQXqTQgTD0euQGFrj1xsmxskdBTwHKoOqEojwSKdZB2DZbOe8 X6SXnw09FGtDM9Yq6vTQFA7u+qgZJK9s8HRzIyEJRW4YIa12rQeywNRaqv3T9EgpXSuf qxmWm7SB8wm/vd6B7YJ8G37Vb16q/ICACwMNlANIYytqgyTtszya4v/DcuY605C1A+gT EmJpy2zrmDC2bs1GcyhYsbAvRZVI1lA4tUcc2WxUAC7vnBG6AA+HqmU0KhcPD77H9/RK oIdzY70Y0/dM8hjnWD5rWXodpAqkvme/cPKvsD3Gd3GkYW/C092h9qdCBPfBcLUexrcK 6Qkw== MIME-Version: 1.0 X-Received: by 10.224.36.4 with SMTP id r4mr47998080qad.69.1410244411909; Mon, 08 Sep 2014 23:33:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Mon, 8 Sep 2014 23:33:31 -0700 (PDT) Received: by 10.224.39.139 with HTTP; Mon, 8 Sep 2014 23:33:31 -0700 (PDT) In-Reply-To: <20140909055310.GA18936@ns.kevlo.org> References: <20140830195721.GA12450@neutralgood.org> <5403AD08.60605@pinyon.org> <20140901105350.GJ57121@e-new.0x20.net> <20140909055310.GA18936@ns.kevlo.org> Date: Mon, 8 Sep 2014 23:33:31 -0700 X-Google-Sender-Auth: 0wCTCXlzzIkt_CNvfkgbzOPG-OA Message-ID: Subject: Re: TL-WN722N support on FreeBSD. From: Adrian Chadd To: Kevin Lo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Tue, 09 Sep 2014 06:33:33 -0000 Oh it is fun. :) +a On Sep 8, 2014 10:54 PM, "Kevin Lo" wrote: > On Mon, Sep 01, 2014 at 11:11:20AM -0700, Adrian Chadd wrote: > > > > The problem -is- the money. The people will come when there's enough > > interest and enough money. > > > > The problem is that people think things like wifi drivers that are > > debugged, perform well and get updated as new standards appear is a > > few months effort - and I think the herculean efforts done in the past > > by people like Sam fuel this myth. > > > > I've spent almost two years of weekends and evenings hacking on > > net80211 and the atheros driver to get it to where it is. The 11n > > support for atheros chips appeared when someone (hi Hobnob!) paid me > > for six months to get 11n done. I'm still debugging weird corner cases > > with rate control and congestion handling even now. And this is _on > > top_ of all the work done by the Atheros team to write the HAL in the > > first place. > > > > I've spent almost 18 months of weekends/evenings hacking on the intel > > iwn driver to find all the little odd corner cases that make it > > unusable by a lot of people. I keep saying I'm not, but since the > > laptops I'm using have iwn in them, I end up getting annoyed enough to > > fix it. This has all been for free. > > > > Wireless stuff is a very complicated, very time consuming thing that's > > immensely fun if you're into this kind of thing. But please understand > > - it's a huge time commitment for each individual device and new > > standard. > > > > So yes, it's the money. I've jokingly said that it's $100k and 2 years > > for me in (evenings, weekends) time and equipment to port and debug > > one driver for a given NIC. Not just do a "oh look here's an openbsd > > driver ported from linux in a month" port - that's just the beginning > > (and I tend to quote something like $10k for that) - I mean, something > > that ends up implementing the updated standards (11n, 11ac soon); > > something that includes powersave, something that includes debugging, > > something that handles a multitude of bad environments that people see > > every day and complain about. Ie - the level of work that makes it "oh > > it just works, I can get on with work now" level of work. > > > > I don't want to let myself be dragged into another two years of > > weekends. I kind of need some sleep here and there. > > I can't find a reason why I disagree with you. > I have almost forgotten that wifi hacking can be fun if it results > in something working... > > > -a > > Kevin > From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 9 08:36:25 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 30D35CAF; Tue, 9 Sep 2014 08:36:25 +0000 (UTC) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (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 DD59E2D7; Tue, 9 Sep 2014 08:36:24 +0000 (UTC) Received: by mail-ob0-f179.google.com with SMTP id uz6so11886476obc.10 for ; Tue, 09 Sep 2014 01:36:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CDiDGLOBiGN+BLu0+kLCjmLLvKFoD+0m2zu/TNqPCuQ=; b=ZEWGAJ7q1CQc9+TjBQ0Zy06ltzOAK8rBqtmyct/YUxAKhGvYLIiMc7UNJHL0ejuqnX zI6JoNy5qHNW5gMVJJe9N3XPODVWpDw1X+Six1Wv/gcdPyz35LgHYWOM6/++e1IAGgZx n7WDekfvs5bv1ldou8NxDAS6aPLO1kRG8LgD7yVW2vkr/4jEGBpGcknIHQZaanijCNk0 lolj2CPp/v9UKPYx3HSH4sZsih3EFGFU/LrkLJUr8pfiLex5YNSn+Sn499GjDcctjBZZ TKPbc1UfSBpl1CILM0SvEd7Wdb9dcjQomf0p2nqPhcCu5/q2a/iA0eTRzJBFSc3j0DgY vcCQ== MIME-Version: 1.0 X-Received: by 10.182.94.230 with SMTP id df6mr37319546obb.36.1410251784116; Tue, 09 Sep 2014 01:36:24 -0700 (PDT) Received: by 10.182.28.100 with HTTP; Tue, 9 Sep 2014 01:36:24 -0700 (PDT) In-Reply-To: References: Date: Tue, 9 Sep 2014 10:36:24 +0200 Message-ID: Subject: Re: Intel Centrino Wireless-N 2230 status From: Oliver Pinter To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 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: Tue, 09 Sep 2014 08:36:25 -0000 The channel 3 was the least used channel in the house; I'm able to change the regdomain on route, eg. to ETSI or some US or AU domain. :) Tomorrow will do. Thanks, Oliver On 9/9/14, Adrian Chadd wrote: > I'm not sure why yours is misbehaving. I don't ahve anything channel 3 > though, that's for sure. I don't also run it in the HU > country/regdomain. :) > > Can you try updating to the latest -HEAD and retrying? > > > -a > From owner-freebsd-wireless@FreeBSD.ORG Wed Sep 10 02:33:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE3392FF; Wed, 10 Sep 2014 02:33:18 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DE4ADB2; Wed, 10 Sep 2014 02:33:17 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s8A2W1rK026977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 10 Sep 2014 10:32:02 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s8A2W16R026976; Wed, 10 Sep 2014 10:32:01 +0800 (CST) (envelope-from kevlo) Date: Wed, 10 Sep 2014 10:32:01 +0800 From: Kevin Lo To: Adrian Chadd Subject: Re: TL-WN722N support on FreeBSD. Message-ID: <20140910023201.GA26967@ns.kevlo.org> References: <20140830195721.GA12450@neutralgood.org> <5403AD08.60605@pinyon.org> <20140901105350.GJ57121@e-new.0x20.net> <20140909055310.GA18936@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) 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: Wed, 10 Sep 2014 02:33:19 -0000 That's because you are "a wireless guy" :-) On Mon, Sep 08, 2014 at 11:33:31PM -0700, Adrian Chadd wrote: > > Oh it is fun. :) > > +a > On Sep 8, 2014 10:54 PM, "Kevin Lo" wrote: > > > On Mon, Sep 01, 2014 at 11:11:20AM -0700, Adrian Chadd wrote: > > > > > > The problem -is- the money. The people will come when there's enough > > > interest and enough money. > > > > > > The problem is that people think things like wifi drivers that are > > > debugged, perform well and get updated as new standards appear is a > > > few months effort - and I think the herculean efforts done in the past > > > by people like Sam fuel this myth. > > > > > > I've spent almost two years of weekends and evenings hacking on > > > net80211 and the atheros driver to get it to where it is. The 11n > > > support for atheros chips appeared when someone (hi Hobnob!) paid me > > > for six months to get 11n done. I'm still debugging weird corner cases > > > with rate control and congestion handling even now. And this is _on > > > top_ of all the work done by the Atheros team to write the HAL in the > > > first place. > > > > > > I've spent almost 18 months of weekends/evenings hacking on the intel > > > iwn driver to find all the little odd corner cases that make it > > > unusable by a lot of people. I keep saying I'm not, but since the > > > laptops I'm using have iwn in them, I end up getting annoyed enough to > > > fix it. This has all been for free. > > > > > > Wireless stuff is a very complicated, very time consuming thing that's > > > immensely fun if you're into this kind of thing. But please understand > > > - it's a huge time commitment for each individual device and new > > > standard. > > > > > > So yes, it's the money. I've jokingly said that it's $100k and 2 years > > > for me in (evenings, weekends) time and equipment to port and debug > > > one driver for a given NIC. Not just do a "oh look here's an openbsd > > > driver ported from linux in a month" port - that's just the beginning > > > (and I tend to quote something like $10k for that) - I mean, something > > > that ends up implementing the updated standards (11n, 11ac soon); > > > something that includes powersave, something that includes debugging, > > > something that handles a multitude of bad environments that people see > > > every day and complain about. Ie - the level of work that makes it "oh > > > it just works, I can get on with work now" level of work. > > > > > > I don't want to let myself be dragged into another two years of > > > weekends. I kind of need some sleep here and there. > > > > I can't find a reason why I disagree with you. > > I have almost forgotten that wifi hacking can be fun if it results > > in something working... > > > > > -a > > > > Kevin > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Wed Sep 10 09:41:00 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 CD34980C for ; Wed, 10 Sep 2014 09:41:00 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B42E81546 for ; Wed, 10 Sep 2014 09:41:00 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8A9f0h0021045 for ; Wed, 10 Sep 2014 09:41:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 193512] New: ath0: bb hang detected (0x1), resetting for AR9287 Date: Wed, 10 Sep 2014 09:41:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: artyom.mirgorodsky@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 10 Sep 2014 09:41:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193512 Bug ID: 193512 Summary: ath0: bb hang detected (0x1), resetting for AR9287 Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: artyom.mirgorodsky@gmail.com Sometime I receive this message on one of access point: ath0: bb hang detected (0x1), resetting After that connection restored only if I turn off wifi by hard button and turn on again. ath0: mem 0xe0500000-0xe050ffff irq 18 at device 0.0 on pci10 ath0: [HT] enabling HT modes ath0: [HT] enabling short-GI in 20MHz mode ath0: [HT] 1 stream STBC receive enabled ath0: [HT] 1 stream STBC transmit enabled ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9287 mac 384.2 RF5133 phy 15.15 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Wed Sep 10 14:18:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E173B43; Wed, 10 Sep 2014 14:18:48 +0000 (UTC) Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) (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 D73761938; Wed, 10 Sep 2014 14:18:47 +0000 (UTC) Received: by mail-we0-f172.google.com with SMTP id k48so3087766wev.3 for ; Wed, 10 Sep 2014 07:18:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:content-transfer-encoding:subject:from:message-id:date :cc:to:mime-version; bh=rh2ovcJiPNhUjsGKFJ8IcQXEtTm6Hy8h2wUFvXJZV4I=; b=0XNZ2Dl/HQB+LVZUdFwqEkgeiTwgO+uBqnFYg55YTq55J6xZEZ1jy93v5OWKSy9Jcn YdFNE9r77IY+e9x8UiidGMX3XQpsQHzshuPjyd8/JpcWFz3n37aI4w59Kwaa4/g+7eO+ iKNXhhUcp/DtUvrBvsOUpRpvq9XuOMiTaIBQDTU6G9IlS9Gl7dbYbFgkmVortXkvSWMi nG5KezqcZhZIOQCRBKbO4h0PHBu+MbdPSFJrwXj2uhX8QO31bEyQ4nC9dhJDUOvwQpoI jJDCH97ZhoCSmJrYT3O0d/v888rspMilLzhjFqpCxumQJm7ahTU8k27DyF7UgAG+CTxd u0Tw== X-Received: by 10.180.20.68 with SMTP id l4mr269001wie.42.1410358726004; Wed, 10 Sep 2014 07:18:46 -0700 (PDT) Received: from [192.168.20.2] ([62.219.134.104]) by mx.google.com with ESMTPSA id a19sm2636447wic.1.2014.09.10.07.18.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Sep 2014 07:18:44 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: Using a USB modem. From: atar Message-Id: Date: Wed, 10 Sep 2014 17:18:18 +0300 To: Mike Tancsa Mime-Version: 1.0 (1.0) X-Mailer: iPod Mail (10B500) Cc: "freebsd-wireless@freebsd.org" , "freebsd-questions@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: Wed, 10 Sep 2014 14:18:48 -0000 Hi there! Thanks you for your answer and sorry for the big delay of my response. I sim= ply hadn't enough time to test your suggestions until now. So, lets start. > Did you load the driver (kldload u3g) ? Yes. > what is the output of > usbconfig Here's the output of usbconfig -d 4.4 dump_device_desc: > ugen4.4: at usbus4, cfg=3D0 m= d=3DHOST spd=3DHIGH (480Mbps) pwr=3DON (500mA) >=20 > bLength =3D 0x0012=20 > bDescriptorType =3D 0x0001=20 > bcdUSB =3D 0x0200=20 > bDeviceClass =3D 0x0000=20 > bDeviceSubClass =3D 0x0000=20 > bDeviceProtocol =3D 0x0000=20 > bMaxPacketSize0 =3D 0x0040=20 > idVendor =3D 0x19d2=20 > idProduct =3D 0x0154=20 > bcdDevice =3D 0x0000=20 > iManufacturer =3D 0x0003 > iProduct =3D 0x0002 > iSerialNumber =3D 0x0004 > bNumConfigurations =3D 0x0001 Lastly, you've written: > Then provide the output of >=20 > # sysctl -a dev.u3g The output is as the following: > sysctl: unknown oid 'dev.u3g': No such file or directory Regards, Atar. From owner-freebsd-wireless@FreeBSD.ORG Wed Sep 10 14:33:24 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 1EA6B519; Wed, 10 Sep 2014 14:33:24 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D93071B9F; Wed, 10 Sep 2014 14:33:23 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.9/8.14.9) with ESMTP id s8AEXJ35008471; Wed, 10 Sep 2014 10:33:19 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <54106143.5050301@sentex.net> Date: Wed, 10 Sep 2014 10:33:39 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: atar Subject: Re: Using a USB modem. References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.74 Cc: "freebsd-wireless@freebsd.org" , "freebsd-questions@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: Wed, 10 Sep 2014 14:33:24 -0000 On 9/10/2014 10:18 AM, atar wrote: > Here's the output of usbconfig -d 4.4 dump_device_desc: > >> ugen4.4: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) >> >> bLength = 0x0012 >> bDescriptorType = 0x0001 >> bcdUSB = 0x0200 >> bDeviceClass = 0x0000 >> bDeviceSubClass = 0x0000 >> bDeviceProtocol = 0x0000 >> bMaxPacketSize0 = 0x0040 >> idVendor = 0x19d2 >> idProduct = 0x0154 >> bcdDevice = 0x0000 >> iManufacturer = 0x0003 >> iProduct = 0x0002 >> iSerialNumber = 0x0004 >> bNumConfigurations = 0x0001 > > Lastly, you've written: > >> Then provide the output of >> >> # sysctl -a dev.u3g > > The output is as the following: The modem is not attaching to the driver. What version of FreeBSD are you using ? What does uname -a show ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-wireless@FreeBSD.ORG Wed Sep 10 14:47:25 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 BE39EA4A; Wed, 10 Sep 2014 14:47:25 +0000 (UTC) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (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 297D31D3A; Wed, 10 Sep 2014 14:47:24 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id m15so4598156wgh.31 for ; Wed, 10 Sep 2014 07:47:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=S8YsY9b977Kq7FVhUKtPnCJnnJAm/xvBsP1gP0dqGB0=; b=VDBKOUkXSsZ7nxGBiKcfGKdv24aVm9ASlGD4tlfWefg6U9SSy5h2MMVO6fK/OzsiBF RDUbqUTTjdzLNcAHDaAfLoVe9pnM1ZrBD5LPt70CEnUCMwd0TsIiuh9nhr9RHYBMnPHY 6SCVnQ9JIU33NJBZHgHrYVtbzMQCzBewI5BKVlTSJY0SQaiNcCRg3Gdk/5qr0T5ApMKB 2IAQgQk31FtKu1wgwAeIcNYzh0ff5QhwaVQbGzxUYEt5pffLngiGzQOJ6ds5sJyOxlAs AofVlUQY0pwDvceZ/kV9Q0ARwIgK3paAcqQL4RuR5kmLnhpQlascdrNagnZL+d6bxD/1 I08w== X-Received: by 10.194.82.194 with SMTP id k2mr3703559wjy.105.1410360443338; Wed, 10 Sep 2014 07:47:23 -0700 (PDT) Received: from [192.168.20.2] ([62.219.134.104]) by mx.google.com with ESMTPSA id el10sm2678697wib.23.2014.09.10.07.47.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Sep 2014 07:47:22 -0700 (PDT) References: <54106143.5050301@sentex.net> Mime-Version: 1.0 (1.0) In-Reply-To: <54106143.5050301@sentex.net> Message-Id: X-Mailer: iPod Mail (10B500) From: atar Subject: Re: Using a USB modem. Date: Wed, 10 Sep 2014 17:47:19 +0300 To: Mike Tancsa Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-wireless@freebsd.org" , "freebsd-questions@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: Wed, 10 Sep 2014 14:47:25 -0000 I'm using at the last release of FreeBSD which is currently FreeBSD 10.0 but= I'm using the i386-memstick.img version of that distribution. > On 9/10/2014 10:18 AM, atar wrote: >> Here's the output of usbconfig -d 4.4 dump_device_desc: >>=20 >>> ugen4.4: at usbus4, cfg=3D= 0 md=3DHOST spd=3DHIGH (480Mbps) pwr=3DON (500mA) >>>=20 >>> bLength =3D 0x0012 >>> bDescriptorType =3D 0x0001 >>> bcdUSB =3D 0x0200 >>> bDeviceClass =3D 0x0000 >>> bDeviceSubClass =3D 0x0000 >>> bDeviceProtocol =3D 0x0000 >>> bMaxPacketSize0 =3D 0x0040 >>> idVendor =3D 0x19d2 >>> idProduct =3D 0x0154 >>> bcdDevice =3D 0x0000 >>> iManufacturer =3D 0x0003 >>> iProduct =3D 0x0002 >>> iSerialNumber =3D 0x0004 >>> bNumConfigurations =3D 0x0001 >>=20 >> Lastly, you've written: >>=20 >>> Then provide the output of >>>=20 >>> # sysctl -a dev.u3g >>=20 >> The output is as the following: >=20 >=20 > The modem is not attaching to the driver. What version of FreeBSD are you u= sing ? What does > uname -a > show ? >=20 > ---Mike >=20 >=20 > --=20 > ------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-wireless@FreeBSD.ORG Wed Sep 10 21:45:29 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2235777F for ; Wed, 10 Sep 2014 21:45:29 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 09634DA for ; Wed, 10 Sep 2014 21:45:29 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8ALjSYt030390 for ; Wed, 10 Sep 2014 21:45:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Wed, 10 Sep 2014 21:45:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dieterich.joh@gmail.com X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Wed, 10 Sep 2014 21:45:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 dieterich.joh@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Triage |Issue Resolved Resolution|--- |FIXED --- Comment #26 from dieterich.joh@gmail.com --- Is fixed for me, trying to clean up. Please (@hiren) reopen if you feel that is required. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Thu Sep 11 17:32:37 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E36481ED for ; Thu, 11 Sep 2014 17:32:37 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B02A4BAB for ; Thu, 11 Sep 2014 17:32:37 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8BHWbxh003906 for ; Thu, 11 Sep 2014 17:32:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 193569] New: [iwn] [wpi] 5GHz association fails on passive channels Date: Thu, 11 Sep 2014 17:32:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Thu, 11 Sep 2014 17:32:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193569 Bug ID: 193569 Summary: [iwn] [wpi] 5GHz association fails on passive channels Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: adrian@freebsd.org The TL;DR is this: * 5GHz passive channels require the station to hear a beacon from an AP doing DFS before it transmits anything; * so net80211 does this; * then it tries to associate; * .. and iwn/wpi will just issue a new RXON to associate, clearing the firmware state * which includes that it's seen beacons; * so then it transmits a frame (association request); * and the firmware immediately fails it with some status code (IWN_TX_*) that says "nope, need to see a beacon first." I forget the status code but it's pretty easy to see with 'sysctl dev.iwn.0.debug=0x1' when associating on a 5GHz channel. What the linux iwlwifi driver does - and what I think we should do - is this: * have a per-vap buffer of temporarily failed frames; * (not per-node; it's not required for this NIC); * if we see a TX fail for this reason, don't free the mbuf - just append it to the vap retry queue - and set some flag + channel number; * upon receiving a beacon notification - if it's for a beacon on the currently associated channel then schedule a taskqueue to flush that queue; * .. then flush this queue as appropriate in iwn_newstate(). * .. and make sure the taskqueue is cancelled during state changes, suspend/resume, etc. the flush may get complicated - we should flush it if we transition away from RUN. Just make sure it works. :) -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Fri Sep 12 14:43:55 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 A95EF1D1 for ; Fri, 12 Sep 2014 14:43:55 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8FDE0A0A for ; Fri, 12 Sep 2014 14:43:55 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8CEhtrZ044839 for ; Fri, 12 Sep 2014 14:43:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 193588] New: [PATCH] Staged malo(4) firmware module Date: Fri, 12 Sep 2014 14:43:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: listjm@club.fr X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Fri, 12 Sep 2014 14:43:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193588 Bug ID: 193588 Summary: [PATCH] Staged malo(4) firmware module Product: Base System Version: 10.0-RELEASE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: listjm@club.fr Created attachment 147248 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D147248&action= =3Dedit Staging patch for Makefile Installing the malo(4) firmware kernel module fails with: =3D=3D=3D> Registering installation for malo-firmware-kmod-3.0.0.39_1 pkg-static: lstat(/root/malo-firmware-1.4/work/stage/boot/modules/malofw.ko= ): No suuh file or directory *** Error code 74 Please find attached patch for staging this port and resolving the issue. The original port was downloaded, as for malo(4) manual, from: http://weongyo.org/project/malo/malo-firmware-1.4.tar.gz NOTE: I=E2=80=99m far from understanding throughly how this (or any other) = Makefile works, but the proposed patch works in my set up. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@FreeBSD.ORG Fri Sep 12 17:57:14 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 A71D8618; Fri, 12 Sep 2014 17:57:14 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89670230; Fri, 12 Sep 2014 17:57:14 +0000 (UTC) Received: from zeppelin.tachypleus.net (airbears2-136-152-142-26.AirBears2.Berkeley.EDU [136.152.142.26]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s8CHv2PA001610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 12 Sep 2014 10:57:02 -0700 Message-ID: <541333ED.8020005@freebsd.org> Date: Fri, 12 Sep 2014 10:57:01 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Issues with urtwn References: <540C751F.6050202@freebsd.org> <540C92D6.4030106@freebsd.org> <540CC53A.90600@freebsd.org> <540E2A2D.4090301@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVZboZMwYIDqTsCtraHPibzOqB0Unf9lWbQjIJ4vi0myuoOjLDwEeemJq1CU77J2GYKEYgfeBkDk9OQ6vyF0gI8rTCmU1DYbpbo= X-Sonic-ID: C;ltTcMqY65BGeATZXoK8kYw== M;hlIPM6Y65BGeATZXoK8kYw== X-Spam-Flag: No X-Sonic-Spam-Details: 0.7/5.0 by cerberusd 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: Fri, 12 Sep 2014 17:57:14 -0000 This is what the debug output looks like when things go wrong: wlan0: [54:78:1a:a0:91:22] sta power save mode on wlan0: wlan0: [54:78:1a:a0:91:22] save frame with age 41, 1 now queued [54:78:1a:a0:91:22] sta power save mode off wlan0: [54:78:1a:a0:91:22] flush ps queue, 1 packets queued wlan0: [54:78:1a:a0:91:22] sta power save mode on wlan0: [54:78:1a:a0:91:22] save frame with age 41, 1 now queued wlan0: [54:78:1a:a0:91:22] save frame with age 0, 2 now queued wlan0: [54:78:1a:a0:91:22] save frame with age 0, 3 now queued wlan0: [54:78:1a:a0:91:22] save frame with age 0, 4 now queued wlan0: ieee80211_sta_tim_notify: TIM=1 wlan0: ieee80211_sta_tim_notify: TIM=1 wlan0: ieee80211_sta_tim_notify: TIM=1 wlan0: ieee80211_sta_tim_notify: TIM=1 wlan0: ieee80211_sta_tim_notify: TIM=1 wlan0: [54:78:1a:a0:91:22] save frame with age 0, 5 now queued wlan0: [54:78:1a:a0:91:22] save frame with age 0, 6 now queued Let me know if I can test anything else. -Nathan On 09/08/14 15:17, Adrian Chadd wrote: > 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 >>> From owner-freebsd-wireless@FreeBSD.ORG Fri Sep 12 18:40:39 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 7ED196FE; Fri, 12 Sep 2014 18:40:39 +0000 (UTC) Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (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 2BA7B8BB; Fri, 12 Sep 2014 18:40:39 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id s7so1163809qap.32 for ; Fri, 12 Sep 2014 11:40:38 -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=tuYu5WGJpyuCdzQNR0BbqAV9qPXc+PAQ7rtfn987YWg=; b=h8ckTnnjRSND70YOVt5+gjBUHI1kS6HMgbuBW6dLs/Rg2xK9XP41VnoxoyGTbH8mFp IlHgBoWjUUEdwmOHIpyrQnjJo1OV/rkesLJN/C673nhKBESguQ9KY3BkCtLm4vMfqOHp nhfnmePweNGTO5wn2atKYHh2zxCEWjh7ZCxuB+YfX9lcNXfbnEpmg4SIkqlR+5SZW3Q1 mKt6J068PkhSSSCKfJ5TgCrsxFCzvc1aep2EL7KeWf3OXu8KzOpIPXoUL3D/cf7+ThUW 9+zO7Y3V0ov7wSqLZhkuWe1SxQU0veGVwaUDVEF+qxJU6u+6dqrzD6q7Zs4WNBgw9+If HG2w== MIME-Version: 1.0 X-Received: by 10.224.86.5 with SMTP id q5mr15195137qal.36.1410547238196; Fri, 12 Sep 2014 11:40:38 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Fri, 12 Sep 2014 11:40:38 -0700 (PDT) In-Reply-To: <541333ED.8020005@freebsd.org> References: <540C751F.6050202@freebsd.org> <540C92D6.4030106@freebsd.org> <540CC53A.90600@freebsd.org> <540E2A2D.4090301@freebsd.org> <541333ED.8020005@freebsd.org> Date: Fri, 12 Sep 2014 11:40:38 -0700 X-Google-Sender-Auth: extDF9VY8gKDhFWjTIQDryoQOv8 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: Fri, 12 Sep 2014 18:40:39 -0000 What the hell is calling sta power save? Can you go put in a stack trace (maybe use dtrace :) whenever the sta powersave routines get called? That's odd. So you see TIM=1 from the AP, but since powersave isn't enabled, it doesn't transition the NIC back to normal. So ieee80211_sta_pwrsave() is set in vap->iv_sta_ps. That's only called in: * the scan task for bgscan; * transitioning in/out of IEEE80211_S_SLEEP state. So, I don't know why you're seeing the above. In fact, if you hacked up urtwn to at least do powersave, the tim_notify will transition the VAP from SLEEP to RUN. In fact, hm. Can you file a bug for the above? There's the bug you're seeing, then there's the "we see a TIM flag for us, maybe we need to force transition out of sleep even if we think we're not in powersave". Thanks, -a On 12 September 2014 10:57, Nathan Whitehorn wrote: > This is what the debug output looks like when things go wrong: > wlan0: [54:78:1a:a0:91:22] sta power save mode on > wlan0: wlan0: [54:78:1a:a0:91:22] save frame with age 41, 1 now queued > [54:78:1a:a0:91:22] sta power save mode off > wlan0: [54:78:1a:a0:91:22] flush ps queue, 1 packets queued > wlan0: [54:78:1a:a0:91:22] sta power save mode on > wlan0: [54:78:1a:a0:91:22] save frame with age 41, 1 now queued > wlan0: [54:78:1a:a0:91:22] save frame with age 0, 2 now queued > wlan0: [54:78:1a:a0:91:22] save frame with age 0, 3 now queued > wlan0: [54:78:1a:a0:91:22] save frame with age 0, 4 now queued > wlan0: ieee80211_sta_tim_notify: TIM=1 > wlan0: ieee80211_sta_tim_notify: TIM=1 > wlan0: ieee80211_sta_tim_notify: TIM=1 > wlan0: ieee80211_sta_tim_notify: TIM=1 > wlan0: ieee80211_sta_tim_notify: TIM=1 > wlan0: [54:78:1a:a0:91:22] save frame with age 0, 5 now queued > wlan0: [54:78:1a:a0:91:22] save frame with age 0, 6 now queued > > Let me know if I can test anything else. > -Nathan > > > On 09/08/14 15:17, Adrian Chadd wrote: >> >> 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 >>>> > From owner-freebsd-wireless@FreeBSD.ORG Fri Sep 12 19:24:12 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5513542E for ; Fri, 12 Sep 2014 19:24:12 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B134D25 for ; Fri, 12 Sep 2014 19:24:12 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8CJOC0d037386 for ; Fri, 12 Sep 2014 19:24:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 193588] [PATCH] Staged malo(4) firmware module Date: Fri, 12 Sep 2014 19:24:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc component version assigned_to product Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Fri, 12 Sep 2014 19:24:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193588 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@freebsd.org Component|wireless |Individual Port(s) Version|10.0-RELEASE |Latest Assignee|freebsd-wireless@FreeBSD.or |freebsd-ports-bugs@FreeBSD. |g |org Product|Base System |Ports Tree --- Comment #1 from Adrian Chadd --- Hi! This is a ports thing! I'd like some help! Thanks! -a -- You are receiving this mail because: You are the assignee for the bug.