From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 25 00:39:48 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14146106564A; Mon, 25 Jul 2011 00:39:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9BCBA8FC08; Mon, 25 Jul 2011 00:39:47 +0000 (UTC) Received: by yic13 with SMTP id 13so2370151yic.13 for ; Sun, 24 Jul 2011 17:39:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Tm+HXjw7fRemi6X4ThcVgONPNPKdJNzi0ncac8gkC5o=; b=UVRHaD20laeUefYYj422C13kAMDzs9Oacs2PzAxvVwd9AXfS+d7Vbc1Aim0x15J2lq G5I6UMsMZ6WDWJDjPOn/F17HRASlOdQdJERILk6zChhGt3vLjggrQz2TaTA6nBTmKKgb X9rVN+s7uz5TjSTrYeNA/PNIqoFlCG/4mOnWs= MIME-Version: 1.0 Received: by 10.150.72.23 with SMTP id u23mr1017004yba.443.1311554386644; Sun, 24 Jul 2011 17:39:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Sun, 24 Jul 2011 17:39:46 -0700 (PDT) In-Reply-To: <4E2A5407.7080808@gmail.com> References: <201107140702.p6E721Y4012318@freefall.freebsd.org> <4E246C95.40601@gmail.com> <4E2A5407.7080808@gmail.com> Date: Mon, 25 Jul 2011 08:39:46 +0800 X-Google-Sender-Auth: LZHzY0UeYRxWOntztUXjuugfHSQ Message-ID: From: Adrian Chadd To: Matt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: ae@freebsd.org, freebsd-wireless@freebsd.org, freebsd-net@freebsd.org Subject: Re: kern/155498: [ral] ral(4) needs to be resynced with OpenBSD's to gain RT2860/2870 support. X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Jul 2011 00:39:48 -0000 Keep up the great work :) Adrian On 23 July 2011 12:54, Matt wrote: > On 07/22/11 18:42, Adrian Chadd wrote: >> >> When do we just give in and commit this merged code for now? >> >> >> Adrian >> >> On 19 July 2011 01:25, Matt =A0wrote: >>> >>> On 07/14/11 00:02, ae@FreeBSD.org wrote: >>>> >>>> Synopsis: [ral] ral(4) needs to be resynced with OpenBSD's to gain >>>> RT2860/2870 support. >>>> >>>> Responsible-Changed-From-To: freebsd-net->freebsd-wireless >>>> Responsible-Changed-By: ae >>>> Responsible-Changed-When: Thu Jul 14 07:00:44 UTC 2011 >>>> Responsible-Changed-Why: >>>> Reassign to wireless team. >>>> >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D155498 >>>> _______________________________________________ >>>> 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" >>>> >>> This is in progress...either from OpenBSD or from Alexandr's rt2860 cod= e. >>> Or a merge of the two. >>> >>> In the mean time, anyone interested should please test. >>> It seems like it may not work on anything but current, but I don't have >>> enough information to be sure. >>> >>> Patches (rt2860 merged with ral): >>> >>> https://docs.google.com/leaf?id=3D0B6YlMzJxarGbMWFmZDUxMTgtOTU4ZC00MjRl= LThhMTctZTE1MDcwNDJiZDIx&hl=3Den_US >>> >>> If you have build errors, please provide output of uname -a, and copyin= g >>> exact error messages if any. >>> >>> Thanks, >>> Matt >>> _______________________________________________ >>> 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" >>> > That may be a good stopgap! > > My next step is to go line by line through OpenBSD ral & existing FreeBSD > ral and try to find a way to either create an abstraction layer for easy > porting or otherwise structure our driver to successfully "eat" OpenBSD > changes in the future. This will take significant time on my part, as I a= m a > noobophyte :). If anyone knows of useful tools for organizing very large = C > sources by function please let me know, it would help! > > I will do some major hacking at it tonight I suppose...it's about time :)= . > I'll post updates sometime soon, but OpenBSD's 80211 stack seems quite > different than ours...pci stuff is all different for sure. > > Matt > _______________________________________________ > 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 Mon Jul 25 11:07:20 2011 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15704106567A for ; Mon, 25 Jul 2011 11:07:20 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EED948FC15 for ; Mon, 25 Jul 2011 11:07:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p6PB7Jq4046554 for ; Mon, 25 Jul 2011 11:07:19 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p6PB7JsU046552 for freebsd-wireless@FreeBSD.org; Mon, 25 Jul 2011 11:07:19 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Jul 2011 11:07:19 GMT Message-Id: <201107251107.p6PB7JsU046552@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 Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Jul 2011 11:07:20 -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/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/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/149307 wireless [ath] Doesn't work Atheros 9285 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/148112 wireless [ath] Atheros 9285 cannot register with wifi AP (timeo o kern/148078 wireless [ath] wireless networking stops functioning 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 bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o kern/143868 wireless [ath] [patch] [request] allow Atheros watchdog timeout o conf/143079 wireless hostapd(8) startup missing multi wlan functionality o kern/140796 wireless [ath] [panic] Cannot attach (unable to attach hardware p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o 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 50 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 25 11:29:10 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C171D106564A for ; Mon, 25 Jul 2011 11:29:10 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7A46D8FC0A for ; Mon, 25 Jul 2011 11:29:10 +0000 (UTC) Received: by vxg33 with SMTP id 33so3829329vxg.13 for ; Mon, 25 Jul 2011 04:29:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BraM2TyauqVMEug9QhQlTicnVbUCsHQIhaleBfiTe60=; b=df8iB9/JQRd0PXA/XAYh6gQA+FVSSOGyA4Tuu2llp0vjGv7nXzwRr4GEHlS7C3wuBz 9QwRP6Qe8wL2xqcw5KN2on9Gevk8ywsDDK4G2od644O7tQcy5QQCyqkOmc9uPYmyhyKh SyIbxulGabFV4sXF0dNtqzNpADXAtXjqTZ5NU= MIME-Version: 1.0 Received: by 10.52.97.163 with SMTP id eb3mr4428781vdb.269.1311593349841; Mon, 25 Jul 2011 04:29:09 -0700 (PDT) Received: by 10.52.155.67 with HTTP; Mon, 25 Jul 2011 04:29:09 -0700 (PDT) In-Reply-To: <4E1B95D6.4050003@gmail.com> References: <4E13F39E.1000302@gmail.com> <4E14F2B8.4090200@gmail.com> <4E163F7B.8030804@gmail.com> <4E1B95D6.4050003@gmail.com> Date: Mon, 25 Jul 2011 12:29:09 +0100 Message-ID: From: "Sevan / Venture37" To: Matt Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org Subject: Re: RT2860/RT3090/RAL: Any brave testers? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Jul 2011 11:29:10 -0000 On 12 July 2011 01:31, Matt wrote: > I do have delete set in supfile. > > I also did this: > rm -rf /usr/src > rm -rf /usr/obj > csup ~/localsupfile (identical to example but with cvsup2.freebsd.org) > tar xvzf ralpatch.tar.gz > mv ralpatch/*.diff . > patch -p1 < ralpatch.diff > patch -p1 < ralmakepatch.diff > > and module makes fine...I have only tested thus far against current, so if > you are not on current or are running a different arch than amd64, please > let me know that information as well as detailed make output failure. > > I'm sorry there appears to be some issue here, hopefully with more info I > can resolve it? PEBKAC blew away src & retried & all was well, will look through the script files to see where it went wrong. Sevan From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 26 11:19:20 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C605106566C for ; Tue, 26 Jul 2011 11:19:20 +0000 (UTC) (envelope-from pptamas01@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9DDF78FC0A for ; Tue, 26 Jul 2011 11:19:19 +0000 (UTC) Received: by ewy1 with SMTP id 1so433405ewy.13 for ; Tue, 26 Jul 2011 04:19:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=hhzPFc3rxDewM4S2tPejdMBDnDjY9nKEXzYK//cRtzE=; b=oRMpUGSZySBfPKrcR0gqMZmlJCjp73EhtW5k+9k+unw5K2WvQW+/DuTodJdyFsbU9D 7PLqsmoPouhlkD4RY8o4F9Jt9n/qojhg0klwepR5x0i20PUTVQPdA9kuLE+17SZZyP61 U1msW7G4zK+dA4WH9+cW+c5JAogWaDq410mcM= MIME-Version: 1.0 Received: by 10.213.114.8 with SMTP id c8mr771172ebq.20.1311677662727; Tue, 26 Jul 2011 03:54:22 -0700 (PDT) Received: by 10.213.7.76 with HTTP; Tue, 26 Jul 2011 03:54:22 -0700 (PDT) Date: Tue, 26 Jul 2011 10:54:22 +0000 Message-ID: From: =?ISO-8859-1?B?cOFsIHDpdGVy?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: bwn0 bug X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Jul 2011 11:19:20 -0000 Hi I have a Compaq mini 311 netbook with freeBSD-8.2-STABLE. I use the bwn kernel modul and wpa_suppliciant to my wireless card. I configured everything, but during the boot process it sais that "bwn0: need multicast update callback" and "bwn0: RX decryption attempted (old 0 keyidx 0X2)". I googled it for a while, and i read, that is an unfixed kernel bug, wich couse 50%-100% packet loss. When i tryed to ping google, it sais "hostname lookup failure", so i tryed to ping my router, and it said "host is down", but it didn't. On my router, the arp table contains my wireless cards MAC adress. Here is the config files, and the output of the commands: siba_bwn0: mem 0x53000000-0x53003fff irq 16 at device 0.0 on pci3 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] bwn0: need multicast update callback bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: status of RF switch is changed to OFF bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: status of RF switch is changed to OFF bwn0: please turns on the RF switch bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: status of RF switch is changed to OFF bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: need multicast update callback siba_bwn0: mem 0x53000000-0x53003fff irq 16 at device 0.0 on pci3 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] bwn0: need multicast update callback bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: status of RF switch is changed to OFF bwn0: please turns on the RF switch bwn0: status of RF switch is changed to ON bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: need multicast update callback my routing table (netstat -rn | head): Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.1.1 UGS 2 19 wlan0 127.0.0.1 link#3 UH 0 4 lo0 192.168.1.0/24 link#4 U 0 0 wlan0 192.168.1.100 link#4 UHS 0 0 lo0 Internet6: /etc/rc.conf: network_enable="YES" gateway_enable="YES" network_interfaces="auto" ifconfig_nfe0="DHCP" wlans_bwi0="wlan0" ifconfig_wlan0="WAP DHCP" ipv6_enable="YES" inetd_enable="YES" hostname="Nikolay" hald_enable="YES" dbus_enable="YES" gdm_enable="YES" gnome_enable="YES" linux_enable="YES" hcsecd_enable="YES" sdpd_enable="YES" webcamd_enable="YES" and my /boot/loader.conf: #if_nfe_load="YES" if_bwi_load="YES" wlan_scan_up_load="YES" wlan_sta_load="YES" wlan_wep_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" nvidia_load="YES" snd_hda_load="YES" ng_ubt_load="YES" cuse4bsd_load="YES" my dmesg masseges about bwn0 (dmesg | grep bwn0 | uniq): siba_bwn0: mem 0x53000000-0x53003fff irq 16 at device 0.0 on pci3 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] bwn0: need multicast update callback bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: status of RF switch is changed to OFF bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: status of RF switch is changed to OFF bwn0: please turns on the RF switch bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: status of RF switch is changed to OFF bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: need multicast update callback siba_bwn0: mem 0x53000000-0x53003fff irq 16 at device 0.0 on pci3 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] bwn0: need multicast update callback bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: status of RF switch is changed to OFF bwn0: please turns on the RF switch bwn0: status of RF switch is changed to ON bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: need multicast update callback my routing table (netstat -rn | head): Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.1.1 UGS 2 19 wlan0 127.0.0.1 link#3 UH 0 4 lo0 192.168.1.0/24 link#4 U 0 0 wlan0 192.168.1.100 link#4 UHS 0 0 lo0 Internet6: From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 26 13:18:36 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 314711065670 for ; Tue, 26 Jul 2011 13:18:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id E4B798FC1E for ; Tue, 26 Jul 2011 13:18:35 +0000 (UTC) Received: by yxl31 with SMTP id 31so283448yxl.13 for ; Tue, 26 Jul 2011 06:18:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=QEm5lKjwzQbMMYLApa5N6pzMoNjIfzBdEwptHqWzaS0=; b=GE0efOcirDeSKZyMZF+jGUlFxhjf6olWx+N8U/lvgHXwfr4epCHSI113E+xiAqorDy 6hKkkJkOb4Vd6X6Bwe7DESVVa+R73CPIBE6At5bLSVhkcWjhFsxE1ax7WbBPv1/IPexU Fqa80QadKBxKfJmgpm6ZDLfM+gTx1ygXONMjk= MIME-Version: 1.0 Received: by 10.150.74.3 with SMTP id w3mr5560350yba.329.1311686313227; Tue, 26 Jul 2011 06:18:33 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Tue, 26 Jul 2011 06:18:33 -0700 (PDT) In-Reply-To: References: Date: Tue, 26 Jul 2011 21:18:33 +0800 X-Google-Sender-Auth: ybGhFQG49-_FFF_NajBPeUZxMMU Message-ID: From: Adrian Chadd To: =?ISO-8859-1?B?cOFsIHDpdGVy?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: bwn0 bug X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Jul 2011 13:18:36 -0000 Hi, Are you able to try -HEAD on this netbook? adrian 2011/7/26 p=E1l p=E9ter : > Hi > > I have a Compaq mini 311 netbook with freeBSD-8.2-STABLE. I use the bwn > kernel modul and wpa_suppliciant to my wireless card. I configured > everything, but during the boot process it sais that "bwn0: need multicas= t > update callback" and "bwn0: RX decryption attempted (old 0 keyidx 0X2)". = I > googled it for a while, and i read, that is an unfixed kernel bug, wich > couse 50%-100% packet loss. When i tryed to ping google, it sais "hostnam= e > lookup failure", so i tryed to ping my router, and it said "host is down"= , > but it didn't. On my router, the arp table contains my wireless cards MAC > adress. Here is the config files, and the output of the commands: siba_bw= n0: > mem 0x53000000-0x53003fff irq 16 at > device 0.0 on pci3 > bwn0 on siba_bwn0 > bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manu= f > 0x17f ver 0x2062 rev 2) > bwn0: DMA (64 bits) > bwn0: Using 1 MSI messages > bwn0: [FILTER] > bwn0: need multicast update callback > bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > bwn0: RX decryption attempted (old 0 keyidx 0x2) > bwn0: need multicast update callback > bwn0: RX decryption attempted (old 0 keyidx 0x2) > bwn0: > bwn0: need multicast update callback > bwn0: RX decryption attempted (old 0 keyidx 0x2) > bwn0: need multicast update callback > bwn0: RX decryption attempted (old 0 keyidx 0x2) > bwn0: need multicast update callback > bwn0: RX decryption attempted (old 0 keyidx 0x2) > bwn0: RX decryption attempted (old 0 keyidx 0x1) > bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > bwn0: RX decryption attempted (old 0 keyidx 0x1) > bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > bwn0: status of RF switch is changed to OFF > bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > bwn0: status of RF switch is changed to OFF > bwn0: please turns on the RF switch > bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > bwn0: status of RF switch is changed to OFF > bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > bwn0: need multicast update callback > siba_bwn0: mem 0x53000000-0x53003ff= f > irq 16 at device 0.0 on pci3 > bwn0 on siba_bwn0 > bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manu= f > 0x17f ver 0x2062 rev 2) > bwn0: DMA (64 bits) > bwn0: Using 1 MSI messages > bwn0: [FILTER] > bwn0: need multicast update callback > bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > bwn0: status of RF switch is changed to OFF > bwn0: please turns on the RF switch > bwn0: status of RF switch is changed to ON > bwn0: need multicast update callback > bwn0: RX decryption attempted (old 0 keyidx 0x1) > bwn0: need multicast update callback > bwn0: RX decryption attempted (old 0 keyidx 0x1) > bwn0: need multicast update callback > > my routing table (netstat -rn | head): > > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 192.168.1.1 UGS 2 19 wlan0 > 127.0.0.1 link#3 UH 0 4 lo0 > 192.168.1.0/24 link#4 U 0 0 wlan0 > 192.168.1.100 link#4 UHS 0 0 lo0 > > Internet6: > > > /etc/rc.conf: > > =A0network_enable=3D"YES" > =A0gateway_enable=3D"YES" > > =A0network_interfaces=3D"auto" > =A0ifconfig_nfe0=3D"DHCP" > =A0wlans_bwi0=3D"wlan0" > =A0ifconfig_wlan0=3D"WAP DHCP" > =A0ipv6_enable=3D"YES" > =A0inetd_enable=3D"YES" > > =A0hostname=3D"Nikolay" > =A0hald_enable=3D"YES" > =A0dbus_enable=3D"YES" > =A0gdm_enable=3D"YES" > =A0gnome_enable=3D"YES" > =A0linux_enable=3D"YES" > > =A0hcsecd_enable=3D"YES" > =A0sdpd_enable=3D"YES" > =A0webcamd_enable=3D"YES" > > and my /boot/loader.conf: > > =A0#if_nfe_load=3D"YES" > =A0if_bwi_load=3D"YES" > =A0wlan_scan_up_load=3D"YES" > =A0wlan_sta_load=3D"YES" > =A0wlan_wep_load=3D"YES" > =A0wlan_ccmp_load=3D"YES" > =A0wlan_tkip_load=3D"YES" > > =A0nvidia_load=3D"YES" > =A0snd_hda_load=3D"YES" > =A0ng_ubt_load=3D"YES" > =A0cuse4bsd_load=3D"YES" > > my dmesg masseges about bwn0 (dmesg | grep bwn0 | uniq): > > =A0siba_bwn0: mem 0x53000000-0x5300= 3fff > irq 16 at device 0.0 on pci3 > =A0bwn0 on siba_bwn0 > =A0bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (m= anuf > 0x17f ver 0x2062 rev 2) > =A0bwn0: DMA (64 bits) > =A0bwn0: Using 1 MSI messages > =A0bwn0: [FILTER] > =A0bwn0: need multicast update callback > =A0bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > =A0bwn0: RX decryption attempted (old 0 keyidx 0x2) > =A0bwn0: need multicast update callback > =A0bwn0: RX decryption attempted (old 0 keyidx 0x2) > =A0bwn0: > =A0bwn0: need multicast update callback > =A0bwn0: RX decryption attempted (old 0 keyidx 0x2) > =A0bwn0: need multicast update callback > =A0bwn0: RX decryption attempted (old 0 keyidx 0x2) > =A0bwn0: need multicast update callback > =A0bwn0: RX decryption attempted (old 0 keyidx 0x2) > =A0bwn0: RX decryption attempted (old 0 keyidx 0x1) > =A0bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > =A0bwn0: RX decryption attempted (old 0 keyidx 0x1) > =A0bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > =A0bwn0: status of RF switch is changed to OFF > =A0bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > =A0bwn0: status of RF switch is changed to OFF > =A0bwn0: please turns on the RF switch > =A0bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > =A0bwn0: status of RF switch is changed to OFF > =A0bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > =A0bwn0: need multicast update callback > =A0siba_bwn0: mem 0x53000000-0x5300= 3fff > irq 16 at device 0.0 on pci3 > =A0bwn0 on siba_bwn0 > =A0bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (m= anuf > 0x17f ver 0x2062 rev 2) > =A0bwn0: DMA (64 bits) > =A0bwn0: Using 1 MSI messages > =A0bwn0: [FILTER] > =A0bwn0: need multicast update callback > =A0bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) > =A0bwn0: status of RF switch is changed to OFF > =A0bwn0: please turns on the RF switch > =A0bwn0: status of RF switch is changed to ON > =A0bwn0: need multicast update callback > =A0bwn0: RX decryption attempted (old 0 keyidx 0x1) > =A0bwn0: need multicast update callback > =A0bwn0: RX decryption attempted (old 0 keyidx 0x1) > =A0bwn0: need multicast update callback > > my routing table (netstat -rn | head): > > =A0Routing tables > > =A0Internet: > =A0Destination Gateway Flags Refs Use Netif Expire > =A0default 192.168.1.1 UGS 2 19 wlan0 > =A0127.0.0.1 link#3 UH 0 4 lo0 > =A0192.168.1.0/24 link#4 U 0 0 wlan0 > =A0192.168.1.100 link#4 UHS 0 0 lo0 > > =A0Internet6: > _______________________________________________ > 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 Jul 26 20:33:02 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93070106566C for ; Tue, 26 Jul 2011 20:33:02 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 647858FC19 for ; Tue, 26 Jul 2011 20:33:02 +0000 (UTC) Received: by pzk5 with SMTP id 5so4025342pzk.17 for ; Tue, 26 Jul 2011 13:33:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=sWu9nJNL5OGJAmXA7lv7EapZ+SvO2SKwm/TS2qjNG0M=; b=x2OktHULO0eq7htcdW9LhjDe0Y9JD4SYHD3697F2L8EGadvVw/AHZIwTkhBps/Fn+X vIVuLnPZ0AOK3n9Og1bQJcZnsAXtLjlzCyUyuA+MaCM0fD5EuucDSPjsjnW3hg+nOBPA eF0UxLzEUWGX/85bCuAWXCUunj+XmqKEGWIJc= Received: by 10.68.64.36 with SMTP id l4mr11247221pbs.48.1311712381626; Tue, 26 Jul 2011 13:33:01 -0700 (PDT) Received: from sidhe.local ([75.101.87.90]) by mx.google.com with ESMTPS id d3sm893360pbh.85.2011.07.26.13.32.56 (version=SSLv3 cipher=OTHER); Tue, 26 Jul 2011 13:32:57 -0700 (PDT) Message-ID: <4E2F2467.5090809@gmail.com> Date: Tue, 26 Jul 2011 13:32:39 -0700 From: Matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110716 Thunderbird/5.0 MIME-Version: 1.0 To: Sevan / Venture37 References: <4E13F39E.1000302@gmail.com> <4E14F2B8.4090200@gmail.com> <4E163F7B.8030804@gmail.com> <4E1B95D6.4050003@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: Re: RT2860/RT3090/RAL: Any brave testers? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Jul 2011 20:33:02 -0000 On 07/25/11 04:29, Sevan / Venture37 wrote: > On 12 July 2011 01:31, Matt wrote: >> I do have delete set in supfile. >> >> I also did this: >> rm -rf /usr/src >> rm -rf /usr/obj >> csup ~/localsupfile (identical to example but with cvsup2.freebsd.org) >> tar xvzf ralpatch.tar.gz >> mv ralpatch/*.diff . >> patch -p1< ralpatch.diff >> patch -p1< ralmakepatch.diff >> >> and module makes fine...I have only tested thus far against current, so if >> you are not on current or are running a different arch than amd64, please >> let me know that information as well as detailed make output failure. >> >> I'm sorry there appears to be some issue here, hopefully with more info I >> can resolve it? > > PEBKAC > blew away src& retried& all was well, will look through the script > files to see where it went wrong. > > > Sevan > Glad it works! I had my share of PEBCAK with pastebin converting my patch to EBDIC or something :). Let me know how it works, what hardware you have, and what doesn't work. Thanks! Matt From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 27 10:46:41 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D59241065673 for ; Wed, 27 Jul 2011 10:46:41 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 91BC88FC24 for ; Wed, 27 Jul 2011 10:46:41 +0000 (UTC) Received: by gxk28 with SMTP id 28so1170833gxk.13 for ; Wed, 27 Jul 2011 03:46:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=IkVvUeX+SxvV+8KV2tDFcEIF5/t8QEcIkhg4E0g+lAU=; b=g0hSUHfB1g6INvfoYAAZ47kz054Pid5qD1LWMYwVFkhaUKd5EOYpgwH+0KkIPglswD nIfL8RtFrZ8LZd9EMq/zMIcBQ0e/vsWlMjjZpBGUk5qKRwY44Z6Xte7OufbOeAbunkpS eYFOrY2kIzcimQmr/WSsnnyLFknRhV60OP6yA= MIME-Version: 1.0 Received: by 10.150.253.2 with SMTP id a2mr6594804ybi.134.1311762225346; Wed, 27 Jul 2011 03:23:45 -0700 (PDT) Received: by 10.151.101.4 with HTTP; Wed, 27 Jul 2011 03:23:45 -0700 (PDT) Date: Wed, 27 Jul 2011 12:23:45 +0200 Message-ID: From: Monthadar Al Jaberi To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2011 10:46:41 -0000 Hi, How is ack frames being handled by the net80211? I guess the driver (or maybe hardware) takes care of resending, but what happens if it max number of retries is reached? How is net8011 notified? There is ieee80211_add_callback that I think should be used for that, but it is only used by managment frames of type IEEE80211_FC0_SUBTYPE_ASSOC_REQ, IEEE80211_FC0_SUBTYPE_REASSOC_REQ and IEEE80211_FC0_SUBTYPE_AUTH (in station mode) and one for HT code. What about the others? I guess the hardware only keeps stat counters for failures.... br, -- //Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 27 10:48:50 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F77A106564A for ; Wed, 27 Jul 2011 10:48:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id C2FA98FC0C for ; Wed, 27 Jul 2011 10:48:49 +0000 (UTC) Received: by gxk28 with SMTP id 28so1171983gxk.13 for ; Wed, 27 Jul 2011 03:48:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=QbA8AZMXNkv7O7TtDpYnsl/UZQannrEyPszAiH9Z38Q=; b=b7ydz5nUTQ9oyKgfqFv6xr6Wt29kF63tV3SJcSHHNyuExhuZgyt++lghfGfovL9+oU FiOOAeqYEB8P2ThcYzv7C0GdtaN3mTodO4JQVROB5HwMZHpg1woVGgo7gVlebCwzi2ST ANl9nQwAf9wtq5dkCUiErDKbZwb18x+kjFJ+Q= MIME-Version: 1.0 Received: by 10.150.225.1 with SMTP id x1mr21552ybg.272.1311763729058; Wed, 27 Jul 2011 03:48:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Wed, 27 Jul 2011 03:48:49 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 18:48:49 +0800 X-Google-Sender-Auth: Y9tD-4AvMOwYetS8OV9pU7npico Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2011 10:48:50 -0000 Hi, Yup, you're right. net80211 doesn't get notification of it by default. What do you need it for? Adrian On 27 July 2011 18:23, Monthadar Al Jaberi wrote: > Hi, > > How is ack frames being handled by the net80211? I guess the driver > (or maybe hardware) takes care of resending, but what happens if it > max number of retries is reached? How is net8011 notified? > > There is ieee80211_add_callback that I think should be used for that, > but it is only used by managment frames of type > IEEE80211_FC0_SUBTYPE_ASSOC_REQ, IEEE80211_FC0_SUBTYPE_REASSOC_REQ and > IEEE80211_FC0_SUBTYPE_AUTH (in station mode) and one for HT code. > > What about the others? I guess the hardware only keeps stat counters > for failures.... > > br, > > -- > //Monthadar Al Jaberi > _______________________________________________ > 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 Jul 27 10:59:09 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29D30106564A for ; Wed, 27 Jul 2011 10:59:09 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id E11818FC0C for ; Wed, 27 Jul 2011 10:59:08 +0000 (UTC) Received: by gxk28 with SMTP id 28so1177640gxk.13 for ; Wed, 27 Jul 2011 03:59:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Bsv3Rks1GTMEvDJcKQJSHsQ5NNyNk7YDbtV1gTOC7vQ=; b=wT8B4fQI1RbEP6p1+Qj+47xvWR2gwmxEF2f5ttscSuB9fH7J99W5Vl9D5DsQdpcakT 2Akb3bydHB5YAgF5EYRKkRYj0MnGi2/COd14iCV+TFfWn5DVtZFo2+aSeZU5Ao26PZ8r wiCZ7FRohe23z1m8eCfk4fxzzTn/DpW6Fp8VU= MIME-Version: 1.0 Received: by 10.150.166.19 with SMTP id o19mr1092000ybe.191.1311764347565; Wed, 27 Jul 2011 03:59:07 -0700 (PDT) Received: by 10.151.101.4 with HTTP; Wed, 27 Jul 2011 03:59:07 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 12:59:07 +0200 Message-ID: From: Monthadar Al Jaberi To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2011 10:59:09 -0000 Ok. For mesh forwarding information, how do I know about link failure (not able to forward an MSDU/MMPDU). Cause then we need to generate a PERR frame. br, On Wed, Jul 27, 2011 at 12:48 PM, Adrian Chadd wrote: > Hi, > > Yup, you're right. net80211 doesn't get notification of it by default. > > What do you need it for? > > > Adrian > > On 27 July 2011 18:23, Monthadar Al Jaberi wrote: >> Hi, >> >> How is ack frames being handled by the net80211? I guess the driver >> (or maybe hardware) takes care of resending, but what happens if it >> max number of retries is reached? How is net8011 notified? >> >> There is ieee80211_add_callback that I think should be used for that, >> but it is only used by managment frames of type >> IEEE80211_FC0_SUBTYPE_ASSOC_REQ, IEEE80211_FC0_SUBTYPE_REASSOC_REQ and >> IEEE80211_FC0_SUBTYPE_AUTH (in station mode) and one for HT code. >> >> What about the others? I guess the hardware only keeps stat counters >> for failures.... >> >> br, >> >> -- >> //Monthadar Al Jaberi >> _______________________________________________ >> 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 -- //Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 27 11:06:52 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C290106564A for ; Wed, 27 Jul 2011 11:06:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1A52E8FC0C for ; Wed, 27 Jul 2011 11:06:51 +0000 (UTC) Received: by gxk28 with SMTP id 28so1182600gxk.13 for ; Wed, 27 Jul 2011 04:06:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=LFRDIBgnOC7SaK4s5LMb+bP36oKbKzlEzFeui0q4GXM=; b=DULe/uFedXcflaOkc74oJIy35bUez7h4SIZJqUQPUVcFRZ2HTsbFnesdGSQOutyIFB ZM88JO4C9Fn3++vrt3sbbTe9z7+mA7nWiNJ6GTPn1BS3QIXNKAVHDzNBtcNUED4NZKqE BSNCghy5KJ0mK6qwZTV4YxSkAeRfa0JU0EMD0= MIME-Version: 1.0 Received: by 10.151.86.11 with SMTP id o11mr2722249ybl.386.1311764811190; Wed, 27 Jul 2011 04:06:51 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Wed, 27 Jul 2011 04:06:51 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 19:06:51 +0800 X-Google-Sender-Auth: LXBEyN94BagBb_2toTVynjBvv7s Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2011 11:06:52 -0000 On 27 July 2011 18:59, Monthadar Al Jaberi wrote: > Ok. For mesh forwarding information, how do I know about link failure > (not able to forward an MSDU/MMPDU). Cause then we need to generate a > PERR frame. Why not create a callback for all TXed frames when you're in mesh mode? Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 27 11:20:41 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A69891065678; Wed, 27 Jul 2011 11:20:41 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 54ACA8FC1A; Wed, 27 Jul 2011 11:20:40 +0000 (UTC) Received: by gyf3 with SMTP id 3so1193145gyf.13 for ; Wed, 27 Jul 2011 04:20:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=enqC/U3KfyhqdCNYdrzdSEB4kFD6RI6VuacQP0jHnMw=; b=rCCyouN7Qpts+5NMdmAg6Rsc6OJPrpdf9HKWkXCqT8n1U5cD9smZ0jeEvMGFwTjEsD 5TS9kl3kUCdEGbcXTISc8Hjq/g9iCt4VexRagDOVIIlqVaUIk+9KdlOR4dIgoo008UGp 7O2nRQh0A/Aqf5q2E4IOqOFDVi1p3AlfEzIuA= MIME-Version: 1.0 Received: by 10.151.29.18 with SMTP id g18mr6187381ybj.362.1311765639713; Wed, 27 Jul 2011 04:20:39 -0700 (PDT) Received: by 10.151.101.4 with HTTP; Wed, 27 Jul 2011 04:20:39 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 13:20:39 +0200 Message-ID: From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2011 11:20:41 -0000 Sounds like a plan! I guess I need to put some code with #ifdefs in: ieee80211_start ieee80211_mgmt_output ? On Wed, Jul 27, 2011 at 1:06 PM, Adrian Chadd wrote: > On 27 July 2011 18:59, Monthadar Al Jaberi wrote: >> Ok. For mesh forwarding information, how do I know about link failure >> (not able to forward an MSDU/MMPDU). Cause then we need to generate a >> PERR frame. > > Why not create a callback for all TXed frames when you're in mesh mode? > > > Adrian > -- //Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 27 11:32:38 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0803B1065670 for ; Wed, 27 Jul 2011 11:32:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id B872C8FC1B for ; Wed, 27 Jul 2011 11:32:37 +0000 (UTC) Received: by gyf3 with SMTP id 3so1201058gyf.13 for ; Wed, 27 Jul 2011 04:32:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=QQqDTLKuElcyqPpIAIRcaYt1EbYO716y983DZoTUmaA=; b=Tmn8LZXxuk0Ef5SdJDUttCYD8mX5qYXAf+MGt6stt+lbWU49sbmezJ6cETazoZ2+Qs bptD/JRhoo8GYj6Up8uBkVdDFj7v5Yv01kmdFqSC1/hrQTllVxJbM6WkThhGWD6g/Ewh yv1y2P77n4MGMSpZC8zHSCfnsW0UZvlNWte/E= MIME-Version: 1.0 Received: by 10.150.74.3 with SMTP id w3mr6483826yba.329.1311766356893; Wed, 27 Jul 2011 04:32:36 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Wed, 27 Jul 2011 04:32:36 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 19:32:36 +0800 X-Google-Sender-Auth: UUmAreSVex8hTLSckBV_ZweZDLc Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2011 11:32:38 -0000 isn't there a tx method that the mesh code overrides? Adrian On 27 July 2011 19:20, Monthadar Al Jaberi wrote: > Sounds like a plan! > > I guess I need to put some code with #ifdefs in: > > ieee80211_start > ieee80211_mgmt_output > > ? > > > > > On Wed, Jul 27, 2011 at 1:06 PM, Adrian Chadd wrote: >> On 27 July 2011 18:59, Monthadar Al Jaberi wrote: >>> Ok. For mesh forwarding information, how do I know about link failure >>> (not able to forward an MSDU/MMPDU). Cause then we need to generate a >>> PERR frame. >> >> Why not create a callback for all TXed frames when you're in mesh mode? >> >> >> Adrian >> > > > > -- > //Monthadar Al Jaberi > From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 27 12:14:32 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBCBC1065670; Wed, 27 Jul 2011 12:14:32 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 87F288FC17; Wed, 27 Jul 2011 12:14:32 +0000 (UTC) Received: by yic13 with SMTP id 13so1238528yic.13 for ; Wed, 27 Jul 2011 05:14:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=86yVqFI7FNNcSXnl9WlgW8tVwaCrS+yC+Pg4wLBpYII=; b=WG1JkkTZriuUb3WDSN05HsoplvdVetIzW2P5MvSjME3dSJvECVGeUwEeLTMvqoXD2p i2xecwmLjj982wxoKZk/lW98FB65Cj6/2xoH75Vvhc0Gg1o/MeNCiy5/2HqYRM2vOmIi O32bZgnGHMiJ+rjFcwSD6G1VxaPpugo7IoFOA= MIME-Version: 1.0 Received: by 10.150.159.4 with SMTP id h4mr6351460ybe.419.1311768871760; Wed, 27 Jul 2011 05:14:31 -0700 (PDT) Received: by 10.151.101.4 with HTTP; Wed, 27 Jul 2011 05:14:31 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 14:14:31 +0200 Message-ID: From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2011 12:14:32 -0000 not from what I can see, it overides vap->iv_input and vap->iv_recv_mgmt but not vap->iv_output... in ieee80211_start there is #ifdef IEEE80211_SUPPORT_MESH :S Okej for ieee80211_mgmt_output I see that mesh_send_action call it, so I can put one callback there... On Wed, Jul 27, 2011 at 1:32 PM, Adrian Chadd wrote: > isn't there a tx method that the mesh code overrides? > > > Adrian > > On 27 July 2011 19:20, Monthadar Al Jaberi wrote: >> Sounds like a plan! >> >> I guess I need to put some code with #ifdefs in: >> >> ieee80211_start >> ieee80211_mgmt_output >> >> ? >> >> >> >> >> On Wed, Jul 27, 2011 at 1:06 PM, Adrian Chadd wrote: >>> On 27 July 2011 18:59, Monthadar Al Jaberi wrote: >>>> Ok. For mesh forwarding information, how do I know about link failure >>>> (not able to forward an MSDU/MMPDU). Cause then we need to generate a >>>> PERR frame. >>> >>> Why not create a callback for all TXed frames when you're in mesh mode? >>> >>> >>> Adrian >>> >> >> >> >> -- >> //Monthadar Al Jaberi >> > -- //Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 27 12:19:24 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2A34106566B for ; Wed, 27 Jul 2011 12:19:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6C8218FC15 for ; Wed, 27 Jul 2011 12:19:24 +0000 (UTC) Received: by gyf3 with SMTP id 3so1238627gyf.13 for ; Wed, 27 Jul 2011 05:19:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=TfEXlmX0Pm7cLOLUCrFSZewpvMDF+Pkcvo0QubOTCvA=; b=vNPYRrZSvTkA+L0lyRwhDEKxwx6hflv5B5FPR0evxWCKjX+5fgMc4dJ8VhNhPp8MhU 3oA+njcKcxHKRZN19jAfPn/4doG0VystjlauiInXCQgQ7eKBJkhYDWe4um4qgpgoX6VY 47BZ9xUPFHUdNYIdQ+CtKusAYmkdxSRBPKWos= MIME-Version: 1.0 Received: by 10.150.74.3 with SMTP id w3mr6521904yba.329.1311769163658; Wed, 27 Jul 2011 05:19:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Wed, 27 Jul 2011 05:19:23 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 20:19:23 +0800 X-Google-Sender-Auth: gzqvmQ-KaFBPtOZVY26NU69n0CE Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Jul 2011 12:19:24 -0000 On 27 July 2011 20:14, Monthadar Al Jaberi wrote: > not from what I can see, it overides vap->iv_input and vap->iv_recv_mgmt > > but not vap->iv_output... > > in ieee80211_start there is #ifdef IEEE80211_SUPPORT_MESH > > :S > > Okej for ieee80211_mgmt_output I see that mesh_send_action call it, so > I can put one callback there... I'll leave it up to you :) I'm knee-deep in ANI and radar detection code at the moment. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jul 28 12:10:12 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 582571065673; Thu, 28 Jul 2011 12:10:12 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0002A8FC18; Thu, 28 Jul 2011 12:10:11 +0000 (UTC) Received: by gyf3 with SMTP id 3so2211019gyf.13 for ; Thu, 28 Jul 2011 05:10:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Y3Mtm2rDY5xY2BZ06e/3DBqAdqqPkn8kH7GamHx/kGE=; b=CCZe7fF6Hj54MnI32A3rfPciNiek/1lCKWhOhpt1HyIw93SX8D4dsnUNGcr4knPcDa 98EQL4lCRwv3H2EUkNg5gas2FnxSbk2I+o/hVT4ZITqc38joPAEgxek0v56IO0Cu7CbG 0KXrUV4Po6JyOJCpNNSRevAZjA2RIeFUEoeLY= MIME-Version: 1.0 Received: by 10.150.170.2 with SMTP id s2mr68655ybe.168.1311855011176; Thu, 28 Jul 2011 05:10:11 -0700 (PDT) Received: by 10.151.46.18 with HTTP; Thu, 28 Jul 2011 05:10:11 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Jul 2011 14:10:11 +0200 Message-ID: From: Monthadar Al Jaberi To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ack, Net80211 & ath X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Jul 2011 12:10:12 -0000 Here is something, one should also implement the amrr_tx_complete() or ammr_tx_update() approch and see how everything react. anyone can test this? =) diff --git a/sys/net80211/ieee80211_mesh.c b/sys/net80211/ieee80211_mesh.c index 571a733..08e1764 100644 --- a/sys/net80211/ieee80211_mesh.c +++ b/sys/net80211/ieee80211_mesh.c @@ -709,6 +709,18 @@ mesh_rt_cleanup_cb(void *arg) mesh_rt_cleanup_cb, vap); } +static void +ieee80211_mesh_tx_cb(struct ieee80211_node *ni, void *arg, int status) +{ + if(status) + mesh_linkchange(ni, IEEE80211_NODE_MESH_HOLDING); +} +void +ieee80211_mesh_add_callback(struct mbuf *m) +{ + ieee80211_add_callback(m, ieee80211_mesh_tx_cb, NULL); +} + /* * Helper function to note the Mesh Peer Link FSM change. diff --git a/sys/net80211/ieee80211_mesh.h b/sys/net80211/ieee80211_mesh.h index ad1b02a..4f012e5 100644 --- a/sys/net80211/ieee80211_mesh.h +++ b/sys/net80211/ieee80211_mesh.h @@ -473,6 +473,7 @@ void ieee80211_mesh_init_neighbor(struct ieee80211_node *, const struct ieee80211_scanparams *); void ieee80211_mesh_update_beacon(struct ieee80211vap *, struct ieee80211_beacon_offsets *); +void ieee80211_mesh_add_callback(struct mbuf *); /* * Return non-zero if proxy operation is enabled. diff --git a/sys/net80211/ieee80211_output.c b/sys/net80211/ieee80211_output.c index 6020144..6a34731 100644 --- a/sys/net80211/ieee80211_output.c +++ b/sys/net80211/ieee80211_output.c @@ -271,6 +271,7 @@ ieee80211_start(struct ifnet *ifp) ifp->if_oerrors++; continue; } + ieee80211_mesh_add_callback(m); /* XXX: right place? */ } #endif if ((ni->ni_flags & IEEE80211_NODE_PWR_MGT) && On Wed, Jul 27, 2011 at 2:19 PM, Adrian Chadd wrote: > On 27 July 2011 20:14, Monthadar Al Jaberi wrote: >> not from what I can see, it overides vap->iv_input and vap->iv_recv_mgmt >> >> but not vap->iv_output... >> >> in ieee80211_start there is #ifdef IEEE80211_SUPPORT_MESH >> >> :S >> >> Okej for ieee80211_mgmt_output I see that mesh_send_action call it, so >> I can put one callback there... > > I'll leave it up to you :) I'm knee-deep in ANI and radar detection > code at the moment. > > > Adrian > -- //Monthadar Al Jaberi