From owner-freebsd-wireless@FreeBSD.ORG Sun Nov 25 06:11:03 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BCFC36EF; Sun, 25 Nov 2012 06:11:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 24FDE8FC0C; Sun, 25 Nov 2012 06:11:02 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id c13so7129749eek.13 for ; Sat, 24 Nov 2012 22:10:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=THnyaQBB9QAIAu12vpAZVaS2prc6ltp542l2ZT6vcR0=; b=wGKo2KSh8ruPoWB8yuAIkmtkzCvVltOyprKajx7lnvGnFNSkeDSFsRoDHQ8iohRhYI Dd8naHHSUNNSgiGx2MAOLQpjnQU3ZP9i6N/qu8Z4l5RYM5/6qbaL9JEHPyQ3AWztWUa3 pQjCuD+f/zB6KZ3oWFRcDyRb1KVYtcNXZGsx7NPR91c5/Q9u/naMNMVE7b2trDjo9LDU qCjt2kidIX/nnDzOZW3bvyeF9ctyL0vTADljFpmv/hQKTgcnA1yDcZ1zw4HZlyAhwXka cB29s+05Ee2eHF8TOM/P8+nF+9LNN+mv3wCjZAF0zZATeZG4yFqvUkmfLl+Uf+/sXaHA n3Rg== MIME-Version: 1.0 Received: by 10.14.209.6 with SMTP id r6mr31334616eeo.34.1353823856516; Sat, 24 Nov 2012 22:10:56 -0800 (PST) Received: by 10.223.71.199 with HTTP; Sat, 24 Nov 2012 22:10:56 -0800 (PST) In-Reply-To: References: <50B16846.5000805@freebsd.org> Date: Sat, 24 Nov 2012 22:10:56 -0800 Message-ID: Subject: Re: wifi + wpa_supplicant in 9.1-RC3 From: Kevin Oberman To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Wireless 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, 25 Nov 2012 06:11:03 -0000 Adrian, I really don't have any data and I do't like to submit a PR that basically says "It don't work good." I only have had an 'N' AP for about three weeks and only noticed the problem a few days ago when I copied some multi-megabyte files between local systems and they were taking way too long. If you or Bernhard can point me at what information I need to gather, I'll open one. (Nogte that I moved this to wireless, since it seems to belong either there or stable, not current. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com On Sat, Nov 24, 2012 at 9:06 PM, Adrian Chadd wrote: > On 24 November 2012 20:58, Kevin Oberman wrote: > >> iwn support N, but my experience has not been good. With a 'G' >> connection to my AP, I get about 20 Mbps, but when I turn on 'N', it >> drops to about 8 Mbps. I would not assume that 'N' is going to work >> better with the current software. > > Have you filed a bug about this? Bernhard has done a pretty amazing > job at getting iwn(4) 802.11n support working quite well. > > > > Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Nov 25 06:15:22 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0765171B for ; Sun, 25 Nov 2012 06:15:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 835CE8FC12 for ; Sun, 25 Nov 2012 06:15:21 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hm6so2076386wib.13 for ; Sat, 24 Nov 2012 22:15:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=+cOgdnLzoEr5Q5VpBhbJSsV3WBLF/uqnt0VbGvaPKVA=; b=DtsG0Y8EA7ig755yRZIqB8ki8FfEHt9sbF466Y9tjEymEwsVjPUoT6FGj9eQRa+fBw R8WOHg5CeG8EWvE5+7hUqapAEGu4yLqMZVwoFZ4K/YWz+tPuTIQoajlZMpnpd2mR1EaV En2gmZ1dhcyADc7LQpfzgHj+MmKqIvBfiWulWmDZD1sMW+wpRWCjleuYybOFFKDUrcXc rzGur9vRmmxSrcaZ4c3BGdXTMt8v0hCsscW+SAHotQGZnn6E6t8ItDAI4JT92swE4Vf+ l3RqdpymvDV+lKuOhe1qWtjMKjZ9DqFy6OVJEylICGakf63JyItGxbW8qLPb5XshZbkD stnA== MIME-Version: 1.0 Received: by 10.216.74.85 with SMTP id w63mr3187899wed.212.1353824120067; Sat, 24 Nov 2012 22:15:20 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sat, 24 Nov 2012 22:15:19 -0800 (PST) In-Reply-To: References: <50B16846.5000805@freebsd.org> Date: Sat, 24 Nov 2012 22:15:19 -0800 X-Google-Sender-Auth: IVGBzc9AGIM9G9UQcaxp5InwA78 Message-ID: Subject: Re: wifi + wpa_supplicant in 9.1-RC3 From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Wireless 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, 25 Nov 2012 06:15:22 -0000 On 24 November 2012 22:10, Kevin Oberman wrote: > Adrian, > > I really don't have any data and I do't like to submit a PR that > basically says "It don't work good." I only have had an 'N' AP for > about three weeks and only noticed the problem a few days ago when I > copied some multi-megabyte files between local systems and they were > taking way too long. > > If you or Bernhard can point me at what information I need to gather, > I'll open one. (Nogte that I moved this to wireless, since it seems to > belong either there or stable, not current. Right. Well, please make a bit of a fuss about it and when Bernhard has some time, we'll see if you two can chase it down. I don't think there's any statistics kept in the net80211 rate control modules (which iwn(4) uses); not to the depth that the ath(4) sample rate control module keeps. That would be niceto add. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Nov 25 19:27:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 10B36A17; Sun, 25 Nov 2012 19:27:09 +0000 (UTC) (envelope-from onyx@z-up.ru) Received: from mx.z-up.ru (mx.z-up.ru [92.50.244.44]) by mx1.freebsd.org (Postfix) with ESMTP id 7BFA78FC15; Sun, 25 Nov 2012 19:27:08 +0000 (UTC) Received: from onyx-y550p.loc (unknown [10.178.235.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.z-up.ru (Postfix) with ESMTPSA id BB45D1149E; Sun, 25 Nov 2012 23:20:04 +0400 (GMT-4) From: Dmitry Kolosov To: Adrian Chadd Subject: Re: Replacing wireless nic on my router Date: Sun, 25 Nov 2012 23:20:07 +0400 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; i386; ; ) References: <201211042144.08807.onyx@z-up.ru> <20121118102530.d334565b8061abda5e7871b3@z-up.ru> In-Reply-To: X-KMail-Markup: true MIME-Version: 1.0 Message-Id: <201211252320.07798.onyx@z-up.ru> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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: 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: Sun, 25 Nov 2012 19:27:09 -0000 > Thanks. Yes, please try a -9 snapshot and see if DHCP works from that > laptop. Done. Everything goes just fine. Tried 9-R livecd-mode. It seems like after replacing a wireless nic on my AP only 8-based laptop refuses to work. It even associating fine, but did not received any packet from AP after association. Same time, AP received DHCP packets from this 8- based laptop, and answered to it. But laptop does not received anything. Anyway, same laptop works fine (wireless) with 9-R, linux debian, win XP at livecd or installed. All other laptops of my own running 9-S and working just fine. Other hardware like cell and tablet also ok with AP nic replacement. Adrian, thanks a lot for work. Waiting for complete 11n in -Stable. From owner-freebsd-wireless@FreeBSD.ORG Sun Nov 25 19:55:53 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A2553EB for ; Sun, 25 Nov 2012 19:55:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 868658FC08 for ; Sun, 25 Nov 2012 19:55:52 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so4221669wey.13 for ; Sun, 25 Nov 2012 11:55:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=jX59V82m3IIfb7jQfFrPpgKSAxro4F9p8Lrp3t7xR38=; b=BbcQmfuF/WUhBsR2B7AaxkLoJgvFYgFwZxhcaSSHLijv28X2+c6NlYTXGJWCaHD2wB DhjvoiXRX0AvbXErUN58nyG3seXrCQpNMtBU3Vxq5h4D7jDnygNeW1+LyhfC4oV0h55Y eMHnxx6xuAl+nxxzhak7mI7C/KDPLrLOd/RZrm8BI+J7nA54Nthico0H5zU9tkgMJLEx 3YEyRwRuPjS0T6JSEdYb+HWU0gZpzq/XsrCYbOvD+SGifVb59NDx/YU3QePw9wUCwoJZ C78CorU3DD0eDvEHQAcjFWxJuqJ/m0414L8HBwl/m2BNGSniD7gNj16fVUxiTDmzX/Qs r6bw== MIME-Version: 1.0 Received: by 10.180.92.166 with SMTP id cn6mr14147361wib.19.1353873351487; Sun, 25 Nov 2012 11:55:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sun, 25 Nov 2012 11:55:50 -0800 (PST) In-Reply-To: <201211252320.07798.onyx@z-up.ru> References: <201211042144.08807.onyx@z-up.ru> <20121118102530.d334565b8061abda5e7871b3@z-up.ru> <201211252320.07798.onyx@z-up.ru> Date: Sun, 25 Nov 2012 11:55:50 -0800 X-Google-Sender-Auth: Kr12-2K5qXQiayKo1nAXQR6dr9M Message-ID: Subject: Re: Replacing wireless nic on my router 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: Sun, 25 Nov 2012 19:55:53 -0000 On 25 November 2012 11:20, Dmitry Kolosov wrote: > It seems like after replacing a wireless nic on my AP only 8-based laptop > refuses to work. It even associating fine, but did not received any packet > from AP after association. Same time, AP received DHCP packets from this > 8-based laptop, and answered to it. But laptop does not received anything. Yup. > Anyway, same laptop works fine (wireless) with 9-R, linux debian, win XP at > livecd or installed. Right. It was very likely the bug I thought it was - the multicast keycache thing. > All other laptops of my own running 9-S and working just fine. Other > hardware like cell and tablet also ok with AP nic replacement. > > Adrian, thanks a lot for work. > > Waiting for complete 11n in -Stable. It's highly unlikely that 11n is going to appear in 9-stable, mostly because of the sheer amount of ABI breaking stuff that has gone on. From owner-freebsd-wireless@FreeBSD.ORG Mon Nov 26 00:10:20 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8D622D7D for ; Mon, 26 Nov 2012 00:10:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 133F28FC12 for ; Mon, 26 Nov 2012 00:10:18 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id 12so5714624wgr.31 for ; Sun, 25 Nov 2012 16:10:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=QKthUdm+wJUZKkmRVPdCP8I+GGkQ0QPgQ5jruvitYbk=; b=JjW+aYN9SBaj53PaHqJQK2Lz158iUN/9C0/tJyJCMNrjtLqYUy6/bnB8wskoPVk83q Xw4oDzPll2aTeWICN5Csy+F9CFtLarvH4zSPjJx8vwKGvpj1PpxdZMF4BBoi+Su9UMj1 IlHSzgb0HsICSBiE2KGxRRXkccLvgsB/DisUjVuig2CSsq+kdFtD77G6FSZ1HR052SNF kfnksH9tjhVV79pQya5qWICqrUpObC0wRMOacw42Bq1yDmZ6zkvaHX6NOq3VdZ5Ul8Tv 3z5VOOmTbJNGh52kcTe2hvWcnAK4gyYgzYrG3fDMsCJPHin0yoRgEXm3VfclgjOtQyeW eUQA== MIME-Version: 1.0 Received: by 10.180.97.137 with SMTP id ea9mr10199068wib.13.1353888617953; Sun, 25 Nov 2012 16:10:17 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sun, 25 Nov 2012 16:10:17 -0800 (PST) In-Reply-To: References: <201211042144.08807.onyx@z-up.ru> <20121118102530.d334565b8061abda5e7871b3@z-up.ru> <201211252320.07798.onyx@z-up.ru> Date: Sun, 25 Nov 2012 16:10:17 -0800 X-Google-Sender-Auth: reYNtqLXm5TA2A9qwshsOoX0ujI Message-ID: Subject: Re: Replacing wireless nic on my router From: Adrian Chadd To: onyx@z-up.ru Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 00:10:20 -0000 Oh, can you -please- smack me around with the PR you filed (you filed a PR, right?) so I can backport this change to -8? Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Nov 26 11:06:54 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3FBFE5AF for ; Mon, 26 Nov 2012 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 1C7268FC0C for ; Mon, 26 Nov 2012 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qAQB6rnp019589 for ; Mon, 26 Nov 2012 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAQB6rwD019587 for freebsd-wireless@FreeBSD.org; Mon, 26 Nov 2012 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 Nov 2012 11:06:53 GMT Message-Id: <201211261106.qAQB6rwD019587@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, 26 Nov 2012 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/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173886 wireless [ath] [net80211] TDMA TX on 802.11n varies wildly o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless 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/171394 wireless [ath] ath0: ath_tx_aggr_comp_aggr: num frames seen=1; o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o 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 139 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Nov 27 02:31:24 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6485F801 for ; Tue, 27 Nov 2012 02:31:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id DE7B18FC12 for ; Tue, 27 Nov 2012 02:31:23 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hm6so3335884wib.13 for ; Mon, 26 Nov 2012 18:31:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=egoCQxlQVAOr5cliI8xihoVwy+ck/ga6CU6WaOEvCWc=; b=zygoZsVygWf+o4xU2aBGiyM9xn1IKD80U+tTnflWAVzKV38MlQxyB7KEtXeZQuBGHE 6QZ43tCC0zapj/vJxiTNz5yTIVKjzbNi1gamkkrdP0x0IzAqKtmhQ2g6Z/odcB89C83F 93JkXzyEsMsZOURvBY/dK/vA84dZoOJ/4/cFrSRCSF5tOSxedOv3IeC91Zp9gychDSlg wXUm0BILC8FFy4bpXeqEstxIYemkI65+Nlu7fPXRxK/L0UPON5U89qDZOSybHudAj3oP xL5k5NNeqJK0YUjTS7T/Wv3OuOSb+XvLs04WQIbaQqA+RpOOSp08Ao+wQlqDVj0+XArx 9Hsw== MIME-Version: 1.0 Received: by 10.216.200.160 with SMTP id z32mr5021624wen.53.1353983482946; Mon, 26 Nov 2012 18:31:22 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Mon, 26 Nov 2012 18:31:22 -0800 (PST) In-Reply-To: References: Date: Mon, 26 Nov 2012 18:31:22 -0800 X-Google-Sender-Auth: csCBq6sXeqC_XywRPXOWL55UPm0 Message-ID: Subject: Re: (Re) Verifying TDMA behaviour on -HEAD From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 02:31:24 -0000 .... and now TDMA works right with the 11n chips. They're only doing 11a rates for now, but the timer programming works. There's a bunch more work to do with the 11n chips and timer programming, mostly to figure out why the clock sync drift is slightly worse/different than the 11a cards. But I don't think it's anything major. Please, go forth and test it out. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Nov 28 05:06:49 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7575E292; Wed, 28 Nov 2012 05:06:49 +0000 (UTC) (envelope-from adrian@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 3EC078FC12; Wed, 28 Nov 2012 05:06:49 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qAS56ndK012325; Wed, 28 Nov 2012 05:06:49 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAS56nd8012321; Wed, 28 Nov 2012 05:06:49 GMT (envelope-from adrian) Date: Wed, 28 Nov 2012 05:06:49 GMT Message-Id: <201211280506.qAS56nd8012321@freefall.freebsd.org> To: adrian@FreeBSD.org, adrian@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Subject: Re: kern/173886: [ath] [net80211] TDMA TX on 802.11n varies wildly X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2012 05:06:49 -0000 Synopsis: [ath] [net80211] TDMA TX on 802.11n varies wildly State-Changed-From-To: open->closed State-Changed-By: adrian State-Changed-When: Wed Nov 28 05:06:03 UTC 2012 State-Changed-Why: This was fixed in r243590, which correctly wrapped and programmed the nexttbtt calculation. http://www.freebsd.org/cgi/query-pr.cgi?pr=173886 From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 19:40:02 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E0376E3 for ; Thu, 29 Nov 2012 19:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id EE5188FC08 for ; Thu, 29 Nov 2012 19:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qATJe1Fs033575 for ; Thu, 29 Nov 2012 19:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qATJe1Jf033574; Thu, 29 Nov 2012 19:40:01 GMT (envelope-from gnats) Date: Thu, 29 Nov 2012 19:40:01 GMT Message-Id: <201211291940.qATJe1Jf033574@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: Martin Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Martin 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, 29 Nov 2012 19:40:02 -0000 The following reply was made to PR kern/149516; it has been noted by GNATS. From: Martin To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated Date: Thu, 29 Nov 2012 20:35:05 +0100 Confirmed on 9.0-RELEASE-p3. Bug still exists. -- Martin From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 20:23:46 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4F789194 for ; Thu, 29 Nov 2012 20:23:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id CA58B8FC08 for ; Thu, 29 Nov 2012 20:23:45 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so6679223wey.13 for ; Thu, 29 Nov 2012 12:23:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/v5HiGS3u3P1Jk26IUoacUGbwSv6trH1IFz7RPa2T9M=; b=ZEvMru7ysfYKqrmOoEN1gqDoh6FDG9dAGDAezHqLbRN63lAmfeDDhiqF9SG2/waWQz 68cejZ8sF0u8d52kzWjFmiwKw0YvG08CEsYwBfqPLvmsz7PWEzYykDGHn9E5SSTIbdEW vKq+SDewx7wJr2CYfg3DjZKH0SiDiTD5OxQYMUjyPwbFnYVSScoJb4pVJvsT1ATdGIO3 vxwZPxn9LWGFnFpYqeD0mPKXLhREuziOq4SR1SYcXopzkpf3dIzx2XYaqvI6DoMoroAi czTrmYNynHeAxpVv6JTvDhaDHw6SJUHc0IdD+cwPTsZyilvo1droJMk4inUbgUJuxeJT jxsg== MIME-Version: 1.0 Received: by 10.180.102.102 with SMTP id fn6mr16624522wib.13.1354220624572; Thu, 29 Nov 2012 12:23:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Thu, 29 Nov 2012 12:23:44 -0800 (PST) In-Reply-To: <201211291940.qATJe1Jf033574@freefall.freebsd.org> References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> Date: Thu, 29 Nov 2012 12:23:44 -0800 X-Google-Sender-Auth: SjmNY1H439OrbvB_0NSEi2reJfc Message-ID: Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated From: Adrian Chadd To: Martin 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, 29 Nov 2012 20:23:46 -0000 Hi, On 29 November 2012 11:40, Martin wrote: > The following reply was made to PR kern/149516; it has been noted by GNATS. > > From: Martin > To: bug-followup@FreeBSD.org > Cc: > Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in > station dropping packets when associated > Date: Thu, 29 Nov 2012 20:35:05 +0100 > > Confirmed on 9.0-RELEASE-p3. Bug still exists. What's the fake mac address that you're using? Some extra code went into the driver which allowed for multicast group keys to be programmed in correctly on later chips. They needed this to be done "right" in order to support muli-vap mode with encryption. This was done incorrectly in 8.x and I fixed it sometime before 9.0-REL was branched. -HEAD definitely has the "right" programming. So, what's the fake MAC address? Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 20:25:36 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 407DB1BE; Thu, 29 Nov 2012 20:25:36 +0000 (UTC) (envelope-from adrian@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 090DA8FC12; Thu, 29 Nov 2012 20:25:36 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qATKPZse035694; Thu, 29 Nov 2012 20:25:35 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qATKPZub035690; Thu, 29 Nov 2012 20:25:35 GMT (envelope-from adrian) Date: Thu, 29 Nov 2012 20:25:35 GMT Message-Id: <201211292025.qATKPZub035690@freefall.freebsd.org> To: adrian@FreeBSD.org, adrian@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Subject: Re: kern/171394: [ath] ath0: ath_tx_aggr_comp_aggr: num frames seen=1; bf nframes=4 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, 29 Nov 2012 20:25:36 -0000 Synopsis: [ath] ath0: ath_tx_aggr_comp_aggr: num frames seen=1; bf nframes=4 State-Changed-From-To: open->closed State-Changed-By: adrian State-Changed-When: Thu Nov 29 20:25:17 UTC 2012 State-Changed-Why: This was fixed and verified; it hasn't shown up since. http://www.freebsd.org/cgi/query-pr.cgi?pr=171394 From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 20:26:39 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B3851DF; Thu, 29 Nov 2012 20:26:39 +0000 (UTC) (envelope-from adrian@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 18BBF8FC12; Thu, 29 Nov 2012 20:26:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qATKQcZI035742; Thu, 29 Nov 2012 20:26:38 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qATKQcSu035738; Thu, 29 Nov 2012 20:26:38 GMT (envelope-from adrian) Date: Thu, 29 Nov 2012 20:26:38 GMT Message-Id: <201211292026.qATKQcSu035738@freefall.freebsd.org> To: adrian@FreeBSD.org, sam@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Subject: Re: kern/121061: [ath] [panic] panic while ejecting ath(4)-adapter during shutdown 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, 29 Nov 2012 20:26:39 -0000 Synopsis: [ath] [panic] panic while ejecting ath(4)-adapter during shutdown Responsible-Changed-From-To: sam->freebsd-wireless Responsible-Changed-By: adrian Responsible-Changed-When: Thu Nov 29 20:26:26 UTC 2012 Responsible-Changed-Why: Flip to maintainer email list. http://www.freebsd.org/cgi/query-pr.cgi?pr=121061 From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 20:45:16 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C128543; Thu, 29 Nov 2012 20:45:16 +0000 (UTC) (envelope-from nakal@web.de) Received: from mout.web.de (mout.web.de [212.227.15.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2DC508FC14; Thu, 29 Nov 2012 20:45:15 +0000 (UTC) Received: from zelda.sugioarto.com ([217.236.0.219]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0Mdueb-1Ts8vM2Tvh-00QB48; Thu, 29 Nov 2012 21:45:13 +0100 Date: Thu, 29 Nov 2012 21:45:12 +0100 From: Martin To: Adrian Chadd Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated Message-ID: <20121129214512.4909fa8f@zelda.sugioarto.com> In-Reply-To: References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.13; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:pUeW9tVLBCXhOA1LD0MEw2PBBGs1OxyrhpEGejOZOyH S4kxbqJHWpOaKe8Z5HEH69IdjcNlzqitnSX8Fb5gIbdmqe+mt2 JwHQSsqkI64bz1iX2bRCt08vT0bfj8gyxwkHV7+0vKfGGKfhRI cITVHfAeww/fLsq3hejuy9pzTXsMvJD1TFcj3zpQ6lamSn6Nwh H0IT0jGvQV6gZIeX3A9hg== 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, 29 Nov 2012 20:45:16 -0000 Am Thu, 29 Nov 2012 12:23:44 -0800 schrieb Adrian Chadd : > > Confirmed on 9.0-RELEASE-p3. Bug still exists. > > What's the fake mac address that you're using? > > Some extra code went into the driver which allowed for multicast group > keys to be programmed in correctly on later chips. They needed this to > be done "right" in order to support muli-vap mode with encryption. > This was done incorrectly in 8.x and I fixed it sometime before > 9.0-REL was branched. -HEAD definitely has the "right" programming. > > So, what's the fake MAC address? Hi, I am using this address: d0:0f:d0:0f:d0:0f (german for "stupid-stupid-stupid) ;) When I setup it on wlan0 and ath0, the stations can associate, but cannot communicate with hostapd. -- Martin From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 20:53:42 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52CA778A for ; Thu, 29 Nov 2012 20:53:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id D38968FC13 for ; Thu, 29 Nov 2012 20:53:41 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so6689774wey.13 for ; Thu, 29 Nov 2012 12:53:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=tjPatkefxDB5dLAhIxZ4I7Ki+ncmMQ2pVxfRKTBnQZM=; b=dBBzne7T2GMMQcjFJPHR3wkPe8DE1TJULGt5gW+7E2X9G5P5TD2uRaJ0Ph2Td2l0Yr sP2xDQIAFaow19PD2pvY/jULp3fnD0jquZRoaFEMhs2uEDgszQuT0fdSfq3/GmyEPdLc UrQk8u3Z4CYW8CXJi8bDEoTr1dG7Rgk6yXY8M38Zsg5rS0+FHD3WzNdo9ovU5nfdHXF5 vjmL4qGOIsoiIpB1yijRwhsxyRbZgGfHDsHCp3j49B4YKKdJKlfNCxBUPdDkHSDAWOtW uGe11IIKdLSKCIY7RJC1a8erv+lI+qiQD6JfeCXFthhiaQ2Ajgl4WfLvs9X6yJ0ZCQRB cEUg== MIME-Version: 1.0 Received: by 10.180.105.105 with SMTP id gl9mr16586633wib.17.1354222420717; Thu, 29 Nov 2012 12:53:40 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Thu, 29 Nov 2012 12:53:40 -0800 (PST) In-Reply-To: <20121129214512.4909fa8f@zelda.sugioarto.com> References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> <20121129214512.4909fa8f@zelda.sugioarto.com> Date: Thu, 29 Nov 2012 12:53:40 -0800 X-Google-Sender-Auth: _psYvNpT5U5hRRv0-R8oO6fI5LA Message-ID: Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated From: Adrian Chadd To: Martin 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, 29 Nov 2012 20:53:42 -0000 You ca'nt set the high bit in the first (left hand) octet, that means something special. Set it to 0x0d and re-test. Adrian On 29 November 2012 12:45, Martin wrote: > Am Thu, 29 Nov 2012 12:23:44 -0800 > schrieb Adrian Chadd : > >> > Confirmed on 9.0-RELEASE-p3. Bug still exists. >> >> What's the fake mac address that you're using? >> >> Some extra code went into the driver which allowed for multicast group >> keys to be programmed in correctly on later chips. They needed this to >> be done "right" in order to support muli-vap mode with encryption. >> This was done incorrectly in 8.x and I fixed it sometime before >> 9.0-REL was branched. -HEAD definitely has the "right" programming. >> >> So, what's the fake MAC address? > > Hi, > > I am using this address: > > d0:0f:d0:0f:d0:0f (german for "stupid-stupid-stupid) ;) > > When I setup it on wlan0 and ath0, the stations can associate, but > cannot communicate with hostapd. > > -- > Martin From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 21:39:10 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 597CF77D; Thu, 29 Nov 2012 21:39:10 +0000 (UTC) (envelope-from nakal@web.de) Received: from mout.web.de (mout.web.de [212.227.17.11]) by mx1.freebsd.org (Postfix) with ESMTP id DA1428FC0C; Thu, 29 Nov 2012 21:39:09 +0000 (UTC) Received: from zelda.sugioarto.com ([217.236.0.188]) by smtp.web.de (mrweb003) with ESMTPSA (Nemesis) id 0LaTdP-1SwMwb41Nv-00m6lm; Thu, 29 Nov 2012 22:39:03 +0100 Date: Thu, 29 Nov 2012 22:39:01 +0100 From: Martin To: Adrian Chadd Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated Message-ID: <20121129223901.686290ce@zelda.sugioarto.com> In-Reply-To: References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> <20121129214512.4909fa8f@zelda.sugioarto.com> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.13; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:02SZemnamC7p6ToIWn31dPUsLfQw7N8MRbEy1y0+zEh QPUrzFZji3loWkCUne1f2Lh/InA8UwIB9gD5QL+cwb6dqjAPBt pHY0eRVietrlX1EHNWsfq5xZFjGPscBBBEU59bTX5T/HljGj5C 5s4ThqAke4Fe7uCV4EQ3zvVVf3G3JeMizrabF6DQQGDLW2XJJH ZT/ww8xkHEwHBN09fif0Q== 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, 29 Nov 2012 21:39:10 -0000 Am Thu, 29 Nov 2012 12:53:40 -0800 schrieb Adrian Chadd : > You ca'nt set the high bit in the first (left hand) octet, that means > something special. > > Set it to 0x0d and re-test. > > > > Adrian Hmm... now this is weird... When I set the first octet to 0x0d, the hostapd does not even appear in the available networks. I also tried to set it to 0x00 and it appeared again, but I could not associate, either. It works only when BSSID = MAC. -- Martin From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 21:43:07 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6239E98E for ; Thu, 29 Nov 2012 21:43:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id E07D18FC13 for ; Thu, 29 Nov 2012 21:43:06 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so6707542wey.13 for ; Thu, 29 Nov 2012 13:43:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=hMCHvQn1chV4hZOzjWKjY1NzQTPAcfjWtIyEJdhz3gg=; b=IWhlEhV+XJ22SM/A40o2g/Q66GOo13eU0M6Xc8J7xBsXpZjuCZsUfrAmBijCmfYzeT bA5ZYf/cKb/IVjix7VtJFUO/QWSgv1Dk+cXfMLfaQEIcG9NMvqz7RRExx7l4zcS6oVBE m2t4A8rm+3SaCNI7Qm0cJn8mPFoDge0t3DJFnPrJetdkOsnfMKjBLNr0AVUhc1lZ0ZCy gvD51fd2FYuXTDnOYSzwU1L7WfR14agbyA1MkcliElb3Y9RbmxCsa7GV0glQU1StZpES 7K0YWvnhJN43gNnT1p/09+rj3JWkfKGJ/28WEZgDaVf0gswWZj3zv5tJ2FHlegctQKF+ 0opA== MIME-Version: 1.0 Received: by 10.180.102.102 with SMTP id fn6mr16844348wib.13.1354225385040; Thu, 29 Nov 2012 13:43:05 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Thu, 29 Nov 2012 13:43:04 -0800 (PST) In-Reply-To: <20121129223901.686290ce@zelda.sugioarto.com> References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> <20121129214512.4909fa8f@zelda.sugioarto.com> <20121129223901.686290ce@zelda.sugioarto.com> Date: Thu, 29 Nov 2012 13:43:04 -0800 X-Google-Sender-Auth: RsWdnRevlaPAH8E4VNp-pNht4lU Message-ID: Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated From: Adrian Chadd To: Martin 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, 29 Nov 2012 21:43:07 -0000 There was someone who posted on -wireless a while ago about how to "correctly" program different mac addresses for different VAPs. The whole setup path is a little un-intuitive and needs some love. So take a look over the -wireless archives for multi-VAP and separate mac addresses. :-) Aha. It's actually having the LSB set in the first octet. Not the MSB. So 0x80 is fine. 0x90 is fine. 0x09 is not. http://en.wikipedia.org/wiki/Multicast_address The hardware treats that address as special, so don't ever configure a MAC with that multicast bit set. Or things won't work out well. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 21:53:51 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5BD8DC8F; Thu, 29 Nov 2012 21:53:51 +0000 (UTC) (envelope-from nakal@web.de) Received: from mout.web.de (mout.web.de [212.227.15.4]) by mx1.freebsd.org (Postfix) with ESMTP id DE9E88FC16; Thu, 29 Nov 2012 21:53:50 +0000 (UTC) Received: from zelda.sugioarto.com ([217.236.14.77]) by smtp.web.de (mrweb003) with ESMTPSA (Nemesis) id 0LmLac-1T4JKx0kmg-00aGPT; Thu, 29 Nov 2012 22:53:49 +0100 Date: Thu, 29 Nov 2012 22:53:47 +0100 From: Martin To: Adrian Chadd Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated Message-ID: <20121129225347.757b1fc8@zelda.sugioarto.com> In-Reply-To: References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> <20121129214512.4909fa8f@zelda.sugioarto.com> <20121129223901.686290ce@zelda.sugioarto.com> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.13; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:w3jjdnwGozC1h2BFNZcl77PuP4Cf6DcJ/cj8LDA7VoB y//BAlc2J1k1DIYADPvH3pLwU7RsbdaQJdfiKR9J9ix4O191R+ rGiZq08elPq9JIUosVvWTLH8vlPlumJ0suG4YNAEVBlWkku40h gmF70byu88iGNiJeT/R55NyVSu+RowNKXz9o3MnwUFr2gGzBJa 9vpE05yLDvpPBJtXpoEmA== 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, 29 Nov 2012 21:53:51 -0000 Am Thu, 29 Nov 2012 13:43:04 -0800 schrieb Adrian Chadd : > There was someone who posted on -wireless a while ago about how to > "correctly" program different mac addresses for different VAPs. The > whole setup path is a little un-intuitive and needs some love. > > So take a look over the -wireless archives for multi-VAP and separate > mac addresses. :-) > > Aha. It's actually having the LSB set in the first octet. Not the MSB. > > So 0x80 is fine. 0x90 is fine. 0x09 is not. > > http://en.wikipedia.org/wiki/Multicast_address > > The hardware treats that address as special, so don't ever configure a > MAC with that multicast bit set. Or things won't work out well. > > > > Adrian When I understand you correctly, this only explains why 0x0d does not work. It still does not explain why 0x00 and 0xd0 do not work. I also wrote that the lowest bit needs to be "0" in my first PR (duh! it has been too long ago!). [1] As I said, everything was OK on FreeBSD 7.x and broke somewhere in 8.1-RELEASE. Please also notice that the problem affects ath(4) on the driver layer (I suppose) not generally on IEEE 802.11 layer, because I also tested with rum(4) and I could use it properly. [1] http://lists.freebsd.org/pipermail/freebsd-stable/2010-July/058059.html -- Martin From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 29 21:56:36 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5B2CD1D for ; Thu, 29 Nov 2012 21:56:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3F52A8FC1C for ; Thu, 29 Nov 2012 21:56:35 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so6712083wey.13 for ; Thu, 29 Nov 2012 13:56:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NzDpH5GRYdz6a3AM94VcKskgKFoL18gNz0LkGG5KsWQ=; b=qj+cx2SMZOQ36CT6HvqSo6Dxn8YRc/HuLU+liN1PqBVJUkse+DuFtKNyLE44A4/la/ QGO8HT3W3j8hgI/a8WUE1JGncylMgX2UlDFp8tEidL32gBN/EY9wVmmoxgI1Xg1+wTL7 fBwgsfpuKXWu9fIn+dPAf2ZqF4eZoUfSMfI+NmdScns8/YO6caAGcK2OWUOhS1xmB4TS 0K6ff4g9LoO2mdo6/zKdFZZPT7B17zxS8iz0L73B5QjGK3xpeZ6RFpWScA+34j6gT1dO cE2EtCHh8swblsnNaDggQXtu8mxRf2QJujFt/NaCz6lv/LRZcULFkhRlp+jKXpeLMCZo E6Rw== MIME-Version: 1.0 Received: by 10.180.88.138 with SMTP id bg10mr37427105wib.13.1354226195253; Thu, 29 Nov 2012 13:56:35 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Thu, 29 Nov 2012 13:56:35 -0800 (PST) In-Reply-To: <20121129225347.757b1fc8@zelda.sugioarto.com> References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> <20121129214512.4909fa8f@zelda.sugioarto.com> <20121129223901.686290ce@zelda.sugioarto.com> <20121129225347.757b1fc8@zelda.sugioarto.com> Date: Thu, 29 Nov 2012 13:56:35 -0800 X-Google-Sender-Auth: ueWk3HEhQQlmw0uCDLMDG21fx00 Message-ID: Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated From: Adrian Chadd To: Martin 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, 29 Nov 2012 21:56:36 -0000 Hi, Yes. As I said, the whole "configure an alternate MAC" thing isn't very consistent and I'm sure that the whole migration to VAP interfaces made some of the MAC BSSID and local ethernet card address programming "inconsistent." If you want to take a look at whta's in the card: * add ATH_DIAGAPI, AH_DEBUG, ATH_DEBUG to your kernel, recompile * compile up src/tools/tools/ath/ * use athregs -i athX , look at the BSS and MAC registers to see what address it has configured. I bet htose aren't "right".. adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 30 06:58:28 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3D4E5D5D; Fri, 30 Nov 2012 06:58:28 +0000 (UTC) (envelope-from nakal@web.de) Received: from mout.web.de (mout.web.de [212.227.15.3]) by mx1.freebsd.org (Postfix) with ESMTP id BDBF38FC0C; Fri, 30 Nov 2012 06:58:27 +0000 (UTC) Received: from zelda.sugioarto.com ([217.236.11.108]) by smtp.web.de (mrweb103) with ESMTPSA (Nemesis) id 0Lw0q9-1T8myu02vd-017kYC; Fri, 30 Nov 2012 07:58:21 +0100 Date: Fri, 30 Nov 2012 07:58:19 +0100 From: Martin To: Adrian Chadd Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated Message-ID: <20121130075819.42a8c41c@zelda.sugioarto.com> In-Reply-To: References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> <20121129214512.4909fa8f@zelda.sugioarto.com> <20121129223901.686290ce@zelda.sugioarto.com> <20121129225347.757b1fc8@zelda.sugioarto.com> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.13; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:KnegbbT6brF+1vRfTL1oBRWyJ/BCZgbRZFlYZq6PbeZ o3piIgVY9vyGFOBOC1Gh0HdRy8U/HUAjj0flygaBf/QnqsE57F A/VS1AVjf+KE6zmJD9lA/Zr7nRwaB9DrGD4vFmguEQmyhx3xWH YzykqEJI13asgS0RMR9iNxygZkfILtMXkWmkr+wFz6rxrTooa3 TvgMb6bBfCkzE+7r2yTxw== 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, 30 Nov 2012 06:58:28 -0000 Am Thu, 29 Nov 2012 13:56:35 -0800 schrieb Adrian Chadd : > Hi, > > Yes. As I said, the whole "configure an alternate MAC" thing isn't > very consistent and I'm sure that the whole migration to VAP > interfaces made some of the MAC BSSID and local ethernet card address > programming "inconsistent." Hi, this is not good, if alternate MACs are not supported, because you also need them to configure multiple access points in hostapd. Take a look at the end of the hostapd.conf in examples. This definitely takes away features. Like I said... the ath(4) driver is dropping/blocking/filtering the packets somewhere in the send code. The receive part and the network operation generally work correctly, as far as I can remember. > If you want to take a look at whta's in the card: > > * add ATH_DIAGAPI, AH_DEBUG, ATH_DEBUG to your kernel, recompile > * compile up src/tools/tools/ath/ > * use athregs -i athX , look at the BSS and MAC registers to see what > address it has configured. > > I bet htose aren't "right".. I'll take a look at it soon. -- Martin From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 30 10:25:06 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D3E0487 for ; Fri, 30 Nov 2012 10:25:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id A40008FC08 for ; Fri, 30 Nov 2012 10:25:05 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so113744wey.13 for ; Fri, 30 Nov 2012 02:25:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=QwesNXWQXMgBLLvnEmFWxMNY/yhKRU0jPafIbeXPmUU=; b=cGjG48nILfBiAzYKz6xCOQt7Z3OJ7kbXnEmx2FtHt3UqjBAnYfbPxRyDVuBTTqdYCT 15Mn6e38E5jyWTWb0u+VK63twPAhPvqz1DP0ofipd23Ne2ki+NIqc03ae5lOlghpenUX edV50/PwvNxsLQCalLCHkJQaLr92hocnLbDpIwLtW19xPQPzY2+TtTqVmxCa3dfxOFa/ mMKyjV29ddd2mGN2j02Am2sRBTMHNgsEdyZp1XEsK0HDWHyOPkt3S3V+pi2/xT862Bw1 ZjS/kbAmzbxWDvp7jqanhdVdouoD7mDGyyk/V/nsXzDWbbsxUQXFRr09lwrYpNUu5/xy TqlA== MIME-Version: 1.0 Received: by 10.216.139.140 with SMTP id c12mr324594wej.46.1354271104526; Fri, 30 Nov 2012 02:25:04 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 30 Nov 2012 02:25:04 -0800 (PST) Date: Fri, 30 Nov 2012 02:25:04 -0800 X-Google-Sender-Auth: NIMSrYFO8SLagxixJ1AFjc9rSKM Message-ID: Subject: Please test - collapsing the TX locking down to ATH_TX_LOCK() From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Nov 2012 10:25:06 -0000 Hi all, This patch collapses all of the TXQ locking down to a single TX lock and (mostly correctly) wraps the TX outbound path in a single, giant lock. The TX completion path is still a patchwork of locking, primarily because _it_ needs to be able to free net80211 node references and that can't be done with the TX lock held (or all kinds of LORs occur.) Once this is done, I'll strip out the ATH_NODE lock (since it's now not really needed any longer) and I'll just do the whole TX and TX completion handling behind this TX lock. I can then undo some of the strange locking going on with the power save handling - then I can move onto implementing correctly behaving PS-POLL. Also, once this is done, I can start doing useful things, like shoehorning traffic from any TID to any hardware TXQ, rather than assuming a fixed mapping between TID and hardware TXQ. (Again, this will be useful for PS-POLL handling.) http://people.freebsd.org/~adrian/ath/20121129-ath-tx-lock-5.diff I'd appreciate it if people would test this out against the latest -HEAD and let me know if it breaks. Since it's just mostly a mechanical copy/paste, I'm only really worried if it causes crashes, hangs or LORs. There's one LOR that will get triggered if you send fragments, but as sending fragments is currently just plain broken, it won't show up. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 30 21:02:55 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 63F3C53A for ; Fri, 30 Nov 2012 21:02:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id DD3978FC0C for ; Fri, 30 Nov 2012 21:02:54 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id dr1so4297323wgb.1 for ; Fri, 30 Nov 2012 13:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=C05Ecw+vjk8fwffw4xeqeoEImkVs4Jrer/RCtMARUXM=; b=J4UyQYbvAJVfnZyTUxnMH7hIg7wJyw2HCliksLyo1NjvdOAfgxrIveF6U9GFYR/1Rz /lnEZrHQl22JFyjWGgHn7PwPvk2108xPG3RwRKK5skrkRGd9vlGN+UTImPWGvkaQjUfj x2C1nVIfYuoI3oQscMZyoZGUvTCplcAbRc7xwViPaE5V+sdI4DrtJ4hwNt/kjAECSgif uHSlLbgBnlKpzkQEA1PrLPJOnENrjD62twgVNp0KKzR7ZFa9Y1o8PAlT4XitAtcbQE4b qP9u89KSOBAqt436n+beqAbKgbajqfmiSMU1XUSLhFEcFAaNgPnS8iWKjSitmqy1k+8L 0fPA== MIME-Version: 1.0 Received: by 10.216.200.160 with SMTP id z32mr929486wen.53.1354309368311; Fri, 30 Nov 2012 13:02:48 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 30 Nov 2012 13:02:48 -0800 (PST) Date: Fri, 30 Nov 2012 13:02:48 -0800 X-Google-Sender-Auth: jk-BUDqrEyuUjmF2K234CDc7KGk Message-ID: Subject: TDMA update: 802.11n NIC -> 802.11n NIC is now working stable (alas at 802.11a rates..) From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Nov 2012 21:02:55 -0000 Hi, I meant to post this last night but fell asleep. :-) I've verified that the 11n NIC <-> 11n NIC TDMA setup is working and working stable. I haven't yet run it over the course of "time needed to wrap a 32 bit TSF", so that's next. In this instance: * TDMA master: AR9280 * TDMA slave: AR5416 I have a couple of small patches to push up just to make the NEXTTBTT register in the 11n chips behave like the AR5212 version does (ie, TU resolution, not TSF resolution) as rounding errors seem to mess with the tsfadjust calculation a little. That'll get resolved when someone makes the logic all TSF aware. I also have a patch that extends sets the PCU AR_MISC_MODE bit that enforces the txop burst window, and doesn't allow the PCU to start TXing the frame if it will blow past the burst window. But it's stable without those two. So; those of you who were playing with it at the beginning of the year and couldn't get it stable - go forth and tinker! It actually works great now. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 30 23:26:00 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 145CDB12; Fri, 30 Nov 2012 23:26:00 +0000 (UTC) (envelope-from eadler@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 D31E28FC15; Fri, 30 Nov 2012 23:25:59 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qAUNPxjY019359; Fri, 30 Nov 2012 23:25:59 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAUNPxrE019355; Fri, 30 Nov 2012 23:25:59 GMT (envelope-from eadler) Date: Fri, 30 Nov 2012 23:25:59 GMT Message-Id: <201211302325.qAUNPxrE019355@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-wireless@FreeBSD.org, eadler@FreeBSD.org From: eadler@FreeBSD.org Subject: Re: kern/173898: [iwn] [patch] iwn(4) DOES support 6235 chip. 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, 30 Nov 2012 23:26:00 -0000 Synopsis: [iwn] [patch] iwn(4) DOES support 6235 chip. Responsible-Changed-From-To: freebsd-wireless->eadler Responsible-Changed-By: eadler Responsible-Changed-When: Fri Nov 30 23:25:59 UTC 2012 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=173898 From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 1 01:28:25 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B59E39A; Sat, 1 Dec 2012 01:28:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id 225048FC0C; Sat, 1 Dec 2012 01:28:24 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hm9so41742wib.13 for ; Fri, 30 Nov 2012 17:28:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4VMGXPHSRoazae5hV4T1PP1ViueDgKFKatGvIQyVTBk=; b=t6imBwZX0jdQf36/dKk7vOQ+G503grIVA8cr6zn4RADxUzy3N4ih36XfkmboRMhdwJ eVexMQsh8jzbBHarq4c0POQ/L4OcEpQ13a5RriE3uCY2a71Mp+Anmvd+K/jdnkIOD6As yXkBJS2fcoOQNEJDU1S25yKvni64FffMJw0CVXCwgz1LgHTrEK0wLK99WygdtoOidyvg rdezkqvfPOaaUKVMZ8tmMRJtMJ69Es4OR5YMss80BHUl+lwCXvGphynjkToILFSPcN9n 8dJWVogHic85UXaCR12v/4O+ff2/rTZDPAuZpnLBu70yu9hDk0dg5Vzd2WYH/Hvci6Wd rEVA== MIME-Version: 1.0 Received: by 10.180.78.1 with SMTP id x1mr441051wiw.17.1354325303931; Fri, 30 Nov 2012 17:28:23 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 30 Nov 2012 17:28:23 -0800 (PST) In-Reply-To: <201211302325.qAUNPxrE019355@freefall.freebsd.org> References: <201211302325.qAUNPxrE019355@freefall.freebsd.org> Date: Fri, 30 Nov 2012 17:28:23 -0800 X-Google-Sender-Auth: QyZZVuA4N3ts43121Fct0Nmm49s Message-ID: Subject: Re: kern/173898: [iwn] [patch] iwn(4) DOES support 6235 chip. From: Adrian Chadd To: eadler@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: Sat, 01 Dec 2012 01:28:25 -0000 It's not that simple. Speak to bernhard. There are other issues that he knows about. I don't know if he's replied to the email or not; poke him on irc. adrian On 30 November 2012 15:25, wrote: > Synopsis: [iwn] [patch] iwn(4) DOES support 6235 chip. > > Responsible-Changed-From-To: freebsd-wireless->eadler > Responsible-Changed-By: eadler > Responsible-Changed-When: Fri Nov 30 23:25:59 UTC 2012 > Responsible-Changed-Why: > I'll take it. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=173898 > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 1 04:37:12 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CE0873AD for ; Sat, 1 Dec 2012 04:37:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) by mx1.freebsd.org (Postfix) with ESMTP id 481858FC08 for ; Sat, 1 Dec 2012 04:37:12 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id 12so514099wgh.31 for ; Fri, 30 Nov 2012 20:37:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1CHI9J0qtMxtpAY5XbkfmRmqI8naiK2ZgTmtOenUtUw=; b=lReuTgVJuREhQ8WIPjzjyPmwqkVKvKDE2nnC0q2r6P6gfXWBGyMRPmpkebYu+IQ+5a VionpoZFmO7YOZ1mCTMEFf3lsggomi4Cpn2ztdo3EzFiKUwsG3xZaloWlcE/4kT2OQHp i361nsPCy9b5qhKiRLRklzYl5eKh/VVC8MUoQqM3vcmIEED9zqEs6rWTUvBGZ3tYAYNx aI1Qrlnk+rUvmwvULdULtIUsDHK5cO8itkM3PC4UiHzs3rEIErviYuMrb23WRLel6YwI b5rGbGcRvNGW03S7R1eMoRz2xkouXbLlVWGtvs/jk5FAHjguZGQ0/y2Aw+QyQQqIUh3r qeHw== MIME-Version: 1.0 Received: by 10.180.102.102 with SMTP id fn6mr847660wib.13.1354336631391; Fri, 30 Nov 2012 20:37:11 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 30 Nov 2012 20:37:11 -0800 (PST) In-Reply-To: <20121130075819.42a8c41c@zelda.sugioarto.com> References: <201211291940.qATJe1Jf033574@freefall.freebsd.org> <20121129214512.4909fa8f@zelda.sugioarto.com> <20121129223901.686290ce@zelda.sugioarto.com> <20121129225347.757b1fc8@zelda.sugioarto.com> <20121130075819.42a8c41c@zelda.sugioarto.com> Date: Fri, 30 Nov 2012 20:37:11 -0800 X-Google-Sender-Auth: gfJ2leJUDrA5i6jwaOUGneWOKno Message-ID: Subject: Re: kern/149516: [ath] ath(4) hostap with fake MAC/BSSID results in station dropping packets when associated From: Adrian Chadd To: Martin 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: Sat, 01 Dec 2012 04:37:13 -0000 On 29 November 2012 22:58, Martin wrote: > this is not good, if alternate MACs are not supported, because you also > need them to configure multiple access points in hostapd. Take a look > at the end of the hostapd.conf in examples. This definitely takes away > features. Alternate MACs are supported, but it likely needs a little further debugging to figure out what is working and what is broken. > Like I said... the ath(4) driver is dropping/blocking/filtering the > packets somewhere in the send code. The receive part and the network > operation generally work correctly, as far as I can remember. The driver doesn't do anything like that. It just passes frames up. The net80211 stack would set the MAC and the hardware TXes it. The ath driver doesn't do any kind of TX filtering by MAC address. >> If you want to take a look at whta's in the card: >> >> * add ATH_DIAGAPI, AH_DEBUG, ATH_DEBUG to your kernel, recompile >> * compile up src/tools/tools/ath/ >> * use athregs -i athX , look at the BSS and MAC registers to see what >> address it has configured. >> >> I bet htose aren't "right".. > > I'll take a look at it soon. Thanks, that'll be very helpful. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 1 04:59:55 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D884F441 for ; Sat, 1 Dec 2012 04:59:55 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 30AC08FC12 for ; Sat, 1 Dec 2012 04:59:54 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so1255149lbb.13 for ; Fri, 30 Nov 2012 20:59:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=3FvPTOZvq2hbhk/x0Kr7oKI4VLX00oktb2Vu6eWqczE=; b=GV8D5qV7zZ1L7V2srM2Y95t66KCtXej8tj0sP0Qcns8rLCmUe8ZvBzOsINIDJQSjmI Clnmt9L97DXBKGX+KEmTkpPYXVFGrs266qmWIiBVN5je0dvcxgg07vhSMfEnGSBu/DFO l1PNt4ZVHlvLqzq25aiXs1ZVCwceqN4IIvkXg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=3FvPTOZvq2hbhk/x0Kr7oKI4VLX00oktb2Vu6eWqczE=; b=QO/daXjXlkg6k2016I11Mrx4m4GU1Y+kO2FiW4jNSlkg2tb/koxfO9dis7ck7UTDDN Ig9jKD/jBc+X+4wg04t6wKGr82883f86WAfJJTraedfB8kw7blNKcGor8Y/6FXAZZZwI UscfgyV5iUZTqxpF7yvl8kZ3B4jXcGGG8+jHUO9wh/QblqOykmaYEx5LsAPR7e0ewMBM b1mXWf+jK2N0rXrnA+X4lfLd2Y6YoFVYFGYzL2uPgn045aGi39u5jWq39TGnf1foGmHt aCaFM2rTBTPciyMnE/YDxfM9rIqakvDInvlEOT60SKdYoSb9jzwfwMgz4CpZhfzS50zl cJ5A== Received: by 10.152.47.75 with SMTP id b11mr3328473lan.14.1354337993563; Fri, 30 Nov 2012 20:59:53 -0800 (PST) MIME-Version: 1.0 Sender: lists@eitanadler.com Received: by 10.112.154.168 with HTTP; Fri, 30 Nov 2012 20:59:22 -0800 (PST) In-Reply-To: References: <201211302325.qAUNPxrE019355@freefall.freebsd.org> From: Eitan Adler Date: Fri, 30 Nov 2012 23:59:22 -0500 X-Google-Sender-Auth: SxwYp27Vkr5QneFEMO55AvTwF7E Message-ID: Subject: Re: kern/173898: [iwn] [patch] iwn(4) DOES support 6235 chip. To: Adrian Chadd , davide@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkzVhHNqWefvBFwMR1IOgRGt46Ff11VTrwMe0HFE6YvBJHc2fap4cl658GCgPqI7rGUK77I Cc: freebsd-wireless@freebsd.org, bug-followup@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, 01 Dec 2012 04:59:55 -0000 On 30 November 2012 20:28, Adrian Chadd wrote: > It's not that simple. Speak to bernhard. Davide, You mention some issues and I asked you to follow up to the PR. Can you please explain them? > There are other issues that he knows about. I don't know if he's > replied to the email or not; poke him on irc. IRC doesn't help as the record does not go into the PR -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 1 16:05:46 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1171D20B for ; Sat, 1 Dec 2012 16:05:46 +0000 (UTC) (envelope-from hg@queue.to) Received: from pickle.queue.to (pickle.queue.to [71.180.69.18]) by mx1.freebsd.org (Postfix) with ESMTP id ADA578FC13 for ; Sat, 1 Dec 2012 16:05:45 +0000 (UTC) Received: (qmail 36355 invoked from network); 1 Dec 2012 11:05:38 -0500 Received: from cally.queue.to (172.16.0.6) by pickle.queue.to with ESMTP; 1 Dec 2012 11:05:38 -0500 Message-ID: <50BA2ACA.5080400@queue.to> Date: Sat, 01 Dec 2012 11:05:30 -0500 From: Howard Goldstein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: adrian@freebsd.org Subject: Re: Please test - collapsing the TX locking down to ATH_TX_LOCK() References: In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA96F13B27DCA14C80D1CBECD" 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, 01 Dec 2012 16:05:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA96F13B27DCA14C80D1CBECD Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/30/2012 05:25, Adrian Chadd wrote: > I'd appreciate it if people would test this out against the latest > -HEAD and let me know if it breaks. Since it's just mostly a > mechanical copy/paste, I'm only really worried if it causes crashes, > hangs or LORs. >=20 > There's one LOR that will get triggered if you send fragments, but as > sending fragments is currently just plain broken, it won't show up. I've been beating the patched head up on an Asus EEE 701 notebook for the better part of a day without any issues. Looks great The 701 identifies as an AR2425/5424 ("Swan") Thanks Howard --------------enigA96F13B27DCA14C80D1CBECD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iD8DBQFQuirSdYVFuiUUgywRAvH6AJ9mBh8SB9zbLXESFx4bZv2Bg4GrowCgsAth MoyaIi8EzzqFj6gLiW7CEAw= =xCFI -----END PGP SIGNATURE----- --------------enigA96F13B27DCA14C80D1CBECD--