From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 23 19:10:07 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C3D4D90; Sun, 23 Dec 2012 19:10:07 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 5488C8FC0A; Sun, 23 Dec 2012 19:10:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBNJA7qm011724; Sun, 23 Dec 2012 19:10:07 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBNJA7H8011720; Sun, 23 Dec 2012 19:10:07 GMT (envelope-from linimon) Date: Sun, 23 Dec 2012 19:10:07 GMT Message-Id: <201212231910.qBNJA7H8011720@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/174661: [wlan] lost alias on wlan interface X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Dec 2012 19:10:07 -0000 Old Synopsis: lost alias on wlan interface New Synopsis: [wlan] lost alias on wlan interface Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Dec 23 19:09:44 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=174661 From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 24 11:06:53 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59E4C687 for ; Mon, 24 Dec 2012 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 351E18FC12 for ; Mon, 24 Dec 2012 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBOB6rH9066246 for ; Mon, 24 Dec 2012 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBOB6qkT066244 for freebsd-wireless@FreeBSD.org; Mon, 24 Dec 2012 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Dec 2012 11:06:52 GMT Message-Id: <201212241106.qBOB6qkT066244@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 24 Dec 2012 11:06:53 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 142 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 25 22:00:23 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C3297B9 for ; Tue, 25 Dec 2012 22:00:23 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 305518FC0C for ; Tue, 25 Dec 2012 22:00:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBPM01cx006345 for ; Tue, 25 Dec 2012 22:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBPM01A6006340; Tue, 25 Dec 2012 22:00:01 GMT (envelope-from gnats) Date: Tue, 25 Dec 2012 22:00:01 GMT Message-Id: <201212252200.qBPM01A6006340@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Raphael Kubo da Costa Subject: Re: kern/172672: [ubt] Bluetooth device recognised but not working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Raphael Kubo da Costa 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, 25 Dec 2012 22:00:23 -0000 The following reply was made to PR kern/172672; it has been noted by GNATS. From: Raphael Kubo da Costa To: bug-followup@FreeBSD.org Cc: David Subject: Re: kern/172672: [ubt] Bluetooth device recognised but not working Date: Tue, 25 Dec 2012 23:50:00 +0200 Could you expand on the "not working properly" part? Are you trying to use an input device via Bluetooth? The Handbook [1] and these pages [2][3] have helped me get my Bluetooth keyboard working on 9-STABLE. [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bluetooth.html [2] http://geekinfo.net/article.php?story=20080427222204364 [3] http://astralblue.livejournal.com/357664.html From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 25 23:08:56 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38F70EFA for ; Tue, 25 Dec 2012 23:08:56 +0000 (UTC) (envelope-from bas_vermin@hotmail.com) Received: from dub0-omc1-s11.dub0.hotmail.com (dub0-omc1-s11.dub0.hotmail.com [157.55.0.210]) by mx1.freebsd.org (Postfix) with ESMTP id BB6D38FC0C for ; Tue, 25 Dec 2012 23:08:55 +0000 (UTC) Received: from DUB002-W64 ([157.55.0.237]) by dub0-omc1-s11.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 25 Dec 2012 15:07:47 -0800 X-EIP: [VVRU9GugePtkfFmwFhm4iROgRy0IrQOJ] X-Originating-Email: [bas_vermin@hotmail.com] Message-ID: From: Bas Vermin To: "freebsd-wireless@freebsd.org" Subject: BCM4313 card for developers willing to work on the Broadcom drivers Date: Wed, 26 Dec 2012 00:07:47 +0100 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 25 Dec 2012 23:07:47.0240 (UTC) FILETIME=[A76C4280:01CDE2F4] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 25 Dec 2012 23:08:56 -0000 Hi guys=2C Upgraded the WiFi card in my laptop last week=2C so I have an unused BCM431= 3 (half-size mini-pcie) lying around. As most of us know all the new Broadcom chips are not supported yet and wil= l require the brcmsmac to be ported to FreeBSD. Anyone interested in doing this=2C or= in need of an extra broadcom chip for testing just let me know and I'll send it to you= after the holidays. Bas = From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 26 00:40:01 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F898BA7 for ; Wed, 26 Dec 2012 00:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 110868FC0C for ; Wed, 26 Dec 2012 00:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBQ0e0rS018670 for ; Wed, 26 Dec 2012 00:40:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBQ0e0mq018667; Wed, 26 Dec 2012 00:40:00 GMT (envelope-from gnats) Date: Wed, 26 Dec 2012 00:40:00 GMT Message-Id: <201212260040.qBQ0e0mq018667@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Raphael Kubo da Costa Subject: Re: kern/172672: [ubt] Bluetooth device recognised but not working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Raphael Kubo da Costa 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, 26 Dec 2012 00:40:01 -0000 The following reply was made to PR kern/172672; it has been noted by GNATS. From: Raphael Kubo da Costa To: bug-followup@FreeBSD.org Cc: David Subject: Re: kern/172672: [ubt] Bluetooth device recognised but not working Date: Wed, 26 Dec 2012 02:35:06 +0200 David writes: > Yes I'm trying to send files via Bluetooth on that netbook. > > It appears to be that PC-BSD has not yet put the right "GUI" tools in > place to make it easy for newbies like me. :) > > On 25/12/2012 21:50, Raphael Kubo da Costa wrote: >> Could you expand on the "not working properly" part? Are you trying to >> use an input device via Bluetooth? >> >> The Handbook [1] and these pages [2][3] have helped me get my Bluetooth >> keyboard working on 9-STABLE. >> >> [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bluetooth.html >> [2] http://geekinfo.net/article.php?story=20080427222204364 >> [3] http://astralblue.livejournal.com/357664.html Please keep bug-followup@ CC'ed otherwise your response won't get noted on the PR. I don't use PC-BSD myself, but it looks like the 9.1 release includes some sort of Bluetooth Manager [1]. In any case, you could also try following the steps in the Handbook to see if there's really a problem on FreeBSD or not. [1] http://wiki.pcbsd.org/index.php/Bluetooth_Manager From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 28 03:25:53 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EBB06450; Fri, 28 Dec 2012 03:25:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B35548FC13; Fri, 28 Dec 2012 03:25:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBS3PrYC096528; Fri, 28 Dec 2012 03:25:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBS3Prjx096524; Fri, 28 Dec 2012 03:25:53 GMT (envelope-from linimon) Date: Fri, 28 Dec 2012 03:25:53 GMT Message-Id: <201212280325.qBS3Prjx096524@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Dec 2012 03:25:54 -0000 Old Synopsis: can't use channel 12 and 13 (14) with my wifi interface New Synopsis: [wlan] can't use channel 12 and 13 (14) with my wifi interface Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Fri Dec 28 03:25:08 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=174722 From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 28 04:00:01 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 36D1B6E3 for ; Fri, 28 Dec 2012 04:00:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 1BDBF8FC13 for ; Fri, 28 Dec 2012 04:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBS400Nl097268 for ; Fri, 28 Dec 2012 04:00:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBS400X5097264; Fri, 28 Dec 2012 04:00:00 GMT (envelope-from gnats) Date: Fri, 28 Dec 2012 04:00:00 GMT Message-Id: <201212280400.qBS400X5097264@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Adrian Chadd Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Adrian Chadd 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, 28 Dec 2012 04:00:01 -0000 The following reply was made to PR kern/174722; it has been noted by GNATS. From: Adrian Chadd To: bug-followup@freebsd.org Cc: Carsten Wiedmann Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface Date: Thu, 27 Dec 2012 19:57:55 -0800 Hi, This may be the problem: :regdomain ETSI country DE anywhere -ecm Please try: ifconfig wlan0 down ifconfig wlan0 ecm ifconfig wlan0 up If ECM isn't enabled then you won't see channels > 11 in 11bg mode. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 28 06:24:42 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6072021D; Fri, 28 Dec 2012 06:24:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 64EFB8FC0A; Fri, 28 Dec 2012 06:24:41 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id es5so4737115wgb.29 for ; Thu, 27 Dec 2012 22:24:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=ZR2R1GCckFbqbI/Q+/cUXAtfUdpnfioLkv48KAwY2R4=; b=kVRUPOe1YXZ+mUpCWX9JjNwSUJcSfOYsKwOsdm5T7biRS9fkcxArG/V1QIPdmHdCiN eGpw7s09y+fDNvi+RxTIg6c/BCjHGrDl3WZW3ZL6dpIwN/joVRMp2S1++jqvsJcGOhTV cX7vJi5Beg4Me+UI7J3KD5YXGpUXjbU00AATNL5zFu7Gf9wOtbZU5jW3RAQycXfgMt5E Q/qzKa05Qp/AeLgTPZHGsIJ9mNKdIIhIk1L+0qaKDXUl3ycduSZzV65BDGPAOMcoPL9J ZVAfPty8B/VdBvUKcvadr0+1l8o2EpC/QM/LPbYabaLrThLhho9my5VXw0zOSaogWPyi Lyyw== MIME-Version: 1.0 Received: by 10.194.83.36 with SMTP id n4mr52007139wjy.59.1356675873796; Thu, 27 Dec 2012 22:24:33 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Thu, 27 Dec 2012 22:24:33 -0800 (PST) Date: Thu, 27 Dec 2012 22:24:33 -0800 X-Google-Sender-Auth: 2VOoaJQMusXV71lYq2EBLCd-jfQ Message-ID: Subject: .. if_transmit() and the quirky issues with node referencing From: Adrian Chadd To: Monthadar Al Jaberi , Bernhard Schmidt , freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Dec 2012 06:24:42 -0000 So I finally figured out my problem with if_transmit()'ifying the ath(4) code. (Yes, this means I have TX fragmentation working with ath(4), as well as some non-trivial performance improvements in TX TCP tests.) In quick summary: net80211's call to the driver will decrement the node ref if the driver if_transmit() call fails. So I went looking for instances of where if_transmit() is called without correct error checking. One is in ieee80211_hwmp.c . It pops frames off of the ageq and calls if_transmit(). It should deref the node ref the same way that the ageq code does. The other is in ieee80211_hostap.c - my fault. It uses the psq; I should deref the node ref the same way that the psq code does. This just highlights some of the rather quirky corners of net80211: * if_transmit() can be called on the driver facing interface (ie, the driver ifp) or the vap ifp. * for driver ifp, the frame should be encapsulated and there must be a node reference held/given when it's called. If if_transmit() fails here, it must deref the node. * for non-encapsulated frames (eg perhaps some stuff in the ageq or one of the psqs), if_transmit() will be called on the VAP interface. * .. now, when if_transmit() is called on the vap interface, the mbuf m_pkthdr.recvif will point to the vap ifp; * .. when if_transmit() is called on the physical interface, the mbuf m_pkthdr.recvif will point to the node reference. This is all a bit kooky and very prone to people making mistakes, especially when mbufs may be pushed up, down and throughout all kinds of weird places. I also bet the re-entrant parts of the codebase (ie stuff that uses the ageq, psq, wds .. maybe the mesh stuff) could do with a bit of a re-review. In any case, what this means is: * we need to be really, really careful with how we route mbufs through net80211 here, aiee! * if a frame has M_ENCAP tagged and it's pushed into an ageq or psq, it _must_ have the TX node ref held; .. thus, if we raw construct an encapsulated frame (locally in net80211, or in a driver, or via ieee80211_output, etc) then when we set M_ENCAP, we must hold the TX node reference and we must set recvif correctly! What I'd really like to do here: * re-review all the if_transmit() error handling - make sure that if it fails, we correctly handle dereferencing the node or things will leak; * make "get/set recvif from ifp" and "get/set recvif from node" as methods; * have those methods check whether M_ENCAP is correctly set/cleared, and complain loudly if we ever try to get the wrong reference for the given situation (eg, if we try to read the node reference from an mbuf, but M_ENCAP isn't set, then complain); * .. figure out some alternate way to store the node reference (mbuf tags?) and start migrating the code that way. Anyway, at least I've been down this rabbit hole and have higher 11n throughput _and_ legacy TX fragmentation working (at least for ath(4).) I'll post a patch tomorrow night and start thoroughly testing the error corner cases. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 28 12:50:02 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 273499A5 for ; Fri, 28 Dec 2012 12:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0B60F8FC0C for ; Fri, 28 Dec 2012 12:50:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBSCo1ua026577 for ; Fri, 28 Dec 2012 12:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBSCo1oY026576; Fri, 28 Dec 2012 12:50:01 GMT (envelope-from gnats) Date: Fri, 28 Dec 2012 12:50:01 GMT Message-Id: <201212281250.qBSCo1oY026576@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: "Carsten Wiedmann" Subject: Re: kern/174722: can't use channel 12 and 13 (14) with my wifi interface X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Carsten Wiedmann 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, 28 Dec 2012 12:50:02 -0000 The following reply was made to PR kern/174722; it has been noted by GNATS. From: "Carsten Wiedmann" To: bug-followup@FreeBSD.org, carsten_sttgt@gmx.de Cc: Subject: Re: kern/174722: can't use channel 12 and 13 (14) with my wifi interface Date: Fri, 28 Dec 2012 13:43:25 +0100 Hmmm, doesn't work: freebsd# ifconfig wlan0 list regdomain :regdomain ETSI country DE anywhere ecm Channel 1 : 2412 MHz 11b Channel 6 : 2437 MHz 11g Channel 1 : 2412 MHz 11g Channel 7 : 2442 MHz 11b Channel 2 : 2417 MHz 11b Channel 7 : 2442 MHz 11g Channel 2 : 2417 MHz 11g Channel 8 : 2447 MHz 11b Channel 3 : 2422 MHz 11b Channel 8 : 2447 MHz 11g Channel 3 : 2422 MHz 11g Channel 9 : 2452 MHz 11b Channel 4 : 2427 MHz 11b Channel 9 : 2452 MHz 11g Channel 4 : 2427 MHz 11g Channel 10 : 2457 MHz 11b Channel 5 : 2432 MHz 11b Channel 10 : 2457 MHz 11g Channel 5 : 2432 MHz 11g Channel 11 : 2462 MHz 11b Channel 6 : 2437 MHz 11b Channel 11 : 2462 MHz 11g BTW: Even "ifconfig wlan0 ecm" is changing this setting, I can't find "ecm" in "man ifconfig"? From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 28 12:50:03 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 171279A6 for ; Fri, 28 Dec 2012 12:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id EF9638FC12 for ; Fri, 28 Dec 2012 12:50:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBSCo270026583 for ; Fri, 28 Dec 2012 12:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBSCo2kR026582; Fri, 28 Dec 2012 12:50:02 GMT (envelope-from gnats) Date: Fri, 28 Dec 2012 12:50:02 GMT Message-Id: <201212281250.qBSCo2kR026582@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: "Carsten Wiedmann" Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Carsten Wiedmann 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, 28 Dec 2012 12:50:03 -0000 The following reply was made to PR kern/174722; it has been noted by GNATS. From: "Carsten Wiedmann" To: bug-followup@FreeBSD.org, carsten_sttgt@gmx.de Cc: Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface Date: Fri, 28 Dec 2012 13:47:59 +0100 Hmmm, doesn't work: freebsd# ifconfig wlan0 list regdomain :regdomain ETSI country DE anywhere ecm Channel 1 : 2412 MHz 11b Channel 6 : 2437 MHz 11g Channel 1 : 2412 MHz 11g Channel 7 : 2442 MHz 11b Channel 2 : 2417 MHz 11b Channel 7 : 2442 MHz 11g Channel 2 : 2417 MHz 11g Channel 8 : 2447 MHz 11b Channel 3 : 2422 MHz 11b Channel 8 : 2447 MHz 11g Channel 3 : 2422 MHz 11g Channel 9 : 2452 MHz 11b Channel 4 : 2427 MHz 11b Channel 9 : 2452 MHz 11g Channel 4 : 2427 MHz 11g Channel 10 : 2457 MHz 11b Channel 5 : 2432 MHz 11b Channel 10 : 2457 MHz 11g Channel 5 : 2432 MHz 11g Channel 11 : 2462 MHz 11b Channel 6 : 2437 MHz 11b Channel 11 : 2462 MHz 11g BTW: Even "ifconfig wlan0 ecm" is changing this setting, I can't find "ecm" in "man ifconfig"? From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 28 14:29:27 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7959C810 for ; Fri, 28 Dec 2012 14:29:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by mx1.freebsd.org (Postfix) with ESMTP id 000428FC0C for ; Fri, 28 Dec 2012 14:29:26 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id o1so5935775wic.6 for ; Fri, 28 Dec 2012 06:29:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1vvg0OZak92yJP13nx8TV6HfG4+TYWtu5+5tAZhvwq0=; b=fBNGjaQzL9J76GeiRLvQQT1w6JbkFGhttuOv38Qo98hiNLqHenwXnR2otB6/q+oTfQ AqmbG8qlF5ofSG1jEIQFR6fBYLsDwJFDSNBvvRjhnasVRp3JWMafTaXVlqFEGOD9PSYL 1WejdGsnUPmrRFGkboLChKz+rN7rJUhnob6Cwv17aQGhKp58STHyJqnmTNivLVsIl5T0 VUzZcSDBbxjb1nuLpHBfXUIJnZzP5WbQqywJ03RlYBEwDlDbADTe+NfjFOSYeuhx0E9K kUUMKDAWMcXrBG2lC6gxzeouZGs86thbYka73xAeZr3Q293qSePgoompDtvxDx9PmPv9 iW2Q== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr54165973wjc.1.1356704959917; Fri, 28 Dec 2012 06:29:19 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 28 Dec 2012 06:29:19 -0800 (PST) In-Reply-To: <201212281250.qBSCo2kR026582@freefall.freebsd.org> References: <201212281250.qBSCo2kR026582@freefall.freebsd.org> Date: Fri, 28 Dec 2012 06:29:19 -0800 X-Google-Sender-Auth: 94DVHLzpMXWOXGjFmybnphS-8G4 Message-ID: Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface From: Adrian Chadd To: Carsten Wiedmann Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Dec 2012 14:29:27 -0000 Hm, ok, so try: ifconfig wlan0 down ifconfig wlan0 ecm ifconfig wlan0 regdomain DE ifconfig wlan0 up ifconfig wlan0 list channel Adrian On 28 December 2012 04:50, Carsten Wiedmann wrote: > The following reply was made to PR kern/174722; it has been noted by GNATS. > > From: "Carsten Wiedmann" > To: bug-followup@FreeBSD.org, carsten_sttgt@gmx.de > Cc: > Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi > interface > Date: Fri, 28 Dec 2012 13:47:59 +0100 > > Hmmm, doesn't work: > > freebsd# ifconfig wlan0 list regdomain > :regdomain ETSI country DE anywhere ecm > Channel 1 : 2412 MHz 11b Channel 6 : 2437 MHz 11g > Channel 1 : 2412 MHz 11g Channel 7 : 2442 MHz 11b > Channel 2 : 2417 MHz 11b Channel 7 : 2442 MHz 11g > Channel 2 : 2417 MHz 11g Channel 8 : 2447 MHz 11b > Channel 3 : 2422 MHz 11b Channel 8 : 2447 MHz 11g > Channel 3 : 2422 MHz 11g Channel 9 : 2452 MHz 11b > Channel 4 : 2427 MHz 11b Channel 9 : 2452 MHz 11g > Channel 4 : 2427 MHz 11g Channel 10 : 2457 MHz 11b > Channel 5 : 2432 MHz 11b Channel 10 : 2457 MHz 11g > Channel 5 : 2432 MHz 11g Channel 11 : 2462 MHz 11b > Channel 6 : 2437 MHz 11b Channel 11 : 2462 MHz 11g > > BTW: > Even "ifconfig wlan0 ecm" is changing this setting, I can't find "ecm" in "man ifconfig"? > > _______________________________________________ > 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 Fri Dec 28 15:17:26 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D6A37E8B for ; Fri, 28 Dec 2012 15:17:26 +0000 (UTC) (envelope-from carsten_sttgt@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by mx1.freebsd.org (Postfix) with ESMTP id 778538FC12 for ; Fri, 28 Dec 2012 15:17:26 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0M8LHQ-1StsTH29Vy-00vxvU for ; Fri, 28 Dec 2012 16:17:25 +0100 Received: (qmail 13342 invoked by uid 0); 28 Dec 2012 15:17:25 -0000 Received: from 84.56.128.19 by www037.gmx.net with HTTP; Fri, 28 Dec 2012 16:17:24 +0100 (CET) Content-Type: text/plain; charset="utf-8" Date: Fri, 28 Dec 2012 16:17:24 +0100 From: "Carsten Wiedmann" In-Reply-To: Message-ID: <20121228151724.299770@gmx.net> MIME-Version: 1.0 References: <201212281250.qBSCo2kR026582@freefall.freebsd.org> Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface To: Adrian Chadd X-Authenticated: #12964898 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1/eGAg5szLegGvYbThsugH9VzdFU6zk/0FuSD5EDN gkXH8bs6mlWIXhE+y1svr9McNbaOrRrLJyug== Content-Transfer-Encoding: 8bit X-GMX-UID: U92vcH0UeSEqQkO3rnQh9Ip+IGRvb8Ak Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Dec 2012 15:17:27 -0000 Hi Adrian, I guess you mean: ifconfig wlan0 regdomain ETSI or ifconfig wlan0 country DE But this makes no difference. I only have the channels 1-11. And "ifconfig wlan0" is always showing the correct: "regdomain ETSI country DE" Of course, I don't understand why it isn't enough to set "country DE" in "/etc/rc.conf"? >From "man ifconfig" --> country: | Set the country code to use in calculating the regulatory con- | straints for operation. In particular the set of available chan- | nels, how the wireless device will operation on the channels, and >From "man regdomain" (The regdomain.xml file): | This information is used by the ifconfig(8) program to construct regula- | tory state for download to the system. And in "/etc/regdomain.xml" I have: | | ETSI | 0x30 | | | | 30 | IEEE80211_CHAN_B | | | | | | 30 | IEEE80211_CHAN_G | | | ... 2412 is channel 1 2472 is channel 13 Regards, Carsten -------- Original-Nachricht -------- > Datum: Fri, 28 Dec 2012 06:29:19 -0800 > Von: Adrian Chadd > An: Carsten Wiedmann > CC: freebsd-wireless@freebsd.org > Betreff: Re: kern/174722: [wlan] can\'t use channel 12 and 13 (14) with my wifi interface > Hm, ok, so try: > > ifconfig wlan0 down > ifconfig wlan0 ecm > ifconfig wlan0 regdomain DE > ifconfig wlan0 up > ifconfig wlan0 list channel > > > > Adrian > > > On 28 December 2012 04:50, Carsten Wiedmann wrote: > > The following reply was made to PR kern/174722; it has been noted by > GNATS. > > > > From: "Carsten Wiedmann" > > To: bug-followup@FreeBSD.org, carsten_sttgt@gmx.de > > Cc: > > Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with > my wifi > > interface > > Date: Fri, 28 Dec 2012 13:47:59 +0100 > > > > Hmmm, doesn't work: > > > > freebsd# ifconfig wlan0 list regdomain > > :regdomain ETSI country DE anywhere ecm > > Channel 1 : 2412 MHz 11b Channel 6 : 2437 MHz > 11g > > Channel 1 : 2412 MHz 11g Channel 7 : 2442 MHz > 11b > > Channel 2 : 2417 MHz 11b Channel 7 : 2442 MHz > 11g > > Channel 2 : 2417 MHz 11g Channel 8 : 2447 MHz > 11b > > Channel 3 : 2422 MHz 11b Channel 8 : 2447 MHz > 11g > > Channel 3 : 2422 MHz 11g Channel 9 : 2452 MHz > 11b > > Channel 4 : 2427 MHz 11b Channel 9 : 2452 MHz > 11g > > Channel 4 : 2427 MHz 11g Channel 10 : 2457 MHz > 11b > > Channel 5 : 2432 MHz 11b Channel 10 : 2457 MHz > 11g > > Channel 5 : 2432 MHz 11g Channel 11 : 2462 MHz > 11b > > Channel 6 : 2437 MHz 11b Channel 11 : 2462 MHz > 11g > > > > BTW: > > Even "ifconfig wlan0 ecm" is changing this setting, I can't find "ecm" > in "man ifconfig"? > > > > _______________________________________________ > > 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 Fri Dec 28 16:41:36 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8F7B6F6A for ; Fri, 28 Dec 2012 16:41:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22a.google.com (wg-in-x022a.1e100.net [IPv6:2a00:1450:400c:c00::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 1B1B18FC12 for ; Fri, 28 Dec 2012 16:41:35 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id dr1so4282499wgb.1 for ; Fri, 28 Dec 2012 08:41:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=G2QR99uzsyW0do8bWTuH2AQUbtwcg04nEdoyXMXVWlc=; b=Ob2XcLHgdXwNMCIHhKPH7pDrtXXRRm60fDhgSaoq/xe1oQQ0ti/z+bwJcJ9SGinVWk he2Tv8zrtZpOxpQ+gcjPlYYzhgOaF0x7rQVWah4p2jFHOH6Zz2XaLC4VpqE1r3x8mhIq T8BM3tEkaZK+j0ujmZRl9qI1NUO3i0g7CBATQBDcgecRGzW2ZhHIrfswWgNCwCxivLI9 pPpeyvAcxqjKDbv2GcrOShOwAWVTzYxyIMuPZjIUv8YqOvqcR/5TdRURMthyEkaWX0Fe rio5Qdboj8eIdgReTseoFnJzLcv0kHO+N2GZLQNARXk5T9vpYv1mN3VrIU8x9RJOZRhZ qBHQ== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr54753528wjc.1.1356712895241; Fri, 28 Dec 2012 08:41:35 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 28 Dec 2012 08:41:34 -0800 (PST) In-Reply-To: <20121228151724.299770@gmx.net> References: <201212281250.qBSCo2kR026582@freefall.freebsd.org> <20121228151724.299770@gmx.net> Date: Fri, 28 Dec 2012 08:41:34 -0800 X-Google-Sender-Auth: 2GcFWf5kZ1HleT4Gbve938CrR6k Message-ID: Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface From: Adrian Chadd To: Carsten Wiedmann Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Dec 2012 16:41:36 -0000 Hi, The problem is likely because the 'ecm' flag isn't set when it creates the channel list. That's why I suggested setting the ecm flag, setting the regdomain or country, then checking the channel list. The iwi code just uses the default net80211 regulatory domain code to populate the channel list. The ath(4) code sets things up based on its own internal channel assembly code. That's why I've not noticed this behaviour before. The net80211 regulatory domain code doesn't check for channels >11 in 11b/g/bg mode if the ecm bit isn't set when the channel list is assembled. And that only gets done when you configure the regulatory domain - when setting/clearing the ecm flag, it doesn't trigger reinitialising the channel list. Hence why I said "set ecm bit, reset channel list, let me know how it goes." Thanks, Adrian On 28 December 2012 07:17, Carsten Wiedmann wrote: > Hi Adrian, > > I guess you mean: > ifconfig wlan0 regdomain ETSI > or > ifconfig wlan0 country DE > > But this makes no difference. I only have the channels 1-11. > > And "ifconfig wlan0" is always showing the correct: > "regdomain ETSI country DE" > > > Of course, I don't understand why it isn't enough to set "country DE" in "/etc/rc.conf"? > > > From "man ifconfig" --> country: > | Set the country code to use in calculating the regulatory con- > | straints for operation. In particular the set of available chan- > | nels, how the wireless device will operation on the channels, and > > > From "man regdomain" (The regdomain.xml file): > | This information is used by the ifconfig(8) program to construct regula- > | tory state for download to the system. > > > And in "/etc/regdomain.xml" I have: > | > | ETSI > | 0x30 > | > | > | > | 30 > | IEEE80211_CHAN_B > | > | > | > | > | > | 30 > | IEEE80211_CHAN_G > | > | > | ... > > 2412 is channel 1 > 2472 is channel 13 > > Regards, > Carsten > > -------- Original-Nachricht -------- >> Datum: Fri, 28 Dec 2012 06:29:19 -0800 >> Von: Adrian Chadd >> An: Carsten Wiedmann >> CC: freebsd-wireless@freebsd.org >> Betreff: Re: kern/174722: [wlan] can\'t use channel 12 and 13 (14) with my wifi interface > >> Hm, ok, so try: >> >> ifconfig wlan0 down >> ifconfig wlan0 ecm >> ifconfig wlan0 regdomain DE >> ifconfig wlan0 up >> ifconfig wlan0 list channel >> >> >> >> Adrian >> >> >> On 28 December 2012 04:50, Carsten Wiedmann wrote: >> > The following reply was made to PR kern/174722; it has been noted by >> GNATS. >> > >> > From: "Carsten Wiedmann" >> > To: bug-followup@FreeBSD.org, carsten_sttgt@gmx.de >> > Cc: >> > Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with >> my wifi >> > interface >> > Date: Fri, 28 Dec 2012 13:47:59 +0100 >> > >> > Hmmm, doesn't work: >> > >> > freebsd# ifconfig wlan0 list regdomain >> > :regdomain ETSI country DE anywhere ecm >> > Channel 1 : 2412 MHz 11b Channel 6 : 2437 MHz >> 11g >> > Channel 1 : 2412 MHz 11g Channel 7 : 2442 MHz >> 11b >> > Channel 2 : 2417 MHz 11b Channel 7 : 2442 MHz >> 11g >> > Channel 2 : 2417 MHz 11g Channel 8 : 2447 MHz >> 11b >> > Channel 3 : 2422 MHz 11b Channel 8 : 2447 MHz >> 11g >> > Channel 3 : 2422 MHz 11g Channel 9 : 2452 MHz >> 11b >> > Channel 4 : 2427 MHz 11b Channel 9 : 2452 MHz >> 11g >> > Channel 4 : 2427 MHz 11g Channel 10 : 2457 MHz >> 11b >> > Channel 5 : 2432 MHz 11b Channel 10 : 2457 MHz >> 11g >> > Channel 5 : 2432 MHz 11g Channel 11 : 2462 MHz >> 11b >> > Channel 6 : 2437 MHz 11b Channel 11 : 2462 MHz >> 11g >> > >> > BTW: >> > Even "ifconfig wlan0 ecm" is changing this setting, I can't find "ecm" >> in "man ifconfig"? >> > >> > _______________________________________________ >> > 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 Sat Dec 29 12:15:42 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B1D2F61 for ; Sat, 29 Dec 2012 12:15:42 +0000 (UTC) (envelope-from carsten_sttgt@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by mx1.freebsd.org (Postfix) with ESMTP id C28918FC0C for ; Sat, 29 Dec 2012 12:15:41 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.16]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MPsKa-1TjxFU43Xe-0055MM for ; Sat, 29 Dec 2012 13:15:35 +0100 Received: (qmail 30525 invoked by uid 0); 29 Dec 2012 12:15:34 -0000 Received: from 84.56.166.218 by www048.gmx.net with HTTP; Sat, 29 Dec 2012 13:15:34 +0100 (CET) Content-Type: text/plain; charset="utf-8" Date: Sat, 29 Dec 2012 13:15:34 +0100 From: "Carsten Wiedmann" In-Reply-To: Message-ID: <20121229121534.299730@gmx.net> MIME-Version: 1.0 References: <201212281250.qBSCo2kR026582@freefall.freebsd.org> <20121228151724.299770@gmx.net> Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) with my wifi interface To: Adrian Chadd X-Authenticated: #12964898 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1+WnjsrfaiWVrnhb+sSHB5ByY3HOSL+lkKxmc0i+H s6keuPXw77rI9qT+VRKk8/8kGWd2XV9ABvgw== Content-Transfer-Encoding: 8bit X-GMX-UID: sbuscHEUeSEqQkO3rnQhqGN+IGRvb8Bf Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 29 Dec 2012 12:15:42 -0000 Hi Adrian, Just to make sure: | ifconfig wlan0 regdomain DE can't work. So I used: | ifconfig wlan0 down | ifconfig wlan0 ecm | ifconfig wlan0 regdomain ETSI | ifconfig wlan0 up | ifconfig wlan0 list channel But this also shows me not the channels 12/13. BTW ath vs. iwi: As you read in my first mail, I have the same issue if I use ndis for my device. If you can build a ndis driver for your interface (NDISulator), you should have the same issue. Regards, Carsten -------- Original-Nachricht -------- > Datum: Fri, 28 Dec 2012 08:41:34 -0800 > Von: Adrian Chadd > An: Carsten Wiedmann > CC: freebsd-wireless@freebsd.org > Betreff: Re: kern/174722: [wlan] can\'t use channel 12 and 13 (14) with my wifi interface > Hi, > > The problem is likely because the 'ecm' flag isn't set when it creates > the channel list. > > That's why I suggested setting the ecm flag, setting the regdomain or > country, then checking the channel list. > > The iwi code just uses the default net80211 regulatory domain code to > populate the channel list. The ath(4) code sets things up based on its > own internal channel assembly code. > That's why I've not noticed this behaviour before. > > The net80211 regulatory domain code doesn't check for channels >11 in > 11b/g/bg mode if the ecm bit isn't set when the channel list is > assembled. > And that only gets done when you configure the regulatory domain - > when setting/clearing the ecm flag, it doesn't trigger reinitialising > the channel list. > > Hence why I said "set ecm bit, reset channel list, let me know how it > goes." > > Thanks, > > > Adrian > > On 28 December 2012 07:17, Carsten Wiedmann wrote: > > Hi Adrian, > > > > I guess you mean: > > ifconfig wlan0 regdomain ETSI > > or > > ifconfig wlan0 country DE > > > > But this makes no difference. I only have the channels 1-11. > > > > And "ifconfig wlan0" is always showing the correct: > > "regdomain ETSI country DE" > > > > > > Of course, I don't understand why it isn't enough to set "country DE" in > "/etc/rc.conf"? > > > > > > From "man ifconfig" --> country: > > | Set the country code to use in calculating the regulatory con- > > | straints for operation. In particular the set of available chan- > > | nels, how the wireless device will operation on the channels, and > > > > > > From "man regdomain" (The regdomain.xml file): > > | This information is used by the ifconfig(8) program to construct > regula- > > | tory state for download to the system. > > > > > > And in "/etc/regdomain.xml" I have: > > | > > | ETSI > > | 0x30 > > | > > | > > | > > | 30 > > | IEEE80211_CHAN_B > > | > > | > > | > > | > > | > > | 30 > > | IEEE80211_CHAN_G > > | > > | > > | ... > > > > 2412 is channel 1 > > 2472 is channel 13 > > > > Regards, > > Carsten > > > > -------- Original-Nachricht -------- > >> Datum: Fri, 28 Dec 2012 06:29:19 -0800 > >> Von: Adrian Chadd > >> An: Carsten Wiedmann > >> CC: freebsd-wireless@freebsd.org > >> Betreff: Re: kern/174722: [wlan] can\'t use channel 12 and 13 (14) with > my wifi interface > > > >> Hm, ok, so try: > >> > >> ifconfig wlan0 down > >> ifconfig wlan0 ecm > >> ifconfig wlan0 regdomain DE > >> ifconfig wlan0 up > >> ifconfig wlan0 list channel > >> > >> > >> > >> Adrian > >> > >> > >> On 28 December 2012 04:50, Carsten Wiedmann > wrote: > >> > The following reply was made to PR kern/174722; it has been noted by > >> GNATS. > >> > > >> > From: "Carsten Wiedmann" > >> > To: bug-followup@FreeBSD.org, carsten_sttgt@gmx.de > >> > Cc: > >> > Subject: Re: kern/174722: [wlan] can't use channel 12 and 13 (14) > with > >> my wifi > >> > interface > >> > Date: Fri, 28 Dec 2012 13:47:59 +0100 > >> > > >> > Hmmm, doesn't work: > >> > > >> > freebsd# ifconfig wlan0 list regdomain > >> > :regdomain ETSI country DE anywhere ecm > >> > Channel 1 : 2412 MHz 11b Channel 6 : 2437 MHz > >> 11g > >> > Channel 1 : 2412 MHz 11g Channel 7 : 2442 MHz > >> 11b > >> > Channel 2 : 2417 MHz 11b Channel 7 : 2442 MHz > >> 11g > >> > Channel 2 : 2417 MHz 11g Channel 8 : 2447 MHz > >> 11b > >> > Channel 3 : 2422 MHz 11b Channel 8 : 2447 MHz > >> 11g > >> > Channel 3 : 2422 MHz 11g Channel 9 : 2452 MHz > >> 11b > >> > Channel 4 : 2427 MHz 11b Channel 9 : 2452 MHz > >> 11g > >> > Channel 4 : 2427 MHz 11g Channel 10 : 2457 MHz > >> 11b > >> > Channel 5 : 2432 MHz 11b Channel 10 : 2457 MHz > >> 11g > >> > Channel 5 : 2432 MHz 11g Channel 11 : 2462 MHz > >> 11b > >> > Channel 6 : 2437 MHz 11b Channel 11 : 2462 MHz > >> 11g > >> > > >> > BTW: > >> > Even "ifconfig wlan0 ecm" is changing this setting, I can't find > "ecm" > >> in "man ifconfig"? > >> > > >> > _______________________________________________ > >> > 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 Sat Dec 29 12:30:02 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C7C95D0 for ; Sat, 29 Dec 2012 12:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 025F88FC0C for ; Sat, 29 Dec 2012 12:30:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBTCU1of000392 for ; Sat, 29 Dec 2012 12:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBTCU1vt000391; Sat, 29 Dec 2012 12:30:01 GMT (envelope-from gnats) Date: Sat, 29 Dec 2012 12:30:01 GMT Message-Id: <201212291230.qBTCU1vt000391@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: "Carsten Wiedmann" Subject: Re: kern/174661: [wlan] lost alias on wlan interface X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Carsten Wiedmann 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: Sat, 29 Dec 2012 12:30:02 -0000 The following reply was made to PR kern/174661; it has been noted by GNATS. From: "Carsten Wiedmann" To: bug-followup@FreeBSD.org, carsten_sttgt@gmx.de Cc: Subject: Re: kern/174661: [wlan] lost alias on wlan interface Date: Sat, 29 Dec 2012 13:23:31 +0100 Well, in "production" setup I'm using the 1st alias for a jail with my mailsserver. And every time I lost this alias, I can't connect to/from my mailserver :-/ If anyone else has this problem too... As a workaround I'm defining my aliases like: | ifconfig_wlan0_alias0="inet 192.168.0.200 netmask 255.255.255.255" | ifconfig_wlan0_alias1="inet 192.168.0.201 netmask 255.255.255.255" | ifconfig_wlan0_alias2="inet 192.168.0.202 netmask 255.255.255.255" And I don't use "192.168.0.200" anywhere. Thus it doesn't matter if I lost this alias. -------- Original-Nachricht -------- > Datum: Sun, 23 Dec 2012 19:00:00 GMT > Von: FreeBSD-gnats-submit@FreeBSD.org > An: Carsten Wiedmann > Betreff: Re: kern/174661: lost alias on wlan interface > Thank you very much for your problem report. > It has the internal identification `kern/174661'. > The individual assigned to look at your > report is: freebsd-bugs. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=174661 > > >Category: kern > >Responsible: freebsd-bugs > >Synopsis: lost alias on wlan interface > >Arrival-Date: Sun Dec 23 19:00:00 UTC 2012