From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 21 03:27:45 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 571B89BE; Sun, 21 Apr 2013 03:27:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id C2A559B; Sun, 21 Apr 2013 03:27:44 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id m1so4998272wea.27 for ; Sat, 20 Apr 2013 20:27:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:cc:content-type; bh=HIfongEEHcKnzaNt7J1wg8khonGBwXyIVF8p1T1CboM=; b=QeK+0PWGhPQTdP61Xw9T9JkGefX6QKSufda7Hailimiy0IlNlOW/IvbJzMO3on9SV1 M4GrLkm5QAN/D49jrMDC/ElkbyzFfBHDn8lqk7aMKU/9Ho/DNz08lOQpjKRTnz4R8C9B C+ZWZUJGCSirbZ4ariczSdbUwHRT2c94u5v7ENIJ87AwE9g6rgUnEAB/40kSulCNf/Eb kQeal8YbNsOGaRFQ6lLWggESDNo1VGV3n+XFyLOCPCwlKyeOhV4FCjIHWa1jr45ksSoa O2q9tBEI3v4cTY7GXFPYyVjRC9OVdt+g4Xf51lZ8wNfkVpCsKboXCiiv+XShTfUtafG7 MEpQ== MIME-Version: 1.0 X-Received: by 10.194.222.100 with SMTP id ql4mr39272008wjc.59.1366514863233; Sat, 20 Apr 2013 20:27:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.88.129 with HTTP; Sat, 20 Apr 2013 20:27:43 -0700 (PDT) Date: Sat, 20 Apr 2013 20:27:43 -0700 X-Google-Sender-Auth: G21_ly6-_wpH5LIZc2MuHc8wIok Message-ID: Subject: Offer: I'm going to automate FreeBSD-wireless AP builds, but what I need is hardware.. From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-embedded@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, 21 Apr 2013 03:27:45 -0000 Hiya, Now that the missing piece of support is almost done (hostap mode powersave/pspoll support) I'm going to move onto the next thing - doing automated FreeBSD builds for people to run on AP equipment. What I have that is publicly available: * Ubiquiti Routerstation * Ubiquiti Routerstation Pro * D-Link DIR-825 * TP-Link TL-WR1043nd .. and lots of Atheros reference designs that are almost-but-not-quite what people actually ship. :-) I've had plenty of people ask me if I can supply builds for their various wifi APs so they don't have to build the software themselves. So here's my offer - if you'd like me to add to the above list of hardware that I'll do automatic builds for, I'll need some hardware. If you send me a supported AP, I'll snaffle the relevant bits from linux/openwrt/atheros and stick it into my build list. The 'supported hardware" list: * .. openwrt runs on it. :-) * anything with an Atheros MIPS24k core - AR71xx, AR913x, AR724x, AR933x * Atheros 802.11n wifi * At least 32MB RAM * At least 8MB of flash The last two are annoying - yes, we could fit inside 16MB RAM and 4MB flash, but we need a lot more work done on the FreeBSD side. So I'm setting the minimum bar there. If you don't know what hardware is in the unit - take a look at the openwrt wiki. I'm just wrapping up some automated build scripts now and I expect to start building test images in the next week or so. Thanks! Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 21 05:07:41 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 20EB8524 for ; Sun, 21 Apr 2013 05:07:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ia0-x236.google.com (mail-ia0-x236.google.com [IPv6:2607:f8b0:4001:c02::236]) by mx1.freebsd.org (Postfix) with ESMTP id E35BD66B for ; Sun, 21 Apr 2013 05:07:40 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id u20so4499186iag.13 for ; Sat, 20 Apr 2013 22:07:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer:x-gm-message-state; bh=o5Vu+H43xP4Sp5/mhU/M4QvPgrl5fvaoXpqNegOj76k=; b=fAB1aiyhOnz0lrFIvpwU2NLNeiigW5zvh8pbFwWKy90pJbIXLTR5zmztsi6pmH7QL7 Iqh5yZNVpFGjqRHgNP2yZDkkei1XVF2Gf5ngy4dUhlRWE+rDHPSiTZY/S4T2EyD/OeDR IsDneCkJdiHGdux3HeOnluqfhyxlrXgSVpZI9DVfeojGFWjkyY34PwrdLAWdFfjO7smB ZkBKY1AfKndJn7imcMEbwDoQu+eQd55ZvSCw0fOgYPOjRCKx/iftoPQMvUk76OACQyIN C8YhBZcTnI/LNSvms9mlo1WiwP6ca5crB4XBL3ra8l6G55JgjHQzGc1wf0xx24u/CQ1a s+3g== X-Received: by 10.50.73.198 with SMTP id n6mr5379531igv.34.1366520860461; Sat, 20 Apr 2013 22:07:40 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id dy5sm11394510igc.1.2013.04.20.22.07.38 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Apr 2013 22:07:39 -0700 (PDT) Sender: Warner Losh Subject: Re: Offer: I'm going to automate FreeBSD-wireless AP builds, but what I need is hardware.. Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sat, 20 Apr 2013 23:07:37 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Adrian Chadd X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQnBLLfrJWGirarZOJRzpc2ww+8GD28QMcXYuZA6uvbg0+mq511rdwDNk+ikfwN3oxdVNm9u Cc: freebsd-wireless@freebsd.org, freebsd-embedded@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, 21 Apr 2013 05:07:41 -0000 On Apr 20, 2013, at 9:27 PM, Adrian Chadd wrote: > Hiya, >=20 > Now that the missing piece of support is almost done (hostap mode > powersave/pspoll support) I'm going to move onto the next thing - > doing automated FreeBSD builds for people to run on AP equipment. >=20 > What I have that is publicly available: >=20 > * Ubiquiti Routerstation > * Ubiquiti Routerstation Pro > * D-Link DIR-825 > * TP-Link TL-WR1043nd >=20 > .. and lots of Atheros reference designs that are almost-but-not-quite > what people actually ship. :-) >=20 > I've had plenty of people ask me if I can supply builds for their > various wifi APs so they don't have to build the software themselves. >=20 > So here's my offer - if you'd like me to add to the above list of > hardware that I'll do automatic builds for, I'll need some hardware. > If you send me a supported AP, I'll snaffle the relevant bits from > linux/openwrt/atheros and stick it into my build list. >=20 > The 'supported hardware" list: >=20 > * .. openwrt runs on it. :-) > * anything with an Atheros MIPS24k core - AR71xx, AR913x, AR724x, = AR933x > * Atheros 802.11n wifi > * At least 32MB RAM > * At least 8MB of flash >=20 > The last two are annoying - yes, we could fit inside 16MB RAM and 4MB > flash, but we need a lot more work done on the FreeBSD side. So I'm > setting the minimum bar there. >=20 > If you don't know what hardware is in the unit - take a look at the > openwrt wiki. >=20 > I'm just wrapping up some automated build scripts now and I expect to > start building test images in the next week or so. That sounds cool, but do we need another st of scripts to build images? = What does yours give that others don't :) Warner= From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 21 05:08: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]) by hub.freebsd.org (Postfix) with ESMTP id CEDFB56B; Sun, 21 Apr 2013 05:08:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by mx1.freebsd.org (Postfix) with ESMTP id 4330D678; Sun, 21 Apr 2013 05:08:58 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id h11so2915577wiv.4 for ; Sat, 20 Apr 2013 22:08:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=XxP/mJNbpRJeBbpfQoL5QZ39V03rVi4wrkFmlJjU6sM=; b=q46n+4CtjZNZ1Rdhd3uNgnBBxCKUaEoG42/kIX0wE7LACN80cmX6y3samh3NP5EgKj PsZ3RGwwLFjtJFOeBhuQwCXSJba10NGCF+yNhP7G3zvGg+Vi60RSjPx0EGH+/046z4B3 fpc0e6Zl6xfniNDRpGDOmMgwuTXH2d7ktYSn2zmGCWCE8P0QSFP7oksnT9pH9Yk0JD6N QelQgctM0bWKzuNmX5IXiB1oV3JBTALO3AsVw6HJx897pR/lr/7BekOg1I1w5287zIVw MFXW4I8hhBqzg/MF/su44WDQ2QjvxBvxoh+8y2IruVpkondC+3a6DJbc8mmGHpm5Z+sX Qc5A== MIME-Version: 1.0 X-Received: by 10.194.142.236 with SMTP id rz12mr40066546wjb.12.1366520937365; Sat, 20 Apr 2013 22:08:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.88.129 with HTTP; Sat, 20 Apr 2013 22:08:57 -0700 (PDT) In-Reply-To: References: Date: Sat, 20 Apr 2013 22:08:57 -0700 X-Google-Sender-Auth: wjX63C9_BEDK1f6UpgVhFw6vD8g Message-ID: Subject: Re: Offer: I'm going to automate FreeBSD-wireless AP builds, but what I need is hardware.. From: Adrian Chadd To: Warner Losh Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, freebsd-embedded@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, 21 Apr 2013 05:08:58 -0000 On 20 April 2013 22:07, Warner Losh wrote: >> I'm just wrapping up some automated build scripts now and I expect to >> start building test images in the next week or so. > > That sounds cool, but do we need another st of scripts to build images? What does yours give that others don't :) nothing in the short term; I'm going to talk about it at bsdcan and see if we can sort out some unification between the arm peeps, me and -head. adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 22 11:06:54 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B8C34624 for ; Mon, 22 Apr 2013 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8F1FC1098 for ; Mon, 22 Apr 2013 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r3MB6sS1089326 for ; Mon, 22 Apr 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r3MB6rFU089324 for freebsd-wireless@FreeBSD.org; Mon, 22 Apr 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Apr 2013 11:06:53 GMT Message-Id: <201304221106.r3MB6rFU089324@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, 22 Apr 2013 11:06:54 -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/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/175870 wireless [iwn] /etc/rc.d/netif restart cause system crash o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne 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 158 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 23 12:41:43 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3487CC4 for ; Tue, 23 Apr 2013 12:41:43 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id F18C21F7A for ; Tue, 23 Apr 2013 12:41:42 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:cc41:618e:ebfd:3416]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 7A3AB4AC58 for ; Tue, 23 Apr 2013 16:41:39 +0400 (MSK) Date: Tue, 23 Apr 2013 16:41:37 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <2810538978.20130423164137@serebryakov.spb.ru> To: freebsd-wireless@FreeBSD.org Subject: New hardware, old problem: stuck beacon when here is WiFi traffic MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 12:41:43 -0000 Hello, Freebsd-wireless. Now my router/AP is new hardware in new case, and it is not overheating for sure. AP's WiFi card is Ubiquity SR-71E MiniPCIe card. Client is Intel Advanced-N card. When AP sends stable stream of data (like RDesktop connection from WiFi client to computer on wired network), AP gives big pauses sometime, with "ath0: stuck beacon; resetting (bmiss count 4)" message. These pauses long enough to RDesktop client notice them and try to reconnect. But no client dissociation occurs. Here is card: ath0: mem 0xd0000000-0xd000ffff irq 18 at device 0.0 on pci3 ath0: [HT] enabling HT modes ath0: [HT] 1 stream STBC receive enabled ath0: [HT] 1 stream STBC transmit enabled ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9280 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 Here is AP settings: > ifconfig ath0 ath0: flags=8843 metric 0 mtu 2290 ether 00:15:6d:85:5f:fc nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running > ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:15:6d:85:5f:fc inet 192.168.135.1 netmask 0xffffff00 broadcast 192.168.135.255 inet6 fe80::215:6dff:fe85:5ffc%wlan0 prefixlen 64 scopeid 0x6 inet6 2001:470:923f:2::1 prefixlen 64 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid home.serebryakov.spb.ru channel 3 (2422 MHz 11g ht/40+) bssid 00:15:6d:85:5f:fc regdomain ROW country DE ecm authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 30 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 -dfs Here is ath-related dmesg: ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: ath_bar_response: huh? bar_tx=0, bar_wait=0 ath0: stuck beacon; resetting (bmiss count 4) Here is my sources: "10.0-CURRENT FreeBSD 10.0-CURRENT #0 r249767M: Mon Apr 22 22:22:47 MSK 2013". I have old router with AR9220 card, which I could use as spectrum analyzer, if I'm giving proper instructions how to setup in in such way :) -- // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 23 14:43:48 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D37FFD18; Tue, 23 Apr 2013 14:43:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 439F1175A; Tue, 23 Apr 2013 14:43:48 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id j13so321332wgh.26 for ; Tue, 23 Apr 2013 07:43:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=KCD/32K94x9BjgbPTV39eU+axmsDv/JRX/sEDnoO9xY=; b=w55E8vGmd9r0uthMiCA5ZsZWha7XVj0ugxRCIREoWBnmqzJ6QWSr+aJi8ek1IrN3Xo tq9BVmG6aB6uW74KGv4lY79YvmD6TG6wx81crd9DqVKXyxi7u7XuHMT6apltVHEllaby E36U0RKXXxSylmWf6C9In5UnuwJcrTUpQ/G1Xe6aGokewe+Wgsf7TakX40OzsRwUfNJm 7gVnenlUh5rIOY08ISnQl9jZXm0KrxAmLVR5hVqcLdbNqpu+mmxgnyst+Y1Uyk0UnIX3 dmkemtZEm1Mxz7jHmTOLbJmRQ4dM4u29Hfk9JOZx/VUkkyL6hFi6yqwnXwtcbemwJicV KeBQ== MIME-Version: 1.0 X-Received: by 10.194.142.236 with SMTP id rz12mr19846261wjb.12.1366728226138; Tue, 23 Apr 2013 07:43:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.88.129 with HTTP; Tue, 23 Apr 2013 07:43:45 -0700 (PDT) In-Reply-To: <2810538978.20130423164137@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> Date: Tue, 23 Apr 2013 07:43:45 -0700 X-Google-Sender-Auth: LQStwWgnhfHNj24tEVv3QcPDhes Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 14:43:48 -0000 Try dropping it down to a HT20 channel. adrian On 23 April 2013 05:41, Lev Serebryakov wrote: > Hello, Freebsd-wireless. > > Now my router/AP is new hardware in new case, and it is not > overheating for sure. > AP's WiFi card is Ubiquity SR-71E MiniPCIe card. Client is Intel > Advanced-N card. When AP sends stable stream of data (like RDesktop > connection from WiFi client to computer on wired network), AP gives > big pauses sometime, with "ath0: stuck beacon; resetting (bmiss count > 4)" message. These pauses long enough to RDesktop client notice them > and try to reconnect. But no client dissociation occurs. > > Here is card: > > ath0: mem 0xd0000000-0xd000ffff irq 18 at device 0.0 on pci3 > ath0: [HT] enabling HT modes > ath0: [HT] 1 stream STBC receive enabled > ath0: [HT] 1 stream STBC transmit enabled > ath0: [HT] 2 RX streams; 2 TX streams > ath0: AR9280 mac 128.2 RF5133 phy 13.0 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > Here is AP settings: > >> ifconfig ath0 > ath0: flags=8843 metric 0 mtu 2290 > ether 00:15:6d:85:5f:fc > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: running >> ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:15:6d:85:5f:fc > inet 192.168.135.1 netmask 0xffffff00 broadcast 192.168.135.255 > inet6 fe80::215:6dff:fe85:5ffc%wlan0 prefixlen 64 scopeid 0x6 > inet6 2001:470:923f:2::1 prefixlen 64 > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: running > ssid home.serebryakov.spb.ru channel 3 (2422 MHz 11g ht/40+) bssid 00:15:6d:85:5f:fc > regdomain ROW country DE ecm authmode WPA2/802.11i privacy MIXED > deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 30 scanvalid 60 > protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst > dtimperiod 1 -dfs > > Here is ath-related dmesg: > > ath0: stuck beacon; resetting (bmiss count 4) > ath0: stuck beacon; resetting (bmiss count 4) > ath0: stuck beacon; resetting (bmiss count 4) > ath0: ath_bar_response: huh? bar_tx=0, bar_wait=0 > ath0: stuck beacon; resetting (bmiss count 4) > > > Here is my sources: "10.0-CURRENT FreeBSD 10.0-CURRENT #0 r249767M: > Mon Apr 22 22:22:47 MSK 2013". > > I have old router with AR9220 card, which I could use as spectrum > analyzer, if I'm giving proper instructions how to setup in in such > way :) > > -- > // Black Lion AKA Lev Serebryakov > > _______________________________________________ > 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 Tue Apr 23 14:45: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]) by hub.freebsd.org (Postfix) with ESMTP id 09CB7D93; Tue, 23 Apr 2013 14:45:40 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id C301D1786; Tue, 23 Apr 2013 14:45:39 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:cc41:618e:ebfd:3416]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 7C4F54AC57; Tue, 23 Apr 2013 18:45:30 +0400 (MSK) Date: Tue, 23 Apr 2013 18:45:28 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1813905823.20130423184528@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@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: Tue, 23 Apr 2013 14:45:40 -0000 Hello, Adrian. You wrote 23 =E0=EF=F0=E5=EB=FF 2013 =E3., 18:43:45: AC> Try dropping it down to a HT20 channel. AP or client or both? Is it enough to disable HT40 channels on client? --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 23 19:57:17 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3302B5F4; Tue, 23 Apr 2013 19:57:17 +0000 (UTC) (envelope-from bordjukov@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id CA1401BC7; Tue, 23 Apr 2013 19:57:16 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id b12so533716qca.18 for ; Tue, 23 Apr 2013 12:57:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DJlX9UAO4YjUW3GNKzkX2GKByth65iq1VL4Tdq1NMFM=; b=fPnDSYGelj0V/jB92kpMRstOo6A+UQ3YiIw3xsK+c4Z+TJ9fbwZYJg9M/t8uv63bhJ tYF64Mph3c4FbzswCJf81yorDSSJjwPLjKTCrtfhrRA88Fi4HTpPfLzBkQ+fvxzu8WKn OfrpwX0DeCDo935tIlMiO4zpkd9ix+kkNC165mUwwJFg97YpfwiijLUq7WkR3nzbRGPm NA9VXdikVE7yd7pryJTLac0lRxc4VMvkKQJItJvjYx1v3a1dbAe6zmltU+oCJq/gP9Ll YXZCAy9KK4aU1pmM3Dart3L6+rFbPXud5WhabjugPNIQwZMHQdmF8hua546pjV0lKqAZ ar+w== MIME-Version: 1.0 X-Received: by 10.49.16.99 with SMTP id f3mr30895985qed.27.1366747035535; Tue, 23 Apr 2013 12:57:15 -0700 (PDT) Received: by 10.49.39.39 with HTTP; Tue, 23 Apr 2013 12:57:15 -0700 (PDT) In-Reply-To: <1813905823.20130423184528@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> Date: Tue, 23 Apr 2013 22:57:15 +0300 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Petko Bordjukov To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 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: Tue, 23 Apr 2013 19:57:17 -0000 Falling back to a ht:20- channel did considerably lower the number of stuck beacon messages on my AR9220. It still periodically hangs though (is this why ``baseband hangs?'' is listed in the wiki?). On Tue, Apr 23, 2013 at 5:45 PM, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 23 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 18:43:45: > > AC> Try dropping it down to a HT20 channel. > AP or client or both? Is it enough to disable HT40 channels on > client? > > -- > // Black Lion AKA Lev Serebryakov > > _______________________________________________ > 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 Tue Apr 23 20:01:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1A31C718; Tue, 23 Apr 2013 20:01:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by mx1.freebsd.org (Postfix) with ESMTP id 80F5B1C05; Tue, 23 Apr 2013 20:01:56 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hm14so1289921wib.5 for ; Tue, 23 Apr 2013 13:01:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=z4gNnnDOKTXxUmPkjub03m3qvkX88shIFmr9SpBRagk=; b=bSt5uQV40y5pH6ulJj4aZHCrtXembVSJz7mzDtqPMrtEKDDrvly9r4EOD6ag78/yPT 8G2vxi7b2w/2h8zW4veESSv8WE9FWsEWFThjyYQ5jKD4nmqUd8kv2ckdcdP460wAniwU 87IqjXqukGr82RSHGhpgpegIs7B2SU6gy//ZHjQF9WkNMqvunqphmSueD/YHH9O/gdY9 NpWnMzvTEPXLuUEpDa7g8Zsvyf3Q8lvjiAFgvZNdzQ+OaAQK73r2sLyI4SaTa2ob8hui EEAn5u4GiekfQYkJw5oVJYSh3KoBAXg1X2Ffw3ZO0OdFY6I6bkN5duaUALslIoe4cjR/ tWAw== MIME-Version: 1.0 X-Received: by 10.194.142.236 with SMTP id rz12mr21796477wjb.12.1366747315717; Tue, 23 Apr 2013 13:01:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.88.129 with HTTP; Tue, 23 Apr 2013 13:01:55 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> Date: Tue, 23 Apr 2013 13:01:55 -0700 X-Google-Sender-Auth: uRMy_W0-RlBVa5CvImJncCp8Lbs Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: Petko Bordjukov Content-Type: text/plain; charset=ISO-8859-1 Cc: lev@freebsd.org, 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, 23 Apr 2013 20:01:57 -0000 On 23 April 2013 12:57, Petko Bordjukov wrote: > Falling back to a ht:20- channel did considerably lower the number of stuck > beacon messages on my AR9220. It still periodically hangs though (is this > why ``baseband hangs?'' is listed in the wiki?). Well, partially. I'm seeing stuck beacons in my testing with my modified AP power save code running, so it's also possible that there's something odd going on with the hardware programming that's locking things up. Luckily I can easy reproduce it, so I'm going to dig into it a bit more and see what I find. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 25 18:35:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 395186A8 for ; Thu, 25 Apr 2013 18:35:08 +0000 (UTC) (envelope-from onyx@z-up.ru) Received: from mx.z-up.ru (mx.z-up.ru [92.241.12.98]) by mx1.freebsd.org (Postfix) with ESMTP id EA4FB132D for ; Thu, 25 Apr 2013 18:35:07 +0000 (UTC) Received: from onyx-y550p.loc (unknown [92.241.14.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.z-up.ru (Postfix) with ESMTPSA id 1452B1BDC22E for ; Thu, 25 Apr 2013 22:27:32 +0400 (MSK) From: Dmitry Kolosov To: freebsd-wireless@freebsd.org Subject: WDS Date: Thu, 25 Apr 2013 22:28:21 +0400 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; i386; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201304252228.21591.onyx@z-up.ru> X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: onyx@z-up.ru List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 18:35:08 -0000 I need to expand my home wireless network. My environment: 1. FreeBSD 9-S based AP with ath0 (AR922X as for pciconf) configured this way: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap dturbo regdomain RU" ifconfig_wlan0="channel 2:g ssid mynet_ath 192.168.22.1/24" hostapd_enable="YES" 2. FreeBSD 9-S based STA with ath0 configured this way: wlans_ath0="wlan0" create_args_wlan0="regdomain RU" ifconfig_wlan0="WPA DHCP" wpa_supplicant_flags="-sq" 3. I have DLink DWL 2100AP with WDS support. Please, point me to corresponding manual to setup a WDS to expand my wireless. Also, any advices about my configuration are _very_ welcomed! Thanks in advance! From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 25 20:01:52 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B3E0879E for ; Thu, 25 Apr 2013 20:01:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by mx1.freebsd.org (Postfix) with ESMTP id 50FC0172E for ; Thu, 25 Apr 2013 20:01:52 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id f11so1718490wgh.27 for ; Thu, 25 Apr 2013 13:01:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PgHJW7gk3Rlw9gO9P7bzxlt3Jrr8YuDrmgunV/1kZMU=; b=yOQqxLOT0+pUQH3Jm2+INiA7EnVKn6z/wm4raJ64xNUKSi3yFWewjWtInhc7+Zy1Kk DvzGN5JslXMHRy4cg+sHum+zz4YE4AI6gbW7BXe67HJoAWzKmvGgzKEGxbnbU2hLIsIM dgDIDRJi+GhKPQijvzE9R2pyuS7WDu5bwotAShcL0eInnKtVpfOAKMp4oVtyUfVDcSmG J+Ma6iKDrvj/8kgl2D4FfvboqE5g3knXyd6U/0Ttuj4+t3MQlJKFwJHpYmtB1HUhhXW1 Q9i2TegYisJ5xpsUO8cV+0C7JLmFVVhLQxatHppePM3nOYHmOSgBxO54yMCjgfBoNVSV mNHA== MIME-Version: 1.0 X-Received: by 10.180.107.6 with SMTP id gy6mr39927428wib.22.1366920111339; Thu, 25 Apr 2013 13:01:51 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Thu, 25 Apr 2013 13:01:51 -0700 (PDT) In-Reply-To: <201304252228.21591.onyx@z-up.ru> References: <201304252228.21591.onyx@z-up.ru> Date: Thu, 25 Apr 2013 13:01:51 -0700 X-Google-Sender-Auth: McmV8KMmG2ueZNL0evO0gAhfUjc Message-ID: Subject: Re: WDS From: Adrian Chadd To: onyx@z-up.ru Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 20:01:52 -0000 hi! There's some WDS scripts in src/tools/tools - but I've never tested WDS. I'd really love it if someone would post a howto on making WDS and DWDS work! adrian On 25 April 2013 11:28, Dmitry Kolosov wrote: > I need to expand my home wireless network. > My environment: > 1. FreeBSD 9-S based AP with ath0 (AR922X as for pciconf) > configured this way: > wlans_ath0="wlan0" > create_args_wlan0="wlanmode hostap dturbo regdomain RU" > ifconfig_wlan0="channel 2:g ssid mynet_ath 192.168.22.1/24" > hostapd_enable="YES" > > 2. FreeBSD 9-S based STA with ath0 configured this way: > wlans_ath0="wlan0" > create_args_wlan0="regdomain RU" > ifconfig_wlan0="WPA DHCP" > wpa_supplicant_flags="-sq" > > 3. I have DLink DWL 2100AP with WDS support. > > Please, point me to corresponding manual to setup a WDS to expand my wireless. > Also, any advices about my configuration are _very_ welcomed! > Thanks in advance! > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 25 20:27: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]) by hub.freebsd.org (Postfix) with ESMTP id 1CB42284; Thu, 25 Apr 2013 20:27:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by mx1.freebsd.org (Postfix) with ESMTP id 806E51876; Thu, 25 Apr 2013 20:27:04 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id m15so1755118wgh.29 for ; Thu, 25 Apr 2013 13:27:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=HPiMWzB9YqRhyNRqcXwdZnnK15FGCBSvXrdDLTOLDr8=; b=ofUbF3xbEtKBbkz22ggcFcqx6CmXm5c/+tr+kGwIWK8NJIfh4mufi4ZYiUUPKTAEdY RL6vkWyJa8MiBlkUDwo+ar1jvcW/oQASnDAklvanf8QWnXein5ztL925BW08IKEzvHfv Jmn7ukCCyCI2RXHSlwuuw6p9/QBcdNsJM0xBT8vprbfm3Sc5RSuxsk6781zl24v4IJ8t RS8VHhVlyl8FcKW04CsYrt5i0I0Pv4JlSsFuyg92kvd03JPJyF+b95AQMJnX2h0FGBOP VBk3jFYWHL/YCEM6xIWVDkdcb88qbrKmJKw0A4iIb0TrUPYGdLrgH6NyqND2Ql62Pcww hTdQ== MIME-Version: 1.0 X-Received: by 10.180.107.6 with SMTP id gy6mr64890wib.22.1366921623595; Thu, 25 Apr 2013 13:27:03 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Thu, 25 Apr 2013 13:27:03 -0700 (PDT) In-Reply-To: <6010292503.20130426001447@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> Date: Thu, 25 Apr 2013 13:27:03 -0700 X-Google-Sender-Auth: cuZKxuvlY0eDJjY-XQ5HTZlh988 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org 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: Thu, 25 Apr 2013 20:27:05 -0000 Hiya, On 25 April 2013 13:14, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 24 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 0:55:52: > > AC> Turn on reset debugging - sysctl dev.ath.0.debug=3D0x20 > Log attached. Debug was set to BAR + reset flags, UDP stream from AP > to client, at some moment AP stops to work and I've bring interface > down. Thanks. Yeah, the reset path isn't logging the contents of the TX queue. I'll go fix that in -HEAD and email you back when it's there. Thanks, adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 00:11: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]) by hub.freebsd.org (Postfix) with ESMTP id 7AF01C33; Fri, 26 Apr 2013 00:11:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id DF4741244; Fri, 26 Apr 2013 00:11:45 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id z2so3103928wey.15 for ; Thu, 25 Apr 2013 17:11:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=mszYyRbH2eX5OVF/aRKBE3Jd9NftJGeKED/fzt/q31Q=; b=RfWG6fpWobf4v6oFl0yl/Icqlqlp0YDO8TxSbhnWtkOJWdWl00Tr6Lm0tTmBXNy6Ia jcq6SXtENfq6TxcsjvJt2KLoH+J+DXfkfw2biCvl5HSFv28A1R73qyCef6wbdcdIorf3 M9ZIwDIT1KwfyoZc4ufqCG7RVvpdgDrHEpiOBNIkq3reFVW8simeV2iuJqSqNKGc97LT VRqozLCSKKC+AOCPQaAZAlk4hqZyRrJAIBzLncM38sQ4JfjcrVMHUy4//eFNT5szKDb+ Q1bx+tj3dVCpsB2nOzv8OKu3dAsPOu4/LYInIccp9h06X9Z8ut+2sJGAoZdeLreAPf3s MYwA== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr78728914wjb.36.1366935104317; Thu, 25 Apr 2013 17:11:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Thu, 25 Apr 2013 17:11:44 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> Date: Thu, 25 Apr 2013 17:11:44 -0700 X-Google-Sender-Auth: j3nhMaoYCbIY9hqBb1ioGm43aYY Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 00:11:46 -0000 Ok. Next time it happens, force a stuck beacon: sysctl dev.ath.X.forcebstuck=1 That will cause the right kind of reset in order to log the frames in the TX queue. Make sure you have the right debug mask though! Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 08:15:01 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 14035161; Fri, 26 Apr 2013 08:15:01 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id CAFF1154A; Fri, 26 Apr 2013 08:15:00 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 63A5D4AC58; Fri, 26 Apr 2013 12:14:58 +0400 (MSK) Date: Fri, 26 Apr 2013 12:14:51 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <147649399.20130426121451@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@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: Fri, 26 Apr 2013 08:15:01 -0000 Hello, Adrian. You wrote 26 =E0=EF=F0=E5=EB=FF 2013 =E3., 4:11:44: AC> Ok. Next time it happens, force a stuck beacon: AC> sysctl dev.ath.X.forcebstuck=3D1 AC> That will cause the right kind of reset in order to log the frames in AC> the TX queue. AC> Make sure you have the right debug mask though! Without reboot (iface dow/up) it showed very low speed (~30Mbit UDP) with clear environment (RSSI 28, RATE 270M according to list sta). After router reboot it is 140-160Mbit/s UDP (2x2 MIMO, HT40 channel), but with drops to 20-50M for 1-2 seconds. But I cannot repeat previous hang in this "clean" conditions :) It looks like I need wait night :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 08:45: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]) by hub.freebsd.org (Postfix) with ESMTP id 09B03415; Fri, 26 Apr 2013 08:45:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by mx1.freebsd.org (Postfix) with ESMTP id 6A2B21872; Fri, 26 Apr 2013 08:45:42 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id m6so325183wiv.15 for ; Fri, 26 Apr 2013 01:45:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=lenNWukPhti1Sy6L3XzPHxa7Q5dto7QxwkeDxodqz5I=; b=FB4xrH+Gdkomhljny9VKCgPuHunzcF/6WCUrOkvEqbSU+YvkS54NAJwLKAxaA0L68C nPUrPQke5Po5BW+xNNMDhR92TaXUakZgDYQm3nzwkm9/XsEIu9zIJckG4TaPZTO5+KF5 SyMf8ga+JDDKZoDzqZyDPwKtllWaMAnBS2YVYYmd3pkm/uV1cDySuyqdejEtuCdHI0ts lRsWOyScX0cykc64ToKBeUmUBizbm/rz9l4neFriLpvhbF7D560vVKBigk93LwZfsIzZ MVeqbsGrPc7RQZnAXFUpnAGs2u6lbHxmVOZz6reGITox9f1Ptvk8i+sASo79EwikCxch A9VQ== MIME-Version: 1.0 X-Received: by 10.180.107.6 with SMTP id gy6mr2477163wib.22.1366965941611; Fri, 26 Apr 2013 01:45:41 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 01:45:41 -0700 (PDT) In-Reply-To: <99510815.20130426122508@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> Date: Fri, 26 Apr 2013 01:45:41 -0700 X-Google-Sender-Auth: GitMCmgmKVKutaBU7jAGxdiBIIs Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org 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, 26 Apr 2013 08:45:43 -0000 Hi, Wait. sysctl dev.ath.0.forcebstuck=3D1 didn't fix it? adrian On 26 April 2013 01:25, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 26 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 4:11:44: > > AC> Ok. Next time it happens, force a stuck beacon: > GOT IT! > > You could use "sudo" messages as markers in log file. > It was: > > sysctl dev.ath.0.debug=3D0x900000020 > > > sysctl dev.ath.0.forsebstuck=3D1 > ifconfig wlan0 down > > ifconfig wlan0 up > /etc/rc.d/hostapd restart > > -- > // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 08:51:19 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6E9136AB; Fri, 26 Apr 2013 08:51:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id D0BA418BE; Fri, 26 Apr 2013 08:51:18 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id t9so2876746wey.5 for ; Fri, 26 Apr 2013 01:51:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ejG2qhn9AnEtP5JT05AMPgZXZroD1NZM12GNz20a9Xk=; b=kLlbKYNhfHu4rcPw/u2+uVGUlAp1qGIiDyYW02+8ghgNI9cbO+FoAOnXMXKrCc5TT+ 4zxXEI0ak/NXc8qpJgWZ4B4GRRu4ogoThQnDqUimpIIQXWbHjna+ebLxnBYkVaUXypc9 bJXZBvQgfANLvPRhHyLroyKO9mC6S/I/tYp8RYCECjGWBnbxwFhzZMzcaZncZ0BePGKJ s8uHPtoqQSmOr2e78i7OrK2XrzKYrDIGzjDeQ54ipGPOIM98JX8+zUxABXaD8JqpXz4n pqkTcBG1JboH/Bt8pBqo6LNrG9rMLxIwY0NhBMonB/RCAkMkWVzAOYG9Q6vE6s66tAFw kzNQ== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr80862719wjb.56.1366966277230; Fri, 26 Apr 2013 01:51:17 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 01:51:17 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> Date: Fri, 26 Apr 2013 01:51:17 -0700 X-Google-Sender-Auth: vEj8OwfsUe8CFMNFg_OuBZJoepY Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 08:51:19 -0000 On 26 April 2013 01:45, Adrian Chadd wrote: > Hi, > > Wait. sysctl dev.ath.0.forcebstuck=1 didn't fix it? So the descriptors are mostly completed. I really need to hack the reset path to continue printing everything in the queue, not just the frames that were completed. But the TXQ[1] head pointer is pointing to the wrong descriptor. It's pointing to a descriptor that's finished, whose next descriptor is also finished. That makes no sense. I'll have to add some more debugging to -HEAD so to dump out the full set of TX descriptors in the queue. That hopefully will shed some light here. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 21:14: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]) by hub.freebsd.org (Postfix) with ESMTP id 040527DC; Fri, 26 Apr 2013 21:14:45 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id B62AA1E06; Fri, 26 Apr 2013 21:14:44 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 2BD354AC57; Sat, 27 Apr 2013 01:14:31 +0400 (MSK) Date: Sat, 27 Apr 2013 01:14:23 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1091133497.20130427011423@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <766430457.20130426125828@serebryakov.spb.ru> MIME-Version: 1.0 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 Reply-To: lev@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: Fri, 26 Apr 2013 21:14:45 -0000 Hello, Adrian. You wrote 26 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 18:56:57: AC> And please cc -wireless with your debugging results :) Ok. It is interesting how throughput is not connected to rate after these problems. Now I have client at stable 270M rate with RSSI ~28, and only 15-20Mbit/s of UDP traffic AP->Client... :( It looks like throughput is bad after card reset without reboot... But no ath_bar_suspend! Yes, after full reboot throughput is osscilate between 65 and 120Mbit/s! But with bar_suspsends! Maybe, it is coincidence, but I npotice this for second time... --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 21:17:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 878268EE; Fri, 26 Apr 2013 21:17:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by mx1.freebsd.org (Postfix) with ESMTP id E89961E4E; Fri, 26 Apr 2013 21:17:26 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id c10so1065966wiw.6 for ; Fri, 26 Apr 2013 14:17:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3SbV+6+MmirHC02tri7I7lCUpKwgcfnqm2mI5qTQj4E=; b=DGAS2/xgyi63eSBnxu9KT80F7DY5B71+y69HA4vQ6ys+AHn9rcpMLeQ0g39Rl5m2tC xg+cnZqHH+7dYUY456DtdvUWKDNqw4vsf7Az7xW7HkZfN+GmyGa/Gp6vnEZfzYbR4Qqi 6TSuL1dXyUx1IpuC1SZX2V5qjWj6Q/I8NCggz7yxLylZ6GmZIlzGrK5cFQOwRco5z03g KVlDBVx7u/JoSs1keY8i3OHfRckAbcOyVqfAy5rBtB2Th1DsHfjPb5rK6u5Le2ryNtA1 UxIxP0ys5d81iVud2iUBoeEbNorE83QP5SO3BQtgWV6DREmgMAZTO1/VKMe/py7XwvsX uvlQ== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr4039288wjb.36.1367011046030; Fri, 26 Apr 2013 14:17:26 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 14:17:25 -0700 (PDT) In-Reply-To: <1091133497.20130427011423@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <766430457.20130426125828@serebryakov.spb.ru> <1091133497.20130427011423@serebryakov.spb.ru> Date: Fri, 26 Apr 2013 14:17:25 -0700 X-Google-Sender-Auth: XmiFOMHpsRzLmoj0tDGCquhx9pQ Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org 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, 26 Apr 2013 21:17:27 -0000 On 26 April 2013 14:14, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 26 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 18:56:57: > > AC> And please cc -wireless with your debugging results :) > Ok. > It is interesting how throughput is not connected to rate after > these problems. Now I have client at stable 270M rate with RSSI ~28, > and only 15-20Mbit/s of UDP traffic AP->Client... :( > > It looks like throughput is bad after card reset without reboot... > But no ath_bar_suspend! > > Yes, after full reboot throughput is osscilate between 65 and > 120Mbit/s! But with bar_suspsends! > > Maybe, it is coincidence, but I npotice this for second time... All kinds of reasons for this behaviour. We'll look into it after we nail down why the TX queue is stalling. adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 21:29: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]) by hub.freebsd.org (Postfix) with ESMTP id 35FCFEB6; Fri, 26 Apr 2013 21:29:01 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id A6CA31EE2; Fri, 26 Apr 2013 21:29:00 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 0CCD84AC57; Sat, 27 Apr 2013 01:28:58 +0400 (MSK) Date: Sat, 27 Apr 2013 01:28:51 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1977535276.20130427012851@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------0431101EA34A2A206" 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 Reply-To: lev@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: Fri, 26 Apr 2013 21:29:01 -0000 ------------0431101EA34A2A206 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Hello, Adrian. You wrote 26 =E0=EF=F0=E5=EB=FF 2013 =E3., 12:51:17: >> Wait. sysctl dev.ath.0.forcebstuck=3D1 didn't fix it? Ok, several such commands helps without down/up of interface. Log attached: a lot of traffic, several BAR retransmits, interface hangs, several "forcebstuck=3D1", client could associate again and interface passes traffic. Maybe, there were too many "forcebstuck=3D1", but one ro two doesn't fix situation for sure, client was not able to assotate after first two of them. --=20 // Black Lion AKA Lev Serebryakov ------------0431101EA34A2A206-- From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 21:34:25 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CAD5577; Fri, 26 Apr 2013 21:34:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 370011F78; Fri, 26 Apr 2013 21:34:25 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id l13so1230447wie.5 for ; Fri, 26 Apr 2013 14:34:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WGe5BKbvrGUjaYAxL3Kb+HMj2k5NnRW7Oprf8hx1/ik=; b=dJ9fgzF88GcyBzAtGx5cC5u6mmhAdaa6gbP0Xp57iU3mWOnbFgQkN1+9qxA3/2C0A8 02wATKvRzMjaLtvBaLz5yO5v7KgJoJYYhhmgZYlUSFeA12+BQS44GbZvX2dDQgqaxCXZ UM5YJvKvBP+gVebAGm9gX05i5JqMf2bBtYDY6oSwLKCyeIvVc5hD5UfCsk0cI5M/WtQz bgyAb8/oCM8+cZgc2wzPJjff7EubFP/ibWhzuSPQSjJcT2J1oPJs5GVTTuQF/jgB8B6I WnnyzKr5Av9lUPDCok51/RNwlwINiGhA+OQSJHkclyLyQUQFMYRfBF+Relw8CIBSw8f9 bFWg== MIME-Version: 1.0 X-Received: by 10.180.107.6 with SMTP id gy6mr6534693wib.22.1367012064338; Fri, 26 Apr 2013 14:34:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 14:34:24 -0700 (PDT) In-Reply-To: <1977535276.20130427012851@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1977535276.20130427012851@serebryakov.spb.ru> Date: Fri, 26 Apr 2013 14:34:24 -0700 X-Google-Sender-Auth: v8u6-D0JiY2Rv9nKB2svTkmEPnE Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org 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, 26 Apr 2013 21:34:25 -0000 You're not doing something like leaving bgscan enabled, or not defining a channel up front? There's a lot of resets hre. adrian On 26 April 2013 14:28, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 26 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 12:51:17: > >>> Wait. sysctl dev.ath.0.forcebstuck=3D1 didn't fix it? > Ok, several such commands helps without down/up of interface. > Log attached: a lot of traffic, several BAR retransmits, interface > hangs, several "forcebstuck=3D1", client could associate again and > interface passes traffic. > > Maybe, there were too many "forcebstuck=3D1", but one ro two doesn't > fix situation for sure, client was not able to assotate after first > two of them. > > -- > // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 21:52:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7D0507E2; Fri, 26 Apr 2013 21:52:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by mx1.freebsd.org (Postfix) with ESMTP id DAE5C104A; Fri, 26 Apr 2013 21:52:07 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id i48so864764wef.34 for ; Fri, 26 Apr 2013 14:52:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nHKmFmeb14E/cgOujnAgm/rfaHInWh6ECDokKMUCk8c=; b=fX8T3w5/omRcRPpr/Kfic3HmFQ9Ls+e4UU5ZiYDQS2bKpO5Kx0l3usmAMp2DeN6vZJ 29HCSslIWUmoNOYKV/ex5R+Nmxu3Ruwglr75r2LvwwgIgV12K6HjAVX/wLZnN9Aw+KuM LmNMCWJ/zolT8GAVYlWUma621lfOxAGvfkjGEpN/H8ZAybL7pEOuybDCbasQZ7XQZGlk SkFt3KtDvmjIUUypvNX1qnM7nnZe1XOpnrJTSr7aeSKmgy/ZtbekYA0rxgXo5F2bfnje fcQu+gY4dzyUiaHZBkwiBJ6wTeHQXt2O1vVVENO3Dy5Hzxj5TCjh5aDFd1nI3gSqhDpS Qpww== MIME-Version: 1.0 X-Received: by 10.180.87.170 with SMTP id az10mr6672668wib.3.1367013126506; Fri, 26 Apr 2013 14:52:06 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 14:52:06 -0700 (PDT) In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1977535276.20130427012851@serebryakov.spb.ru> Date: Fri, 26 Apr 2013 14:52:06 -0700 X-Google-Sender-Auth: dSMsZPseaCJt7VVGfWK4CNG-akk Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 21:52:08 -0000 Hi, I've just committed something to -HEAD that logs -all- the descriptors in the TX queue during a reset. This requires ATH_DEBUG_RESET to be set (0x20), so use the same debug mask as before. Thanks! Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 22:30:16 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4A194CC for ; Fri, 26 Apr 2013 22:30:16 +0000 (UTC) (envelope-from rushilpaul@gmail.com) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id CCF191188 for ; Fri, 26 Apr 2013 22:30:15 +0000 (UTC) Received: by mail-la0-f50.google.com with SMTP id fl20so2062846lab.9 for ; Fri, 26 Apr 2013 15:30:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=0oC85Xl3jmVK40Bt+G6tR4ZeWI0aJW5ZUVYI7uuAXvo=; b=EgvODrNyNXIpWqhE9B9QiUMFvdFp5XdUGcGW5mXHo127GCvaGpzJwCvgrhHnPqtYT7 CJxB4lbmyUPlvxHyKUCqISCe5GFjU1aMeLXwCwXUVSzhKiouevFIElzNlcZzA/Y0Xh/H ZqFZ2/f8Lc3v78ZiirDsgrjEujuUMYJEmgWCXq9mmKKPa+e+Pok6uyrnUxtAfY06hyPU ZnlO2wicG2lnFlzyxMeDDDmKSP22yZvYJtwfzwFqNteus49Iq8djPKhf5djGJIoBVpYR RXROETrEEfauV1uUNH6t71yoJ8CvLpGSuq5vEPOMQ+wZfjdhSItAjUU24h2WcWfhVmEn qDAA== MIME-Version: 1.0 X-Received: by 10.112.189.133 with SMTP id gi5mr1912754lbc.91.1367015413741; Fri, 26 Apr 2013 15:30:13 -0700 (PDT) Received: by 10.112.140.225 with HTTP; Fri, 26 Apr 2013 15:30:13 -0700 (PDT) Date: Sat, 27 Apr 2013 04:00:13 +0530 Message-ID: Subject: 802.11 Fuzzing and Testing (GSoC) From: Rushil Paul To: 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: Fri, 26 Apr 2013 22:30:16 -0000 Can somebody give me more information on this project? I have already tested scapy on FreeBSD 9.1 and it works very well. All I'll have to do is build some test cases and test the 802.11 code? What will the test cases be like? I suppose that if we find any bugs in the code, then I will be required to provide a fix as well. I think because I have already thought of scapy, a big part of the project is automatically dealt with, and suddenly the project seems a little short for GSoC. Or am I wrong? Actually I am having trouble writing my proposal as I'm supposed to give code milestones and deliverables and there will not really be any code unless I find a bug and provide a fix. Any help is greatly appreciated. -- Regards, Rushil From owner-freebsd-wireless@FreeBSD.ORG Fri Apr 26 22:41:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F3F2E1F8 for ; Fri, 26 Apr 2013 22:41:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by mx1.freebsd.org (Postfix) with ESMTP id 8F9C111F6 for ; Fri, 26 Apr 2013 22:41:39 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id l13so1129551wie.6 for ; Fri, 26 Apr 2013 15:41:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=VhGm8d3tPq0dIGhcPJeDZ5XZ0yLJrSRisgbSEcAn02Y=; b=aXCOfZRZ0xvyQ5NcUPkyy/CWUDQ7qSzBbQBEpCFaXMlkLC6YSOJ2ec4kRDDlWsKsUC MnJvrJ4MXGO1uV4B+tLWpzFTtCrdqR0n4kwAhCeFXMvw+KYPOR3VkFvjuI0CjSjHYF2W PL+butK6YUfSfsHlqYEyy1SMp/P/nMXM64WkH8osJOW30Ac7BKbjJ6e0ycQsYU3Y+Fq6 0es97v9IrvEZ0wDoYMkyzE49oB91U6Z9Rz5bQOt4i39GYX2dtnlIw1NcfrwG5NI51fqj WV+dR3EZH2b2BhaX1zOH8gPpsabA4g+3OAdPGf2u6zBpFvt5N500wfB6gg0rZVlWHjBN wE4A== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr85202695wjb.56.1367016098634; Fri, 26 Apr 2013 15:41:38 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Fri, 26 Apr 2013 15:41:38 -0700 (PDT) In-Reply-To: References: Date: Fri, 26 Apr 2013 15:41:38 -0700 X-Google-Sender-Auth: _dW7Wmxl6Tfu4Vos_SY6lh5dgXo Message-ID: Subject: Re: 802.11 Fuzzing and Testing (GSoC) From: Adrian Chadd To: Rushil Paul Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 22:41:40 -0000 Hi! Well, that's great! Can you post instructions on what you did to get it up and working? Does it come with a large set of test cases? If not, then writing a large set of test cases would be good. And no, you don't _have_ to fix issues that you may see creep up in net80211 / drivers as a consequence of fuzzing. It'd be nice, but it doesn't have to be a part of your GSoC application! Thanks, adrian On 26 April 2013 15:30, Rushil Paul wrote: > Can somebody give me more information on this project? > I have already tested scapy on FreeBSD 9.1 and it works very well. All I'll > have to do is build some test cases and test the 802.11 code? > What will the test cases be like? I suppose that if we find any bugs in the > code, then I will be required to provide a fix as well. > I think because I have already thought of scapy, a big part of the project > is automatically dealt with, and suddenly the project seems a little short > for GSoC. Or am I wrong? > Actually I am having trouble writing my proposal as I'm supposed to give > code milestones and deliverables and there will not really be any code > unless I find a bug and provide a fix. Any help is greatly appreciated. > > -- > Regards, > Rushil > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 27 08:34:01 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DBBC32DA; Sat, 27 Apr 2013 08:34:01 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 976E512D4; Sat, 27 Apr 2013 08:34:01 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c1ca:3dbc:5137:8c40]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id E3EB84AC57; Sat, 27 Apr 2013 12:33:59 +0400 (MSK) Date: Sat, 27 Apr 2013 12:33:52 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <777510536.20130427123352@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic In-Reply-To: References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <1977535276.20130427012851@serebryakov.s pb.ru> MIME-Version: 1.0 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 Reply-To: lev@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: Sat, 27 Apr 2013 08:34:01 -0000 Hello, Adrian. You wrote 27 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 1:34:24: AC> You're not doing something like leaving bgscan enabled, or not AC> defining a channel up front? Here is my config: ifconfig_wlan0=3D"inet 192.168.135.1 netmask 255.255.255.0 mode 11ng channe= l 3:ht/40 -bgscan ssid home.serebryakov.spb.ru country DE regdomain row txp= ower 30" --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 27 09:40:53 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CD9EFFEE; Sat, 27 Apr 2013 09:40:53 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 41FC7149B; Sat, 27 Apr 2013 09:40:53 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id hm14so1355404wib.17 for ; Sat, 27 Apr 2013 02:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=U7TRyuDCXXPwYY4r/JsHXvaEJlyAFLRkGPQJhvdNuq0=; b=BhI9j1O0k4BNCcLZ/XD1xSVChrbI1W8uaf74lC+QSUGaGkzAkFwVPtcOXpdQTDP8Tl 9WhbHVOk4zHr17Qr0e8hLvxUPauypbhm1wa053HYFe/akRQC9JXRKYGKZb0vdkd3P3HJ lm5/tmbaZ9Cee9EZpX/BxKAO2r/s4owC9woJyzSsz9XYippKj9Ng+dNbmyY22DhZnBnp 92wA9cyYw1nDD5NCO90hJaJsCgb2rFJQ6QEQUIUI+tinJIcU7mpK527DxC+R0v7QcUl/ 1reKGho/wijfHIVtZi+BHC2u56BCQVPzu+59GKppl4IPwM9yLGSatFaH5QSfVlpSo2Ii iTzw== MIME-Version: 1.0 X-Received: by 10.180.93.134 with SMTP id cu6mr8390221wib.8.1367055652418; Sat, 27 Apr 2013 02:40:52 -0700 (PDT) Received: by 10.227.11.76 with HTTP; Sat, 27 Apr 2013 02:40:52 -0700 (PDT) In-Reply-To: References: Date: Sat, 27 Apr 2013 11:40:52 +0200 Message-ID: Subject: Re: 802.11 Fuzzing and Testing (GSoC) From: Monthadar Al Jaberi 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, Rushil Paul 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, 27 Apr 2013 09:40:53 -0000 Hi! Sounds nice! Have you tried to do some 802.11 tests yet? I remember I tried it once but I couldn't inject 802.11 frames, the coded needed some patching but nothing big. Yet again that was long time ago. Yeah we can help you with fixing issues. :) br, On Sat, Apr 27, 2013 at 12:41 AM, Adrian Chadd wrote: > Hi! > > Well, that's great! Can you post instructions on what you did to get > it up and working? > > Does it come with a large set of test cases? If not, then writing a > large set of test cases would be good. > > And no, you don't _have_ to fix issues that you may see creep up in > net80211 / drivers as a consequence of fuzzing. It'd be nice, but it > doesn't have to be a part of your GSoC application! > > Thanks, > > > > adrian > > > On 26 April 2013 15:30, Rushil Paul wrote: > > Can somebody give me more information on this project? > > I have already tested scapy on FreeBSD 9.1 and it works very well. All > I'll > > have to do is build some test cases and test the 802.11 code? > > What will the test cases be like? I suppose that if we find any bugs in > the > > code, then I will be required to provide a fix as well. > > I think because I have already thought of scapy, a big part of the > project > > is automatically dealt with, and suddenly the project seems a little > short > > for GSoC. Or am I wrong? > > Actually I am having trouble writing my proposal as I'm supposed to give > > code milestones and deliverables and there will not really be any code > > unless I find a bug and provide a fix. Any help is greatly appreciated. > > > > -- > > Regards, > > Rushil > > _______________________________________________ > > 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 > " > -- Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 27 18:56:31 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E6E8DEE4; Sat, 27 Apr 2013 18:56:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 5185215B4; Sat, 27 Apr 2013 18:56:31 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id l13so1779889wie.1 for ; Sat, 27 Apr 2013 11:56:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=orFkRKqB8KggO4z92dbEaA3qpnrQgliEYb+vBrJd6WI=; b=nbexs32op+AVffGVdCCK3V+fntkA/mgrzQS1Vjx/C4z+QvwIu84m6HygbDmTBp9kyf TFejktJXiE6CXOt1BEV3IrvIYejdjXcQihVuIstisbh2x63M4f5Ob4741n+QgWzA5CH/ iH98F3REeDqdoNowWLTrMZX9rCEYCBDoKFI3SL1aBotCLvs+Ty1nZftaE2puBeVg4v89 ucGDAv6XsSszVLVFRTbe8emWHi7o4OcTxr17+QFZ2ZmWmGoQSdicgOpi2i8Rkn0ytsT9 7tlGk6W1nmLfeJifu2aM2ovDiO+RqcC5/8DrJDursfGjbAKUTf06fd/hBQTyPcM7QCSy r2VQ== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr88697039wjb.56.1367088990408; Sat, 27 Apr 2013 11:56:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Sat, 27 Apr 2013 11:56:30 -0700 (PDT) In-Reply-To: <777510536.20130427123352@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> <99510815.20130426122508@serebryakov.spb.ru> <777510536.20130427123352@serebryakov.spb.ru> Date: Sat, 27 Apr 2013 11:56:30 -0700 X-Google-Sender-Auth: CZdHd6u1zQP9ys0oD9l2cDBkYGY Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org 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: Sat, 27 Apr 2013 18:56:32 -0000 On 27 April 2013 01:33, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 27 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 1:34:24: > > AC> You're not doing something like leaving bgscan enabled, or not > AC> defining a channel up front? > Here is my config: > > ifconfig_wlan0=3D"inet 192.168.135.1 netmask 255.255.255.0 mode 11ng chan= nel 3:ht/40 -bgscan ssid home.serebryakov.spb.ru country DE regdomain row t= xpower 30" Is it a bridge? If so, put an IP address on the bridge, not wlan0. By putting inet there early on, it's bringing the interface up very early. It's a side effect of hte network stack - if you assign an IP address, the VAP comes up immediately. thus i do the inet line after _all_ other things are done, and on a separate line. Anyway, leave it how it is for now. Just update to the latest -HEAD ath code and redo the testing. It will now log the whole TX queue contents, not just the completed frames. Hopefully it'll be more obvious. Thanks, adrian