From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 3 10:22:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D835BB30 for ; Sun, 3 Mar 2013 10:22:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 4B867E11 for ; Sun, 3 Mar 2013 10:22:55 +0000 (UTC) Received: by mail-we0-f172.google.com with SMTP id x10so3731807wey.3 for ; Sun, 03 Mar 2013 02:22:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=R7cw9KUc+An59ThVC1/OxdjIJ1lzOPE7pPPJnfnu4tI=; b=E6YqfNi0qrNz3UlZDxZK9kjk9BmQr4iP64okJPVVJu6YrdkoYREfmiXfYkpiB5Ia/b cIico+yg8+cE+UFRIZIT4kjZSz4eSU9B+j30oIxT3ryWehXoCjn0hHiOI2K5rr4IYnL9 KtjXfLTQ+qPq6mRoFwQAcshYxqee/YCqD3kW8ckajKOOjZiqtfJ9nUzMFUoQeD+D+AcI FSylxEfYZJpo7u48jbnHQB54Zyxc2/c0zM+eLNFfcaaIu+oeMcFax6WPI08VmLR2Wx+b mdsW4tzMu/ej1PuKPbYA7ePV3Z+RL2NRDNDKry9EM17W4U9lMO55kGZ/cpOxJDKJbCai Dwvg== MIME-Version: 1.0 X-Received: by 10.180.97.233 with SMTP id ed9mr5952577wib.32.1362306174173; Sun, 03 Mar 2013 02:22:54 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Sun, 3 Mar 2013 02:22:54 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Mar 2013 02:22:54 -0800 X-Google-Sender-Auth: hxL6quu90kT-ImD01tWM0xTlN1s Message-ID: Subject: Re: [RFC] net80211 TX, take 4 (final) From: Adrian Chadd To: 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: Sun, 03 Mar 2013 10:22:55 -0000 Hi, I have finished this round of work, intended for -HEAD. Besides the stuff in the ath and iwn driver, here's what I'd like to commit: http://people.freebsd.org/~adrian/ath/20130303-net80211_tx-1.diff What it implements: * the code that transmits a VAP frame is now in ieee80211_start_pkt(). I may rename that to something vap like later * nothing calls if_transmit() direct - it goes via ieee80211_parent_transmit() or ieee80211_vap_transmit() * nothing calls ic_raw_xmit() direct - it calls via ieee80211_raw_output() * the VAP TX and parent TX path is locked using an ieee80211com TX lock - until the parent transmit code is serialised (eg via a taskqueue to do deferred transmit, or a specific ic TX lock) this lock will be used both to serialise the VAP / STA TX state (ie, sequence numbers and general VAP TX ordering) and enforcing the same ordering is occuring during driver handoff * tidy up the parent/vap TX code in hostap recv_pspoll() * tidy up the hwmp discover completion code which dispatches frames from the staging queue - those frames aren't encapsulated, so just call ieee80211_vap_transmit() I'd appreciate thorough testing with INVARIANTS and WITNESS enabled for hostap, sta and mesh modes. I'll likely commit the non-locking changes soon - ie, the ieee80211_parent_transmit(), ieee80211_vap_transmit(), ieee80211_raw_output() changes. Those seem no brainers - the only later optimisation would be to turn them into inlines in ieee80211_freebsd.h . I've verified that this patch applies cleanly to the latest -HEAD. Thanks! Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 4 02:11:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B170055C for ; Mon, 4 Mar 2013 02:11:57 +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 52B5E34E for ; Mon, 4 Mar 2013 02:11:57 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id ez12so1397380wid.12 for ; Sun, 03 Mar 2013 18:11:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=GScJAg4KCEq9LWOIxXrelEhuzBAJj5/m/SdgTZHU/SY=; b=ul9h43EB0J48QzDLTFLntOt45h4JnwvRtiH5Bk1Yt5af1TlHWoWFxHPUtNLh0ssaRq +5m8VUE3K9Ogc6bcUThr/Dam/0YDxxOP0AsXkiQc0uCyD0qsxpLH3CZpAmVhcm8w28bZ RFUUw+7bvvc6hTBHnh0NbajOo+yf5s29sF26RvmXoiRPPY1i5hBCNpN49krdiZuWjrmZ LtAfImzNNOA0tpa3nSDYW08b4USgH6gSq9XkDADavvwTMOW6KCJBKTRTIzyR0T9b8CDk KYvnfdA9nAwviBQUmkfrUHLGNMGiNu409U90YjIciT6M56GLRQZKPRZG/0Thq8jf6HG4 4xiA== MIME-Version: 1.0 X-Received: by 10.194.20.40 with SMTP id k8mr28962757wje.16.1362363110485; Sun, 03 Mar 2013 18:11:50 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Sun, 3 Mar 2013 18:11:50 -0800 (PST) In-Reply-To: References: Date: Sun, 3 Mar 2013 18:11:50 -0800 X-Google-Sender-Auth: eDc9RWQWiEe9wbkHCrj9f0x8e9w Message-ID: Subject: Re: [RFC] net80211 TX, take 4 (final) From: Adrian Chadd To: 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: Mon, 04 Mar 2013 02:11:57 -0000 Hi, So this stuff breaks Monthadar's meshing code. The mesh forwarding stuff takes mesh frames in mesh_input() that are destined for another node and potentially stuffs them back into the parent transmit queue, bypassing the rest of the stack. This has a bunch of potential interesting implications, like how exactly sequence numbers, encryption, power save and aggregation are supposed to work. Since the forwarded packets are being forwarded direct to the driver, there's no nice place to tie in things like power save. I don't know what the right thing to do is - should the frames be de-encapsulated and then reinjected into the VAP but with an already resolved destination node? Or? I'm open to other suggestions. I'm happy to just "fix" the mesh code right now to not panic with the locking work that I'm currently doing. But we do need to fix this. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 4 11:06:52 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9D5CBF7A for ; Mon, 4 Mar 2013 11:06:52 +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 8F895E71 for ; Mon, 4 Mar 2013 11:06:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r24B6q9P038968 for ; Mon, 4 Mar 2013 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r24B6qEb038966 for freebsd-wireless@FreeBSD.org; Mon, 4 Mar 2013 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Mar 2013 11:06:52 GMT Message-Id: <201303041106.r24B6qEb038966@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, 04 Mar 2013 11:06:52 -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/176238 wireless [ath] [patch] Correct buffer size calculation and simp o kern/176201 wireless [net80211] [patch] 11n station includes unrelated ht p o kern/176104 wireless [iwn] iwn0: iwn_intr: fatal firmware error o kern/175870 wireless [iwn] /etc/rc.d/netif restart cause system crash o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i 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/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. 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/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 153 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 4 17:50:52 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 81CB2BE6 for ; Mon, 4 Mar 2013 17:50:52 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4D86AAB6 for ; Mon, 4 Mar 2013 17:50:49 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:9421:367:9d7d:512b]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 3C9BA4AC57 for ; Mon, 4 Mar 2013 21:50:41 +0400 (MSK) Date: Mon, 4 Mar 2013 21:50:39 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <779060320.20130304215039@serebryakov.spb.ru> To: freebsd-wireless@FreeBSD.org Subject: Does ath in 802.11g builds map of client <-> antenna "distance"? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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, 04 Mar 2013 17:50:52 -0000 Hello, Freebsd-wireless. Situation (theoretical one, I didn't try it, but I'm thinking about WiFi coverage of my parent's cottage and lot): WiFi card with 2 antennas, in 802.11g (or single-channel 802.11n) mode. Both antennas are attached, but they are directed )not uni-directional, but something with 180 degree or less diagram), and they are "see" different sectors (and different clients). Will it work? will card/driver understand, that different packets should be sent via different antennas? -- // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 4 19:34:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 025C6EAF; Mon, 4 Mar 2013 19:34:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 7517CFD6; Mon, 4 Mar 2013 19:34:54 +0000 (UTC) Received: by mail-we0-f173.google.com with SMTP id r5so4725239wey.4 for ; Mon, 04 Mar 2013 11:34:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=aZEH7t4vzaW0rHuGAR7AHuGkT2E+U+XlVGPO5VQ2ye8=; b=QWgnjpg+d1wQstunW+Qpocr8r/qjvIuM3CeN1GoEbpMzzeWAxm97LThK0TkWc7/PCX /ZWUPNnWORDQSDSuNovcgzJyOSLuY/3mh1VoJo61a6tOqs9DOuiWslPXzGY/H4S5/wQ8 g0aWxMYzg2sNmmoeH/nrTF9yJaS9cwOnnCuJDog8Z/UQfabMsBw13XfjtdiI14yHUrs0 QJDjr2IMwBn29ZcU/NP2ZHR+6dEs2SjqaM+KmXZlkP2p5M6NeJ7fcQ+JDsSIB82c7lOs aDPwqIMMy+2IsyVTsyaQoTIh7xnqy3+MiVfBsSYTF8ZCsEZ5R13Yx9Z8S6W5Fnx68Ola GsFQ== MIME-Version: 1.0 X-Received: by 10.180.108.3 with SMTP id hg3mr13856261wib.33.1362425693686; Mon, 04 Mar 2013 11:34:53 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Mon, 4 Mar 2013 11:34:53 -0800 (PST) In-Reply-To: <779060320.20130304215039@serebryakov.spb.ru> References: <779060320.20130304215039@serebryakov.spb.ru> Date: Mon, 4 Mar 2013 11:34:53 -0800 X-Google-Sender-Auth: ijPEhN6R51tmq8jQAwbZ0nsfizg Message-ID: Subject: Re: Does ath in 802.11g builds map of client <-> antenna "distance"? From: Adrian Chadd To: Lev Serebryakov 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: Mon, 04 Mar 2013 19:34:55 -0000 On 4 March 2013 09:50, Lev Serebryakov wrote: > Hello, Freebsd-wireless. > > Situation (theoretical one, I didn't try it, but I'm thinking about > WiFi coverage of my parent's cottage and lot): WiFi card with 2 > antennas, in 802.11g (or single-channel 802.11n) mode. Both antennas > are attached, but they are directed )not uni-directional, but > something with 180 degree or less diagram), and they are "see" > different sectors (and different clients). Will it work? will > card/driver understand, that different packets should be sent via > different antennas? Performance will suck. For lots of reasons. :-) You're better off with two NICs, one per directional antenna. The driver and NIC does try to "probe" which antenna to send frames out and keep that in the keycache. But it's not going to be 100% correct. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 4 20:58:59 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2B382629 for ; Mon, 4 Mar 2013 20:58:59 +0000 (UTC) (envelope-from onyx@z-up.ru) Received: from mx.z-up.ru (mx.z-up.ru [92.241.12.98]) by mx1.freebsd.org (Postfix) with ESMTP id DB54E14B9 for ; Mon, 4 Mar 2013 20:58:58 +0000 (UTC) Received: from onyx-y550p.loc (unknown [92.241.12.59]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.z-up.ru (Postfix) with ESMTPSA id 6CA5E11464 for ; Tue, 5 Mar 2013 00:49:46 +0400 (GMT-4) From: Dmitry Kolosov To: freebsd-wireless@freebsd.org Subject: Max wireless throughput Date: Tue, 5 Mar 2013 00:49:49 +0400 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; i386; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201303050049.50218.onyx@z-up.ru> X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: onyx@z-up.ru 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, 04 Mar 2013 20:58:59 -0000 Hello dear FreeBSD users! What is maximum wireless throughput you have reached (seen) on -STABLE (mean 11g only mode)? I have 54Mbps as for `ifconfig` and 24-28Mbps as for file fransfer (nfs). HostAP hardware is: ath0@pci0:5:0:0: class=0x028000 card=0x3a781186 chip=0x0029168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR922X Wireless Network Adapter' class = network And STA hardware is: ath0@pci0:6:0:0: class=0x028000 card=0x30a117aa chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9285 Wireless Network Adapter (PCI-Express)' class = network The second question is - what max wireless throughput i can reach on such hardware on -STABLE? Thanks in advance! From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 4 21:06:36 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B9A8570E for ; Mon, 4 Mar 2013 21:06:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by mx1.freebsd.org (Postfix) with ESMTP id 4A55E150D for ; Mon, 4 Mar 2013 21:06:36 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id t11so5112366wey.0 for ; Mon, 04 Mar 2013 13:06:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=lLfmcPwjVIJg9CN/fQz5/v3I7MGoH06+ykXPXef2f9w=; b=UcPomoRsWsvImDTyRPGWJtnIyURAoFzy2z9g/CL3oox72kJ9bOWBsdHdC5JfKEkbwu KqyI5sQ5U+cG+KVKI1gXimiUES8bcqsmLJogsTI1+hNSOerJlHBTy/s2K+zDOXPCKKDm cE++e5ix0nr4fObxrKD3MRDDBINnF2/cfBOLZ1ysXOw4ez5yLUocH3s1D5+WhGoz36ZC 3xvD+IfDDmp0iscYZp6zEaGTflZ//uIGXqBLEQBc2Dh7SDlWamfQYW4VG41LiWnKOQtg bisDkXvqdsIHdcP57F98BlFZws0iDA2nr1tk6zJBfvgClLMwaX3gOVJcYOBT1uBwns1b mxcw== MIME-Version: 1.0 X-Received: by 10.194.110.69 with SMTP id hy5mr34898764wjb.1.1362431195235; Mon, 04 Mar 2013 13:06:35 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Mon, 4 Mar 2013 13:06:35 -0800 (PST) In-Reply-To: References: <201303050049.50218.onyx@z-up.ru> Date: Mon, 4 Mar 2013 13:06:35 -0800 X-Google-Sender-Auth: H8NtDW_hrY7oRb398zmS3A2j2HI Message-ID: Subject: Re: Max wireless throughput From: Adrian Chadd To: onyx@z-up.ru 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: Mon, 04 Mar 2013 21:06:36 -0000 .. and it's an 11n 1x1 NIC that can do either 20 or 40MHz wide channels. So if you're running -HEAD you can get upwards of 100mbit on TCP. Adrian On 4 March 2013 13:05, Adrian Chadd wrote: > Yup, that's what you expect for OFDM 54MB rates. > > Why do you ask? > > > > Adrian > > On 4 March 2013 12:49, Dmitry Kolosov wrote: >> Hello dear FreeBSD users! >> What is maximum wireless throughput you have reached (seen) on -STABLE (mean >> 11g only mode)? I have 54Mbps as for `ifconfig` and 24-28Mbps as for file >> fransfer (nfs). >> HostAP hardware is: >> ath0@pci0:5:0:0: class=0x028000 card=0x3a781186 chip=0x0029168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR922X Wireless Network Adapter' >> class = network >> And STA hardware is: >> ath0@pci0:6:0:0: class=0x028000 card=0x30a117aa chip=0x002b168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR9285 Wireless Network Adapter (PCI-Express)' >> class = network >> The second question is - what max wireless throughput i can reach on such >> hardware on -STABLE? >> Thanks in advance! >> _______________________________________________ >> 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 Mon Mar 4 21:12:01 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 51F58937 for ; Mon, 4 Mar 2013 21:12:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id E94BC1560 for ; Mon, 4 Mar 2013 21:12:00 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id k14so4893532wer.39 for ; Mon, 04 Mar 2013 13:12:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=b/rl6V/y19K5j0bviUi3xT3bgY5EuErzhbLMPjpq6gg=; b=y8KRUJVolCMFWa/42Jl4nHJe2+50elOjr1nIqJKeXTzWPpiXKGJqGwt93bBl2+GNu2 3wQYBuAM+0rKWovARAX5BvKgvO7lJGfudv7HJl9uxvSHJFi9FRElPBYGU7AmgMQd1ftr OoycWpKe4Q6iTyk+vBxHLjhjmYeXjCAHrKC4L1xXX1IfMsKpX7EnHWMrb05fnDvFQSac o7KcwwdUK63GXFkbYkUfimvVO9h8NELGrIxQRS5XESSWIy+vPdxQCzQurOjkBHVQT5vT kdvKjjutP55PTB+Z5pca/pqcUkksSXrG855CSJFlWKPtOJk3bHXYfRiSrNd/vgPl6B9J ibng== MIME-Version: 1.0 X-Received: by 10.180.108.3 with SMTP id hg3mr14277475wib.33.1362431137457; Mon, 04 Mar 2013 13:05:37 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Mon, 4 Mar 2013 13:05:37 -0800 (PST) In-Reply-To: <201303050049.50218.onyx@z-up.ru> References: <201303050049.50218.onyx@z-up.ru> Date: Mon, 4 Mar 2013 13:05:37 -0800 X-Google-Sender-Auth: WvvQMZEWUG3virt6Kjxo5Xbihjk Message-ID: Subject: Re: Max wireless throughput From: Adrian Chadd To: onyx@z-up.ru 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: Mon, 04 Mar 2013 21:12:01 -0000 Yup, that's what you expect for OFDM 54MB rates. Why do you ask? Adrian On 4 March 2013 12:49, Dmitry Kolosov wrote: > Hello dear FreeBSD users! > What is maximum wireless throughput you have reached (seen) on -STABLE (mean > 11g only mode)? I have 54Mbps as for `ifconfig` and 24-28Mbps as for file > fransfer (nfs). > HostAP hardware is: > ath0@pci0:5:0:0: class=0x028000 card=0x3a781186 chip=0x0029168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR922X Wireless Network Adapter' > class = network > And STA hardware is: > ath0@pci0:6:0:0: class=0x028000 card=0x30a117aa chip=0x002b168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR9285 Wireless Network Adapter (PCI-Express)' > class = network > The second question is - what max wireless throughput i can reach on such > hardware on -STABLE? > Thanks in advance! > _______________________________________________ > 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 Mar 9 18:54:56 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D163296B for ; Sat, 9 Mar 2013 18:54:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by mx1.freebsd.org (Postfix) with ESMTP id 4CA8B646 for ; Sat, 9 Mar 2013 18:54:56 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id e12so3747710wge.22 for ; Sat, 09 Mar 2013 10:54:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=Xf9o2SjZ6tr3uzbsV8fMvtGYtW7hVmWqmrtPzxLYUdU=; b=ORFPLLMzes8NAONIXP6tJW02tunJnXOGoJeFM5JHyTaytSHTWjIyasDsruOs719cZ2 qSf2raIQ99VSzDR4Ev5kiKHrrL98isYgqctwtBY1Z50//W5Btl/lGPIoY1RhsxRZWpSN F0Ztbmwmffttk4sX7U6NWsy8g9mfRKKx22TmCgpZPvlAYINluv3S6bdfLMrKlxVGiWh2 KBEG5IVL79HT+BiG8GGgoecEp3vu5v47HqHcyGREVg/C2w1Cb0f+BJXCM+/AKa4O8co2 Uvkm3Uq7+WKj5nfoQLxQDHzfvnCqsUEai2W5z2sUOqFTP7QrqKIMf9edoHZQvGdbn1UP iB1w== MIME-Version: 1.0 X-Received: by 10.180.97.233 with SMTP id ed9mr4589415wib.32.1362855295128; Sat, 09 Mar 2013 10:54:55 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.111.201 with HTTP; Sat, 9 Mar 2013 10:54:54 -0800 (PST) Date: Sat, 9 Mar 2013 10:54:54 -0800 X-Google-Sender-Auth: YXK9wkkQUm5jhIRYebCAc9KRNJ0 Message-ID: Subject: Fine, OK, here's my initial AR9380/AR9485 support From: Adrian Chadd To: 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: Sat, 09 Mar 2013 18:54:56 -0000 I finally got the legal all-clear to push this open source version of the QCA mainline HAL into open source. So, without further ado: https://github.com/qca/ The open HAL is there. I then forked it: https://github.com/erikarn/qcamain_open_hal_public .. and then I created a branch, called local/freebsd, which has the FreeBSD specific changes needed to make this thing work. Now, I'm going to prefix this by saying: "This stuff can break your hardware. Only run it if you're willing to debug and diagnose issues. Yes, this means you. I don't take any responsibility for your equipment or whether this breaks the RF around you. Don't be a dick. It's your responsibility." What's tested: * legacy, 1x1 and 2x2 HT20/HT40, STA mode * AR9380 (1x1, 2x2 - 2/5ghz) * AR9485 (1x1, 2ghz only) What's not tested: * Any hostap, mesh, tdma, adhoc modes * _ANY_ 3x3 operation * .. pretty much everything. * ar9390/ar9590/ar9462 - but they _SHOULD_ work! There's a lot missing. There's no MSI support just yet. There's no optimal TX or RX path just yet. There's likely all kinds of weird behaviour in AP mode. Heck, STA mode is likely full of hilarity. ANI is full of hacks just so I don't have to finish writing it up. The statistics counters are likely somewhat whacked, as I've stubbed some of those functions out too. There's no PAPRD calibration, so you won't get full TX power at the higher TX rates. Heck, the TX power may even be totally garbage; I haven't yet sat down and written an EVM test suite to check that everything is fine. So if you want to test it - please note that I'm not going to be able to help you figure out what is or isn't working. I'm still busy fixing up other issues on previous NICs. But the code is here; I'll take debugging, diagnostics and diffs. :-) So, the 30 second version: * Clone this: https://github.com/erikarn/qcamain_open_hal_public * switch to the local/freebsd branch * Do this in your -HEAD checkout: $ cd sys/dev/ath/ath_hal/ar9003/ $ ln -s /path/to/git/qcamain_open_hal_public/hal/ar9300/* . * Edit the ath makefile - sys/modules/ath/Makefile - and remove the comments in front of the AR9300 .PATH and SRCS lines * Rebuild your kernel/modules I'm not going to whack this into -HEAD until I've finished off some other stuff. But it's there, and it's public. Adrian