From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 13 23:09:02 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 47A34573 for ; Sun, 13 Oct 2013 23:09:02 +0000 (UTC) (envelope-from ericturgeon.bsd@gmail.com) Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 197B22C64 for ; Sun, 13 Oct 2013 23:09:02 +0000 (UTC) Received: by mail-ie0-f170.google.com with SMTP id x13so13780607ief.29 for ; Sun, 13 Oct 2013 16:09:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=IIo/vgbIZh8edoCpaD+m/jnvDm2De801GyzXGGvE0Tg=; b=v+XObL46JyDCzIeZ8+vUfzlkRzHQ7LkpHpwbNIrLhYQc0fO0ejKzGazOCr118jHndg k3GcfZ8KqXhlrjS/A10qYz+7Wuwk3mRs1cSmEvYNBrK24zwOSlNNFMI/ExnnrV1iF4WS xJ3lDHZ/5P1grj2PwNpXaq8jVNvDfFh2uIfy9CN5DPbvDITEV32bVvH0AryDdv9a9Ars ocQUNmyO2BUDs/usWDUedx3NV5D7A/vaan79ETi5Q+7lJUVr87+glGCvdgDAi0LA9QWk s10Qf2bhZo0cou4tx/zYe5ZMoMSB54izgVXPYyXx0jpKQdXDfVGr66E3YFWQ1W6XKHET hmKw== X-Received: by 10.42.189.132 with SMTP id de4mr2167027icb.35.1381705741169; Sun, 13 Oct 2013 16:09:01 -0700 (PDT) Received: from ericbsd.ghostbsd.org (CPEc8fb2647578c-CMc8fb26475789.cpe.net.cable.rogers.com. [99.252.37.230]) by mx.google.com with ESMTPSA id m1sm17341326igj.10.2013.10.13.16.09.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Oct 2013 16:09:00 -0700 (PDT) Message-ID: <525B2802.5050904@gmail.com> Date: Sun, 13 Oct 2013 20:08:50 -0300 From: Eric Tugeon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20131004 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Wireless API Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Sun, 13 Oct 2013 23:09:02 -0000 Hi, I work on a Python GTK network manager for FreeBSD/GhostBSD, it will look similar to https://projects.gnome.org/NetworkManager/. I want to know if we have wireless API like connection percentage? From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 13 23:57:21 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7B44BC4F for ; Sun, 13 Oct 2013 23:57:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x229.google.com (mail-qe0-x229.google.com [IPv6:2607:f8b0:400d:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3D4C72DF3 for ; Sun, 13 Oct 2013 23:57:21 +0000 (UTC) Received: by mail-qe0-f41.google.com with SMTP id x7so3617030qeu.28 for ; Sun, 13 Oct 2013 16:57:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=rKeFVfMMv9FeL/6vqN8GNdqRc4fW7xAZCRS2GY1Qt2o=; b=B7a4mn1Z58xo8L3ohy7YlWmF4i7wv6S2ECRtmFCFaAhl4tLuAeK79bqCZLNDixV0V3 /5OMPdqOvkji50h93NtYKOhaNxNk5kGpU3p6Y0GkW77FbrAJVIr0v4Fg8DAHQ9Egpjf5 TsjjRLbNAEhUhjsieTdfoCiW6v7bZkAtVRnJ6NhE9wjMGOkefv16TSc7+4ToqVH3hrsQ Mv3YO4kGKJKAoUPgKp+7BLESJLIQckdiUC/ghG0YYuS8Kd2KOExTMtBfUScLTOow43OS gN/vVaXpRr0kP67qYEv9O8ECoctw5gJDU8Ku8e/jwM5bHLcVHtFTpZcsbY1I3WXfSdt2 mB3Q== MIME-Version: 1.0 X-Received: by 10.224.11.133 with SMTP id t5mr19014012qat.34.1381708639228; Sun, 13 Oct 2013 16:57:19 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sun, 13 Oct 2013 16:57:19 -0700 (PDT) In-Reply-To: <525B2802.5050904@gmail.com> References: <525B2802.5050904@gmail.com> Date: Sun, 13 Oct 2013 16:57:19 -0700 X-Google-Sender-Auth: 4hXKIKSOfe6v2jq9DkM4kMDp3WQ Message-ID: Subject: Re: Wireless API From: Adrian Chadd To: Eric Tugeon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Sun, 13 Oct 2013 23:57:21 -0000 What do you mean like "connection percentage" ? Do you mean like signal strength? If so, then yes. You can then make some basic heuristic guesses mapping signal level / RSSI to a connection percentage based on some assumptions. For example, you could look at the minimum RSSI required to guarantee some decent stability at each receive/transmit rate (from 1mbit->54mbit, then MCS1->MCS23) and then use that to map out connection percentage (where stable at MCS0 / 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.) HTH, -adrian On 13 October 2013 16:08, Eric Tugeon wrote: > Hi, > I work on a Python GTK network manager for FreeBSD/GhostBSD, it will look > similar to https://projects.gnome.org/**NetworkManager/. > I want to know if we have wireless API like connection percentage? > ______________________________**_________________ > 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 Oct 14 00:09:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 272CFD61; Mon, 14 Oct 2013 00:09:40 +0000 (UTC) (envelope-from ericturgeon.bsd@gmail.com) Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EFF4B2E66; Mon, 14 Oct 2013 00:09:39 +0000 (UTC) Received: by mail-pb0-f51.google.com with SMTP id jt11so6656176pbb.10 for ; Sun, 13 Oct 2013 17:09:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q0iYm8mpCPdmWR3KYppv4MVPdSe0oxrYJ1yHdMfE5uM=; b=MDtuK2yUN1K2NfyYDKkd5xbGIodr0/Qk8HKrPtCxCI3pM9iOTIceROpzS3RHKYpt71 W/S6j6H/866jXDswTEa4n+mUPcOU2dVVs/NO52NXxj4hA+x4c1bSbsqwx+hUQIE7aHVG X8UgF83GOfLDA0PUL+NBbMCDziSMuhLcTQ0I0cX8jJJJd02zhKrEdqer4nzxZYbelqzP 2hZFJn6miEd9oTM/xD/0riVsDgGnMlRdm6QAjW9QqKpzyIxYMfwjlGttYonJDJTVCOSI 5FFmjR1mmtv1o9mHz7ckr5uYHEzGYFKR3NFvAN32T1DlunHLLlR50LI0iCS0LG/DOAO3 5XsQ== MIME-Version: 1.0 X-Received: by 10.66.163.164 with SMTP id yj4mr35117845pab.91.1381709379571; Sun, 13 Oct 2013 17:09:39 -0700 (PDT) Received: by 10.68.200.136 with HTTP; Sun, 13 Oct 2013 17:09:39 -0700 (PDT) In-Reply-To: References: <525B2802.5050904@gmail.com> Date: Sun, 13 Oct 2013 21:09:39 -0300 Message-ID: Subject: Re: Wireless API From: Eric Turgeon To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 14 Oct 2013 00:09:40 -0000 Were is the documentation for that API. On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd wrote: > What do you mean like "connection percentage" ? > > Do you mean like signal strength? If so, then yes. > > You can then make some basic heuristic guesses mapping signal level / RSSI > to a connection percentage based on some assumptions. For example, you > could look at the minimum RSSI required to guarantee some decent stability > at each receive/transmit rate (from 1mbit->54mbit, then MCS1->MCS23) and > then use that to map out connection percentage (where stable at MCS0 / > 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.) > > HTH, > > > > -adrian > > > > On 13 October 2013 16:08, Eric Tugeon wrote: > >> Hi, >> I work on a Python GTK network manager for FreeBSD/GhostBSD, it will look >> similar to https://projects.gnome.org/**NetworkManager/. >> I want to know if we have wireless API like connection percentage? >> ______________________________**_________________ >> 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 " >> > > -- *Eric Turgeon **GhostBSD project* Office location: 1-11 connaught Moncton NB Canada www.ghostbsd.org From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 14 11:06:58 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9AE2057E for ; Mon, 14 Oct 2013 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 870B42C9B for ; Mon, 14 Oct 2013 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9EB6woM035399 for ; Mon, 14 Oct 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9EB6whn035397 for freebsd-wireless@FreeBSD.org; Mon, 14 Oct 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Oct 2013 11:06:58 GMT Message-Id: <201310141106.r9EB6whn035397@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, 14 Oct 2013 11:06:58 -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/181898 wireless [iwn] [patch] Centrino Advanced-N 6235 with latest iwn o kern/181694 wireless [iwn] [patch] Initialize hardware in iwn(4) resume cod o kern/181161 wireless [wl] config a old compaq wl-110 wireless card make ker o kern/181132 wireless [iwn] stream calculation is wrong for the Intel 4965 o kern/181100 wireless [bwi] Turning up bwi0 crashes / deadlocks the kernel o kern/180816 wireless [iwl] Intel Centrino Wireless-N 2200 not supported o kern/179847 wireless [ath] [patch] Update regdomain in ath drivers includin o kern/179709 wireless [ath] Atheros 5212 does not work: stuck beacon; resett o kern/179547 wireless [ath] Add AR9485 custom board fixes (CUS198) o kern/179482 wireless [ath] [patch] Fix AR9462 external LNA configuration o kern/179269 wireless [ath] [AR9285] RX antenna diversity is not functioning o kern/179232 wireless [ath] panic in ath o kern/178986 wireless [ath] Change mac address of ath(4) is not reflected wh o kern/178492 wireless [ath] ath0 (AR9287) panic o kern/178491 wireless [ath] ath0 (AR9287) stuck beacon o kern/178477 wireless [ath] missed beacon / soft reset in STA mode results i o kern/178470 wireless [panic][ath] bss vap can and does change o kern/178411 wireless [ral] [panic] FreeBSD kernel crash in rt2860 o kern/178379 wireless [net80211] [ath] WPA rekey on the STA side fails when o kern/178378 wireless [net80211] crypto state isn't reset during a reassocia o kern/178263 wireless [ath] review the use of ic_freq / ic_ieee / ic_flags / o kern/177847 wireless [ath] With TPC enabled, TX power values aren't clamped o kern/177846 wireless [ath] [net80211] net80211 TX power limit isn't correct o conf/177688 wireless WiFi regodmains information is inconsistent between "e o kern/177530 wireless [ath] ath driver isn't 32 bit int clean o kern/177465 wireless [iwn] 20%-100% packet loss with iwn driver o kern/177451 wireless [ieee80211] page fault in ieee80211_tx_mgt_timeout 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/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/170411 wireless [ath] Uninitialized variables in if_ath.c 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/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 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 178 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 14 15:01:36 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7EF3DFAA for ; Mon, 14 Oct 2013 15:01:36 +0000 (UTC) (envelope-from sean_bruno@yahoo.com) Received: from nm3-vm4.bullet.mail.gq1.yahoo.com (nm3-vm4.bullet.mail.gq1.yahoo.com [98.136.218.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2EEB32E6D for ; Mon, 14 Oct 2013 15:01:35 +0000 (UTC) Received: from [98.137.12.189] by nm3.bullet.mail.gq1.yahoo.com with NNFMP; 14 Oct 2013 15:01:29 -0000 Received: from [208.71.42.194] by tm10.bullet.mail.gq1.yahoo.com with NNFMP; 14 Oct 2013 15:01:29 -0000 Received: from [127.0.0.1] by smtp205.mail.gq1.yahoo.com with NNFMP; 14 Oct 2013 15:01:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381762889; bh=gpd6F++ya2JeCCRwq9lmW8VqZdy2/Kwq2kV3PgBTX+w=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=XFgFOYjnPKXGY7AtMQQyxGjnV0QS0ddERBWIuEp33XBAjvsHA5Dcb4EodjxYBlGov3WYV4RNCHdHhuXbQkN13fHXWsI8plKdX9ED1fFtIBbAv7BCPJqAlKSzF89VPvxOfF4CeOX62+E40qczdlRLyvqSnLLc4dovOdztgZ/phlA= X-Yahoo-Newman-Id: 428384.64233.bm@smtp205.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: KfzpAnYVM1nomLYkIVgqXXD67REmxM.Md91iL01QT.9e0.t rGvnuPOFfyOR09yp24U4JLdFp0UQUvvG8R.5IplE8vTBM4s6lFbVM0NCsIhQ Xhrv48ySAicKl3dslpFEKSxNCxU60Ac7bXimFSpOCl_W7ToBINMD81uUQzdG zDEH8X1aoi_Hl.VmKr1sar3G1ULkoX7Dodyg3Twllwukg4Ff_WniyM06SncN xGYrnlhnHoj.n15sD1pMEo63N_dFgsCIWEVurEOZItZUUBy38tunu2xkYmlg ysvVGZfGITpnddeWmXYu2iVWdKN7qgzqSxHAfKER2WlEwyKZOLRZ3AxQKv2n AQmsUVnSYz_8sZaBnTL3xrmjkWOhhQCnZbQ4lIo_.1hc_orn3G1h8zq0BfK_ fqzxRx2Dbi4saIkWBSCKudUZZMPufCxeP7XYKGAaIjRIc7Rz4g2aq5t4LH0f OTDbt062PsBNoA9AWEIXFGMyxMoCEdW5kNFjMXBLHWwgRZkCAnvkHiBQefvg PJkmUZkrgC7QJCDYVRFKN88lCQonMFM0BhQm2tFWA10uhieUOjox7MgdNBTz v0g-- X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [10.73.160.242] (sean_bruno@209.131.62.116 with ) by smtp205.mail.gq1.yahoo.com with SMTP; 14 Oct 2013 08:01:24 -0700 PDT Subject: RE: [IWN] Review From: Sean Bruno To: Cedric GROSS In-Reply-To: <003301cebdeb$fc941350$f5bc39f0$@info> References: <002701cebc6f$634c0040$29e400c0$@info> <003301cebdeb$fc941350$f5bc39f0$@info> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-7cRomDcHOyZ7BONDhMBK" Date: Mon, 14 Oct 2013 08:01:23 -0700 Message-ID: <1381762883.2593.0.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@freebsd.org 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, 14 Oct 2013 15:01:36 -0000 --=-7cRomDcHOyZ7BONDhMBK Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Mon, 2013-09-30 at 16:47 +0200, Cedric GROSS wrote: > Hello, >=20 > =20 >=20 > I forgot your lastest commit but it?s done now. >=20 > =20 >=20 > So split_6 and split_7 are sync with most recent ?HEAD. >=20 > =20 >=20 > Cedric Cedric: Which branch should we be testing? sean --=-7cRomDcHOyZ7BONDhMBK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (FreeBSD) iQEcBAABAgAGBQJSXAdAAAoJEBkJRdwI6BaHD9cH/2nW1vxUuju+slqGbEBtG04t bXU//It0btYND211g6dRpsHg7e2g1oqZc3xlP9qqcy1Xr2H1Eo+pjt3pjukaP2ay nK7Ocfavq2SjLCYQGUJHoBsl5IwR82yYVHzoxZltf2QZrhHmjjxWBsHB+g7+hPTj lQ/JkUXDm4vt+Kp+uszrAC6oL/dRxQIE4RZibE9R1loLE/K50ktzaUq4MXbKGvh4 Vu62oD4/kwvDzWE2BOD8CJddfWyZ3AfdCKVi3aFqRKiMCcQMdJIUqMENA55ksy0k dF3C4Z+R9q7qjUnrmSS9bwrnU4pOlVZa4ynd8cLSVG4PtWOvRQM51vmF6a3QEUo= =l5bf -----END PGP SIGNATURE----- --=-7cRomDcHOyZ7BONDhMBK-- From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 14 15:17:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EB809329; Mon, 14 Oct 2013 15:17:08 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id B32532F51; Mon, 14 Oct 2013 15:17:08 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id E8F8A49F; Mon, 14 Oct 2013 17:17:06 +0200 (CEST) From: "Cedric GROSS" To: References: <002701cebc6f$634c0040$29e400c0$@info> <003301cebdeb$fc941350$f5bc39f0$@info> <1381762883.2593.0.camel@localhost> In-Reply-To: <1381762883.2593.0.camel@localhost> Subject: RE: [IWN] Review Date: Mon, 14 Oct 2013 17:17:03 +0200 Message-ID: <002e01cec8f0$71c400e0$554c02a0$@info> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac7I7kvP7FJk9LoETv6cyAoo6FA0+wAAUojw Content-Language: fr 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, 14 Oct 2013 15:17:09 -0000 > De=A0: Sean Bruno [mailto:sean_bruno@yahoo.com] > =C0=A0: Cedric GROSS > Cc=A0: 'Adrian Chadd'; freebsd-wireless@freebsd.org > Objet=A0: RE: [IWN] Review >=20 > On Mon, 2013-09-30 at 16:47 +0200, Cedric GROSS wrote: > > Hello, > > I forgot your lastest commit but it?s done now. > > > > So split_6 and split_7 are sync with most recent ?HEAD. > > Cedric >=20 > Cedric: Hi Sean, >=20 > Which branch should we be testing? > As Adrian wish to smoothly include changes into FreeBSD repo, split_6 an split_7 doesn't change big things regarding latest NIC.=20 Instead Split_8, is minimal version for managing 2200 and so on NIC = series. Could be a good idea to test this version with =E0 lot of NIC. > sean Thanks Cedric From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 14 19:51:45 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BC38E21A for ; Mon, 14 Oct 2013 19:51:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22e.google.com (mail-qe0-x22e.google.com [IPv6:2607:f8b0:400d:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7C591228B for ; Mon, 14 Oct 2013 19:51:45 +0000 (UTC) Received: by mail-qe0-f46.google.com with SMTP id s14so4220947qeb.5 for ; Mon, 14 Oct 2013 12:51:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=4Ddl50QUlgp4boNkJAuVW0U8+G0C6sGSZ9LdwhFaVOM=; b=aZqv94XLIvEC33BcbdFBcNGJqV55T3DzqZSdQYhkDXnk2IhLtiRZ4KCBcPu0GHWW63 BTUmbS6M0jCecDH0vhW0ogNxA9XNEc4smg0f0Qi37EJLWgUKsZu3j+fD1jSOqmatKM6C QkJOXbBTewinLzsgHItJSOY6rPhB9ChMTkjILOV3xDe+A0Ke6CdhQufrg3nifVfFjhtC p/bpChwcDpmJ+/OYAGfG68EkqiN4pr346Qq97UWHTt9WnxtVA1BgGezUYD5+Ac15Llz3 yi51mZ/GWGUk2UsYYAs7TD94ZGWAN1ksl2lDwBIFjJ/JAsObhhS1xOmsd8LpKeGljdl7 QTmw== MIME-Version: 1.0 X-Received: by 10.229.201.67 with SMTP id ez3mr51845679qcb.1.1381780304595; Mon, 14 Oct 2013 12:51:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 14 Oct 2013 12:51:44 -0700 (PDT) In-Reply-To: References: <525B2802.5050904@gmail.com> Date: Mon, 14 Oct 2013 12:51:44 -0700 X-Google-Sender-Auth: FQhactgC6TE3yFtLtEbLwocaqdQ Message-ID: Subject: Re: Wireless API From: Adrian Chadd To: Eric Turgeon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 14 Oct 2013 19:51:45 -0000 Not sure. I've not really focused on the userland side of the API at all I'm sorry. Thanks, -adrian On 13 October 2013 17:09, Eric Turgeon wrote: > Were is the documentation for that API. > > > On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd wrote: > >> What do you mean like "connection percentage" ? >> >> Do you mean like signal strength? If so, then yes. >> >> You can then make some basic heuristic guesses mapping signal level / >> RSSI to a connection percentage based on some assumptions. For example, you >> could look at the minimum RSSI required to guarantee some decent stability >> at each receive/transmit rate (from 1mbit->54mbit, then MCS1->MCS23) and >> then use that to map out connection percentage (where stable at MCS0 / >> 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.) >> >> HTH, >> >> >> >> -adrian >> >> >> >> On 13 October 2013 16:08, Eric Tugeon wrote: >> >>> Hi, >>> I work on a Python GTK network manager for FreeBSD/GhostBSD, it will >>> look similar to https://projects.gnome.org/**NetworkManager/. >>> I want to know if we have wireless API like connection percentage? >>> ______________________________**_________________ >>> 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 " >>> >> >> > > > -- > *Eric Turgeon > **GhostBSD project* > Office location: > 1-11 connaught > Moncton NB Canada > www.ghostbsd.org > From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 15 11:16:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EF980D8; Tue, 15 Oct 2013 11:16:23 +0000 (UTC) (envelope-from ericturgeon.bsd@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C226725EE; Tue, 15 Oct 2013 11:16:23 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id bj1so8875849pad.35 for ; Tue, 15 Oct 2013 04:16:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IwcUTaakadIhTCJCFHMK3KviEBR14Cq0kWIQ5CjvQ+o=; b=pw275LsgTqT7hQ36SRzu6kcupICQJDJP2B9KfCUE+ldsLqx9a5vVOkqiOBfx98ldnv vdOScEJtEau1EpjtBLZ/NBON5fPjie4bVZ5nkyENhBnIzpwD7GHnYMW1gi5pzauFf047 FwIygpxbcgeoJ/LYztwyc6RfQvz1XfW3oUSHogKxrszGCPBOM0qQS+v++spdzXjYqb45 iadq5Ma5m49/to+qqn4pNsXkyv9fQxwKcuWr7lfibC9whXZuzAUWZ+DyQFsFh6wbALk6 ixJL7PUBKRVQeWn8yi6IIQQq8CuFKOxow1T2a4PNDWYYlnWVgDNj4MDLNdWj4JJI28RG 9gng== MIME-Version: 1.0 X-Received: by 10.66.158.196 with SMTP id ww4mr42987536pab.57.1381835783309; Tue, 15 Oct 2013 04:16:23 -0700 (PDT) Received: by 10.68.200.136 with HTTP; Tue, 15 Oct 2013 04:16:23 -0700 (PDT) In-Reply-To: References: <525B2802.5050904@gmail.com> Date: Tue, 15 Oct 2013 08:16:23 -0300 Message-ID: Subject: Re: Wireless API From: Eric Turgeon To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 15 Oct 2013 11:16:24 -0000 Hi Adrian That is OK, I have download the source code of Wifimgr, it use ifconfig. I was using "ifconfig wlan0 scan", it was to slow to display info, but in the Wifimgr code they use "ifconfig -v wlan* list scan" and "ifconfig wlan* list scan". I also found wifimgr calculate S:N to find the percentage of the connection, it is (S - N) * 4. I have also read further ifconfig manual, I suppose ifconfig will be a kind of API for my work. Thanks Eric On Mon, Oct 14, 2013 at 4:51 PM, Adrian Chadd wrote: > Not sure. I've not really focused on the userland side of the API at all > I'm sorry. > > Thanks, > > > -adrian > > > > On 13 October 2013 17:09, Eric Turgeon wrote: > >> Were is the documentation for that API. >> >> >> On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd wrote: >> >>> What do you mean like "connection percentage" ? >>> >>> Do you mean like signal strength? If so, then yes. >>> >>> You can then make some basic heuristic guesses mapping signal level / >>> RSSI to a connection percentage based on some assumptions. For example, you >>> could look at the minimum RSSI required to guarantee some decent stability >>> at each receive/transmit rate (from 1mbit->54mbit, then MCS1->MCS23) and >>> then use that to map out connection percentage (where stable at MCS0 / >>> 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.) >>> >>> HTH, >>> >>> >>> >>> -adrian >>> >>> >>> >>> On 13 October 2013 16:08, Eric Tugeon wrote: >>> >>>> Hi, >>>> I work on a Python GTK network manager for FreeBSD/GhostBSD, it will >>>> look similar to https://projects.gnome.org/**NetworkManager/. >>>> I want to know if we have wireless API like connection percentage? >>>> ______________________________**_________________ >>>> 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 " >>>> >>> >>> >> >> >> -- >> *Eric Turgeon >> **GhostBSD project* >> Office location: >> 1-11 connaught >> Moncton NB Canada >> www.ghostbsd.org >> > > -- *Eric Turgeon **GhostBSD project* Office location: 1-11 connaught Moncton NB Canada www.ghostbsd.org From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 15 14:03:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2D71818B for ; Tue, 15 Oct 2013 14:03:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E070F26C3 for ; Tue, 15 Oct 2013 14:03:39 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id k4so2322045qaq.14 for ; Tue, 15 Oct 2013 07:03:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=gu3IiN3zOG1oEm5a5MnfQ+jFdFKJX1w/Wj7PPFRmJXQ=; b=LDofBTdEkrHC9USuptNzOrR1LFr08P3c5lf+hnUaFS+gVW49vMyPgSYgUczPDh3AYl o7bb6pjwNflO6oelGOqJqBtpasTizJkkLuloaOwbXN14UluB0xbcoLeW3NYLakk3e1Av xNXbq5zz4MnS9aIzf0QNnc0T1EMhizR1+OKTNC0CJ9zA8CQMhniGMUup7NNFrZEFltR8 1hI7z6UfyI8qNyL33CcY6VU5Pc2L8gtFmKu7foQJwb4Rn19i8pZg05dBBfCZpJwHOp1C gqPIMAOq8Fzhov9ZfOsMLW5Up+yi3+1G3CjgSKuA13v80pxgMza6Apsoe5p7eQILinI8 dRnw== MIME-Version: 1.0 X-Received: by 10.224.157.14 with SMTP id z14mr10497221qaw.90.1381845817174; Tue, 15 Oct 2013 07:03:37 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 15 Oct 2013 07:03:37 -0700 (PDT) In-Reply-To: References: <525B2802.5050904@gmail.com> Date: Tue, 15 Oct 2013 07:03:37 -0700 X-Google-Sender-Auth: seYfrvZv8mX12sSFCcYczvvSYAs Message-ID: Subject: Re: Wireless API From: Adrian Chadd To: Eric Turgeon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 15 Oct 2013 14:03:40 -0000 I'd rather that the ioctl API be used, rather than the output of 'ifconfig'. It's likely about time the ioctl API was turned into a library for userland to use. That way it could be imported into python/etc via C bindings. Thanks, -adrian On 15 October 2013 04:16, Eric Turgeon wrote: > Hi Adrian > > That is OK, I have download the source code of Wifimgr, it use ifconfig. > I was using "ifconfig wlan0 scan", it was to slow to display info, but in > the Wifimgr code they use > "ifconfig -v wlan* list scan" and "ifconfig wlan* list scan". I also > found wifimgr calculate S:N to find the percentage of the connection, it is > (S - N) * 4. > I have also read further ifconfig manual, I suppose ifconfig will be a > kind of API for my work. > > Thanks > > Eric > > > On Mon, Oct 14, 2013 at 4:51 PM, Adrian Chadd wrote: > >> Not sure. I've not really focused on the userland side of the API at all >> I'm sorry. >> >> Thanks, >> >> >> -adrian >> >> >> >> On 13 October 2013 17:09, Eric Turgeon wrote: >> >>> Were is the documentation for that API. >>> >>> >>> On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd wrote: >>> >>>> What do you mean like "connection percentage" ? >>>> >>>> Do you mean like signal strength? If so, then yes. >>>> >>>> You can then make some basic heuristic guesses mapping signal level / >>>> RSSI to a connection percentage based on some assumptions. For example, you >>>> could look at the minimum RSSI required to guarantee some decent stability >>>> at each receive/transmit rate (from 1mbit->54mbit, then MCS1->MCS23) and >>>> then use that to map out connection percentage (where stable at MCS0 / >>>> 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.) >>>> >>>> HTH, >>>> >>>> >>>> >>>> -adrian >>>> >>>> >>>> >>>> On 13 October 2013 16:08, Eric Tugeon wrote: >>>> >>>>> Hi, >>>>> I work on a Python GTK network manager for FreeBSD/GhostBSD, it will >>>>> look similar to https://projects.gnome.org/**NetworkManager/. >>>>> I want to know if we have wireless API like connection percentage? >>>>> ______________________________**_________________ >>>>> 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 " >>>>> >>>> >>>> >>> >>> >>> -- >>> *Eric Turgeon >>> **GhostBSD project* >>> Office location: >>> 1-11 connaught >>> Moncton NB Canada >>> www.ghostbsd.org >>> >> >> > > > -- > *Eric Turgeon > **GhostBSD project* > Office location: > 1-11 connaught > Moncton NB Canada > www.ghostbsd.org > From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 15 14:35:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 66587BC6; Tue, 15 Oct 2013 14:35:08 +0000 (UTC) (envelope-from ericturgeon.bsd@gmail.com) Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 38E5029A8; Tue, 15 Oct 2013 14:35:08 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id rr4so8800460pbb.6 for ; Tue, 15 Oct 2013 07:35:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=THX4yXHCBIpKUMjJPVKp2hwILmRBPjJHEP/2zBb1oPU=; b=Wz5LO4FJrpyP2tNFTFW/cx1uK5etd1iyXKch3a/z3C1RPNKr1fysaJy/1YZTNX+Olo cOIsWDeYbiKWr9adnNEZiLHWagpflX9jmbdCiCMbS+I7eDLZaGcPrhGeh3nyb/GGSNvg lOpLM1+OS6k1SGSBI13wyl1HcipyToIoeWYcQY6j2Tvmc64hocbsdTGuFgFdpweab8zP pqSehiAASpC/80uT8O/NKLoPtEouHqaIdkDxV0z5h4c5WXBXqmRbWXu8kJ8Tod5TENnY R9s2ewsGp5IonveaC+F/gXg/NFWruw/akqiM6QCKFU4ApNwM9mnWvIvwNDOvtN4q7nzD XSfw== MIME-Version: 1.0 X-Received: by 10.68.58.137 with SMTP id r9mr8691042pbq.148.1381847707727; Tue, 15 Oct 2013 07:35:07 -0700 (PDT) Received: by 10.68.200.136 with HTTP; Tue, 15 Oct 2013 07:35:07 -0700 (PDT) In-Reply-To: References: <525B2802.5050904@gmail.com> Date: Tue, 15 Oct 2013 11:35:07 -0300 Message-ID: Subject: Re: Wireless API From: Eric Turgeon To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 15 Oct 2013 14:35:08 -0000 If You have user documentation, I could use that rather then ifconfig. On Tue, Oct 15, 2013 at 11:03 AM, Adrian Chadd wrote: > I'd rather that the ioctl API be used, rather than the output of > 'ifconfig'. > > It's likely about time the ioctl API was turned into a library for > userland to use. That way it could be imported into python/etc via C > bindings. > > Thanks, > > > > -adrian > > > > On 15 October 2013 04:16, Eric Turgeon wrote: > >> Hi Adrian >> >> That is OK, I have download the source code of Wifimgr, it use ifconfig. >> I was using "ifconfig wlan0 scan", it was to slow to display info, but in >> the Wifimgr code they use >> "ifconfig -v wlan* list scan" and "ifconfig wlan* list scan". I also >> found wifimgr calculate S:N to find the percentage of the connection, it is >> (S - N) * 4. >> I have also read further ifconfig manual, I suppose ifconfig will be a >> kind of API for my work. >> >> Thanks >> >> Eric >> >> >> On Mon, Oct 14, 2013 at 4:51 PM, Adrian Chadd wrote: >> >>> Not sure. I've not really focused on the userland side of the API at all >>> I'm sorry. >>> >>> Thanks, >>> >>> >>> -adrian >>> >>> >>> >>> On 13 October 2013 17:09, Eric Turgeon wrote: >>> >>>> Were is the documentation for that API. >>>> >>>> >>>> On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd wrote: >>>> >>>>> What do you mean like "connection percentage" ? >>>>> >>>>> Do you mean like signal strength? If so, then yes. >>>>> >>>>> You can then make some basic heuristic guesses mapping signal level / >>>>> RSSI to a connection percentage based on some assumptions. For example, you >>>>> could look at the minimum RSSI required to guarantee some decent stability >>>>> at each receive/transmit rate (from 1mbit->54mbit, then MCS1->MCS23) and >>>>> then use that to map out connection percentage (where stable at MCS0 / >>>>> 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.) >>>>> >>>>> HTH, >>>>> >>>>> >>>>> >>>>> -adrian >>>>> >>>>> >>>>> >>>>> On 13 October 2013 16:08, Eric Tugeon wrote: >>>>> >>>>>> Hi, >>>>>> I work on a Python GTK network manager for FreeBSD/GhostBSD, it will >>>>>> look similar to https://projects.gnome.org/**NetworkManager/. >>>>>> I want to know if we have wireless API like connection percentage? >>>>>> ______________________________**_________________ >>>>>> 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 " >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Eric Turgeon >>>> **GhostBSD project* >>>> Office location: >>>> 1-11 connaught >>>> Moncton NB Canada >>>> www.ghostbsd.org >>>> >>> >>> >> >> >> -- >> *Eric Turgeon >> **GhostBSD project* >> Office location: >> 1-11 connaught >> Moncton NB Canada >> www.ghostbsd.org >> > > -- *Eric Turgeon **GhostBSD project* Office location: 1-11 connaught Moncton NB Canada www.ghostbsd.org From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 15 15:15:51 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A528B273 for ; Tue, 15 Oct 2013 15:15:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6249B2DF2 for ; Tue, 15 Oct 2013 15:15:51 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id i13so3431747qae.1 for ; Tue, 15 Oct 2013 08:15:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=9KvPHk86z/jO7AEqVCxOew7P/PMh4+swG348sTWZJ+4=; b=rYGeymJO/bldteGyn98i+jUxjE+JL3sBotSIH1JzPUxnlEX6NWbIjbkjGtyKJvnc29 vfdy2PR+cJ+BysBbYmAYLeY4UKty4WIR2RgX0piiHvM+6AccMC/tKTkFc2hLczOeH9kX m2oeKwr09GGHmv3nUo94sXBUuZmSWxCysBlMBC/heMO/0Vz7MZyNLJf0dT5ZuBGSa0SG +5q+Cn2g0AFfYFIVW+yeHm/rgqaT4k2aiW96/+PreMad1mhhUkY6M1MCuee1kzvtTdWA rAIRFsP6Uk/iwW+OZ+TnqGoztWPNJZ1VNTXFBVllX+VtPss299Ebcc3iCcAvgeg8XCY7 B/Cw== MIME-Version: 1.0 X-Received: by 10.224.51.131 with SMTP id d3mr44225445qag.0.1381850149972; Tue, 15 Oct 2013 08:15:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 15 Oct 2013 08:15:49 -0700 (PDT) In-Reply-To: References: <525B2802.5050904@gmail.com> Date: Tue, 15 Oct 2013 08:15:49 -0700 X-Google-Sender-Auth: ofrIEVkcLOdzHnuOj0u-U_2a-aQ Message-ID: Subject: Re: Wireless API From: Adrian Chadd To: Eric Turgeon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 15 Oct 2013 15:15:51 -0000 Well, up until now the interactions have all been via the ioctl API or the ifconfig command. Both are cumbersome. There's a decent amount of library code in ifconfig for wifi and regulatory related stuff. It could be broken out into a public library.. -adrian On 15 October 2013 07:35, Eric Turgeon wrote: > If You have user documentation, I could use that rather then ifconfig. > > > On Tue, Oct 15, 2013 at 11:03 AM, Adrian Chadd wrote: > >> I'd rather that the ioctl API be used, rather than the output of >> 'ifconfig'. >> >> It's likely about time the ioctl API was turned into a library for >> userland to use. That way it could be imported into python/etc via C >> bindings. >> >> Thanks, >> >> >> >> -adrian >> >> >> >> On 15 October 2013 04:16, Eric Turgeon wrote: >> >>> Hi Adrian >>> >>> That is OK, I have download the source code of Wifimgr, it use >>> ifconfig. I was using "ifconfig wlan0 scan", it was to slow to display >>> info, but in the Wifimgr code they use >>> "ifconfig -v wlan* list scan" and "ifconfig wlan* list scan". I also >>> found wifimgr calculate S:N to find the percentage of the connection, it is >>> (S - N) * 4. >>> I have also read further ifconfig manual, I suppose ifconfig will be a >>> kind of API for my work. >>> >>> Thanks >>> >>> Eric >>> >>> >>> On Mon, Oct 14, 2013 at 4:51 PM, Adrian Chadd wrote: >>> >>>> Not sure. I've not really focused on the userland side of the API at >>>> all I'm sorry. >>>> >>>> Thanks, >>>> >>>> >>>> -adrian >>>> >>>> >>>> >>>> On 13 October 2013 17:09, Eric Turgeon wrote: >>>> >>>>> Were is the documentation for that API. >>>>> >>>>> >>>>> On Sun, Oct 13, 2013 at 8:57 PM, Adrian Chadd wrote: >>>>> >>>>>> What do you mean like "connection percentage" ? >>>>>> >>>>>> Do you mean like signal strength? If so, then yes. >>>>>> >>>>>> You can then make some basic heuristic guesses mapping signal level / >>>>>> RSSI to a connection percentage based on some assumptions. For example, you >>>>>> could look at the minimum RSSI required to guarantee some decent stability >>>>>> at each receive/transmit rate (from 1mbit->54mbit, then MCS1->MCS23) and >>>>>> then use that to map out connection percentage (where stable at MCS0 / >>>>>> 1mbit would be lowest, and stable at MCS7/54mbit would be 100%.) >>>>>> >>>>>> HTH, >>>>>> >>>>>> >>>>>> >>>>>> -adrian >>>>>> >>>>>> >>>>>> >>>>>> On 13 October 2013 16:08, Eric Tugeon wrote: >>>>>> >>>>>>> Hi, >>>>>>> I work on a Python GTK network manager for FreeBSD/GhostBSD, it will >>>>>>> look similar to https://projects.gnome.org/**NetworkManager/. >>>>>>> I want to know if we have wireless API like connection percentage? >>>>>>> ______________________________**_________________ >>>>>>> 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 " >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Eric Turgeon >>>>> **GhostBSD project* >>>>> Office location: >>>>> 1-11 connaught >>>>> Moncton NB Canada >>>>> www.ghostbsd.org >>>>> >>>> >>>> >>> >>> >>> -- >>> *Eric Turgeon >>> **GhostBSD project* >>> Office location: >>> 1-11 connaught >>> Moncton NB Canada >>> www.ghostbsd.org >>> >> >> > > > -- > *Eric Turgeon > **GhostBSD project* > Office location: > 1-11 connaught > Moncton NB Canada > www.ghostbsd.org > From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 15 16:26:37 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 48406FD6 for ; Tue, 15 Oct 2013 16:26:37 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2778C2458 for ; Tue, 15 Oct 2013 16:26:36 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id B506867584 for ; Tue, 15 Oct 2013 09:26:36 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 82506-07 for ; Tue, 15 Oct 2013 09:26:36 -0700 (PDT) Received: from [192.168.0.51] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id 3FB826757E for ; Tue, 15 Oct 2013 09:26:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ixsystems.com; s=newknight0; t=1381854396; bh=xhusM5Mjrex9AYcZw3chvYDnxjFY8f1IV0M5k9z2ZvA=; h=Date:From:To:Subject:References:In-Reply-To; b=R10A+t8slEnP89sZ1gKQpnw1tSA1FNqXlcK1S5LJBDMyuz76HkE0ND/Vp2/xb9UU3 FT2EnCWDypg/GA6AH7Wo+ll163mSYPhTbTBg7xN6tLqsEZwYQrfN8lGX/zZ5fGoGMt nXaYTC2Xan2OFGurILXN0DEanmDM5t6jiFw8lDFw= Message-ID: <525D6CBA.4010101@pcbsd.org> Date: Tue, 15 Oct 2013 12:26:34 -0400 From: Kris Moore User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Re: Wireless API References: <525B2802.5050904@gmail.com> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 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: Tue, 15 Oct 2013 16:26:37 -0000 On 10/15/2013 11:15, Adrian Chadd wrote: > Well, up until now the interactions have all been via the ioctl API or the > ifconfig command. Both are cumbersome. > > There's a decent amount of library code in ifconfig for wifi and regulatory > related stuff. It could be broken out into a public library.. > > -adrian > Yea, our PC-BSD network utils are using a mixture of C ioctl and "ifconfig" parsing, +1 for a public library API at some point ;) -- Kris Moore PC-BSD Software iXsystems From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 15 16:39:01 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 71A705F2 for ; Tue, 15 Oct 2013 16:39:01 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-vb0-x229.google.com (mail-vb0-x229.google.com [IPv6:2607:f8b0:400c:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2E8B92547 for ; Tue, 15 Oct 2013 16:39:01 +0000 (UTC) Received: by mail-vb0-f41.google.com with SMTP id g17so5467785vbg.28 for ; Tue, 15 Oct 2013 09:39:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vD0lspS9IJDyK0N9yeykCRZ0o4mfCzi4HMo5LBt1Mb0=; b=UoPPqyxuMs1ErmNetODjMOEmMNzub4Z6R2d4FK/3AJmbVD6GG1NNFcUMTpGB5YOfPW vTOijoZsPH1SLYKkm6QG1AV4XpjpTGlcFHcRBcgg622a4sr9FG7DuCeUBNC5VVsXmnJ9 XSaxh7D1EhXIHM02Bp/yhVWuDMl6xPqUhtT42cL+9E3dPnfw1cqbtdUnj7Zd5RylJdmQ /QNJHQd1mSsh9i+kwu2p10WAroRPZlrBjpjc/PmeY2EP/FNCbiVjIdpVqZmTYWMQO+EY vXZImXfdKVLASqkORg789T1d5Ly2MpEEuWY1PpiDaoWtC9PMVurtQm+2VEsdOpZPuzuz fHMQ== MIME-Version: 1.0 X-Received: by 10.220.184.70 with SMTP id cj6mr1593312vcb.23.1381855140233; Tue, 15 Oct 2013 09:39:00 -0700 (PDT) Received: by 10.220.111.200 with HTTP; Tue, 15 Oct 2013 09:39:00 -0700 (PDT) Received: by 10.220.111.200 with HTTP; Tue, 15 Oct 2013 09:39:00 -0700 (PDT) In-Reply-To: <525D6CBA.4010101@pcbsd.org> References: <525B2802.5050904@gmail.com> <525D6CBA.4010101@pcbsd.org> Date: Tue, 15 Oct 2013 16:39:00 +0000 Message-ID: Subject: Re: Wireless API From: "Sam Fourman Jr." To: Kris Moore Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 15 Oct 2013 16:39:01 -0000 On Oct 15, 2013 12:26 PM, "Kris Moore" wrote: > > On 10/15/2013 11:15, Adrian Chadd wrote: > > Well, up until now the interactions have all been via the ioctl API or the > > ifconfig command. Both are cumbersome. > > > > There's a decent amount of library code in ifconfig for wifi and regulatory > > related stuff. It could be broken out into a public library.. > > > > -adrian > > > > Yea, our PC-BSD network utils are using a mixture of C ioctl and > "ifconfig" parsing, +1 for a public library API at some point ;) This really is somthing that should be brought to the FreeBSD foundations attetion. As an example the network manager in Gnome hasn't been ported for years, and I belive the largest part of the reason is lack of an API. The importance of this really can't be underestimated. Is there a formal way, to propose a project to the FreeBSD foundation? Sam Fourman Jr. From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 04:29:42 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3F44DDBC; Wed, 16 Oct 2013 04:29:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D23D92E8F; Wed, 16 Oct 2013 04:29:41 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id l13so160149qcy.18 for ; Tue, 15 Oct 2013 21:29:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=0elHvNL8jKOfY9iew4uJDTpey+d35FFCf3VP1WIUss8=; b=YDkR25Qj/3K24pT9xl63OxKAg6qXNP+qYj01dX0an/+UcS+4kXiPCyrx/Wrn2CAT3G rVUwV0wTTwXcW3Lj+5fMhfiCsjqz2mYSEDsqha5fsU10G3vPV7r/SGafkNQUf3bShA4c AREM3dOuo59xdElihtGXFcr2CFTbx/WVclHigptYKmtk76c0ArMIBAQYICdFqopZ7MMY VmhmkNIpRqo73TwAN9937jipP3nztVjB7Ms+P3wxjqIqMTlmNyEK74fCerBq/JUf27yI xIKRyMu3MMEmMHRvN3rPZ1VUE7GKUuwQOz5l1812BlnoEWYIB5obfI/38aMTZrpcmcga 2Ekw== MIME-Version: 1.0 X-Received: by 10.49.12.14 with SMTP id u14mr1032234qeb.74.1381897780973; Tue, 15 Oct 2013 21:29:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 15 Oct 2013 21:29:40 -0700 (PDT) Date: Tue, 15 Oct 2013 21:29:40 -0700 X-Google-Sender-Auth: m-To70lzj7FD9_KiaTEzI3ZUQ-U Message-ID: Subject: AR934x initial support is now in the tree From: Adrian Chadd To: "freebsd-mips@freebsd.org" , "freebsd-embedded@freebsd.org" , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 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: Wed, 16 Oct 2013 04:29:42 -0000 Hi all, The initial AR934x support is now in the tree. The basics: * the basic hacks needed to bring up mips74k support is now in the tree; * I've added MIPS bus space barriers to things; * on-board wifi works; * slow UART works (ie, rs232 console); * on-chip switch support works (but no VLAN support - see below); * on-chip USB probes/attaches fine; * ethernet seems to work fine. It passes packets and such! What I haven't yet done (and I'll accept patches!) * the fast UART code from the AR933x should work for the fast UART port but I haven't yet tested it! * I haven't tried USB yet! * taught the arswitch code about the VLAN registers for the AR934x on-chip switch. * taught the ath(4) driver to use the bus space barrier stuff. So the wifi is likely going to be angry at us for a while. * There's no support for the newer switch chips (AR8327 in particular.) * NAND, I2S support, etc. Thanks! -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 04:52:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E2FB770 for ; Wed, 16 Oct 2013 04:52:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9E1AB2FB5 for ; Wed, 16 Oct 2013 04:52:08 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id j15so301807qaq.13 for ; Tue, 15 Oct 2013 21:52:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=seNGPO8SnJ+3BvPxlu9yHFJ6apdvrMf69F1aKaC+UQs=; b=mR8vrcMNVKZQoR6j0oqdyElXgauRGRLefG2DyboCS3pcyIWp1LBRDRy9RnN/sf8Duo bo9lXrFuwRX9zNYifUQNgz2VfbmJcHqh618FB+ytHttRft9EisVHIOuRkyuyshYav9GR uJWoiy1BeMGx4hVu6kokQQFGb1UFT0f6EszlZUVUTnDNJSVynHICtrM2FWzXQijab4On 0qODAWMacKyBAEpT2r/DkILKEKMmYnol7lXilLOW1UfWeRPDO+DLJX8awrxB33Uaxm0d p5RF7KF+IUMHzrUptPfhP7HO+nbN8akjwm3LyHMQDRehOigQuEYNGXBFOMgU15OOYWcH KdLw== MIME-Version: 1.0 X-Received: by 10.49.12.14 with SMTP id u14mr1120613qeb.74.1381899127007; Tue, 15 Oct 2013 21:52:07 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Tue, 15 Oct 2013 21:52:06 -0700 (PDT) In-Reply-To: References: <525B2802.5050904@gmail.com> <525D6CBA.4010101@pcbsd.org> Date: Tue, 15 Oct 2013 21:52:06 -0700 Message-ID: Subject: Re: Wireless API From: Adrian Chadd To: "Sam Fourman Jr." Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 04:52:09 -0000 The wireless API used to be the same as what's in Linux. So, in theory, we could just use anything that used Linux wireless extensions. Save, of course, the API drift. So, you could just write a full wireless manager that used the ioctl API for the basic manipulation of the VAP (eg link status, current association state, etc) and the wpa_supplicant socket API for talking to the supplicant for the scan list, telling it which SSID to try associating to, etc. -adrian On 15 October 2013 09:39, Sam Fourman Jr. wrote: > On Oct 15, 2013 12:26 PM, "Kris Moore" wrote: > > > > On 10/15/2013 11:15, Adrian Chadd wrote: > > > Well, up until now the interactions have all been via the ioctl API or > the > > > ifconfig command. Both are cumbersome. > > > > > > There's a decent amount of library code in ifconfig for wifi and > regulatory > > > related stuff. It could be broken out into a public library.. > > > > > > -adrian > > > > > > > Yea, our PC-BSD network utils are using a mixture of C ioctl and > > "ifconfig" parsing, +1 for a public library API at some point ;) > > This really is somthing that should be brought to the FreeBSD foundations > attetion. > As an example the network manager in Gnome hasn't been ported for years, > and I belive the largest part of the reason is lack of an API. > > The importance of this really can't be underestimated. > Is there a formal way, to propose a project to the FreeBSD foundation? > > Sam Fourman Jr. > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 04:54:01 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CCE5E9A for ; Wed, 16 Oct 2013 04:54:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8BE4B2FB9 for ; Wed, 16 Oct 2013 04:54:01 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id q4so195643qcx.40 for ; Tue, 15 Oct 2013 21:54:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Ugo6V0Bn5Lo2ui6rbpzbMVwOoaneYVw9uOF1eNizA9Q=; b=i+DKRTn/UNMI4HBQpkurAr7TWo3QYnG4YTqH0MWc7U2LAclKYKDNDXQ30VAF20huox 8DDaG8XVmkg78HU1vOaEzzWOJJa2v6Pm+srlfsMzZrQu8kJFlv6U+Cd434xaHMFudhmf 6Up5I5TKkVN++HXybtNmzqFLVI9rBlwRKwWS7lkvW8MTMzzb7uWJTcU8rgxGuqnDadXB hZXir6qSFZAk6g6UWwa0ioVEEHVkteVtQcOmMhNpc4xbQEQclrt7G3zNIACAbi0fIwdB uHRYBm/2zACqeS5TQar7SerK28d3lvOMrdjOy1LqmfPghktWZRi+AMiJq16YR8BJNWXG xaAQ== MIME-Version: 1.0 X-Received: by 10.224.167.147 with SMTP id q19mr198134qay.119.1381899240289; Tue, 15 Oct 2013 21:54:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 15 Oct 2013 21:54:00 -0700 (PDT) In-Reply-To: References: Date: Tue, 15 Oct 2013 21:54:00 -0700 X-Google-Sender-Auth: TBLNoMiCsONKY9abQZwPqClPWXQ Message-ID: Subject: Re: Ralink RT2860 frame aggregation From: Adrian Chadd To: Ramanujan Seshadri Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 04:54:02 -0000 I don't have any real answers for you. I'd look at the interframe spacing and timing; see if it's due to big gaps in transmission/reception, see if it's something silly like AMPDU density being way too big, or maybe just lots of retries. I'm sorry I can't be more helpful than this! -adrian On 11 October 2013 11:18, Ramanujan Seshadri wrote: > It's in the NIC. But it seems that it sometimes aggregates more than the > set BA win size (in the driver). In fact i was wondering - if it can > actually achieve up to 80 Mbps throughput with just 8 frames aggregated. In > fact the aggregation size doesn't seem to matter much for the throughput > because any aggregation from 5-8 seems to get the same throughput. So, i > was wondering if this is something weird in NIC or can we do some thing to > control it in the driver ? > > ram > > > On Thu, Oct 10, 2013 at 4:41 PM, Adrian Chadd wrote: > >> I forget .. is the driver or the NIC itself doing aggregation? >> >> >> -a >> >> >> On 10 October 2013 10:33, Ramanujan Seshadri wrote: >> >>> Hello all, >>> i was testing some features of ralink rt2860 driver. i saw a bit weird >>> results. below is the result of what i saw. The throughput achieved >>> doesn't >>> change much when the MPDU aggregation in an AMPDU goes from 3 to 8. And >>> also, the driver doesn't seem to aggregate more than 8 MPDU's in an AMPDU >>> even when the BA win size is set to max of 64. i was testing this by >>> fixing >>> the rate at MCS 15 >>> >>> Is there anything else i need to do to force the driver to aggregate >>> more >>> MPDU's in an AMPDU ? >>> >>> >>> >>> BA Win Size No. of MPDU's Throughput(Mbps) >>> aggregated >>> >>> 1. 64 7-8 85.7 >>> >>> 2. 32 6-7 84.2 >>> >>> 3. 16 6-7 81.7 >>> >>> 4. 8 6-7 79.9 >>> >>> 5. 4 5 84.7 >>> >>> 6. 2 3 71.8 >>> >>> 7. 1 2 73.5 >>> >>> >>> Thanks >>> ram >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to " >>> freebsd-wireless-unsubscribe@freebsd.org" >>> >> >> > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 04:54:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1D743C5 for ; Wed, 16 Oct 2013 04:54:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA8A52FBB for ; Wed, 16 Oct 2013 04:54:32 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id i13so300137qae.8 for ; Tue, 15 Oct 2013 21:54:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=JpkdHFSQ8XNg7aLeoy+Bh036a4EeS1iVY1aFpLJ1oek=; b=cQVu9CvKMa0a/xXkmIbjKIs0scnD/GdJy2SPpVQquvB5Y8GGTqAjTiPPvs2CypGiup UlLpmtK8VMVLBLmFc6pKyI+J032xwEtOswKomfM5rK2yCMBmpYQEIY+80As8Rs3ne1OH b6chWYq71/X2ANObBi7m/WzdnlYhI6W+5eZngBoOm43GvW2Y0trvYylsF864JD2SD7NC VCPZt9cXStblN+nEroUOaucrOiXD5jLqMrgpT6ww9ywRz6Sv1JS/ajzQOeyT0CU/BxRx M78UIeCUs7zekEYHMUhW1PEr0Rjy//JNOlEnVdXKoC8ugajDrNTyK4GMYgqsNdMQMY4S YBGg== MIME-Version: 1.0 X-Received: by 10.49.127.179 with SMTP id nh19mr1053986qeb.1.1381899272025; Tue, 15 Oct 2013 21:54:32 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 15 Oct 2013 21:54:31 -0700 (PDT) In-Reply-To: References: Date: Tue, 15 Oct 2013 21:54:31 -0700 X-Google-Sender-Auth: RTvngcBhIEx0lYn7HjcKm5H_h8k Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: Adrian Chadd To: w Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 04:54:33 -0000 Hi! Thanks for reviewing this stuff! Please file (more) PRs with patches. I'll make sure these get fixed soon. Thanks! -adrian On 10 October 2013 21:01, w wrote: > With open source, we should be able to change it from "wrong" to "right" = :) > > I just spotted a little more bugs to be corrected: > \freebsd\sys\dev\ath\ath_hal\ar5416\ar5416_ani.c > Search "+1 <" (3 hits in 1 file) > Line 382: if (aniState->noiseImmunityLevel+1 < > params->maxNoiseImmunityLevel) { > Line 388: if (aniState->spurImmunityLevel+1 < > params->maxSpurImmunityLevel) { > Line 480: aniState->noiseImmunityLevel+1 < > params->maxNoiseImmunityLevel)) { > I think there shouldn=92t be a +1 before the the < sign because the > variables are integers. > > Thanks again for your help. > > ~ w ~ > > On Fri, Oct 11, 2013 at 9:34 AM, Adrian Chadd wrote: > > I don't have any open source PHY documentation. :) I'd have to write it= . > > > > Which isn't a bad thing; I'm happy to go and re-read what I (legally, > > legitimately!) have from Atheros about their PHY design and ANI and > write up > > what's implemented in the driver. > > > > The thing with ANI is that a lot of the parameters (like self-correlati= on > > thresholds) have to do with how signal detection in the PHY works. So > it's > > not specifically noise immunity as much as it's tweaking the sensitivit= y > > range and thresholds of the receiver hardware. > > > > There's some interesting things that should be re-investigated (ie, the > > m1/m2 thresholds and how weak signal detection works); I vaguely recall > when > > I was working there that ANI was doing it "wrong". I'll setup a meeting > or > > two with the PHY team when I'm back in California and jot down some > further > > notes about this. > > > > > > > > -adrian > > > > (note: so I'm legally allowed to have all this stuff and I'm legally > allowed > > to code up open source drivers with it, but what I can't do is share th= e > > documentation I have. So no, I won't share it. But whatever goes into > open > > source to improve their chips is open/fair game. Hence, I can write > > documentation and discuss whatever ends up in the open source drivers..= ) > > > > > > > > On 10 October 2013 18:30, w wrote: > >> > >> Do you have the open source link for the PHY documentation so I could > read > >> it? > >> > >> Actually my goal is quite simple I think: To test the effectiveness of > >> ANI. > >> > >> Thanks very much. > >> > >> ~ w ~ > >> > >> On Fri, Oct 11, 2013 at 4:43 AM, Adrian Chadd > wrote: > >> > Yeah, it's all a bit confusing. I'd have to re-read the PHY > >> > documentation i > >> > have here in order to really understand whta's going on. > >> > > >> > What are you trying to achieve herE? > >> > > >> > > >> > -adrian > >> > > >> > > >> > > >> > On 9 October 2013 20:03, w wrote: > >> >> > >> >> Update: looking at the patent again: > >> >> http://www.freepatentsonline.com/7349503.html > >> >> > >> >> Note that bb_m1thres and bb_m2thres refer to normalized, > >> >> self-correlated thresholds, bb_m2count_thr refers to the number of > >> >> self-correlation values (wherein a typical count would not exceed > 31), > >> >> and bb_use_self_corr_low refers to an enabling bit value. > >> >> > >> >> (but the variables are still quite confusing.) > >> >> > >> >> > >> >> ~ w ~ > >> >> > >> >> On Thu, Oct 10, 2013 at 10:12 AM, w wrote: > >> >> > Yup, I read the patent. I have also read the Atheros documentatio= n > >> >> > for > >> >> > ANI (for a different hardware version but it says the operation i= s > >> >> > similar). > >> >> > > >> >> > Are we able to see physical layer parameters like signal level / > >> >> > correlation / channel state information, > >> >> > or are they hidden inside the hardware? > >> >> > > >> >> > ~ w ~ > >> >> > > >> >> > > >> >> > > >> >> > On Thu, Oct 10, 2013 at 10:05 AM, Adrian Chadd > > >> >> > wrote: > >> >> >> I'm not sure. I think it's a signal level. Have you read the ANI > >> >> >> patent(s) ? > >> >> >> > >> >> >> > >> >> >> > >> >> >> -adrian > >> >> >> > >> >> >> > >> >> >> > >> >> >> On 9 October 2013 19:04, w wrote: > >> >> >>> > >> >> >>> Is there any way I can printk the correlation values for > >> >> >>> ar5416_ani.c? > >> >> >>> > >> >> >>> I couldn=92t find the variable that contains the correlation va= lue. > >> >> >>> Line 267 of the ar5416_ani.c file says: > >> >> >>> OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, > >> >> >>> AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); > >> >> >>> > >> >> >>> I don=92t know what the variables mean or what the function mea= ns > or > >> >> >>> what data type the variables are because I want to printk them. > >> >> >>> > >> >> >>> References: > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar5416_ani= .c?view=3Dmarkup > >> >> >>> > >> >> >>> > https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity > >> >> >>> > >> >> >>> ~ w ~ > >> >> >>> _______________________________________________ > >> >> >>> 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" > >> >> >> > >> >> >> > >> >> _______________________________________________ > >> >> freebsd-wireless@freebsd.org mailing list > >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> >> To unsubscribe, send any mail to > >> >> "freebsd-wireless-unsubscribe@freebsd.org" > >> > > >> > > > > > > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 04:56:11 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8BD0E105; Wed, 16 Oct 2013 04:56:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 390352FC5; Wed, 16 Oct 2013 04:56:11 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id c9so171084qcz.31 for ; Tue, 15 Oct 2013 21:56:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=hd5nX5BXzJtkk2YCpU9wZMsHrBqb9FuR9aGLWuURcA4=; b=FySNpBtLOP6nSrSyGf0nGzHBx2CY8kKOwVh3YJ7b4d+OsZXx6ElrvWC0vsixsX81uB /5JbDX7JzihGsa6SSdgJo4S9MSXBsbdz9OAc4rbx5Mfxk5dDawOK68bM3ztmuYe5lp2g aoCNLDnDBDJSAd7jrfywzY/yj3bM2zBkX3xzSjTedz35IKkMclDLeLHRW4QQ8yKIgF8i jPCcelnJTtMx8+Pxp2k7T5NoCBQ13wX/ISoTPVIBeVw45IIRABN2KbC64Vbk/aNfKuTR QKPKfVRCHVyK5hUd3Fqap7HvJm8j+3tcEV+R3YkXzjRWFgZoR3M17V9dBrYKJZUvVpdq P33w== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr2028856qai.74.1381899370324; Tue, 15 Oct 2013 21:56:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 15 Oct 2013 21:56:10 -0700 (PDT) In-Reply-To: <002e01cec8f0$71c400e0$554c02a0$@info> References: <002701cebc6f$634c0040$29e400c0$@info> <003301cebdeb$fc941350$f5bc39f0$@info> <1381762883.2593.0.camel@localhost> <002e01cec8f0$71c400e0$554c02a0$@info> Date: Tue, 15 Oct 2013 21:56:10 -0700 X-Google-Sender-Auth: WE3zXdla7ObQpIJzEf6ElFNG7Ds Message-ID: Subject: Re: [IWN] Review From: Adrian Chadd To: Cedric GROSS Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 04:56:11 -0000 Ok, so what, I should test out split_8, get that into the tree, then merge in more stuff from you? -adrian On 14 October 2013 08:17, Cedric GROSS wrote: > > De : Sean Bruno [mailto:sean_bruno@yahoo.com] > > =C0 : Cedric GROSS > > Cc : 'Adrian Chadd'; freebsd-wireless@freebsd.org > > Objet : RE: [IWN] Review > > > > On Mon, 2013-09-30 at 16:47 +0200, Cedric GROSS wrote: > > > Hello, > > > I forgot your lastest commit but it?s done now. > > > > > > So split_6 and split_7 are sync with most recent ?HEAD. > > > Cedric > > > > Cedric: > Hi Sean, > > > > > Which branch should we be testing? > > > > As Adrian wish to smoothly include changes into FreeBSD repo, split_6 an > split_7 doesn't change big things regarding latest NIC. > > Instead Split_8, is minimal version for managing 2200 and so on NIC serie= s. > Could be a good idea to test this version with =E0 lot of NIC. > > > sean > > Thanks > Cedric > > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 07:32:44 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A31E9300 for ; Wed, 16 Oct 2013 07:32:44 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 6E4182724 for ; Wed, 16 Oct 2013 07:32:43 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:22482] helo=localhost) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id E8/1F-02506-5114E525; Wed, 16 Oct 2013 07:32:37 +0000 Date: Wed, 16 Oct 2013 07:32:37 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: Subject: Re: AR934x initial support is now in the tree X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 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: Wed, 16 Oct 2013 07:32:44 -0000 > The initial AR934x support is now in the tree. Is there any relation between AR934x chip and AR9271? MSI M77 MPOWER motherboard has this chip (quasi-USB wireless) as well as Realtek 8111E Ethernet which doesn't work with FreeBSD or OpenBSD but good with NetBSD-current and Linux. I'd like to know if there is any work on this (AR9271) chip, or what subgroup it belongs to. I'm also trying to set up with Hiro H50191 USB-stick-type wifi adapter (device rsu), have never set up wifi before. What reading do I need to do? Tom From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 09:13:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0C5DDD88; Wed, 16 Oct 2013 09:13:40 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id 555002D5C; Wed, 16 Oct 2013 09:13:39 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id B7599A40; Wed, 16 Oct 2013 11:13:29 +0200 (CEST) From: "Cedric GROSS" To: "'Adrian Chadd'" References: <002701cebc6f$634c0040$29e400c0$@info> <003301cebdeb$fc941350$f5bc39f0$@info> <1381762883.2593.0.camel@localhost> <002e01cec8f0$71c400e0$554c02a0$@info> In-Reply-To: Subject: RE: [IWN] Review Date: Wed, 16 Oct 2013 11:13:20 +0200 Message-ID: <003101ceca4f$fea3fc30$fbebf490$@info> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac7KLA1AoZFVb9heTLWD3L4vl5ZaaQAIzN7g Content-Language: fr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 09:13:40 -0000 Hello Adrian, =20 It=92s up to you. If you wish to continue commit small part review split_6, split_7 and split_8. Or directly test and commit split_8. =20 >From split_8, it=92s remaining Sean=92s work : - Led management - Power supply management =20 After that, freebsd repo will be at same level as my github repo.=20 And may be will able to work on improving speed and add hostap mode. =20 Cedric =20 =20 De : adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] De la part = de Adrian Chadd Envoy=E9 : mercredi 16 octobre 2013 06:56 =C0 : Cedric GROSS Cc : Sean Bruno; freebsd-wireless@freebsd.org Objet : Re: [IWN] Review =20 Ok, so what, I should test out split_8, get that into the tree, then = merge in more stuff from you? =20 =20 -adrian =20 =20 On 14 October 2013 08:17, Cedric GROSS wrote: > De : Sean Bruno [mailto:sean_bruno@yahoo.com] > =C0 : Cedric GROSS > Cc : 'Adrian Chadd'; freebsd-wireless@freebsd.org > Objet : RE: [IWN] Review > > On Mon, 2013-09-30 at 16:47 +0200, Cedric GROSS wrote: > > Hello, > > I forgot your lastest commit but it?s done now. > > > > So split_6 and split_7 are sync with most recent ?HEAD. > > Cedric > > Cedric: Hi Sean, > > Which branch should we be testing? > As Adrian wish to smoothly include changes into FreeBSD repo, split_6 an split_7 doesn't change big things regarding latest NIC. Instead Split_8, is minimal version for managing 2200 and so on NIC = series. Could be a good idea to test this version with =E0 lot of NIC. > sean Thanks Cedric =20 From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 13:01:23 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AD2299FA for ; Wed, 16 Oct 2013 13:01:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6E86E2BAC for ; Wed, 16 Oct 2013 13:01:23 +0000 (UTC) Received: by mail-qe0-f51.google.com with SMTP id q19so535776qeb.10 for ; Wed, 16 Oct 2013 06:01:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=N1G7N1xplAMscak2AXSXZEfUfitixC85wvLZDSPzABM=; b=RXLE1sDwxTobk8uxsZaaTvaz2Y2Mmbb4JuJUzyzu3AmMONVrVDK4s/KTiCe1s5ej9L 2lL66/O1Mg9ahMJh8ittcdludlee5h4haujMpMLsQnMx4I2RSaW5EBKOl66HObwTB7IE gHzaml2Z+0TTUgAxXnOpFXWpaCE8q0+9yfC/PqubjD5+FeS9qib9Atxp4kCvSuCAIGV+ mMrS26NUQqjevnLFXBbm2ge4FwLgl+56KEJR7HJS2Ys8LbTkoZlWvSRvREhiwArLFsxT cPrjYlSLzNCeD03sl71V+nki3/tv1rmjR9N9Dr3N0IXs1jxbkw+b1YGq7EH0R66/5V9q peHQ== MIME-Version: 1.0 X-Received: by 10.49.59.115 with SMTP id y19mr3603419qeq.8.1381928480549; Wed, 16 Oct 2013 06:01:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 16 Oct 2013 06:01:20 -0700 (PDT) In-Reply-To: References: Date: Wed, 16 Oct 2013 06:01:20 -0700 X-Google-Sender-Auth: wiSgmFJTKDvuzhyHBskSwwCxo6o Message-ID: Subject: Re: AR934x initial support is now in the tree From: Adrian Chadd To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 13:01:23 -0000 The AR9271 is a USB-connected AR9285, for all intents and purposes. So it would use ath(4), if ath(4) had the required USB glue. Sorry. -adrian On 16 October 2013 00:32, Thomas Mueller wrote: > > The initial AR934x support is now in the tree. > > Is there any relation between AR934x chip and AR9271? > > MSI M77 MPOWER motherboard has this chip (quasi-USB wireless) as well as > Realtek 8111E Ethernet which doesn't work with FreeBSD or OpenBSD but good > with NetBSD-current and Linux. > > I'd like to know if there is any work on this (AR9271) chip, or what > subgroup it belongs to. > > I'm also trying to set up with Hiro H50191 USB-stick-type wifi adapter > (device rsu), have never set up wifi before. > > What reading do I need to do? > > Tom > > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 17:29:30 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BE7D62A4 for ; Wed, 16 Oct 2013 17:29:30 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8C2132DF5 for ; Wed, 16 Oct 2013 17:29:30 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id va2so867931obc.41 for ; Wed, 16 Oct 2013 10:29:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UyTBBhSXbQHX3jdoheUbzgJIvbOozJYbeXNl/h0FyT4=; b=rb3uruEjuBz7n9kU6RoGQgic8bM7vTEgUsAPTdS/l9FbqTg06YQj5rFYP/vJJS5gbX sYKpjNMUfywLo0Fns6JCiRifxyK7lDQ5fuRNbLQ2rjONFNdxgYAFnnBxjU88yJfirjkr 1iFIiYbfLcDnxWz+HjdRj2tnR1TUErRPVBqtEp0QpebWplmvW4/S3tvy1cifY77DrKOh N0lkLIwREiqU3lVf5KvhiWAyBE+UnUMlHvoDj91ZvNGgNHEt3/UqILBjt6t1ohRo+UFP OyFVDSVtfr1bpteksBNrNFpYEid0BwSmHylwz0wuTQqGA8pu0EYi1DU643Umbv9TyS9Q 8l0Q== MIME-Version: 1.0 X-Received: by 10.182.148.69 with SMTP id tq5mr137763obb.97.1381944569875; Wed, 16 Oct 2013 10:29:29 -0700 (PDT) Received: by 10.76.69.104 with HTTP; Wed, 16 Oct 2013 10:29:29 -0700 (PDT) Date: Wed, 16 Oct 2013 19:29:29 +0200 Message-ID: Subject: Why does ath(4) suck, and what else to buy? From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= To: wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 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: Wed, 16 Oct 2013 17:29:30 -0000 Hey, I'm running this small -CURRENT box as router/AP and it has a miniPCI ath(4) card that typically works fine, it only reports the occasional ath0: stuck beacon; resetting (bmiss count 4) not sure if that is problematic, the wifi used to work fine. If that message is harmless, maybe it should not be printed. But that's not what I'm here for. I've tried setting up a 2nd wlan device and run hostapd on it for a guest SSID for house guests, etc. So I created wlan2 next to wlan0, ran an exact copy of the hostapd.conf (except different SSID and PSK) and that made lots of phones/tablets have trouble connecting or staying connected (wlan2 is bridged to the same bridge as wlan0 and the wired interfaces, so DHCP/DNS/routes are unlikely to be the problem). It looks like this: ath0: mem 0xe0a00000-0xe0a0ffff irq 17 at device 0.0 on pci4 ath0: AR9280 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 /etc/rc.conf: cloned_interfaces="bridge0" autobridge_interfaces="bridge0" autobridge_bridge0="port* wlan0 wlan2" wlans_ath0="wlan0 wlan2" create_args_wlan0="wlanmode hostap country DE authmode wpa" ifconfig_wlan0="ssid COYOTE mode 11g pureg up" create_args_wlan2="wlanmode hostap country DE authmode wpa" ifconfig_wlan2="ssid COYOTE_GUEST mode 11g pureg up" Haven't rebooted, so I've brought up wlan2 by hand: root@coyote:~# ifconfig wlan2 create wlandev ath0 wlanmode hostap country DE authmode wpa ifconfig: SIOCS80211: Device busy Exit 1 root@coyote:~# ifconfig wlan2 wlan2: flags=8943 metric 0 mtu 1500 ether 68:a3:c4:51:44:99 inet6 fe80::6aa3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative scopeid 0xd nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid COYOTE_GUEST channel 8 (2447 MHz 11g) bssid 68:a3:c4:51:44:99 regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIXED deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme burst dtimperiod 1 -dfs and it also magically got added to bridge0. root@coyote:~# /etc/rc.d/hostapd start wlan2 Starting hostapd. Configuration file: /etc/hostapd-wlan2.conf Using interface wlan2 with hwaddr 68:a3:c4:51:44:99 and ssid "COYOTE_GUEST" root@coyote:~# egrep -v '^#|^$|passphrase' /etc/hostapd-wlan2.conf interface=wlan2 driver=bsd logger_syslog=-1 logger_syslog_level=3 logger_stdout=-1 logger_stdout_level=2 debug=1 dump_file=/tmp/hostapd-wlan2.dump ctrl_interface=/var/run/hostapd-wlan2 ctrl_interface_group=wheel ssid=COYOTE_GUEST country_code=DE hw_mode=g macaddr_acl=0 auth_algs=1 wme_enabled=1 wpa=2 wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP and that's when the trouble starts to appear, dmesg now get's funny messages like: wlan2: Ethernet address: 68:a3:c4:51:44:99 wlan2: promiscuous mode enabled ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 0) ath0: ath_transmit: sc_inreset_cnt > 0; bailing ath0: ath_tx_should_swq_frame: 50:46:5d:21:16:df: Node is asleep; sending mgmt (type=0, subtype=176) ath0: ath_tx_should_swq_frame: 38:e7:d8:69:c0:6e: Node is asleep; sending mgmt (type=0, subtype=176) ath0: ath_tx_should_swq_frame: b4:07:f9:e8:8f:8e: Node is asleep; sending mgmt (type=0, subtype=176) ath0: ath_node_recv_pspoll: 38:e7:d8:69:c0:6e: not in powersave? ath0: ath_tx_node_wakeup: an=0xfffffe0126489000: node was already awake ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? ath0: ath_tx_node_wakeup: an=0xfffffe001e413000: node was already awake ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? ath0: ath_tx_node_wakeup: an=0xfffffe0088add000: node was already awake Looking at some Android devices, they see that SSID as "Secured with WEP", so no WPA2 :/ An oldish HTC Desire won't even see that SSID. Neither will a Ubuntu laptop. Can someone unstupid me? Do I need a wlanbssid override for wlan2? Now that it is in this state, the first devices fail to re-authenticate (on wlan0) with this AP. Guess I'll tear down wlan2 again. The second part of my question is related to buying recommendations for 5GHz USB wlan fobs that work solid as an AP (and virtual AP) under FreeBSD. Not all of my equipment can to 5GHz, so I need a dual-band solution (with VAPs for the 2.4GHz band). What do people use around here, what works solidly? Cheers, Uli From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 18:03:04 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 23657B4A for ; Wed, 16 Oct 2013 18:03:04 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (secure.freebsdsolutions.net [69.55.234.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 05F40205F for ; Wed, 16 Oct 2013 18:03:03 +0000 (UTC) Received: from [10.10.1.32] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by ns1.jnielsen.net (8.14.4/8.14.4) with ESMTP id r9GHeLXr032940 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 16 Oct 2013 13:40:22 -0400 (EDT) (envelope-from lists@jnielsen.net) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Why does ath(4) suck, and what else to buy? From: John Nielsen In-Reply-To: Date: Wed, 16 Oct 2013 11:40:23 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <1B911791-BC03-4740-BD2B-4060BB0C5FFB@jnielsen.net> References: To: =?iso-8859-1?Q?Ulrich_Sp=F6rlein?= X-Mailer: Apple Mail (2.1510) X-DCC-sonic.net-Metrics: ns1.jnielsen.net 1156; Body=2 Fuz1=2 Fuz2=2 X-Virus-Scanned: clamav-milter 0.97.8 at ns1.jnielsen.net X-Virus-Status: Clean Cc: 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: Wed, 16 Oct 2013 18:03:04 -0000 On Oct 16, 2013, at 11:29 AM, Ulrich Sp=F6rlein = wrote: > Hey, I'm running this small -CURRENT box as router/AP and it has a > miniPCI ath(4) card that typically works fine, it only reports the > occasional >=20 > ath0: stuck beacon; resetting (bmiss count 4) >=20 > not sure if that is problematic, the wifi used to work fine. If that > message is harmless, maybe it should not be printed. But that's not > what I'm here for. I've tried setting up a 2nd wlan device and run > hostapd on it for a guest SSID for house guests, etc. >=20 > So I created wlan2 next to wlan0, ran an exact copy of the > hostapd.conf (except different SSID and PSK) and that made lots of > phones/tablets have trouble connecting or staying connected (wlan2 is > bridged to the same bridge as wlan0 and the wired interfaces, so > DHCP/DNS/routes are unlikely to be the problem). >=20 > It looks like this: >=20 > ath0: mem 0xe0a00000-0xe0a0ffff irq 17 at device 0.0 on = pci4 > ath0: AR9280 mac 128.2 RF5133 phy 13.0 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >=20 >=20 > /etc/rc.conf: >=20 > cloned_interfaces=3D"bridge0" > autobridge_interfaces=3D"bridge0" > autobridge_bridge0=3D"port* wlan0 wlan2" >=20 > wlans_ath0=3D"wlan0 wlan2" > create_args_wlan0=3D"wlanmode hostap country DE authmode wpa" > ifconfig_wlan0=3D"ssid COYOTE mode 11g pureg up" > create_args_wlan2=3D"wlanmode hostap country DE authmode wpa" > ifconfig_wlan2=3D"ssid COYOTE_GUEST mode 11g pureg up" >=20 >=20 > Haven't rebooted, so I've brought up wlan2 by hand: >=20 > root@coyote:~# ifconfig wlan2 create wlandev ath0 wlanmode hostap > country DE authmode wpa > ifconfig: SIOCS80211: Device busy > Exit 1 > root@coyote:~# ifconfig wlan2 > wlan2: flags=3D8943 > metric 0 mtu 1500 > ether 68:a3:c4:51:44:99 > inet6 fe80::6aa3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative = scopeid 0xd > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g = > status: running > ssid COYOTE_GUEST channel 8 (2447 MHz 11g) bssid = 68:a3:c4:51:44:99 > regdomain ETSI country DE indoor ecm authmode 802.1x privacy = MIXED > deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme = burst > dtimperiod 1 -dfs >=20 > and it also magically got added to bridge0. >=20 > root@coyote:~# /etc/rc.d/hostapd start wlan2 > Starting hostapd. > Configuration file: /etc/hostapd-wlan2.conf > Using interface wlan2 with hwaddr 68:a3:c4:51:44:99 and ssid = "COYOTE_GUEST" >=20 > root@coyote:~# egrep -v '^#|^$|passphrase' /etc/hostapd-wlan2.conf > interface=3Dwlan2 > driver=3Dbsd > logger_syslog=3D-1 > logger_syslog_level=3D3 > logger_stdout=3D-1 > logger_stdout_level=3D2 > debug=3D1 > dump_file=3D/tmp/hostapd-wlan2.dump > ctrl_interface=3D/var/run/hostapd-wlan2 > ctrl_interface_group=3Dwheel > ssid=3DCOYOTE_GUEST > country_code=3DDE > hw_mode=3Dg > macaddr_acl=3D0 > auth_algs=3D1 > wme_enabled=3D1 > wpa=3D2 > wpa_key_mgmt=3DWPA-PSK > wpa_pairwise=3DCCMP >=20 > and that's when the trouble starts to appear, dmesg now get's funny > messages like: >=20 > wlan2: Ethernet address: 68:a3:c4:51:44:99 > wlan2: promiscuous mode enabled > ath0: stuck beacon; resetting (bmiss count 4) > ath0: stuck beacon; resetting (bmiss count 0) > ath0: ath_transmit: sc_inreset_cnt > 0; bailing > ath0: ath_tx_should_swq_frame: 50:46:5d:21:16:df: Node is asleep; > sending mgmt (type=3D0, subtype=3D176) > ath0: ath_tx_should_swq_frame: 38:e7:d8:69:c0:6e: Node is asleep; > sending mgmt (type=3D0, subtype=3D176) > ath0: ath_tx_should_swq_frame: b4:07:f9:e8:8f:8e: Node is asleep; > sending mgmt (type=3D0, subtype=3D176) > ath0: ath_node_recv_pspoll: 38:e7:d8:69:c0:6e: not in powersave? > ath0: ath_tx_node_wakeup: an=3D0xfffffe0126489000: node was already = awake > ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? > ath0: ath_tx_node_wakeup: an=3D0xfffffe001e413000: node was already = awake > ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? > ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? > ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? > ath0: ath_tx_node_wakeup: an=3D0xfffffe0088add000: node was already = awake >=20 >=20 > Looking at some Android devices, they see that SSID as "Secured with > WEP", so no WPA2 :/ An oldish HTC Desire won't even see that SSID. > Neither will a Ubuntu laptop. Can someone unstupid me? Do I need a > wlanbssid override for wlan2? >=20 > Now that it is in this state, the first devices fail to > re-authenticate (on wlan0) with this AP. Guess I'll tear down wlan2 > again. Do wlan0 and wlan2 have different MAC addresses? They need to. You could = try adding the "bssid" flag to create_args_wlan2; that's supposed to = make a unique MAC for you based on the hardware's real MAC. However last = time I tried it (it's been a while) with my hardware it didn't work. So = alternatively, you can add "wlanaddr aa:bb:cc:dd:ee:ff" to = create_args_wlan2 (substituting a better MAC, of course). > The second part of my question is related to buying recommendations > for 5GHz USB wlan fobs that work solid as an AP (and virtual AP) under > FreeBSD. Not all of my equipment can to 5GHz, so I need a dual-band > solution (with VAPs for the 2.4GHz band). What do people use around > here, what works solidly? >=20 > Cheers, > Uli > _______________________________________________ > 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" >=20 From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 18:23:30 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 72C6534F for ; Wed, 16 Oct 2013 18:23:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3110E21EF for ; Wed, 16 Oct 2013 18:23:30 +0000 (UTC) Received: by mail-qa0-f52.google.com with SMTP id w8so916468qac.4 for ; Wed, 16 Oct 2013 11:23:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uTV4GB1+wqhWPtzaSUFzRZwX/3ZgGrWFnoZW+XlAQU4=; b=zdf/EZH9WD0cRVwd0WmAXfeW+Bj0KdlgKajLxL4vCREjTP5jodf50vjGkjlBvgVd8y 5u9IOLybzMieArj8BmtKqUlnHoX5N5k8oCluIxLilIlxd5Wh62hYawoZ7VfrMBnLi0H6 tmzUCpXt7DcumbOpTPuL7osyTXwa5PPW1mh6a1D/2Vpptg2giLEVuCVE+xXu9+WeCM5y ibhHlhTwb1k9hSQ6uVYDdqgzVvrLIylIPCklILTicB7Re7VN2lza7oU+l0ecQ4VsHshH Xb/WdzOPodGbVqVQfqRRIhHQK6Hx+YSgS6XeyjU1fe4dpzJiFyOkIo3pPvqO94a4mScS dB5A== MIME-Version: 1.0 X-Received: by 10.229.201.67 with SMTP id ez3mr5892639qcb.1.1381947809187; Wed, 16 Oct 2013 11:23:29 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Wed, 16 Oct 2013 11:23:29 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Wed, 16 Oct 2013 11:23:29 -0700 (PDT) In-Reply-To: <1B911791-BC03-4740-BD2B-4060BB0C5FFB@jnielsen.net> References: <1B911791-BC03-4740-BD2B-4060BB0C5FFB@jnielsen.net> Date: Wed, 16 Oct 2013 11:23:29 -0700 Message-ID: Subject: Re: Why does ath(4) suck, and what else to buy? From: Adrian Chadd To: John Nielsen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= , "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: Wed, 16 Oct 2013 18:23:30 -0000 Right. There's different Mac addresses. Then him.. Wonder whether I should make staggered beacons optional. Burst beacons work better but I will need to do surgery... Adrian On Oct 16, 2013 2:03 PM, "John Nielsen" wrote: > On Oct 16, 2013, at 11:29 AM, Ulrich Sp=F6rlein > wrote: > > > Hey, I'm running this small -CURRENT box as router/AP and it has a > > miniPCI ath(4) card that typically works fine, it only reports the > > occasional > > > > ath0: stuck beacon; resetting (bmiss count 4) > > > > not sure if that is problematic, the wifi used to work fine. If that > > message is harmless, maybe it should not be printed. But that's not > > what I'm here for. I've tried setting up a 2nd wlan device and run > > hostapd on it for a guest SSID for house guests, etc. > > > > So I created wlan2 next to wlan0, ran an exact copy of the > > hostapd.conf (except different SSID and PSK) and that made lots of > > phones/tablets have trouble connecting or staying connected (wlan2 is > > bridged to the same bridge as wlan0 and the wired interfaces, so > > DHCP/DNS/routes are unlikely to be the problem). > > > > It looks like this: > > > > ath0: mem 0xe0a00000-0xe0a0ffff irq 17 at device 0.0 on > pci4 > > ath0: AR9280 mac 128.2 RF5133 phy 13.0 > > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > > > > > /etc/rc.conf: > > > > cloned_interfaces=3D"bridge0" > > autobridge_interfaces=3D"bridge0" > > autobridge_bridge0=3D"port* wlan0 wlan2" > > > > wlans_ath0=3D"wlan0 wlan2" > > create_args_wlan0=3D"wlanmode hostap country DE authmode wpa" > > ifconfig_wlan0=3D"ssid COYOTE mode 11g pureg up" > > create_args_wlan2=3D"wlanmode hostap country DE authmode wpa" > > ifconfig_wlan2=3D"ssid COYOTE_GUEST mode 11g pureg up" > > > > > > Haven't rebooted, so I've brought up wlan2 by hand: > > > > root@coyote:~# ifconfig wlan2 create wlandev ath0 wlanmode hostap > > country DE authmode wpa > > ifconfig: SIOCS80211: Device busy > > Exit 1 > > root@coyote:~# ifconfig wlan2 > > wlan2: flags=3D8943 > > metric 0 mtu 1500 > > ether 68:a3:c4:51:44:99 > > inet6 fe80::6aa3:c4ff:fe51:4499%wlan2 prefixlen 64 tentative > scopeid 0xd > > nd6 options=3D29 > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > > status: running > > ssid COYOTE_GUEST channel 8 (2447 MHz 11g) bssid 68:a3:c4:51:44:= 99 > > regdomain ETSI country DE indoor ecm authmode 802.1x privacy MIX= ED > > deftxkey UNDEF txpower 30 scanvalid 60 pureg protmode CTS wme > burst > > dtimperiod 1 -dfs > > > > and it also magically got added to bridge0. > > > > root@coyote:~# /etc/rc.d/hostapd start wlan2 > > Starting hostapd. > > Configuration file: /etc/hostapd-wlan2.conf > > Using interface wlan2 with hwaddr 68:a3:c4:51:44:99 and ssid > "COYOTE_GUEST" > > > > root@coyote:~# egrep -v '^#|^$|passphrase' /etc/hostapd-wlan2.conf > > interface=3Dwlan2 > > driver=3Dbsd > > logger_syslog=3D-1 > > logger_syslog_level=3D3 > > logger_stdout=3D-1 > > logger_stdout_level=3D2 > > debug=3D1 > > dump_file=3D/tmp/hostapd-wlan2.dump > > ctrl_interface=3D/var/run/hostapd-wlan2 > > ctrl_interface_group=3Dwheel > > ssid=3DCOYOTE_GUEST > > country_code=3DDE > > hw_mode=3Dg > > macaddr_acl=3D0 > > auth_algs=3D1 > > wme_enabled=3D1 > > wpa=3D2 > > wpa_key_mgmt=3DWPA-PSK > > wpa_pairwise=3DCCMP > > > > and that's when the trouble starts to appear, dmesg now get's funny > > messages like: > > > > wlan2: Ethernet address: 68:a3:c4:51:44:99 > > wlan2: promiscuous mode enabled > > ath0: stuck beacon; resetting (bmiss count 4) > > ath0: stuck beacon; resetting (bmiss count 0) > > ath0: ath_transmit: sc_inreset_cnt > 0; bailing > > ath0: ath_tx_should_swq_frame: 50:46:5d:21:16:df: Node is asleep; > > sending mgmt (type=3D0, subtype=3D176) > > ath0: ath_tx_should_swq_frame: 38:e7:d8:69:c0:6e: Node is asleep; > > sending mgmt (type=3D0, subtype=3D176) > > ath0: ath_tx_should_swq_frame: b4:07:f9:e8:8f:8e: Node is asleep; > > sending mgmt (type=3D0, subtype=3D176) > > ath0: ath_node_recv_pspoll: 38:e7:d8:69:c0:6e: not in powersave? > > ath0: ath_tx_node_wakeup: an=3D0xfffffe0126489000: node was already awa= ke > > ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? > > ath0: ath_tx_node_wakeup: an=3D0xfffffe001e413000: node was already awa= ke > > ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? > > ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? > > ath0: ath_node_recv_pspoll: b4:07:f9:e8:8f:8e: not in powersave? > > ath0: ath_tx_node_wakeup: an=3D0xfffffe0088add000: node was already awa= ke > > > > > > Looking at some Android devices, they see that SSID as "Secured with > > WEP", so no WPA2 :/ An oldish HTC Desire won't even see that SSID. > > Neither will a Ubuntu laptop. Can someone unstupid me? Do I need a > > wlanbssid override for wlan2? > > > > Now that it is in this state, the first devices fail to > > re-authenticate (on wlan0) with this AP. Guess I'll tear down wlan2 > > again. > > Do wlan0 and wlan2 have different MAC addresses? They need to. You could > try adding the "bssid" flag to create_args_wlan2; that's supposed to make= a > unique MAC for you based on the hardware's real MAC. However last time I > tried it (it's been a while) with my hardware it didn't work. So > alternatively, you can add "wlanaddr aa:bb:cc:dd:ee:ff" to > create_args_wlan2 (substituting a better MAC, of course). > > > The second part of my question is related to buying recommendations > > for 5GHz USB wlan fobs that work solid as an AP (and virtual AP) under > > FreeBSD. Not all of my equipment can to 5GHz, so I need a dual-band > > solution (with VAPs for the 2.4GHz band). What do people use around > > here, what works solidly? > > > > Cheers, > > Uli > > _______________________________________________ > > 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" > > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g > " > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 20:55:44 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 777CB390 for ; Wed, 16 Oct 2013 20:55:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 39B602A4A for ; Wed, 16 Oct 2013 20:55:44 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id i13so1056808qae.8 for ; Wed, 16 Oct 2013 13:55:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=EJljB6+KjLtfGau8ONcGu7EFfyg6FWZbgKO5fgLNwkc=; b=ob4ALqC0K0iAYXrKGb8wLWXHJ+tjdCq36jvYd5kSb+2xlo3MoTjtrq0xmuBj5huo7I yxBi3xvQXoQsQTWuaDFC31LzWiK+h/1uNl1j9OWjaUfbxmE1MQhyL0X9548qX9sT3uwd pOZWMxnZD4/vcS+LJseeD8VxXgFb2sxEnk+Yuv+RRywleAMAsNH8L/yIX2bUNX4l/qYt RVqM5mR62awWpdZ8jh0u5Y4bZ16PDX7VPQ0ufIBF/t2piXe4+it3EW80lk7Q3qulSCoc WWEVmiT2TNfsQPdafSzAW+/ZZ3Y1VFlT3AlGaYIXfsyPe8HAFbG0Nnzc1cEu7MS2J6Cu 2toA== MIME-Version: 1.0 X-Received: by 10.49.62.3 with SMTP id u3mr6742123qer.6.1381956943436; Wed, 16 Oct 2013 13:55:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 16 Oct 2013 13:55:43 -0700 (PDT) In-Reply-To: References: Date: Wed, 16 Oct 2013 13:55:43 -0700 X-Google-Sender-Auth: S-SMRziBzFvlnNnoBlWxIOeuf0Y Message-ID: Subject: Re: Why does ath(4) suck, and what else to buy? From: Adrian Chadd To: =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 20:55:44 -0000 .. and there aren't currently any USB fobs that work rock solid in AP mode in 5GHz. Sorry. -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 21:18:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 89684C8C for ; Wed, 16 Oct 2013 21:18:39 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 516192B82 for ; Wed, 16 Oct 2013 21:18:38 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:11789] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id C6/BA-15942-DA20F525; Wed, 16 Oct 2013 21:18:37 +0000 Date: Wed, 16 Oct 2013 21:18:37 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: Subject: Re: AR934x initial support is now in the tree X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 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: Wed, 16 Oct 2013 21:18:39 -0000 > The AR9271 is a USB-connected AR9285, for all intents and purposes. > So it would use ath(4), if ath(4) had the required USB glue. > Sorry. > -adrian NetBSD-current seems to support AR9271, so maybe the required USB glue is not too far away? I haven't set it up yet, so can't see if it really works. So far, I use NetBSD-current amd64 with subversion built from pkgsrc to checkout and update FreeBSD source tree. NetBSD-current amd64 works with Realtek 8111E Ethernet on MSI Z77 MPOWER motherboard, while FreeBSD fails to connect. Otherwise, I can try to set up wifi through rsu or ndis, or see if ndis can work with Realtek 8111E Ethernet. Tom From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 21:23:20 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A880A15B for ; Wed, 16 Oct 2013 21:23:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 68A622BD5 for ; Wed, 16 Oct 2013 21:23:20 +0000 (UTC) Received: by mail-qa0-f46.google.com with SMTP id j15so4914963qaq.5 for ; Wed, 16 Oct 2013 14:23:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=wO067gnfTmTxCmFFvnLr8OQyCYAqlHfvUdonc9jbzGA=; b=BAhZEr13EJZgWzFjP/FVNoDBxdFMdRxtDCQhcQiCvhr7zpP6QgMIwV91oXiCxpcKpd 2B/3v/pEfBQHPAvm5yz+eV6ehVekeEDai8gMDbuRsze0zrQDyl7eKusTToOcl8fK2PMh 32TpvwjdJpUM2p1yoswC7iE+wwaNEojuVsY5q4IJl27wbh9fLRwUk34vg2PmLbQB1fI7 mZPfct6lZd+hWc1nkN8Et3WfqLQqoROuExJl7v3K8JI1Z/Gx0m9Qrm8iH5x89rm538g/ fCPyjZCbjZyzHuHKjRHvu2hofPCNrsLY9rD0mTR4uw6xBsDXLd3e7kcpfb0Q7FDqWGWD BKGg== MIME-Version: 1.0 X-Received: by 10.49.12.14 with SMTP id u14mr6963497qeb.74.1381958599625; Wed, 16 Oct 2013 14:23:19 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 16 Oct 2013 14:23:19 -0700 (PDT) In-Reply-To: References: Date: Wed, 16 Oct 2013 14:23:19 -0700 X-Google-Sender-Auth: PZTKrpNgdJple7BOcP-D2ILPbMg Message-ID: Subject: Re: AR934x initial support is now in the tree From: Adrian Chadd To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 21:23:20 -0000 Where in their repo is the AR9271 support? -adrian On 16 October 2013 14:18, Thomas Mueller wrote: > > The AR9271 is a USB-connected AR9285, for all intents and purposes. > > > So it would use ath(4), if ath(4) had the required USB glue. > > > Sorry. > > > > -adrian > > NetBSD-current seems to support AR9271, so maybe the required USB glue is > not too far away? > > I haven't set it up yet, so can't see if it really works. > > So far, I use NetBSD-current amd64 with subversion built from pkgsrc to > checkout and update FreeBSD source tree. > > NetBSD-current amd64 works with Realtek 8111E Ethernet on MSI Z77 MPOWER > motherboard, while FreeBSD fails to connect. > > Otherwise, I can try to set up wifi through rsu or ndis, or see if ndis > can work with Realtek 8111E Ethernet. > > Tom > > From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 16 21:25:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 57AEF18D for ; Wed, 16 Oct 2013 21:25:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 170692BE5 for ; Wed, 16 Oct 2013 21:25:24 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id w8so4963344qac.15 for ; Wed, 16 Oct 2013 14:25:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=VqW+jXl0LPr1u2Mzh4JCOXV6ptNOrxZJZRIrs3XyvgE=; b=A5RvfUndSc6WYqa18OynA/motYUsxA4WsJduy/Bq+jnMMPF1J9Wq3lijrEtzOXnxWt M251c1duRrW1NlVqsHuwuZiatpsjoXmsDF9cF0Voi/iTiOdShexnWQLG/OjYJqFJEuDX BfXaKbsSx/jCydDdeRPlO7chFmW1E0W0KzPkGF7NrMwOsrXbaAh4ZY4ROOr97D26XNtv dACesk63svdkZERDYK5NUM4Ht9JZbtEbVFoT80lUh9mR4sAnX8TH0rRfN+soHVJvlNp3 QTgR+Kw67WdePTR1FczGjn5xrywidQZzUCx+BCOpFX048/zhyBGiBJ8j6gNSIPy8Uqfz PauQ== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr7766984qai.74.1381958723195; Wed, 16 Oct 2013 14:25:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 16 Oct 2013 14:25:23 -0700 (PDT) In-Reply-To: References: Date: Wed, 16 Oct 2013 14:25:23 -0700 X-Google-Sender-Auth: xN_o5EAiyMirHqQ6jq2BegV2LLU Message-ID: Subject: Re: AR934x initial support is now in the tree From: Adrian Chadd To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 16 Oct 2013 21:25:24 -0000 oh, it's the athn port from openbsd. Sure, if someone ports the USB glue from that over, but glues it into our ath driver and ath_hal code, I'll commit it. The only bits are: * usb probe/attach * usb command send/receive * basic register read/write ops * HTC commands (new station, del station, rate control setup, etc.) if someone gets the first three done I'll help massage the rest of the ath driver to work with the USB nics. But, you should start on an AR7010 NIC as the AR9271 requires USB _AND_ HAL changes. I don't mind porting the HAL changes over (there aren't many) but I'd rather have the USB bits working before I try that. -adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 17 06:03:12 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5AC4148 for ; Thu, 17 Oct 2013 06:03:12 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 7F0612483 for ; Thu, 17 Oct 2013 06:03:11 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:18455] helo=localhost) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id DF/93-02506-E9D7F525; Thu, 17 Oct 2013 06:03:11 +0000 Date: Thu, 17 Oct 2013 06:03:10 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: Subject: Re: AR934x initial support is now in the tree X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 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: Thu, 17 Oct 2013 06:03:12 -0000 > Where in their repo is the AR9271 support? > -adrian AR9271 support in NetBSD-current is in the kernel source. In $SRCDIR/sys/dev/usb I see, among many other source-code files, if_athn_usb.c if_athn_usb.h Device falls under athn. You can do man athn. NetBSD man pages are online at http://man.netbsd.org/ which redirects to http://netbsd.gw.com/cgi-bin/man-cgi?++NetBSD-current Tom From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 17 08:28:43 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 965351CF for ; Thu, 17 Oct 2013 08:28:43 +0000 (UTC) (envelope-from sbremal@hotmail.com) Received: from dub0-omc1-s32.dub0.hotmail.com (dub0-omc1-s32.dub0.hotmail.com [157.55.0.231]) by mx1.freebsd.org (Postfix) with ESMTP id 3BC212C65 for ; Thu, 17 Oct 2013 08:28:42 +0000 (UTC) Received: from DUB126-W3 ([157.55.0.238]) by dub0-omc1-s32.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Oct 2013 01:28:40 -0700 X-TMN: [ODbHipE3Bz7k4lEE6SStU9jrkieCUGYK] X-Originating-Email: [sbremal@hotmail.com] Message-ID: From: To: "freebsd-wireless@freebsd.org" Subject: RE: WLAN PCIe HW recommendation for 8.1 Date: Thu, 17 Oct 2013 08:28:40 +0000 Importance: Normal In-Reply-To: References: , , , , , , , , , , , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 17 Oct 2013 08:28:40.0929 (UTC) FILETIME=[E271ED10:01CECB12] 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: Thu, 17 Oct 2013 08:28:43 -0000 Thought I share good news as well:=0A= =0A= 1. Temporarily switched to power line network=2C so the server is 'wireless= ' and functions as wanted. Speed dropped from about 1.2 Mbit within the apa= rtment to 300 Kbit between the 2 floors=2C however=2C reliability is over s= peed in my case. There was no need to upgrade the server from R8.1 either.= =0A= =0A= 2. In the meantime did a test with R10 beta. Booted the server yesterday ni= ght from a R10 memory stick=2C configured a TL-WDN4800=2C and voila=2C abou= t 700 Mbit without much tuning (AP is 5 years old). (Manual config after bo= ot did not seem to work=2C but mounting the pen drive in write mode and upd= ating rc.conf=2C wpa_supplicant.conf cut it.) I will do a full night test t= he next days.=0A= =0A= Wonder if beta releases count as normal release from the upgrading perspect= ive? I could start with R10 beta on a 2nd disk=2C it will take a while unti= l all ports are reinstalled=2C configured etc. Once this is done (I will ta= ke my time) R10 final should be out. Question is: R10 beta -> R10 final upg= rade is just like any other upgrade? Or=2C shall I wait 1 month for the fin= al R10?=0A= =0A= =0A= Cheers=0A= Balazs=0A= =0A= ----------------------------------------=0A= > From: sbremal@hotmail.com=0A= > To: freebsd-wireless@freebsd.org=0A= > Subject: RE: WLAN PCIe HW recommendation for 8.1=0A= > Date: Tue=2C 8 Oct 2013 08:53:27 +0000=0A= >=0A= > 'wikidevi.com' is the answer to all questions. Many thanks!=0A= >=0A= > Wonder if there is a link to 'wikidevi.com' on the FreeBSD WLAN driver pr= oject site...=0A= >=0A= >=0A= > Cheers=0A= > Balazs=0A= >=0A= > ----------------------------------------=0A= >> Date: Mon=2C 7 Oct 2013 14:10:37 -0600=0A= >> From: wblock@wonkity.com=0A= >> To: sbremal@hotmail.com=0A= >> CC: freebsd-wireless@freebsd.org=0A= >> Subject: RE: WLAN PCIe HW recommendation for 8.1=0A= >>=0A= >> On Mon=2C 7 Oct 2013=2C sbremal@hotmail.com wrote:=0A= >>=0A= >>> I found it cumbersome to map Atheros chipsets to PCIe cards=2C most of= =0A= >>> the time this info is hidden from the adapters data sheet. I must be=0A= >>> completely on the wrong way. I would expect 10 min. to pick a PCIe=0A= >>> WLAN card from the Freebsd HW notes=2C order it=2C plug it in=2C config= ure=0A= >>> and enjoy. Like with LAN cards=2C hard disks etc. What do I do wrong?= =0A= >>=0A= >> A search at wikidevi.com for "atheros pcie" finds a few PCIe cards=2C an= d=0A= >> a bunch of mini-PCIe cards. There might be a better search term to show= =0A= >> just desktop-type PCIe.=0A= >>=0A= >> There are adapter cards to put a mini-PCIe card in a PCIe slot=2C which= =0A= >> provides more versatility.=0A= > _______________________________________________=0A= > freebsd-wireless@freebsd.org mailing list=0A= > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless=0A= > To unsubscribe=2C send any mail to "freebsd-wireless-unsubscribe@freebsd.= org" = From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 17 09:29:09 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 17299DC6; Thu, 17 Oct 2013 09:29:09 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CADA82F65; Thu, 17 Oct 2013 09:29:08 +0000 (UTC) Received: by mail-oa0-f42.google.com with SMTP id k14so1460746oag.29 for ; Thu, 17 Oct 2013 02:29:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gd5br2bPMQBxaDKyOuNyyIF7yo/qGs7H54rm5cLVn6E=; b=syGTGeIi91YBmwgcazNG0fWaJKQMpEh63xsbEDF5YQqDIlAc3T2wPiQJ6oUsRHYqmJ dzIXjUQJF6AQKJLm6hn6GmrRLW9ah2v2skzVxvliHJ4Mq0LdEBiMUZhoyO3OtBJqc0Xe E7ZPVzGWI53EGXyqBQXw7OuBgnwJSk14zg3bbG6bAIbvaPY3JqUX8AGhEIv1LuOQfgVF fhW7pBdrx2Dg5e/3m4yG8xfAJe7VGVmBb6bPbzIv0qBMSznfME+X3m6Ik3wSHWKyDtP9 JXrEU4DrfQyLTHSvoq3XLq5IYFhMZYJ2JDC3XF1hSixaWI2z7MtZ6SsJCcAleLwKQHSq n88w== MIME-Version: 1.0 X-Received: by 10.182.16.227 with SMTP id j3mr160901obd.68.1382002147972; Thu, 17 Oct 2013 02:29:07 -0700 (PDT) Received: by 10.76.69.104 with HTTP; Thu, 17 Oct 2013 02:29:07 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Oct 2013 11:29:07 +0200 Message-ID: Subject: Re: Why does ath(4) suck, and what else to buy? From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 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: Thu, 17 Oct 2013 09:29:09 -0000 2013/10/16 Adrian Chadd : > .. and there aren't currently any USB fobs that work rock solid in AP mode > in 5GHz. Sorry. Well, I'm happy to do it the other way round! That is, have the minipci ath(4) serve my 5GHz needs (one AP only), and then have a USB fob that does 2.4GHz and 2x APs (private + guest AP). I'm also happy to try patches against ath(4), if you have some that might improve stability and stuff. Cheers, Uli From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 17 12:29:37 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8C66C5F5 for ; Thu, 17 Oct 2013 12:29:37 +0000 (UTC) (envelope-from kevin.haeni@gmail.com) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6319C2B42 for ; Thu, 17 Oct 2013 12:29:37 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id u16so3638830iet.4 for ; Thu, 17 Oct 2013 05:29:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=srRHfls6ig1bA6tJRp6g0wOSXjYOn8sLSDb8GzPVn/M=; b=iV2hna74vJP7FGDUTR4dNKoRVeRbNwKsPrcA+nN3kkBPy+lbR1JXbf5HJwvxlb3UuG QdD2lnGk/Qjknidq9eC2N3YfLkjtMcw06SZrl2Q+ORj2Wx8WLYyb7sWwZNWxCJnr3ONt TI/lqPYZCKJ0UzIxqedAJ4nxtKmWkM7qORnZZ//t/HKkNoX7G3szRVPW+jL/P8V4qgYX Wh85BgJ35og2bU2s1kX5kvZ4OlETZ3jD4gSC4BpokFOtS2WcEdkkpWjRC8rMVbBAYg3z cY0r43VLsGO5PbRgVCmsDaeiWwMuzAm0f0xG7jxs/w8nGP6KUJghSMutFXn6Fr9jdl6S bfVw== MIME-Version: 1.0 X-Received: by 10.50.85.115 with SMTP id g19mr21360448igz.1.1382012976672; Thu, 17 Oct 2013 05:29:36 -0700 (PDT) Received: by 10.64.225.199 with HTTP; Thu, 17 Oct 2013 05:29:36 -0700 (PDT) Date: Thu, 17 Oct 2013 14:29:36 +0200 Message-ID: Subject: From: Kevin Haeni 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: Thu, 17 Oct 2013 12:29:37 -0000 Hello Has anybody managed to install a Intel 7260 wireless card in freebsd 9.2? I have no idea what I could do to make it work. Can anyone help me? Thanks a lot! From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 17 12:41:58 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7667BC3E for ; Thu, 17 Oct 2013 12:41:58 +0000 (UTC) (envelope-from cg@cgross.info) Received: from alpha.kreiz-it.fr (alpha.kreiz-it.fr [IPv6:2001:41d0:8:dda6::1]) by mx1.freebsd.org (Postfix) with ESMTP id 3E73A2C68 for ; Thu, 17 Oct 2013 12:41:58 +0000 (UTC) Received: from DirTech (lnr56-1-82-246-51-185.fbx.proxad.net [82.246.51.185]) by alpha.kreiz-it.fr (Postfix) with ESMTPSA id F0634E5C; Thu, 17 Oct 2013 14:41:55 +0200 (CEST) From: "Cedric GROSS" To: "'Kevin Haeni'" References: In-Reply-To: Subject: RE: Date: Thu, 17 Oct 2013 14:41:51 +0200 Message-ID: <000001cecb36$42d08f40$c871adc0$@info> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac7LNJbbztSGO4h6TWGw0aPl9mFpTQAAKDuw Content-Language: fr 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: Thu, 17 Oct 2013 12:41:58 -0000 > -----Message d'origine----- > De=A0: owner-freebsd-wireless@freebsd.org [mailto:owner-freebsd- > wireless@freebsd.org] De la part de Kevin Haeni > Envoy=E9=A0: jeudi 17 octobre 2013 14:30 > =C0=A0: freebsd-wireless@freebsd.org > Objet=A0: >=20 > Hello Hello Kevin, > Has anybody managed to install a Intel 7260 wireless card in freebsd > 9.2? > I have no idea what I could do to make it work. As the 7260 and 3160 are supported by a Linux kernel v3.10+ with = specific firmware there no chance that your NIC work with an freebsd 9.2. Sorry May be in short future within FreeBSD -HEAD. >=20 > Can anyone help me? > Thanks a lot! Cedric From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 17 16:16:01 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 95E18707 for ; Thu, 17 Oct 2013 16:16:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 56E702DEF for ; Thu, 17 Oct 2013 16:16:01 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id w8so5690119qac.15 for ; Thu, 17 Oct 2013 09:16:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3S1e6OMjSY3KarQAJ55q5XlCDpvBmdagou2KVEbVt6I=; b=lmtvs8xAOi9rzxGJKTATx/KpsCYbakelTY/SQIEDFUiTCFA++OfZ/JQRaECK18V1eC dZlZXKqHY9bNCzxduV7orFtNvar2uaV0qXU0y14Nklxna/QJKa9WkEPNXwS08nG1GvdC qKp0KpM2uvWPaB1Od5MqjBKJZ8IGbfgOz4MMBv2gqFvw4D9foo4dBDCoBXLz2AacDLEk XREzC5AGt4BDeBKvi0RZ0NjOpNodGAJxEa0ZSKUPIiR5phfDJ7+0Yu5JDeSCl6LEGkIv x9hGKN5NU1couLcXOZUFGxo+9RBTUIYpaAd8TuUR4wsVmhnfq4ssSHHmswKuwzC9NWY4 sHEA== MIME-Version: 1.0 X-Received: by 10.224.36.201 with SMTP id u9mr13229596qad.76.1382026560433; Thu, 17 Oct 2013 09:16:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 17 Oct 2013 09:16:00 -0700 (PDT) In-Reply-To: <000001cecb36$42d08f40$c871adc0$@info> References: <000001cecb36$42d08f40$c871adc0$@info> Date: Thu, 17 Oct 2013 09:16:00 -0700 X-Google-Sender-Auth: vSICELyuUWv9aZZAE6-11t1QzPM Message-ID: Subject: Re: From: Adrian Chadd To: Cedric GROSS Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Thu, 17 Oct 2013 16:16:01 -0000 Yeah, someone (hi!) has sent me a 7260. I'll give it a shot once I get Cedric's stuff in HEAD. The 7260 support is _very new_ in Linux. There's no guarantee that it would work in FreeBSD once we port things 1:1 from Linux. :-) -adrian On 17 October 2013 05:41, Cedric GROSS wrote: > > > -----Message d'origine----- > > De : owner-freebsd-wireless@freebsd.org [mailto:owner-freebsd- > > wireless@freebsd.org] De la part de Kevin Haeni > > Envoy=E9 : jeudi 17 octobre 2013 14:30 > > =C0 : freebsd-wireless@freebsd.org > > Objet : > > > > Hello > > > Hello Kevin, > > > Has anybody managed to install a Intel 7260 wireless card in freebsd > > 9.2? > > I have no idea what I could do to make it work. > > As the 7260 and 3160 are supported by a Linux kernel v3.10+ with specific > firmware there no chance that your NIC work with an freebsd 9.2. > Sorry > > May be in short future within FreeBSD -HEAD. > > > > > Can anyone help me? > > Thanks a lot! > > Cedric > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g > " > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 17 16:18:19 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D19BE8EB for ; Thu, 17 Oct 2013 16:18:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 920FB2E15 for ; Thu, 17 Oct 2013 16:18:19 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id i13so5713706qae.9 for ; Thu, 17 Oct 2013 09:18:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=wIYQmWMuUqAX4XPD4/Gbr0H0bFevd1jjQEd9BaM9ifQ=; b=IIKnLJTGgbV9EiSxPhQNEXali0RRmnUBgM2jNlPc8S0wp3d3RBa1nfraVSaiHfAAvV MMjXUKzLY0PM3e+34qMrP642pk2kyY5wx3WFS0k/cAYOVGysrV7dFAKfJGigcXgYJzeV IHW8YZ/4N13sfGGkFgRP182vmX4m2Iznm+C/sboiC9STRMYG7jZg7++j7DQOlEIo8e1W JwrkxDuhQiO2c5dyD0gFItqULdx6849DOsuUzUnuBcokXPqRjfedilaLo8CKvKJTXOss nvSXfAIzM8sMcU3dbtkSQwsbOZnlRiefBcl/Bzp0xp+PTWEtvsB72M7H66VHpSXzpnGF Aoww== MIME-Version: 1.0 X-Received: by 10.229.118.10 with SMTP id t10mr12525141qcq.5.1382026698564; Thu, 17 Oct 2013 09:18:18 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 17 Oct 2013 09:18:18 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Oct 2013 09:18:18 -0700 X-Google-Sender-Auth: oB8hY9tSMj9lw8NQ5-4sV-Foi7U Message-ID: Subject: Re: Why does ath(4) suck, and what else to buy? From: Adrian Chadd To: =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Thu, 17 Oct 2013 16:18:20 -0000 .. same deal in 2GHz. There's currently nothing that's rock solid stable and works with a large variety of devices. Sorry. -adrian On 17 October 2013 02:29, Ulrich Sp=F6rlein wrote: > 2013/10/16 Adrian Chadd : > > .. and there aren't currently any USB fobs that work rock solid in AP > mode > > in 5GHz. Sorry. > > Well, I'm happy to do it the other way round! That is, have the > minipci ath(4) serve my 5GHz needs (one AP only), and then have a USB > fob that does 2.4GHz and 2x APs (private + guest AP). > > I'm also happy to try patches against ath(4), if you have some that > might improve stability and stuff. > > Cheers, > Uli > From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 17:44:01 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 14AD1BB9; Fri, 18 Oct 2013 17:44:01 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C1FE723B5; Fri, 18 Oct 2013 17:44:00 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id n10so861877oag.39 for ; Fri, 18 Oct 2013 10:44:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=tl+U8XuUH1i+ke/Lz72XRi9RVXxYZ6HUYZIU1xHBMOc=; b=Ark2UivpX6gNMDX12d9pWAkq54PgmQ68GB82DTjezwp+S7hzznbmL3Xlv9FwWdk0az 8ag6xqOsFg+rAKjhOPQdFmnhRuxC3HsM5GuK8V7CRrbSwzrkCgY8qm8L+nEXv7WfjD/s WRvm0ZyP+UT09BgoaQn9BCcITjxekcNOrYQXkZe1Ukir8QYRE+IVYwyfgpjy+giwb3Qi +FcFMbkcChSSk5A9R2skq82DDfFKyLv+PuPx8k1hdD8TAjkuOt3QNHfBLC0J+fHjfbWh 1RI4Rs6I/MiOVHmT28fEw9lq3I4F8yAg7zx0YqdWiw2zwmjgomx9DHiDKKaVSxWZtvXW i+3g== MIME-Version: 1.0 X-Received: by 10.182.40.134 with SMTP id x6mr6387483obk.31.1382118239976; Fri, 18 Oct 2013 10:43:59 -0700 (PDT) Received: by 10.76.69.104 with HTTP; Fri, 18 Oct 2013 10:43:59 -0700 (PDT) In-Reply-To: References: Date: Fri, 18 Oct 2013 19:43:59 +0200 Message-ID: Subject: Re: Why does ath(4) suck, and what else to buy? From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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, 18 Oct 2013 17:44:01 -0000 Well, the VAP support is not a hard requirement, as I can just buy one USB fob per AP that I need (I have plenty of USB ports on this little thing). So no USB wireless device with working AP mode? :( What are other people using? Would hardware donations speed things up? Anyo= ne? Sad, Uli 2013/10/17 Adrian Chadd : > .. same deal in 2GHz. There's currently nothing that's rock solid stable = and > works with a large variety of devices. Sorry. > > > -adrian > > > > On 17 October 2013 02:29, Ulrich Sp=C3=B6rlein wro= te: >> >> 2013/10/16 Adrian Chadd : >> > .. and there aren't currently any USB fobs that work rock solid in AP >> > mode >> > in 5GHz. Sorry. >> >> Well, I'm happy to do it the other way round! That is, have the >> minipci ath(4) serve my 5GHz needs (one AP only), and then have a USB >> fob that does 2.4GHz and 2x APs (private + guest AP). >> >> I'm also happy to try patches against ath(4), if you have some that >> might improve stability and stuff. >> >> Cheers, >> Uli > > From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 17:45:25 2013 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DE71BC96 for ; Fri, 18 Oct 2013 17:45:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9CE4223D5 for ; Fri, 18 Oct 2013 17:45:25 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id j15so894671qaq.6 for ; Fri, 18 Oct 2013 10:45:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=mV+znOK/1zNoo9mmLESvm0gGN9s2cHBiHGVhlvw7wMQ=; b=UK0bdIBC1HIzX5RTTYeKE9jag39lwfm6dEvEbAPuUJMc3hji0MlSXRif2QwFoVd3u2 7b4KwZBAzHPgelGlMeSGSWdM6JV9RCvbFDO8eNX5qkFJfUNtNWvuZyEeryCuG/dLwRRt Ns+73cyiQXiuP3MRM7g3OTGWtdFfGR1fLcv3VAEubKZAfd2Nk8BjC1Dusf8dr2NZAdol gDYFzizvdhFURlpKh7JtQQ4RS4u6ea3x9zp6jobgnysmqsXWQSDCCnoTRNz5HEVtEBj6 QP3BgL2Uc9jrJXtC9UHyW1UdqVNV1eu4nufqhdxLeyb3mNDC2FG8faA692W5HNg89MzI IMIg== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr6341098qai.74.1382118324803; Fri, 18 Oct 2013 10:45:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Fri, 18 Oct 2013 10:45:24 -0700 (PDT) In-Reply-To: References: Date: Fri, 18 Oct 2013 10:45:24 -0700 X-Google-Sender-Auth: Wm1ut-N-UIl31_NgIrYfa_lEvwY Message-ID: Subject: Re: Why does ath(4) suck, and what else to buy? From: Adrian Chadd To: =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 18 Oct 2013 17:45:25 -0000 Hi, No. I have infinite hardware. I just don't have time/drive to hack on other wireless hardware at the moment. I'd appreciate it if someone else stepped up with decent interest in a USB device or two, but the interest seems .. ephemeral. -adrian On 18 October 2013 10:43, Ulrich Sp=F6rlein wrote: > Well, the VAP support is not a hard requirement, as I can just buy one > USB fob per AP that I need (I have plenty of USB ports on this little > thing). > > So no USB wireless device with working AP mode? :( > What are other people using? Would hardware donations speed things up? > Anyone? > > Sad, > Uli > > 2013/10/17 Adrian Chadd : > > .. same deal in 2GHz. There's currently nothing that's rock solid stabl= e > and > > works with a large variety of devices. Sorry. > > > > > > -adrian > > > > > > > > On 17 October 2013 02:29, Ulrich Sp=F6rlein wrot= e: > >> > >> 2013/10/16 Adrian Chadd : > >> > .. and there aren't currently any USB fobs that work rock solid in A= P > >> > mode > >> > in 5GHz. Sorry. > >> > >> Well, I'm happy to do it the other way round! That is, have the > >> minipci ath(4) serve my 5GHz needs (one AP only), and then have a USB > >> fob that does 2.4GHz and 2x APs (private + guest AP). > >> > >> I'm also happy to try patches against ath(4), if you have some that > >> might improve stability and stuff. > >> > >> Cheers, > >> Uli > > > > > From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 18:00:21 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C5465D0; Fri, 18 Oct 2013 18:00:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 77E7C249A; Fri, 18 Oct 2013 18:00:21 +0000 (UTC) Received: by mail-qe0-f47.google.com with SMTP id b4so2090258qen.20 for ; Fri, 18 Oct 2013 11:00:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=rTd67h0ktdRFATINDm8x7hISSmoWFUVLUkUypL168BE=; b=Ht6nnXo8S0sbnedWfgwA178vnf4NxtErU0co3PNex3tZvKiTXF8LUOWNdOAEFVRPDt S6v+QrojMzf0o8cEWZnGOeLcbS+fUnYkDX5g4lgHtjRwN0pZF1JD3xSUFJWNLLM3z1aF kcS5gak4OfRCEAM0kQsDe5/QR0VAbc8fgkXXCi4bBFy3KykO7Jh1hfm1KHzpyI+5FRiE +KfNnG8Vph/QGZ5p3JO4caJJXeMJetaHVTo3f/D/a8MIvLtuLoSzS7bAEi6wIcCTV3Yc BrnKj5BFLDBsz0DpkxaF1lUBofiO2mSmbsVPHJPydwdtbXib5c1MPz+3upGW+9CJBTZB 4mPg== MIME-Version: 1.0 X-Received: by 10.224.157.14 with SMTP id z14mr6403087qaw.90.1382119220640; Fri, 18 Oct 2013 11:00:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Fri, 18 Oct 2013 11:00:20 -0700 (PDT) Date: Fri, 18 Oct 2013 11:00:20 -0700 X-Google-Sender-Auth: FZrzP8rMpkhObh7lbHyPnoa3uX8 Message-ID: Subject: [rfc] removing the NDISulator From: Adrian Chadd To: "freebsd-wireless@freebsd.org" , freebsd-current Content-Type: text/plain; charset=ISO-8859-1 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: Fri, 18 Oct 2013 18:00:21 -0000 Hi all, I'd like to remove the NDISulator. I've had many requests to update it to the latest NDIS version and support more of the 64 bit wifi drivers. But, to be perfectly honest, I have no desire to keep hacking at this. The world has changed quite a bit - we can port/reimplement drivers from Linux and other BSDs. So I plan on deorbiting it - I'll mark it deprecated during 11-HEAD and target to have it removed by 11.0-RELEASE. I'd rather see more of an effort writing new drivers and porting drivers from other operating systems. Thanks, -adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 20:54:05 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 853AC55C; Fri, 18 Oct 2013 20:54:05 +0000 (UTC) (envelope-from swills@mouf.net) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 484A12D43; Fri, 18 Oct 2013 20:54:05 +0000 (UTC) Received: from mouf.net (swills@mouf [199.48.129.64]) by mouf.net (8.14.5/8.14.5) with ESMTP id r9IKrtMo049810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 18 Oct 2013 20:54:00 GMT (envelope-from swills@mouf.net) Received: (from swills@localhost) by mouf.net (8.14.5/8.14.5/Submit) id r9IKrtUv049809; Fri, 18 Oct 2013 20:53:55 GMT (envelope-from swills) Date: Fri, 18 Oct 2013 20:53:54 +0000 From: Steve Wills To: Adrian Chadd Subject: Re: [rfc] removing the NDISulator Message-ID: <20131018205352.GA44565@mouf.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Fri, 18 Oct 2013 20:54:00 +0000 (UTC) X-Spam-Status: No, score=0.0 required=4.5 tests=none autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.8 at mouf.net X-Virus-Status: Clean Cc: "freebsd-wireless@freebsd.org" , freebsd-current 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, 18 Oct 2013 20:54:05 -0000 I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4313 802.11b/g/n Wireless LAN Controller' class = network Are there docs or other drivers available that we could look at? Steve On Fri, Oct 18, 2013 at 11:00:20AM -0700, Adrian Chadd wrote: > Hi all, > > I'd like to remove the NDISulator. I've had many requests to update it to > the latest NDIS version and support more of the 64 bit wifi drivers. But, > to be perfectly honest, I have no desire to keep hacking at this. The world > has changed quite a bit - we can port/reimplement drivers from Linux and > other BSDs. > > So I plan on deorbiting it - I'll mark it deprecated during 11-HEAD and > target to have it removed by 11.0-RELEASE. > > I'd rather see more of an effort writing new drivers and porting drivers > from other operating systems. > > Thanks, > > > > -adrian > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 21:03:42 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 390E27A1; Fri, 18 Oct 2013 21:03:42 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 180A42DC1; Fri, 18 Oct 2013 21:03:42 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r9IL1NHo033851; Fri, 18 Oct 2013 14:01:23 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r9IL1Nw1033850; Fri, 18 Oct 2013 14:01:23 -0700 (PDT) (envelope-from sgk) Date: Fri, 18 Oct 2013 14:01:23 -0700 From: Steve Kargl To: Steve Wills Subject: Re: [rfc] removing the NDISulator Message-ID: <20131018210123.GA33820@troutmask.apl.washington.edu> References: <20131018205352.GA44565@mouf.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131018205352.GA44565@mouf.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , freebsd-current 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, 18 Oct 2013 21:03:42 -0000 On Fri, Oct 18, 2013 at 08:53:54PM +0000, Steve Wills wrote: > I would love to have a native driver for this: > > none2@pci0:2:0:0: > class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4313 802.11b/g/n Wireless LAN Controller' > class = network > > Are there docs or other drivers available that we could look at? > Please, don't top post as it loses context. http://www.broadcom.com/support/802.11/linux_sta.php -- Steve From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 21:19:43 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B4154B89; Fri, 18 Oct 2013 21:19:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 502622E6C; Fri, 18 Oct 2013 21:19:43 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id l13so3055458qcy.4 for ; Fri, 18 Oct 2013 14:19:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=GcK0YYwJebYhFttu/1LoilDccL5i7B7dWs12Sr2iMbc=; b=zxAOf4xXlUWe4PR1kGSseA/PnByKTxIKpSYtlRPJO5bfXWM2bx6cSqZ2g2gpaHskzo EHg3uf0edknuKEaZkHEVPgdeWWmAlgBpIG1I/J8IeyHrrDyA6mB3UzuwPlrd4ljKMEQx w+4LjW3tUeCtncD0KU7cT7MrgI+/JMxP+Z0n+HivbiDAyjGytIgNNB7j/PDRScbTP7if BDQX+0ttnONQbM7X9KCSsIDe6z0+kLvqwWVWcYS/qw2ptjCUnvNOoUq6euUpbIRqfzy6 Sh8xxCOYzjyEt7YBMuiJ9Y120M7VO36bSv92JK3yut4ihin9/d3DJSjOEz2vAMXKam1R poSg== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr7512029qai.74.1382131182489; Fri, 18 Oct 2013 14:19:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Fri, 18 Oct 2013 14:19:42 -0700 (PDT) In-Reply-To: <20131018205352.GA44565@mouf.net> References: <20131018205352.GA44565@mouf.net> Date: Fri, 18 Oct 2013 14:19:42 -0700 X-Google-Sender-Auth: puR7MLhvYeacnC7KXvTOjgUt7mk Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: Steve Wills Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" , freebsd-current 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, 18 Oct 2013 21:19:43 -0000 Hi, On 18 October 2013 13:53, Steve Wills wrote: > I would love to have a native driver for this: > > none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4313 802.11b/g/n Wireless LAN Controller' > class = network > > Are there docs or other drivers available that we could look at? > There's multiple broadcom drivers in/for the linux kernel: * b43, the reverse engineered one, from the community * brcmsmac - the softmac broadcom driver, from broadcom * the STA only binary driver from broadcom, closed source, not in the kernel. I'd really like to see bwi/bwn maintained and have support added for the later hardware. Thanks, -adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 21:26:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E1079E33; Fri, 18 Oct 2013 21:26:30 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from mail.icecube.wisc.edu (trout.icecube.wisc.edu [128.104.255.119]) by mx1.freebsd.org (Postfix) with ESMTP id B09AF2EC8; Fri, 18 Oct 2013 21:26:30 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 72D2C5838F; Fri, 18 Oct 2013 16:04:17 -0500 (CDT) X-Virus-Scanned: amavisd-new at icecube.wisc.edu Received: from mail.icecube.wisc.edu ([127.0.0.1]) by localhost (trout.icecube.wisc.edu [127.0.0.1]) (amavisd-new, port 10030) with ESMTP id Trv3U1yb7+MC; Fri, 18 Oct 2013 16:04:17 -0500 (CDT) Received: from terminus.icecube.wisc.edu (terminus.icecube.wisc.edu [172.16.223.97]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 4C9CB5838D; Fri, 18 Oct 2013 16:04:17 -0500 (CDT) Message-ID: <5261A251.4000806@freebsd.org> Date: Fri, 18 Oct 2013 16:04:17 -0500 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Steve Kargl , Steve Wills Subject: Re: [rfc] removing the NDISulator References: <20131018205352.GA44565@mouf.net> <20131018210123.GA33820@troutmask.apl.washington.edu> In-Reply-To: <20131018210123.GA33820@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" , freebsd-current 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, 18 Oct 2013 21:26:31 -0000 On 10/18/13 16:01, Steve Kargl wrote: > On Fri, Oct 18, 2013 at 08:53:54PM +0000, Steve Wills wrote: >> I would love to have a native driver for this: >> >> none2@pci0:2:0:0: >> class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 >> vendor = 'Broadcom Corporation' >> device = 'BCM4313 802.11b/g/n Wireless LAN Controller' >> class = network >> >> Are there docs or other drivers available that we could look at? >> > Please, don't top post as it loses context. > > http://www.broadcom.com/support/802.11/linux_sta.php > Have you looked at bwn(4)? It might just need an additional PCI ID. -Nathan From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 21:51:56 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E5E066C6; Fri, 18 Oct 2013 21:51:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6FB1920B7; Fri, 18 Oct 2013 21:51:56 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id x12so3130537qcv.28 for ; Fri, 18 Oct 2013 14:51:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=TKvbT2qXyk86K7kBLHhGuGXAxd6ywhGedwtJPjK1dk0=; b=f4I4naPQieiQ52Ytwu8zy1mPj+m7jHH0iMZJMyTDQIGO9ZXj8H/YL8/+xZoTzDMiV3 lIL9t/3gtiOvjVe9IsG3Z5AIU29VK7T7ls1qVXId6QpzoRmCCQrexCORSx1wReHKRcx2 +MyZOoBebqMP5LhgBG1CCKZSVt/YrdTcvoX0MYqIKMWrgecyZisWVdy3gpxmsF6B5/P/ eguPmgvOuXioS7VT5E/5WrNw4eJZG9V5wd2OSge5zIywZ7hEdWwyEt1QMYUvGbplYAku Ejtwn3nuU18eSgFd9ObF/hX2Z/sDFpB8luNMa/0T5kpeIL65udiIvlfCh4lngMx12GCV V+yg== MIME-Version: 1.0 X-Received: by 10.49.103.161 with SMTP id fx1mr7036566qeb.68.1382133115614; Fri, 18 Oct 2013 14:51:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Fri, 18 Oct 2013 14:51:55 -0700 (PDT) In-Reply-To: <5261A251.4000806@freebsd.org> References: <20131018205352.GA44565@mouf.net> <20131018210123.GA33820@troutmask.apl.washington.edu> <5261A251.4000806@freebsd.org> Date: Fri, 18 Oct 2013 14:51:55 -0700 X-Google-Sender-Auth: JQKT1PXwGFWebkNLk0PxQYgtDuE Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: Nathan Whitehorn Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Steve Wills , "freebsd-wireless@freebsd.org" , Steve Kargl , freebsd-current 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, 18 Oct 2013 21:51:57 -0000 bwn(4) requires a lot more than just an additional PCI ID. The driver is somewhat architected for all the different RF and PHY modules that plug into the internal bus (the whole SIBA thing) but it does sorely need updating. Thanks, -adrian On 18 October 2013 14:04, Nathan Whitehorn wrote: > On 10/18/13 16:01, Steve Kargl wrote: > >> On Fri, Oct 18, 2013 at 08:53:54PM +0000, Steve Wills wrote: >> >>> I would love to have a native driver for this: >>> >>> none2@pci0:2:0:0: >>> class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 >>> vendor = 'Broadcom Corporation' >>> device = 'BCM4313 802.11b/g/n Wireless LAN Controller' >>> class = network >>> >>> Are there docs or other drivers available that we could look at? >>> >>> Please, don't top post as it loses context. >> >> http://www.broadcom.com/**support/802.11/linux_sta.php >> >> > Have you looked at bwn(4)? It might just need an additional PCI ID. > -Nathan > From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 22:47:37 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 10D91669; Fri, 18 Oct 2013 22:47:37 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id EE24023E4; Fri, 18 Oct 2013 22:47:36 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 364371A3CDC; Fri, 18 Oct 2013 15:47:35 -0700 (PDT) Message-ID: <5261BA8E.4080803@mu.org> Date: Fri, 18 Oct 2013 15:47:42 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Nathan Whitehorn , Steve Kargl , Steve Wills Subject: Re: [rfc] removing the NDISulator References: <20131018205352.GA44565@mouf.net> <20131018210123.GA33820@troutmask.apl.washington.edu> <5261A251.4000806@freebsd.org> In-Reply-To: <5261A251.4000806@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" , freebsd-current 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, 18 Oct 2013 22:47:37 -0000 On 10/18/13 2:04 PM, Nathan Whitehorn wrote: > On 10/18/13 16:01, Steve Kargl wrote: >> On Fri, Oct 18, 2013 at 08:53:54PM +0000, Steve Wills wrote: >>> I would love to have a native driver for this: >>> >>> none2@pci0:2:0:0: >>> class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 >>> vendor = 'Broadcom Corporation' >>> device = 'BCM4313 802.11b/g/n Wireless LAN Controller' >>> class = network >>> >>> Are there docs or other drivers available that we could look at? >>> >> Please, don't top post as it loses context. >> >> http://www.broadcom.com/support/802.11/linux_sta.php >> > > Have you looked at bwn(4)? It might just need an additional PCI ID. > -Nathan > I'm having no love with if_bwn. Any tips on making it work better? I have -current as of ~2 weeks ago. -- Alfred Perlstein From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 18 23:17:25 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 29E8AFEF; Fri, 18 Oct 2013 23:17:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A96CF256E; Fri, 18 Oct 2013 23:17:24 +0000 (UTC) Received: by mail-qa0-f53.google.com with SMTP id k15so1143105qaq.19 for ; Fri, 18 Oct 2013 16:17:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=bhZ3HiR/1whzInSiDH1wprM12AMXDk6FDNBPpJvPn4s=; b=DJ1KCbehaaSh+VcGZV7VdnbnRAny4YOOqm9xLsFW7K5LRMK+4Tr2rHwm34J48HfMsp iFmuvyc6wQzMdnZksnWEHjGJBckcXwjAwRFGeNirQqmu7IVuL3mEQ4sCxKlc6w50vifU UaV+ZGNmdZ/Z+p+5NBhrQQ5Fi2t5S4KA+aBArpMjsQFVLNF7yUDMJiRDExUxEdk0xrPC zQI+42eXFyjhhphO6UhlinpAEncp5BcszsPUqQL8wxqE9tOo4TXsb2Y/Zf12pScu1jHL kWkbBl+n5PTT4hzDyilglWHcZ3XxvhDqjoSF4M05K+Mus9m0e+cgl8c8mlXH4Hn5gQZ1 pg+Q== MIME-Version: 1.0 X-Received: by 10.224.63.199 with SMTP id c7mr8032699qai.74.1382138243888; Fri, 18 Oct 2013 16:17:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Fri, 18 Oct 2013 16:17:23 -0700 (PDT) In-Reply-To: <5261BA8E.4080803@mu.org> References: <20131018205352.GA44565@mouf.net> <20131018210123.GA33820@troutmask.apl.washington.edu> <5261A251.4000806@freebsd.org> <5261BA8E.4080803@mu.org> Date: Fri, 18 Oct 2013 16:17:23 -0700 X-Google-Sender-Auth: -nyOGYUYuxPyWVlBiNvMDOup0VI Message-ID: Subject: Re: [rfc] removing the NDISulator From: Adrian Chadd To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Steve Wills , "freebsd-wireless@freebsd.org" , Nathan Whitehorn , Steve Kargl , freebsd-current 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, 18 Oct 2013 23:17:25 -0000 I don't know how many times i can say "it needs a maintainer" and "it needs updating." So yeah, it needs (a) a maintainer, (b) updating. -adrian On 18 October 2013 15:47, Alfred Perlstein wrote: > On 10/18/13 2:04 PM, Nathan Whitehorn wrote: > >> On 10/18/13 16:01, Steve Kargl wrote: >> >>> On Fri, Oct 18, 2013 at 08:53:54PM +0000, Steve Wills wrote: >>> >>>> I would love to have a native driver for this: >>>> >>>> none2@pci0:2:0:0: >>>> class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 >>>> vendor = 'Broadcom Corporation' >>>> device = 'BCM4313 802.11b/g/n Wireless LAN Controller' >>>> class = network >>>> >>>> Are there docs or other drivers available that we could look at? >>>> >>>> Please, don't top post as it loses context. >>> >>> http://www.broadcom.com/**support/802.11/linux_sta.php >>> >>> >> Have you looked at bwn(4)? It might just need an additional PCI ID. >> -Nathan >> >> I'm having no love with if_bwn. Any tips on making it work better? > > I have -current as of ~2 weeks ago. > > -- > Alfred Perlstein > > From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 19 06:01:46 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E831BD03 for ; Sat, 19 Oct 2013 06:01:46 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id B2D4627E2 for ; Sat, 19 Oct 2013 06:01:46 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:42053] helo=localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 81/4D-19454-84022625; Sat, 19 Oct 2013 06:01:45 +0000 Date: Sat, 19 Oct 2013 06:01:44 +0000 Message-ID: <81.4D.19454.84022625@cdptpa-oedge03> From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: Subject: Re: [rfc] removing the NDISulator X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 Cc: freebsd-current@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, 19 Oct 2013 06:01:47 -0000 > I'd like to remove the NDISulator. I've had many requests to update it to > the latest NDIS version and support more of the 64 bit wifi drivers. But, > to be perfectly honest, I have no desire to keep hacking at this. The world > has changed quite a bit - we can port/reimplement drivers from Linux and > other BSDs. > So I plan on deorbiting it - I'll mark it deprecated during 11-HEAD and > target to have it removed by 11.0-RELEASE. > I'd rather see more of an effort writing new drivers and porting drivers > from other operating systems. > Thanks, > -adrian I too would like to see more effort writing new Ethernet and wifi drivers and porting from other operating systems. But I would like to keep the NDISulator/NDISwrapper as a fallback. There are still wifi adapters, Ethernet too, where there is no FreeBSD driver (AR9271 for instance), or the FreeBSD driver is buggy. Realtek 8111E on MSI Z77 MPOWER motherboard is one case in point: good with NetBSD-current and Linux but not OpenBSD 5.3 LiveUSB or FreeBSD. I see FreeBSD 10.0-to-be has a bigger selection of drivers than 9.2. I don't see improvements so far in 11-HEAD over 10.0-BETA1, but that's because 11-HEAD is at a very early stage. Regarding NDISulator, I see that it seems nowadays that many MS-Windows driver packages, when unzipped, have setup.exe, some .ini files, some .cab and .hdr files but no .inf and .sys files necessary for the NDISulator. Presumably these files are created/unpacked when the driver is installed in MS-Windows. Tom From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 19 11:01:56 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2BBA550A; Sat, 19 Oct 2013 11:01:56 +0000 (UTC) (envelope-from mp39590@gmail.com) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1E375247F; Sat, 19 Oct 2013 11:01:54 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id er20so1573073lab.7 for ; Sat, 19 Oct 2013 04:01:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=u2TGggmqKW2W12UH76g0+izyb+n/rT3Ro9hUaOo371M=; b=KWGk9Otu2mgdAa269/aaKbASAP60LoM3nwzr4CQvA6X7z6CkNXgq6+TNTuArvQ6QLp kKBP+fIMU70Dbi0/M9JvPFjPfiAC/ThVIjQEVT4gsbI24/MOoN9JyQXSu+ZjZ/G46e0h qK9GS/37648ln/5lb2+qOWPFnChJ404VRPV29UVTRbEN0DnWb6WkXkXyp84xkNhkeJhd mRS3f7g0PhXo421APQ0n1Efp+16V9zRBK50VWzmfRN03hs5zXV718lbKz6JB2o1py1xt n4P3rur4EkHKySgV+e6pVnFtQC08FSK7Rc+D5QoQd+LH5G+KZTAEE9Y79/yCWXgubtlt 6qgQ== X-Received: by 10.152.121.3 with SMTP id lg3mr5781825lab.0.1382180513073; Sat, 19 Oct 2013 04:01:53 -0700 (PDT) Received: from edge ([91.123.18.167]) by mx.google.com with ESMTPSA id ua4sm4939236lbb.17.2013.10.19.04.01.52 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 19 Oct 2013 04:01:52 -0700 (PDT) Date: Sat, 19 Oct 2013 15:01:47 +0400 From: m To: Adrian Chadd Subject: Re: [rfc] removing the NDISulator Message-ID: <20131019110147.GA1095@edge> References: <20131018205352.GA44565@mouf.net> <20131018210123.GA33820@troutmask.apl.washington.edu> <5261A251.4000806@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Steve Wills , "freebsd-wireless@freebsd.org" , Nathan Whitehorn , Steve Kargl 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, 19 Oct 2013 11:01:56 -0000 On 01:51 19-Oct 2013 Adrian Chadd wrote: > bwn(4) requires a lot more than just an additional PCI ID. > > The driver is somewhat architected for all the different RF and PHY modules > that plug into the internal bus (the whole SIBA thing) but it does sorely > need updating. > In brcsmac (driver that supports 4313 and whole bunch of new chips) they have replaced SIBA with AMBA-like bus[1]. Although, README says, that they don't use anything AMBA-specific. Probably SIBA can be hacked up at least for PCI case. Actually, I've started playing with Linux version of the driver[2], it's opensource and dual-licensed, but code seem to me very tangled. (Code of the bus part is GPL-only) Can you recommend any papers about wireless drivers in general? Particularly, I'm interested in working with PHY/ratetables. [1] https://github.com/torvalds/linux/blob/master/drivers/bcma/README [2] https://github.com/torvalds/linux/tree/master/drivers/net/wireless/brcm80211/brcmsmac From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 19 12:16:44 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 51C9F2F3; Sat, 19 Oct 2013 12:16:44 +0000 (UTC) (envelope-from ftp51246-2575596@sh4-5.1blu.de) Received: from sh4-5.1blu.de (sh4-5.1blu.de [178.254.11.41]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 12D0D279A; Sat, 19 Oct 2013 12:16:43 +0000 (UTC) Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.76) (envelope-from ) id 1VXVWj-00008K-Tc; Sat, 19 Oct 2013 14:21:05 +0200 Date: Sat, 19 Oct 2013 14:21:05 +0200 From: Matthias Apitz To: Adrian Chadd Subject: Re: [rfc] removing the NDISulator Message-ID: <20131019122105.GA28947@sh4-5.1blu.de> References: <20131018205352.GA44565@mouf.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 7.0-RELEASE (i386) User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-wireless@freebsd.org" , freebsd-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Matthias Apitz 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, 19 Oct 2013 12:16:44 -0000 El día Friday, October 18, 2013 a las 02:19:42PM -0700, Adrian Chadd escribió: > I'd really like to see bwi/bwn maintained and have support added for the > later hardware. Hi Adrian, $ pciconf -vl ndis0@pci0:1:0:0: class=0x028000 card=0xe01b105b chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4312 802.11b/g LP-PHY' class = network I'm using NDIS as well in r250588. Is bwi/bwn the point to start to look into for this chip? Thanks matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards