From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 19 07:11:41 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 EF761106566C; Sun, 19 Aug 2012 07:11:40 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 7F11E8FC08; Sun, 19 Aug 2012 07:11:40 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T2zhz-000IF7-D5; Sun, 19 Aug 2012 11:14:03 +0400 Date: Sun, 19 Aug 2012 11:14:03 +0400 From: Slawa Olhovchenkov To: freebsd-wireless@freebsd.org, Adrian Chadd Message-ID: <20120819071403.GF98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1311732708.20120815005429@serebryakov.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Subject: New ath code works well as AP 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: Sun, 19 Aug 2012 07:11:41 -0000 ... and still works bad as client: [138084] ath0: mem 0xb0200000-0xb020ffff irq 18 at device 5.0 on pci6 [138085] ath0: DMA setup: legacy [138085] ath0: [HT] enabling HT modes [138085] ath0: [HT] 2 RX streams; 2 TX streams [138085] ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps [138085] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps [138085] ath0: 2T2R [138085] ath0: 11ng MCS 20MHz [138085] ath0: MCS 0-7: 6.5Mbps - 65Mbps [138085] ath0: MCS 8-15: 13Mbps - 130Mbps [138085] ath0: 11ng MCS 40MHz: [138085] ath0: MCS 0-7: 13.5Mbps - 135Mbps [138085] ath0: MCS 8-15: 27Mbps - 270Mbps [138085] ath0: 11ng MCS 40MHz SGI: [138085] ath0: MCS 0-7: 15Mbps - 150Mbps [138085] ath0: MCS 8-15: 30Mbps - 300Mbps [138085] ath0: AR9220 mac 128.2 RF5133 phy 13.0 [138085] ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 [138085] ath0: Use hw queue 1 for WME_AC_BE traffic [138085] ath0: Use hw queue 0 for WME_AC_BK traffic [138085] ath0: Use hw queue 2 for WME_AC_VI traffic [138085] ath0: Use hw queue 3 for WME_AC_VO traffic [138085] ath0: Use hw queue 8 for CAB traffic [138085] ath0: Use hw queue 9 for beacons [138085] ath0: using multicast key search [138086] wlan0: bpf attached [138086] wlan0: bpf attached [138086] wlan0: Ethernet address: f4:ec:38:a3:10:dc [138088] wlan0: link state changed to UP [138088] Aug 18 13:13:20 notebook kernel: [138088] wlan0: link state changed to UP [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=0xc4b2cdf0: addbaw=0, dobaw=0, seqno=242, retry=0 [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=0xc4b2cdf0: tid txq_depth=1 hwq_depth=0, bar_wait=0 [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=16627 [145438] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV 01 1d 00 02 00 00 KID 0] 0M [145438] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 200f 011d 0020 0200 0000 aaaa 0300 0000 0800 4500 0054 7e70 4000 4006 2770 0a00 001b c346 c762 f69d 0016 1a05 4198 1648 1015 8018 040f 01f8 0000 0101 080a 08ab 35d4 50c5 6e53 f988 6d22 6676 20bf 51b9 b74c 3fb2 933e 5d5a f972 eec7 7545 3be7 475c ad3b b052 [145438] wlan0: link state changed to DOWN [145440] wlan0: link state changed to UP [145450] wlan0: link state changed to DOWN [145452] wlan0: link state changed to UP [145505] wlan0: link state changed to DOWN [145507] wlan0: link state changed to UP [145517] wlan0: link state changed to DOWN [145519] wlan0: link state changed to UP [147013] wlan0: link state changed to DOWN [147015] wlan0: link state changed to UP [147025] wlan0: link state changed to DOWN [147028] wlan0: link state changed to UP [154244] wlan0: link state changed to DOWN [154246] wlan0: link state changed to UP [155821] ath0: bb hang detected (0x4), resetting [175886] wlan0: link state changed to DOWN [175889] wlan0: link state changed to UP [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41ff0: addbaw=0, dobaw=0, seqno=0, retry=0 [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41ff0: tid txq_depth=1 hwq_depth=0, bar_wait=0 [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=40661 [177174] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) probe_req 0M [177174] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 40ed 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c [177174] wlan0: link state changed to DOWN [177176] wlan0: link state changed to UP [177186] wlan0: link state changed to DOWN [177188] wlan0: link state changed to UP [177375] wlan0: link state changed to DOWN [177378] wlan0: link state changed to UP [177388] wlan0: link state changed to DOWN [177390] wlan0: link state changed to UP [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b39d20: addbaw=0, dobaw=0, seqno=2062, retry=0 [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b39d20: tid txq_depth=13 hwq_depth=0, bar_wait=0 [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=47131 [179397] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV 0b b8 00 05 00 00 KID 0] 0M [179397] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 e080 0bb8 0020 0500 0000 aaaa 0300 0000 0800 4500 0034 1535 4000 4006 90cb 0a00 001b c346 c762 f65f 0014 b6aa cfc8 46ad 84ba 8010 03fc e360 0000 0101 080a 428d 489d f0d1 3651 [179399] wlan0: link state changed to UP [179409] wlan0: link state changed to DOWN [179411] wlan0: link state changed to UP [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=0xc4b355f0: addbaw=0, dobaw=0, seqno=948, retry=0 [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=0xc4b355f0: tid txq_depth=4 hwq_depth=0, bar_wait=0 [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=41912 [179636] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV b1 a3 00 00 00 00 KID 0] 0M [179636] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 403b b1a3 0020 0000 0000 aaaa 0300 0000 0800 4500 0034 bb4b 4000 4006 eab4 0a00 001b c346 c762 b0cc 0014 5ba9 9748 1033 a13f 8010 03fc 39f3 0000 0101 080a f0d2 a239 f0d4 cae3 [179636] wlan0: link state changed to DOWN [179638] wlan0: link state changed to UP [179648] wlan0: link state changed to DOWN [179650] wlan0: link state changed to UP [180075] wlan0: link state changed to DOWN [180077] wlan0: link state changed to UP [180087] wlan0: link state changed to DOWN [180089] wlan0: link state changed to UP [180486] wlan0: link state changed to DOWN [180488] wlan0: link state changed to UP [180498] wlan0: link state changed to DOWN [180500] wlan0: link state changed to UP [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41bb0: addbaw=0, dobaw=0, seqno=0, retry=0 [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41bb0: tid txq_depth=1 hwq_depth=0, bar_wait=0 [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=58839 [181165] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) probe_req 0M [181165] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 605d 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c [181165] wlan0: link state changed to DOWN [181166] Aug 19 01:11:18 notebook kernel: [181165] wlan0: link state changed to DOWN [181168] wlan0: link state changed to UP [181168] Aug 19 01:11:20 notebook kernel: [181168] wlan0: link state changed to UP [181178] wlan0: link state changed to DOWN [181178] Aug 19 01:11:30 notebook kernel: [181178] wlan0: link state changed to DOWN [181180] wlan0: link state changed to UP [181612] wlan0: link state changed to DOWN [181614] wlan0: link state changed to UP [181624] wlan0: link state changed to DOWN [181626] wlan0: link state changed to UP [190739] wlan0: link state changed to DOWN [190741] wlan0: link state changed to UP [190751] wlan0: link state changed to DOWN [190754] wlan0: link state changed to UP [194052] ath0: device timeout [202568] ath0: device timeout [205182] wlan0: link state changed to DOWN [205184] wlan0: link state changed to UP [214975] ath0: bb hang detected (0x4), resetting [216007] wlan0: link state changed to DOWN [216009] wlan0: link state changed to UP From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 19 07:12: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 DE416106564A for ; Sun, 19 Aug 2012 07:12:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id AFFC38FC12 for ; Sun, 19 Aug 2012 07:12:20 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so5818103pbb.13 for ; Sun, 19 Aug 2012 00:12:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=MfiXGpJ2xFrgqyHGOwDzNIE7C/qwU3cEc1kJ0yofkuw=; b=CtFC7OiLqnSdnH9CMSCOVXRk0l5Ot1pcIVGTZck+nyPu484i5HGoWpFrHS9IOO8KNU hHIMg6MQprGlhg7UEzhdZW+emcp8x5hvfNf4nzMHrjX7A1HHU64gVM/DfUgDGWXdUYod M0EwmXQgF4/x5jgoq749zTuT3H9jD5PjYvAG2E6nkZrD6RBLIqwIijVnOB93LWV8IqEG QM3pihKA/ak4uzIUjxjleUDafrwdv3aQ4q5cK93D1kqB6ksLuAdov4JPvSvuaVDQt0a0 Cl5TdZivRbFMDPLS8rL4xe9hiQlDGn6EB49WQ/AfNk/8HBTzUQ2D8C3s2MDws16sPwfP SAsw== MIME-Version: 1.0 Received: by 10.66.72.130 with SMTP id d2mr21068682pav.59.1345360340121; Sun, 19 Aug 2012 00:12:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Sun, 19 Aug 2012 00:12:20 -0700 (PDT) In-Reply-To: <20120819071403.GF98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> Date: Sun, 19 Aug 2012 00:12:20 -0700 X-Google-Sender-Auth: ohzN3hbxX6ND4PuwW8faOfGtbe8 Message-ID: From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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: Sun, 19 Aug 2012 07:12:21 -0000 I don't see this kind of behaviour in STA mode. What are you associating to= ? What channel is it on? Adrian On 19 August 2012 00:14, Slawa Olhovchenkov wrote: > ... and still works bad as client: > > [138084] ath0: mem 0xb0200000-0xb020ffff irq 18 at device = 5.0 on pci6 > [138085] ath0: DMA setup: legacy > [138085] ath0: [HT] enabling HT modes > [138085] ath0: [HT] 2 RX streams; 2 TX streams > [138085] ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > [138085] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 1= 8Mbps 24Mbps 36Mbps 48Mbps 54Mbps > [138085] ath0: 2T2R > [138085] ath0: 11ng MCS 20MHz > [138085] ath0: MCS 0-7: 6.5Mbps - 65Mbps > [138085] ath0: MCS 8-15: 13Mbps - 130Mbps > [138085] ath0: 11ng MCS 40MHz: > [138085] ath0: MCS 0-7: 13.5Mbps - 135Mbps > [138085] ath0: MCS 8-15: 27Mbps - 270Mbps > [138085] ath0: 11ng MCS 40MHz SGI: > [138085] ath0: MCS 0-7: 15Mbps - 150Mbps > [138085] ath0: MCS 8-15: 30Mbps - 300Mbps > [138085] ath0: AR9220 mac 128.2 RF5133 phy 13.0 > [138085] ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > [138085] ath0: Use hw queue 1 for WME_AC_BE traffic > [138085] ath0: Use hw queue 0 for WME_AC_BK traffic > [138085] ath0: Use hw queue 2 for WME_AC_VI traffic > [138085] ath0: Use hw queue 3 for WME_AC_VO traffic > [138085] ath0: Use hw queue 8 for CAB traffic > [138085] ath0: Use hw queue 9 for beacons > [138085] ath0: using multicast key search > [138086] wlan0: bpf attached > [138086] wlan0: bpf attached > [138086] wlan0: Ethernet address: f4:ec:38:a3:10:dc > [138088] wlan0: link state changed to UP > [138088] Aug 18 13:13:20 notebook kernel: [138088] wlan0: link state chan= ged to UP > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=3D0xc4b2cdf0: addbaw= =3D0, dobaw=3D0, seqno=3D242, retry=3D0 > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=3D0xc4b2cdf0: tid tx= q_depth=3D1 hwq_depth=3D0, bar_wait=3D0 > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: tid 16: txq_depth=3D2, = txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, baw_h= ead=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D16627 > [145438] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) dat= a WEP [IV 01 1d 00 02 00 00 KID 0] 0M > [145438] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 200f 011= d 0020 0200 0000 aaaa 0300 0000 0800 4500 0054 7e70 4000 4006 2770 0a00 001= b c346 c762 f69d 0016 1a05 4198 1648 1015 8018 040f 01f8 0000 0101 080a 08a= b 35d4 50c5 6e53 f988 6d22 6676 20bf 51b9 b74c 3fb2 933e 5d5a f972 eec7 754= 5 > 3be7 475c ad3b b052 > [145438] wlan0: link state changed to DOWN > [145440] wlan0: link state changed to UP > [145450] wlan0: link state changed to DOWN > [145452] wlan0: link state changed to UP > [145505] wlan0: link state changed to DOWN > [145507] wlan0: link state changed to UP > [145517] wlan0: link state changed to DOWN > [145519] wlan0: link state changed to UP > [147013] wlan0: link state changed to DOWN > [147015] wlan0: link state changed to UP > [147025] wlan0: link state changed to DOWN > [147028] wlan0: link state changed to UP > [154244] wlan0: link state changed to DOWN > [154246] wlan0: link state changed to UP > [155821] ath0: bb hang detected (0x4), resetting > [175886] wlan0: link state changed to DOWN > [175889] wlan0: link state changed to UP > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b41ff0: addbaw= =3D0, dobaw=3D0, seqno=3D0, retry=3D0 > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b41ff0: tid tx= q_depth=3D1 hwq_depth=3D0, bar_wait=3D0 > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=3D2, = txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, baw_h= ead=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D40661 > [177174] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) pro= be_req 0M > [177174] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 40ed 000= 3 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 000= 0 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c > [177174] wlan0: link state changed to DOWN > [177176] wlan0: link state changed to UP > [177186] wlan0: link state changed to DOWN > [177188] wlan0: link state changed to UP > [177375] wlan0: link state changed to DOWN > [177378] wlan0: link state changed to UP > [177388] wlan0: link state changed to DOWN > [177390] wlan0: link state changed to UP > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b39d20: addbaw= =3D0, dobaw=3D0, seqno=3D2062, retry=3D0 > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b39d20: tid tx= q_depth=3D13 hwq_depth=3D0, bar_wait=3D0 > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=3D2, = txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, baw_h= ead=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D47131 > [179397] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) dat= a WEP [IV 0b b8 00 05 00 00 KID 0] 0M > [179397] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 e080 0bb= 8 0020 0500 0000 aaaa 0300 0000 0800 4500 0034 1535 4000 4006 90cb 0a00 001= b c346 c762 f65f 0014 b6aa cfc8 46ad 84ba 8010 03fc e360 0000 0101 080a 428= d 489d f0d1 3651 > [179399] wlan0: link state changed to UP > [179409] wlan0: link state changed to DOWN > [179411] wlan0: link state changed to UP > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=3D0xc4b355f0: addbaw= =3D0, dobaw=3D0, seqno=3D948, retry=3D0 > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=3D0xc4b355f0: tid tx= q_depth=3D4 hwq_depth=3D0, bar_wait=3D0 > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: tid 16: txq_depth=3D2, = txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, baw_h= ead=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D41912 > [179636] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) dat= a WEP [IV b1 a3 00 00 00 00 KID 0] 0M > [179636] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 403b b1a= 3 0020 0000 0000 aaaa 0300 0000 0800 4500 0034 bb4b 4000 4006 eab4 0a00 001= b c346 c762 b0cc 0014 5ba9 9748 1033 a13f 8010 03fc 39f3 0000 0101 080a f0d= 2 a239 f0d4 cae3 > [179636] wlan0: link state changed to DOWN > [179638] wlan0: link state changed to UP > [179648] wlan0: link state changed to DOWN > [179650] wlan0: link state changed to UP > [180075] wlan0: link state changed to DOWN > [180077] wlan0: link state changed to UP > [180087] wlan0: link state changed to DOWN > [180089] wlan0: link state changed to UP > [180486] wlan0: link state changed to DOWN > [180488] wlan0: link state changed to UP > [180498] wlan0: link state changed to DOWN > [180500] wlan0: link state changed to UP > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b41bb0: addbaw= =3D0, dobaw=3D0, seqno=3D0, retry=3D0 > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b41bb0: tid tx= q_depth=3D1 hwq_depth=3D0, bar_wait=3D0 > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=3D2, = txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, baw_h= ead=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D58839 > [181165] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) pro= be_req 0M > [181165] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 605d 000= 3 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 000= 0 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c > [181165] wlan0: link state changed to DOWN > [181166] Aug 19 01:11:18 notebook kernel: [181165] wlan0: link state chan= ged to DOWN > [181168] wlan0: link state changed to UP > [181168] Aug 19 01:11:20 notebook kernel: [181168] wlan0: link state chan= ged to UP > [181178] wlan0: link state changed to DOWN > [181178] Aug 19 01:11:30 notebook kernel: [181178] wlan0: link state chan= ged to DOWN > [181180] wlan0: link state changed to UP > [181612] wlan0: link state changed to DOWN > [181614] wlan0: link state changed to UP > [181624] wlan0: link state changed to DOWN > [181626] wlan0: link state changed to UP > [190739] wlan0: link state changed to DOWN > [190741] wlan0: link state changed to UP > [190751] wlan0: link state changed to DOWN > [190754] wlan0: link state changed to UP > [194052] ath0: device timeout > [202568] ath0: device timeout > [205182] wlan0: link state changed to DOWN > [205184] wlan0: link state changed to UP > [214975] ath0: bb hang detected (0x4), resetting > [216007] wlan0: link state changed to DOWN > [216009] wlan0: link state changed to UP From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 19 07:20:31 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 376241065673; Sun, 19 Aug 2012 07:20:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id BDA918FC0A; Sun, 19 Aug 2012 07:20:30 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T2zqY-000IId-Sy; Sun, 19 Aug 2012 11:22:54 +0400 Date: Sun, 19 Aug 2012 11:22:54 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Message-ID: <20120819072254.GG98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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: Sun, 19 Aug 2012 07:20:31 -0000 On Sun, Aug 19, 2012 at 12:12:20AM -0700, Adrian Chadd wrote: > I don't see this kind of behaviour in STA mode. What are you associating to? > > What channel is it on? # ifconfig -v wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:11:95:ca:ae:7c 1 6 11M 19.5 0 3125 54960 EPS AE SSID RATES DSPARMS<6> TIM<050400010000> RSN WPA ERP<0x0> XRATES<48,72,96,108> > Adrian > > > On 19 August 2012 00:14, Slawa Olhovchenkov wrote: > > ... and still works bad as client: > > > > [138084] ath0: mem 0xb0200000-0xb020ffff irq 18 at device 5.0 on pci6 > > [138085] ath0: DMA setup: legacy > > [138085] ath0: [HT] enabling HT modes > > [138085] ath0: [HT] 2 RX streams; 2 TX streams > > [138085] ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > [138085] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > > [138085] ath0: 2T2R > > [138085] ath0: 11ng MCS 20MHz > > [138085] ath0: MCS 0-7: 6.5Mbps - 65Mbps > > [138085] ath0: MCS 8-15: 13Mbps - 130Mbps > > [138085] ath0: 11ng MCS 40MHz: > > [138085] ath0: MCS 0-7: 13.5Mbps - 135Mbps > > [138085] ath0: MCS 8-15: 27Mbps - 270Mbps > > [138085] ath0: 11ng MCS 40MHz SGI: > > [138085] ath0: MCS 0-7: 15Mbps - 150Mbps > > [138085] ath0: MCS 8-15: 30Mbps - 300Mbps > > [138085] ath0: AR9220 mac 128.2 RF5133 phy 13.0 > > [138085] ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > [138085] ath0: Use hw queue 1 for WME_AC_BE traffic > > [138085] ath0: Use hw queue 0 for WME_AC_BK traffic > > [138085] ath0: Use hw queue 2 for WME_AC_VI traffic > > [138085] ath0: Use hw queue 3 for WME_AC_VO traffic > > [138085] ath0: Use hw queue 8 for CAB traffic > > [138085] ath0: Use hw queue 9 for beacons > > [138085] ath0: using multicast key search > > [138086] wlan0: bpf attached > > [138086] wlan0: bpf attached > > [138086] wlan0: Ethernet address: f4:ec:38:a3:10:dc > > [138088] wlan0: link state changed to UP > > [138088] Aug 18 13:13:20 notebook kernel: [138088] wlan0: link state changed to UP > > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=0xc4b2cdf0: addbaw=0, dobaw=0, seqno=242, retry=0 > > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=0xc4b2cdf0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=16627 > > [145438] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV 01 1d 00 02 00 00 KID 0] 0M > > [145438] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 200f 011d 0020 0200 0000 aaaa 0300 0000 0800 4500 0054 7e70 4000 4006 2770 0a00 001b c346 c762 f69d 0016 1a05 4198 1648 1015 8018 040f 01f8 0000 0101 080a 08ab 35d4 50c5 6e53 f988 6d22 6676 20bf 51b9 b74c 3fb2 933e 5d5a f972 eec7 7545 > > 3be7 475c ad3b b052 > > [145438] wlan0: link state changed to DOWN > > [145440] wlan0: link state changed to UP > > [145450] wlan0: link state changed to DOWN > > [145452] wlan0: link state changed to UP > > [145505] wlan0: link state changed to DOWN > > [145507] wlan0: link state changed to UP > > [145517] wlan0: link state changed to DOWN > > [145519] wlan0: link state changed to UP > > [147013] wlan0: link state changed to DOWN > > [147015] wlan0: link state changed to UP > > [147025] wlan0: link state changed to DOWN > > [147028] wlan0: link state changed to UP > > [154244] wlan0: link state changed to DOWN > > [154246] wlan0: link state changed to UP > > [155821] ath0: bb hang detected (0x4), resetting > > [175886] wlan0: link state changed to DOWN > > [175889] wlan0: link state changed to UP > > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41ff0: addbaw=0, dobaw=0, seqno=0, retry=0 > > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41ff0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=40661 > > [177174] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) probe_req 0M > > [177174] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 40ed 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c > > [177174] wlan0: link state changed to DOWN > > [177176] wlan0: link state changed to UP > > [177186] wlan0: link state changed to DOWN > > [177188] wlan0: link state changed to UP > > [177375] wlan0: link state changed to DOWN > > [177378] wlan0: link state changed to UP > > [177388] wlan0: link state changed to DOWN > > [177390] wlan0: link state changed to UP > > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b39d20: addbaw=0, dobaw=0, seqno=2062, retry=0 > > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b39d20: tid txq_depth=13 hwq_depth=0, bar_wait=0 > > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=47131 > > [179397] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV 0b b8 00 05 00 00 KID 0] 0M > > [179397] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 e080 0bb8 0020 0500 0000 aaaa 0300 0000 0800 4500 0034 1535 4000 4006 90cb 0a00 001b c346 c762 f65f 0014 b6aa cfc8 46ad 84ba 8010 03fc e360 0000 0101 080a 428d 489d f0d1 3651 > > [179399] wlan0: link state changed to UP > > [179409] wlan0: link state changed to DOWN > > [179411] wlan0: link state changed to UP > > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=0xc4b355f0: addbaw=0, dobaw=0, seqno=948, retry=0 > > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=0xc4b355f0: tid txq_depth=4 hwq_depth=0, bar_wait=0 > > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=41912 > > [179636] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV b1 a3 00 00 00 00 KID 0] 0M > > [179636] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 403b b1a3 0020 0000 0000 aaaa 0300 0000 0800 4500 0034 bb4b 4000 4006 eab4 0a00 001b c346 c762 b0cc 0014 5ba9 9748 1033 a13f 8010 03fc 39f3 0000 0101 080a f0d2 a239 f0d4 cae3 > > [179636] wlan0: link state changed to DOWN > > [179638] wlan0: link state changed to UP > > [179648] wlan0: link state changed to DOWN > > [179650] wlan0: link state changed to UP > > [180075] wlan0: link state changed to DOWN > > [180077] wlan0: link state changed to UP > > [180087] wlan0: link state changed to DOWN > > [180089] wlan0: link state changed to UP > > [180486] wlan0: link state changed to DOWN > > [180488] wlan0: link state changed to UP > > [180498] wlan0: link state changed to DOWN > > [180500] wlan0: link state changed to UP > > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41bb0: addbaw=0, dobaw=0, seqno=0, retry=0 > > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41bb0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=58839 > > [181165] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) probe_req 0M > > [181165] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 605d 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c > > [181165] wlan0: link state changed to DOWN > > [181166] Aug 19 01:11:18 notebook kernel: [181165] wlan0: link state changed to DOWN > > [181168] wlan0: link state changed to UP > > [181168] Aug 19 01:11:20 notebook kernel: [181168] wlan0: link state changed to UP > > [181178] wlan0: link state changed to DOWN > > [181178] Aug 19 01:11:30 notebook kernel: [181178] wlan0: link state changed to DOWN > > [181180] wlan0: link state changed to UP > > [181612] wlan0: link state changed to DOWN > > [181614] wlan0: link state changed to UP > > [181624] wlan0: link state changed to DOWN > > [181626] wlan0: link state changed to UP > > [190739] wlan0: link state changed to DOWN > > [190741] wlan0: link state changed to UP > > [190751] wlan0: link state changed to DOWN > > [190754] wlan0: link state changed to UP > > [194052] ath0: device timeout > > [202568] ath0: device timeout > > [205182] wlan0: link state changed to DOWN > > [205184] wlan0: link state changed to UP > > [214975] ath0: bb hang detected (0x4), resetting > > [216007] wlan0: link state changed to DOWN > > [216009] wlan0: link state changed to UP From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 19 07:26: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 BE780106566B for ; Sun, 19 Aug 2012 07:26:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8E8AF8FC0A for ; Sun, 19 Aug 2012 07:26:51 +0000 (UTC) Received: by dadr6 with SMTP id r6so1634364dad.13 for ; Sun, 19 Aug 2012 00:26:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=N10Udeaew/wkYE5NOianu/iNT2frKpgoyuXV61zkhTo=; b=KvUtCWlfyXvRqFOKHfUrBTFclwIy2/ANLQFlR2WuvWs82vl3lk89lxIKJJX/m7NCD/ 0NgBdSUjZZ6ttbdfOSnVpfuQ8K/0EIQODpApJkvL7lesYUDCuLRtS95IrjwEp3JHgtpv BHzvHjsAD6ccT78iRH8etxLTq3c3WD1nbzjs4RSXXqAEq8leRGojVgorL0Q6lT/yiTXi hxck/vdhqHEm2OhgzvUxLMse+GyJIq2ersuQH8XqQ0MvCgONS7XIMOTl1ArF40atLf/3 KXWLSV/Y9dWBXxrdGharVAFULiN0dbKEErBdvz+4I5pbjeFRIxRVtbXZPtCWtcjgE1Vm Qtsg== MIME-Version: 1.0 Received: by 10.68.238.74 with SMTP id vi10mr2620137pbc.48.1345361210841; Sun, 19 Aug 2012 00:26:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Sun, 19 Aug 2012 00:26:50 -0700 (PDT) In-Reply-To: <20120819072254.GG98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120819072254.GG98910@zxy.spb.ru> Date: Sun, 19 Aug 2012 00:26:50 -0700 X-Google-Sender-Auth: IJf9jbAMfCk6OgK5PuQg0SOOPOg Message-ID: From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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: Sun, 19 Aug 2012 07:26:51 -0000 run athsurvey, see how busy the channel is? Adrian On 19 August 2012 00:22, Slawa Olhovchenkov wrote: > On Sun, Aug 19, 2012 at 12:12:20AM -0700, Adrian Chadd wrote: > >> I don't see this kind of behaviour in STA mode. What are you associating= to? >> >> What channel is it on? > > # ifconfig -v wlan0 list sta > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 00:11:95:ca:ae:7c 1 6 11M 19.5 0 3125 54960 EPS AE SSID R= ATES DSPARMS<6> TIM<050400010000> RSN WPA ERP<0x0> XRATES<48,72,96,108> > > >> Adrian >> >> >> On 19 August 2012 00:14, Slawa Olhovchenkov wrote: >> > ... and still works bad as client: >> > >> > [138084] ath0: mem 0xb0200000-0xb020ffff irq 18 at devi= ce 5.0 on pci6 >> > [138085] ath0: DMA setup: legacy >> > [138085] ath0: [HT] enabling HT modes >> > [138085] ath0: [HT] 2 RX streams; 2 TX streams >> > [138085] ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps >> > [138085] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbp= s 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps >> > [138085] ath0: 2T2R >> > [138085] ath0: 11ng MCS 20MHz >> > [138085] ath0: MCS 0-7: 6.5Mbps - 65Mbps >> > [138085] ath0: MCS 8-15: 13Mbps - 130Mbps >> > [138085] ath0: 11ng MCS 40MHz: >> > [138085] ath0: MCS 0-7: 13.5Mbps - 135Mbps >> > [138085] ath0: MCS 8-15: 27Mbps - 270Mbps >> > [138085] ath0: 11ng MCS 40MHz SGI: >> > [138085] ath0: MCS 0-7: 15Mbps - 150Mbps >> > [138085] ath0: MCS 8-15: 30Mbps - 300Mbps >> > [138085] ath0: AR9220 mac 128.2 RF5133 phy 13.0 >> > [138085] ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >> > [138085] ath0: Use hw queue 1 for WME_AC_BE traffic >> > [138085] ath0: Use hw queue 0 for WME_AC_BK traffic >> > [138085] ath0: Use hw queue 2 for WME_AC_VI traffic >> > [138085] ath0: Use hw queue 3 for WME_AC_VO traffic >> > [138085] ath0: Use hw queue 8 for CAB traffic >> > [138085] ath0: Use hw queue 9 for beacons >> > [138085] ath0: using multicast key search >> > [138086] wlan0: bpf attached >> > [138086] wlan0: bpf attached >> > [138086] wlan0: Ethernet address: f4:ec:38:a3:10:dc >> > [138088] wlan0: link state changed to UP >> > [138088] Aug 18 13:13:20 notebook kernel: [138088] wlan0: link state c= hanged to UP >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=3D0xc4b2cdf0: add= baw=3D0, dobaw=3D0, seqno=3D242, retry=3D0 >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=3D0xc4b2cdf0: tid= txq_depth=3D1 hwq_depth=3D0, bar_wait=3D0 >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: tid 16: txq_depth=3D= 2, txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, ba= w_head=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D16627 >> > [145438] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) = data WEP [IV 01 1d 00 02 00 00 KID 0] 0M >> > [145438] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 200f = 011d 0020 0200 0000 aaaa 0300 0000 0800 4500 0054 7e70 4000 4006 2770 0a00 = 001b c346 c762 f69d 0016 1a05 4198 1648 1015 8018 040f 01f8 0000 0101 080a = 08ab 35d4 50c5 6e53 f988 6d22 6676 20bf 51b9 b74c 3fb2 933e 5d5a f972 eec7 = 7545 >> > 3be7 475c ad3b b052 >> > [145438] wlan0: link state changed to DOWN >> > [145440] wlan0: link state changed to UP >> > [145450] wlan0: link state changed to DOWN >> > [145452] wlan0: link state changed to UP >> > [145505] wlan0: link state changed to DOWN >> > [145507] wlan0: link state changed to UP >> > [145517] wlan0: link state changed to DOWN >> > [145519] wlan0: link state changed to UP >> > [147013] wlan0: link state changed to DOWN >> > [147015] wlan0: link state changed to UP >> > [147025] wlan0: link state changed to DOWN >> > [147028] wlan0: link state changed to UP >> > [154244] wlan0: link state changed to DOWN >> > [154246] wlan0: link state changed to UP >> > [155821] ath0: bb hang detected (0x4), resetting >> > [175886] wlan0: link state changed to DOWN >> > [175889] wlan0: link state changed to UP >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b41ff0: add= baw=3D0, dobaw=3D0, seqno=3D0, retry=3D0 >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b41ff0: tid= txq_depth=3D1 hwq_depth=3D0, bar_wait=3D0 >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=3D= 2, txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, ba= w_head=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D40661 >> > [177174] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) = probe_req 0M >> > [177174] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 40ed = 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 = 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 = 6c >> > [177174] wlan0: link state changed to DOWN >> > [177176] wlan0: link state changed to UP >> > [177186] wlan0: link state changed to DOWN >> > [177188] wlan0: link state changed to UP >> > [177375] wlan0: link state changed to DOWN >> > [177378] wlan0: link state changed to UP >> > [177388] wlan0: link state changed to DOWN >> > [177390] wlan0: link state changed to UP >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b39d20: add= baw=3D0, dobaw=3D0, seqno=3D2062, retry=3D0 >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b39d20: tid= txq_depth=3D13 hwq_depth=3D0, bar_wait=3D0 >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=3D= 2, txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, ba= w_head=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D47131 >> > [179397] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) = data WEP [IV 0b b8 00 05 00 00 KID 0] 0M >> > [179397] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 e080 = 0bb8 0020 0500 0000 aaaa 0300 0000 0800 4500 0034 1535 4000 4006 90cb 0a00 = 001b c346 c762 f65f 0014 b6aa cfc8 46ad 84ba 8010 03fc e360 0000 0101 080a = 428d 489d f0d1 3651 >> > [179399] wlan0: link state changed to UP >> > [179409] wlan0: link state changed to DOWN >> > [179411] wlan0: link state changed to UP >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=3D0xc4b355f0: add= baw=3D0, dobaw=3D0, seqno=3D948, retry=3D0 >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=3D0xc4b355f0: tid= txq_depth=3D4 hwq_depth=3D0, bar_wait=3D0 >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: tid 16: txq_depth=3D= 2, txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, ba= w_head=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D41912 >> > [179636] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) = data WEP [IV b1 a3 00 00 00 00 KID 0] 0M >> > [179636] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 403b = b1a3 0020 0000 0000 aaaa 0300 0000 0800 4500 0034 bb4b 4000 4006 eab4 0a00 = 001b c346 c762 b0cc 0014 5ba9 9748 1033 a13f 8010 03fc 39f3 0000 0101 080a = f0d2 a239 f0d4 cae3 >> > [179636] wlan0: link state changed to DOWN >> > [179638] wlan0: link state changed to UP >> > [179648] wlan0: link state changed to DOWN >> > [179650] wlan0: link state changed to UP >> > [180075] wlan0: link state changed to DOWN >> > [180077] wlan0: link state changed to UP >> > [180087] wlan0: link state changed to DOWN >> > [180089] wlan0: link state changed to UP >> > [180486] wlan0: link state changed to DOWN >> > [180488] wlan0: link state changed to UP >> > [180498] wlan0: link state changed to DOWN >> > [180500] wlan0: link state changed to UP >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b41bb0: add= baw=3D0, dobaw=3D0, seqno=3D0, retry=3D0 >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=3D0xc4b41bb0: tid= txq_depth=3D1 hwq_depth=3D0, bar_wait=3D0 >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=3D= 2, txq_aggr_depth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, ba= w_head=3D0, baw_tail=3D0 txa_start=3D-1, ni_txseqs=3D58839 >> > [181165] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) = probe_req 0M >> > [181165] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 605d = 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 = 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 = 6c >> > [181165] wlan0: link state changed to DOWN >> > [181166] Aug 19 01:11:18 notebook kernel: [181165] wlan0: link state c= hanged to DOWN >> > [181168] wlan0: link state changed to UP >> > [181168] Aug 19 01:11:20 notebook kernel: [181168] wlan0: link state c= hanged to UP >> > [181178] wlan0: link state changed to DOWN >> > [181178] Aug 19 01:11:30 notebook kernel: [181178] wlan0: link state c= hanged to DOWN >> > [181180] wlan0: link state changed to UP >> > [181612] wlan0: link state changed to DOWN >> > [181614] wlan0: link state changed to UP >> > [181624] wlan0: link state changed to DOWN >> > [181626] wlan0: link state changed to UP >> > [190739] wlan0: link state changed to DOWN >> > [190741] wlan0: link state changed to UP >> > [190751] wlan0: link state changed to DOWN >> > [190754] wlan0: link state changed to UP >> > [194052] ath0: device timeout >> > [202568] ath0: device timeout >> > [205182] wlan0: link state changed to DOWN >> > [205184] wlan0: link state changed to UP >> > [214975] ath0: bb hang detected (0x4), resetting >> > [216007] wlan0: link state changed to DOWN >> > [216009] wlan0: link state changed to UP From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 19 07:30: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 0FCC2106564A; Sun, 19 Aug 2012 07:30:24 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 58F2E8FC0A; Sun, 19 Aug 2012 07:30:23 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3007-000IM5-9I; Sun, 19 Aug 2012 11:32:47 +0400 Date: Sun, 19 Aug 2012 11:32:47 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Message-ID: <20120819073247.GH98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120819072254.GG98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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: Sun, 19 Aug 2012 07:30:24 -0000 On Sun, Aug 19, 2012 at 12:26:50AM -0700, Adrian Chadd wrote: > run athsurvey, see how busy the channel is? I don't know how run athsurvey to correlation with message log, currently: min avg max tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% ( 0.0 8.3 9.1 83.5) ( 0.0 10.5 12.1 87.9) ( 0.4 13.8 16.5 90.9) ( 0.0 8.3 9.1 83.5) ( 0.0 10.9 12.8 87.2) ( 0.4 13.8 16.5 90.9) ( 0.0 8.3 9.1 80.4) ( 0.0 11.5 13.6 86.3) ( 0.4 16.0 19.6 90.9) ( 0.0 9.2 10.8 80.4) ( 0.0 11.3 13.4 86.6) ( 0.4 16.0 19.6 89.2) ( 0.0 6.1 6.8 80.4) ( 0.0 10.6 12.2 87.8) ( 0.0 16.0 19.6 93.2) ( 0.0 6.1 6.8 80.4) ( 0.0 9.9 11.3 88.7) ( 0.0 15.8 19.6 93.2) ( 0.0 6.1 6.8 76.7) ( 0.0 10.3 12.0 88.0) ( 0.2 18.1 23.3 93.2) ( 0.0 6.1 6.8 76.7) ( 0.0 10.5 12.5 87.5) ( 0.4 18.1 23.3 93.2) ( 0.0 7.8 9.9 76.7) ( 0.1 10.9 13.0 87.0) ( 0.6 18.1 23.3 90.1) ( 0.0 7.8 9.9 72.1) ( 0.1 12.1 14.1 85.8) ( 0.9 25.4 27.9 90.1) ( 0.0 8.8 9.9 72.1) ( 0.1 13.0 15.2 84.8) ( 0.9 25.4 27.9 90.1) ( 0.0 6.5 7.0 72.1) ( 0.1 13.0 15.1 84.9) ( 0.9 25.4 27.9 93.0) ( 0.0 6.5 7.0 72.6) ( 0.1 12.3 14.3 85.7) ( 0.4 23.2 27.4 93.0) ( 0.0 6.5 7.0 78.1) ( 0.1 11.7 13.7 86.3) ( 0.4 19.1 21.9 93.0) ( 0.0 7.9 9.3 78.1) ( 0.1 11.6 13.7 86.2) ( 0.4 19.1 21.9 90.7) ( 0.0 7.9 9.3 78.1) ( 0.1 11.1 13.1 86.9) ( 0.4 19.1 21.9 90.7) ( 0.0 7.9 9.3 80.2) ( 0.1 10.9 12.8 87.2) ( 0.4 16.4 19.8 90.7) ( 0.0 8.1 9.4 79.2) ( 0.1 11.9 13.9 86.1) ( 0.4 19.3 20.8 90.5) ( 0.0 9.6 11.1 78.2) ( 0.0 12.8 15.1 84.9) ( 0.4 19.3 21.8 88.9) ( 0.0 9.6 10.8 67.2) ( 0.1 13.8 16.3 83.7) ( 0.5 29.9 32.8 89.2) ( 0.0 8.7 9.2 67.2) ( 0.1 12.6 14.6 85.4) ( 0.5 29.9 32.8 90.8) ( 0.0 8.7 9.2 67.2) ( 0.1 11.6 13.3 86.7) ( 0.5 29.9 32.8 90.8) ( 0.0 8.1 9.2 86.0) ( 0.1 10.2 11.6 88.4) ( 0.5 12.1 14.0 90.8) min avg max tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% ( 0.0 8.1 9.2 83.7) ( 0.1 10.6 12.2 87.8) ( 0.4 14.5 16.3 90.8) ( 0.0 7.1 7.7 83.7) ( 0.1 10.3 11.9 88.1) ( 0.4 14.6 16.3 92.3) ( 0.0 7.1 7.7 83.7) ( 0.1 10.3 11.8 88.1) ( 0.4 14.6 16.3 92.3) ( 0.0 7.1 7.7 83.9) ( 0.1 9.9 11.3 88.7) ( 1.4 14.6 16.1 92.3) ( 0.0 7.1 7.7 79.1) ( 0.1 11.0 12.6 87.4) ( 1.4 19.3 20.9 92.3) ( 0.0 7.3 8.3 79.1) ( 0.1 11.2 12.8 87.2) ( 1.4 19.3 20.9 91.7) ( 0.0 7.3 8.3 79.1) ( 0.1 11.6 13.5 86.5) ( 0.5 19.3 20.9 91.7) ( 0.0 7.3 8.3 72.7) ( 0.1 12.1 14.4 85.6) ( 0.5 22.3 27.3 91.7) ( 0.0 7.9 8.6 72.7) ( 0.1 13.0 15.6 84.4) ( 0.5 22.3 27.3 91.4) ( 0.0 9.7 12.1 72.7) ( 0.1 13.7 16.5 83.5) ( 0.3 22.3 27.3 87.9) ( 0.0 9.7 11.7 72.7) ( 0.1 13.6 16.4 83.6) ( 0.4 22.3 27.3 88.3) ( 0.0 9.7 11.4 77.6) ( 0.1 13.0 15.6 84.3) ( 0.4 17.1 22.4 88.6) ( 0.0 8.6 10.4 77.6) ( 0.1 12.4 14.9 85.1) ( 0.4 17.1 22.4 89.6) ( 0.0 7.9 8.9 78.5) ( 0.1 11.6 13.7 86.3) ( 0.4 17.1 21.5 91.1) ( 0.0 5.9 6.4 78.5) ( 0.0 10.4 12.2 87.8) ( 0.4 17.1 21.5 93.6) ( 0.0 5.9 6.4 78.5) ( 0.0 10.5 12.2 87.7) ( 0.0 17.1 21.5 93.6) ( 0.0 5.9 6.4 81.1) ( 0.0 9.7 11.1 88.9) ( 0.0 14.4 18.9 93.6) ( 0.0 6.1 6.6 81.1) ( 0.0 10.0 11.3 88.7) ( 0.0 14.4 18.9 93.4) ( 0.0 6.1 6.6 82.5) ( 0.0 9.8 11.0 89.0) ( 0.0 14.7 17.5 93.4) ( 0.0 7.5 7.8 82.5) ( 0.0 10.9 12.5 87.4) ( 0.0 14.7 17.5 92.2) ( 0.0 9.1 11.2 77.0) ( 0.0 11.8 13.9 86.0) ( 0.0 19.3 23.0 88.8) > Adrian > > > On 19 August 2012 00:22, Slawa Olhovchenkov wrote: > > On Sun, Aug 19, 2012 at 12:12:20AM -0700, Adrian Chadd wrote: > > > >> I don't see this kind of behaviour in STA mode. What are you associating to? > >> > >> What channel is it on? > > > > # ifconfig -v wlan0 list sta > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:11:95:ca:ae:7c 1 6 11M 19.5 0 3125 54960 EPS AE SSID RATES DSPARMS<6> TIM<050400010000> RSN WPA ERP<0x0> XRATES<48,72,96,108> > > > > > >> Adrian > >> > >> > >> On 19 August 2012 00:14, Slawa Olhovchenkov wrote: > >> > ... and still works bad as client: > >> > > >> > [138084] ath0: mem 0xb0200000-0xb020ffff irq 18 at device 5.0 on pci6 > >> > [138085] ath0: DMA setup: legacy > >> > [138085] ath0: [HT] enabling HT modes > >> > [138085] ath0: [HT] 2 RX streams; 2 TX streams > >> > [138085] ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > >> > [138085] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > >> > [138085] ath0: 2T2R > >> > [138085] ath0: 11ng MCS 20MHz > >> > [138085] ath0: MCS 0-7: 6.5Mbps - 65Mbps > >> > [138085] ath0: MCS 8-15: 13Mbps - 130Mbps > >> > [138085] ath0: 11ng MCS 40MHz: > >> > [138085] ath0: MCS 0-7: 13.5Mbps - 135Mbps > >> > [138085] ath0: MCS 8-15: 27Mbps - 270Mbps > >> > [138085] ath0: 11ng MCS 40MHz SGI: > >> > [138085] ath0: MCS 0-7: 15Mbps - 150Mbps > >> > [138085] ath0: MCS 8-15: 30Mbps - 300Mbps > >> > [138085] ath0: AR9220 mac 128.2 RF5133 phy 13.0 > >> > [138085] ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > >> > [138085] ath0: Use hw queue 1 for WME_AC_BE traffic > >> > [138085] ath0: Use hw queue 0 for WME_AC_BK traffic > >> > [138085] ath0: Use hw queue 2 for WME_AC_VI traffic > >> > [138085] ath0: Use hw queue 3 for WME_AC_VO traffic > >> > [138085] ath0: Use hw queue 8 for CAB traffic > >> > [138085] ath0: Use hw queue 9 for beacons > >> > [138085] ath0: using multicast key search > >> > [138086] wlan0: bpf attached > >> > [138086] wlan0: bpf attached > >> > [138086] wlan0: Ethernet address: f4:ec:38:a3:10:dc > >> > [138088] wlan0: link state changed to UP > >> > [138088] Aug 18 13:13:20 notebook kernel: [138088] wlan0: link state changed to UP > >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=0xc4b2cdf0: addbaw=0, dobaw=0, seqno=242, retry=0 > >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=0xc4b2cdf0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=16627 > >> > [145438] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV 01 1d 00 02 00 00 KID 0] 0M > >> > [145438] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 200f 011d 0020 0200 0000 aaaa 0300 0000 0800 4500 0054 7e70 4000 4006 2770 0a00 001b c346 c762 f69d 0016 1a05 4198 1648 1015 8018 040f 01f8 0000 0101 080a 08ab 35d4 50c5 6e53 f988 6d22 6676 20bf 51b9 b74c 3fb2 933e 5d5a f972 eec7 7545 > >> > 3be7 475c ad3b b052 > >> > [145438] wlan0: link state changed to DOWN > >> > [145440] wlan0: link state changed to UP > >> > [145450] wlan0: link state changed to DOWN > >> > [145452] wlan0: link state changed to UP > >> > [145505] wlan0: link state changed to DOWN > >> > [145507] wlan0: link state changed to UP > >> > [145517] wlan0: link state changed to DOWN > >> > [145519] wlan0: link state changed to UP > >> > [147013] wlan0: link state changed to DOWN > >> > [147015] wlan0: link state changed to UP > >> > [147025] wlan0: link state changed to DOWN > >> > [147028] wlan0: link state changed to UP > >> > [154244] wlan0: link state changed to DOWN > >> > [154246] wlan0: link state changed to UP > >> > [155821] ath0: bb hang detected (0x4), resetting > >> > [175886] wlan0: link state changed to DOWN > >> > [175889] wlan0: link state changed to UP > >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41ff0: addbaw=0, dobaw=0, seqno=0, retry=0 > >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41ff0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=40661 > >> > [177174] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) probe_req 0M > >> > [177174] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 40ed 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c > >> > [177174] wlan0: link state changed to DOWN > >> > [177176] wlan0: link state changed to UP > >> > [177186] wlan0: link state changed to DOWN > >> > [177188] wlan0: link state changed to UP > >> > [177375] wlan0: link state changed to DOWN > >> > [177378] wlan0: link state changed to UP > >> > [177388] wlan0: link state changed to DOWN > >> > [177390] wlan0: link state changed to UP > >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b39d20: addbaw=0, dobaw=0, seqno=2062, retry=0 > >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b39d20: tid txq_depth=13 hwq_depth=0, bar_wait=0 > >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=47131 > >> > [179397] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV 0b b8 00 05 00 00 KID 0] 0M > >> > [179397] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 e080 0bb8 0020 0500 0000 aaaa 0300 0000 0800 4500 0034 1535 4000 4006 90cb 0a00 001b c346 c762 f65f 0014 b6aa cfc8 46ad 84ba 8010 03fc e360 0000 0101 080a 428d 489d f0d1 3651 > >> > [179399] wlan0: link state changed to UP > >> > [179409] wlan0: link state changed to DOWN > >> > [179411] wlan0: link state changed to UP > >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=0xc4b355f0: addbaw=0, dobaw=0, seqno=948, retry=0 > >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=0xc4b355f0: tid txq_depth=4 hwq_depth=0, bar_wait=0 > >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=41912 > >> > [179636] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV b1 a3 00 00 00 00 KID 0] 0M > >> > [179636] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 403b b1a3 0020 0000 0000 aaaa 0300 0000 0800 4500 0034 bb4b 4000 4006 eab4 0a00 001b c346 c762 b0cc 0014 5ba9 9748 1033 a13f 8010 03fc 39f3 0000 0101 080a f0d2 a239 f0d4 cae3 > >> > [179636] wlan0: link state changed to DOWN > >> > [179638] wlan0: link state changed to UP > >> > [179648] wlan0: link state changed to DOWN > >> > [179650] wlan0: link state changed to UP > >> > [180075] wlan0: link state changed to DOWN > >> > [180077] wlan0: link state changed to UP > >> > [180087] wlan0: link state changed to DOWN > >> > [180089] wlan0: link state changed to UP > >> > [180486] wlan0: link state changed to DOWN > >> > [180488] wlan0: link state changed to UP > >> > [180498] wlan0: link state changed to DOWN > >> > [180500] wlan0: link state changed to UP > >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41bb0: addbaw=0, dobaw=0, seqno=0, retry=0 > >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41bb0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=58839 > >> > [181165] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) probe_req 0M > >> > [181165] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 605d 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c > >> > [181165] wlan0: link state changed to DOWN > >> > [181166] Aug 19 01:11:18 notebook kernel: [181165] wlan0: link state changed to DOWN > >> > [181168] wlan0: link state changed to UP > >> > [181168] Aug 19 01:11:20 notebook kernel: [181168] wlan0: link state changed to UP > >> > [181178] wlan0: link state changed to DOWN > >> > [181178] Aug 19 01:11:30 notebook kernel: [181178] wlan0: link state changed to DOWN > >> > [181180] wlan0: link state changed to UP > >> > [181612] wlan0: link state changed to DOWN > >> > [181614] wlan0: link state changed to UP > >> > [181624] wlan0: link state changed to DOWN > >> > [181626] wlan0: link state changed to UP > >> > [190739] wlan0: link state changed to DOWN > >> > [190741] wlan0: link state changed to UP > >> > [190751] wlan0: link state changed to DOWN > >> > [190754] wlan0: link state changed to UP > >> > [194052] ath0: device timeout > >> > [202568] ath0: device timeout > >> > [205182] wlan0: link state changed to DOWN > >> > [205184] wlan0: link state changed to UP > >> > [214975] ath0: bb hang detected (0x4), resetting > >> > [216007] wlan0: link state changed to DOWN > >> > [216009] wlan0: link state changed to UP From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 19 07:38:56 2012 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 777B4106564A; Sun, 19 Aug 2012 07:38:56 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id C43AF8FC0A; Sun, 19 Aug 2012 07:38:55 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T308N-000IPT-Pk; Sun, 19 Aug 2012 11:41:19 +0400 Date: Sun, 19 Aug 2012 11:41:19 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Message-ID: <20120819074119.GI98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120819072254.GG98910@zxy.spb.ru> <20120819073247.GH98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120819073247.GH98910@zxy.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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: Sun, 19 Aug 2012 07:38:56 -0000 On Sun, Aug 19, 2012 at 11:32:47AM +0400, Slawa Olhovchenkov wrote: > On Sun, Aug 19, 2012 at 12:26:50AM -0700, Adrian Chadd wrote: > > > run athsurvey, see how busy the channel is? > > I don't know how run athsurvey to correlation with message log, > currently: from time to time (~60s): min avg max tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% ( 0.0 7.3 7.9 77.0) ( 0.0 9.7 10.8 89.2) ( 0.0 12.6 23.0 92.1) ( 0.0 7.3 7.7 77.0) ( 0.0 9.4 10.4 89.6) ( 0.0 12.4 23.0 92.3) ( 0.0 7.1 7.4 77.0) ( 0.0 9.1 10.1 89.9) ( 0.0 12.4 23.0 92.6) ( 0.0 7.1 7.4 75.8) ( 0.0 10.1 10.9 89.1) ( 0.0 20.6 24.2 92.6) ( 0.0 7.1 7.4 75.8) ( 0.0 11.5 12.5 87.5) ( 0.0 20.6 24.2 92.6) ( 0.0 7.1 7.4 75.8) ( 0.0 12.7 14.0 1611.2) ( 0.0 20.6 24.2 48893.6) ( 0.0 8.0 8.9 76.3) ( 0.0 12.3 13.7 1611.4) ( 0.0 20.1 23.7 48893.6) ( 0.0 6.4 7.0 79.0) ( 0.0 11.0 12.2 1612.9) ( 0.0 20.1 21.0 48893.6) ( 0.0 6.4 7.0 79.9) ( 0.0 9.5 10.6 89.4) ( 0.2 16.5 20.1 93.0) ( 0.0 6.4 7.0 79.9) ( 0.0 10.1 11.2 88.8) ( 0.2 18.5 20.1 93.0) ( 0.0 6.4 7.0 80.4) ( 0.0 9.8 10.9 89.1) ( 0.2 18.5 19.6 93.0) ( 0.0 6.2 6.7 80.4) ( 0.0 10.0 10.8 89.1) ( 0.0 18.5 19.6 93.3) no messages in console at this time. > min avg max > tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% > ( 0.0 8.3 9.1 83.5) ( 0.0 10.5 12.1 87.9) ( 0.4 13.8 16.5 90.9) > ( 0.0 8.3 9.1 83.5) ( 0.0 10.9 12.8 87.2) ( 0.4 13.8 16.5 90.9) > ( 0.0 8.3 9.1 80.4) ( 0.0 11.5 13.6 86.3) ( 0.4 16.0 19.6 90.9) > ( 0.0 9.2 10.8 80.4) ( 0.0 11.3 13.4 86.6) ( 0.4 16.0 19.6 89.2) > ( 0.0 6.1 6.8 80.4) ( 0.0 10.6 12.2 87.8) ( 0.0 16.0 19.6 93.2) > ( 0.0 6.1 6.8 80.4) ( 0.0 9.9 11.3 88.7) ( 0.0 15.8 19.6 93.2) > ( 0.0 6.1 6.8 76.7) ( 0.0 10.3 12.0 88.0) ( 0.2 18.1 23.3 93.2) > ( 0.0 6.1 6.8 76.7) ( 0.0 10.5 12.5 87.5) ( 0.4 18.1 23.3 93.2) > ( 0.0 7.8 9.9 76.7) ( 0.1 10.9 13.0 87.0) ( 0.6 18.1 23.3 90.1) > ( 0.0 7.8 9.9 72.1) ( 0.1 12.1 14.1 85.8) ( 0.9 25.4 27.9 90.1) > ( 0.0 8.8 9.9 72.1) ( 0.1 13.0 15.2 84.8) ( 0.9 25.4 27.9 90.1) > ( 0.0 6.5 7.0 72.1) ( 0.1 13.0 15.1 84.9) ( 0.9 25.4 27.9 93.0) > ( 0.0 6.5 7.0 72.6) ( 0.1 12.3 14.3 85.7) ( 0.4 23.2 27.4 93.0) > ( 0.0 6.5 7.0 78.1) ( 0.1 11.7 13.7 86.3) ( 0.4 19.1 21.9 93.0) > ( 0.0 7.9 9.3 78.1) ( 0.1 11.6 13.7 86.2) ( 0.4 19.1 21.9 90.7) > ( 0.0 7.9 9.3 78.1) ( 0.1 11.1 13.1 86.9) ( 0.4 19.1 21.9 90.7) > ( 0.0 7.9 9.3 80.2) ( 0.1 10.9 12.8 87.2) ( 0.4 16.4 19.8 90.7) > ( 0.0 8.1 9.4 79.2) ( 0.1 11.9 13.9 86.1) ( 0.4 19.3 20.8 90.5) > ( 0.0 9.6 11.1 78.2) ( 0.0 12.8 15.1 84.9) ( 0.4 19.3 21.8 88.9) > ( 0.0 9.6 10.8 67.2) ( 0.1 13.8 16.3 83.7) ( 0.5 29.9 32.8 89.2) > ( 0.0 8.7 9.2 67.2) ( 0.1 12.6 14.6 85.4) ( 0.5 29.9 32.8 90.8) > ( 0.0 8.7 9.2 67.2) ( 0.1 11.6 13.3 86.7) ( 0.5 29.9 32.8 90.8) > ( 0.0 8.1 9.2 86.0) ( 0.1 10.2 11.6 88.4) ( 0.5 12.1 14.0 90.8) > min avg max > tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% > ( 0.0 8.1 9.2 83.7) ( 0.1 10.6 12.2 87.8) ( 0.4 14.5 16.3 90.8) > ( 0.0 7.1 7.7 83.7) ( 0.1 10.3 11.9 88.1) ( 0.4 14.6 16.3 92.3) > ( 0.0 7.1 7.7 83.7) ( 0.1 10.3 11.8 88.1) ( 0.4 14.6 16.3 92.3) > ( 0.0 7.1 7.7 83.9) ( 0.1 9.9 11.3 88.7) ( 1.4 14.6 16.1 92.3) > ( 0.0 7.1 7.7 79.1) ( 0.1 11.0 12.6 87.4) ( 1.4 19.3 20.9 92.3) > ( 0.0 7.3 8.3 79.1) ( 0.1 11.2 12.8 87.2) ( 1.4 19.3 20.9 91.7) > ( 0.0 7.3 8.3 79.1) ( 0.1 11.6 13.5 86.5) ( 0.5 19.3 20.9 91.7) > ( 0.0 7.3 8.3 72.7) ( 0.1 12.1 14.4 85.6) ( 0.5 22.3 27.3 91.7) > ( 0.0 7.9 8.6 72.7) ( 0.1 13.0 15.6 84.4) ( 0.5 22.3 27.3 91.4) > ( 0.0 9.7 12.1 72.7) ( 0.1 13.7 16.5 83.5) ( 0.3 22.3 27.3 87.9) > ( 0.0 9.7 11.7 72.7) ( 0.1 13.6 16.4 83.6) ( 0.4 22.3 27.3 88.3) > ( 0.0 9.7 11.4 77.6) ( 0.1 13.0 15.6 84.3) ( 0.4 17.1 22.4 88.6) > ( 0.0 8.6 10.4 77.6) ( 0.1 12.4 14.9 85.1) ( 0.4 17.1 22.4 89.6) > ( 0.0 7.9 8.9 78.5) ( 0.1 11.6 13.7 86.3) ( 0.4 17.1 21.5 91.1) > ( 0.0 5.9 6.4 78.5) ( 0.0 10.4 12.2 87.8) ( 0.4 17.1 21.5 93.6) > ( 0.0 5.9 6.4 78.5) ( 0.0 10.5 12.2 87.7) ( 0.0 17.1 21.5 93.6) > ( 0.0 5.9 6.4 81.1) ( 0.0 9.7 11.1 88.9) ( 0.0 14.4 18.9 93.6) > ( 0.0 6.1 6.6 81.1) ( 0.0 10.0 11.3 88.7) ( 0.0 14.4 18.9 93.4) > ( 0.0 6.1 6.6 82.5) ( 0.0 9.8 11.0 89.0) ( 0.0 14.7 17.5 93.4) > ( 0.0 7.5 7.8 82.5) ( 0.0 10.9 12.5 87.4) ( 0.0 14.7 17.5 92.2) > ( 0.0 9.1 11.2 77.0) ( 0.0 11.8 13.9 86.0) ( 0.0 19.3 23.0 88.8) > > > > > Adrian > > > > > > On 19 August 2012 00:22, Slawa Olhovchenkov wrote: > > > On Sun, Aug 19, 2012 at 12:12:20AM -0700, Adrian Chadd wrote: > > > > > >> I don't see this kind of behaviour in STA mode. What are you associating to? > > >> > > >> What channel is it on? > > > > > > # ifconfig -v wlan0 list sta > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > 00:11:95:ca:ae:7c 1 6 11M 19.5 0 3125 54960 EPS AE SSID RATES DSPARMS<6> TIM<050400010000> RSN WPA ERP<0x0> XRATES<48,72,96,108> > > > > > > > > >> Adrian > > >> > > >> > > >> On 19 August 2012 00:14, Slawa Olhovchenkov wrote: > > >> > ... and still works bad as client: > > >> > > > >> > [138084] ath0: mem 0xb0200000-0xb020ffff irq 18 at device 5.0 on pci6 > > >> > [138085] ath0: DMA setup: legacy > > >> > [138085] ath0: [HT] enabling HT modes > > >> > [138085] ath0: [HT] 2 RX streams; 2 TX streams > > >> > [138085] ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > >> > [138085] ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > > >> > [138085] ath0: 2T2R > > >> > [138085] ath0: 11ng MCS 20MHz > > >> > [138085] ath0: MCS 0-7: 6.5Mbps - 65Mbps > > >> > [138085] ath0: MCS 8-15: 13Mbps - 130Mbps > > >> > [138085] ath0: 11ng MCS 40MHz: > > >> > [138085] ath0: MCS 0-7: 13.5Mbps - 135Mbps > > >> > [138085] ath0: MCS 8-15: 27Mbps - 270Mbps > > >> > [138085] ath0: 11ng MCS 40MHz SGI: > > >> > [138085] ath0: MCS 0-7: 15Mbps - 150Mbps > > >> > [138085] ath0: MCS 8-15: 30Mbps - 300Mbps > > >> > [138085] ath0: AR9220 mac 128.2 RF5133 phy 13.0 > > >> > [138085] ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > >> > [138085] ath0: Use hw queue 1 for WME_AC_BE traffic > > >> > [138085] ath0: Use hw queue 0 for WME_AC_BK traffic > > >> > [138085] ath0: Use hw queue 2 for WME_AC_VI traffic > > >> > [138085] ath0: Use hw queue 3 for WME_AC_VO traffic > > >> > [138085] ath0: Use hw queue 8 for CAB traffic > > >> > [138085] ath0: Use hw queue 9 for beacons > > >> > [138085] ath0: using multicast key search > > >> > [138086] wlan0: bpf attached > > >> > [138086] wlan0: bpf attached > > >> > [138086] wlan0: Ethernet address: f4:ec:38:a3:10:dc > > >> > [138088] wlan0: link state changed to UP > > >> > [138088] Aug 18 13:13:20 notebook kernel: [138088] wlan0: link state changed to UP > > >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=0xc4b2cdf0: addbaw=0, dobaw=0, seqno=242, retry=0 > > >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: bf=0xc4b2cdf0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > > >> > [145438] ath0: ath_tx_tid_drain: node 0xc4b4a000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=16627 > > >> > [145438] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV 01 1d 00 02 00 00 KID 0] 0M > > >> > [145438] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 200f 011d 0020 0200 0000 aaaa 0300 0000 0800 4500 0054 7e70 4000 4006 2770 0a00 001b c346 c762 f69d 0016 1a05 4198 1648 1015 8018 040f 01f8 0000 0101 080a 08ab 35d4 50c5 6e53 f988 6d22 6676 20bf 51b9 b74c 3fb2 933e 5d5a f972 eec7 7545 > > >> > 3be7 475c ad3b b052 > > >> > [145438] wlan0: link state changed to DOWN > > >> > [145440] wlan0: link state changed to UP > > >> > [145450] wlan0: link state changed to DOWN > > >> > [145452] wlan0: link state changed to UP > > >> > [145505] wlan0: link state changed to DOWN > > >> > [145507] wlan0: link state changed to UP > > >> > [145517] wlan0: link state changed to DOWN > > >> > [145519] wlan0: link state changed to UP > > >> > [147013] wlan0: link state changed to DOWN > > >> > [147015] wlan0: link state changed to UP > > >> > [147025] wlan0: link state changed to DOWN > > >> > [147028] wlan0: link state changed to UP > > >> > [154244] wlan0: link state changed to DOWN > > >> > [154246] wlan0: link state changed to UP > > >> > [155821] ath0: bb hang detected (0x4), resetting > > >> > [175886] wlan0: link state changed to DOWN > > >> > [175889] wlan0: link state changed to UP > > >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41ff0: addbaw=0, dobaw=0, seqno=0, retry=0 > > >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41ff0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > > >> > [177174] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=40661 > > >> > [177174] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) probe_req 0M > > >> > [177174] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 40ed 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c > > >> > [177174] wlan0: link state changed to DOWN > > >> > [177176] wlan0: link state changed to UP > > >> > [177186] wlan0: link state changed to DOWN > > >> > [177188] wlan0: link state changed to UP > > >> > [177375] wlan0: link state changed to DOWN > > >> > [177378] wlan0: link state changed to UP > > >> > [177388] wlan0: link state changed to DOWN > > >> > [177390] wlan0: link state changed to UP > > >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b39d20: addbaw=0, dobaw=0, seqno=2062, retry=0 > > >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b39d20: tid txq_depth=13 hwq_depth=0, bar_wait=0 > > >> > [179397] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=47131 > > >> > [179397] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV 0b b8 00 05 00 00 KID 0] 0M > > >> > [179397] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 e080 0bb8 0020 0500 0000 aaaa 0300 0000 0800 4500 0034 1535 4000 4006 90cb 0a00 001b c346 c762 f65f 0014 b6aa cfc8 46ad 84ba 8010 03fc e360 0000 0101 080a 428d 489d f0d1 3651 > > >> > [179399] wlan0: link state changed to UP > > >> > [179409] wlan0: link state changed to DOWN > > >> > [179411] wlan0: link state changed to UP > > >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=0xc4b355f0: addbaw=0, dobaw=0, seqno=948, retry=0 > > >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: bf=0xc4b355f0: tid txq_depth=4 hwq_depth=0, bar_wait=0 > > >> > [179636] ath0: ath_tx_tid_drain: node 0xc4b5b000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=41912 > > >> > [179636] TODS f4:ec:38:a3:10:dc->00:1c:58:56:bf:a8(00:11:95:ca:ae:7c) data WEP [IV b1 a3 00 00 00 00 KID 0] 0M > > >> > [179636] 0841 0000 0011 95ca ae7c f4ec 38a3 10dc 001c 5856 bfa8 403b b1a3 0020 0000 0000 aaaa 0300 0000 0800 4500 0034 bb4b 4000 4006 eab4 0a00 001b c346 c762 b0cc 0014 5ba9 9748 1033 a13f 8010 03fc 39f3 0000 0101 080a f0d2 a239 f0d4 cae3 > > >> > [179636] wlan0: link state changed to DOWN > > >> > [179638] wlan0: link state changed to UP > > >> > [179648] wlan0: link state changed to DOWN > > >> > [179650] wlan0: link state changed to UP > > >> > [180075] wlan0: link state changed to DOWN > > >> > [180077] wlan0: link state changed to UP > > >> > [180087] wlan0: link state changed to DOWN > > >> > [180089] wlan0: link state changed to UP > > >> > [180486] wlan0: link state changed to DOWN > > >> > [180488] wlan0: link state changed to UP > > >> > [180498] wlan0: link state changed to DOWN > > >> > [180500] wlan0: link state changed to UP > > >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41bb0: addbaw=0, dobaw=0, seqno=0, retry=0 > > >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: bf=0xc4b41bb0: tid txq_depth=1 hwq_depth=0, bar_wait=0 > > >> > [181165] ath0: ath_tx_tid_drain: node 0xc50dd000: tid 16: txq_depth=2, txq_aggr_depth=0, sched=0, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=58839 > > >> > [181165] NODS f4:ec:38:a3:10:dc->00:11:95:ca:ae:7c(00:11:95:ca:ae:7c) probe_req 0M > > >> > [181165] 4000 0000 0011 95ca ae7c f4ec 38a3 10dc 0011 95ca ae7c 605d 0003 736c 7701 0882 848b 960c 1218 2430 2601 0000 0fac 0201 0000 0fac 0401 0000 0fac 0100 0001 002a d59e 9e8d ea21 0eea 3d42 9bdc 4f4e 4432 0430 4860 6c > > >> > [181165] wlan0: link state changed to DOWN > > >> > [181166] Aug 19 01:11:18 notebook kernel: [181165] wlan0: link state changed to DOWN > > >> > [181168] wlan0: link state changed to UP > > >> > [181168] Aug 19 01:11:20 notebook kernel: [181168] wlan0: link state changed to UP > > >> > [181178] wlan0: link state changed to DOWN > > >> > [181178] Aug 19 01:11:30 notebook kernel: [181178] wlan0: link state changed to DOWN > > >> > [181180] wlan0: link state changed to UP > > >> > [181612] wlan0: link state changed to DOWN > > >> > [181614] wlan0: link state changed to UP > > >> > [181624] wlan0: link state changed to DOWN > > >> > [181626] wlan0: link state changed to UP > > >> > [190739] wlan0: link state changed to DOWN > > >> > [190741] wlan0: link state changed to UP > > >> > [190751] wlan0: link state changed to DOWN > > >> > [190754] wlan0: link state changed to UP > > >> > [194052] ath0: device timeout > > >> > [202568] ath0: device timeout > > >> > [205182] wlan0: link state changed to DOWN > > >> > [205184] wlan0: link state changed to UP > > >> > [214975] ath0: bb hang detected (0x4), resetting > > >> > [216007] wlan0: link state changed to DOWN > > >> > [216009] wlan0: link state changed to UP From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 19 16:13:52 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 1520E106566C for ; Sun, 19 Aug 2012 16:13:52 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 893F08FC08 for ; Sun, 19 Aug 2012 16:13:50 +0000 (UTC) Received: by bkcje9 with SMTP id je9so2046647bkc.13 for ; Sun, 19 Aug 2012 09:13:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:message-id:x-gm-message-state; bh=5htU7arfM9vbE+dpB8lVw3Je0juXbJiHRM6Rpp8B5IY=; b=Bs8zNHhvKejW3tNtq3ivtUGkjbcAxBMaicuzxUAoQKN+dIl9Re5/onXcrRfzkHQ4c9 mxvjqgC8hTV1CejUJZM66k5Nzv39dO83e+hOP1LsMtXbfgisj5JVGNSa4B6O2T68wp0U ZsgWi0Gr/4hxMuIBjsma79WkjuujGYsBNi1GXt0mfAGV9A2PbI33cg6bt+jz1nQUVRsv jzZs1fR/Vy93WwBAMDfBEDUZqxkjbT0+IdbkXACx3jtefWoW5TaNJZqU4q20N1jHDt2+ cVGnHFbTbB6xvlIvElpbq5eJzoHeMFa2HyfVBC2cpZlHBC4buG0GQOIVQcElusTemLc/ +7YQ== Received: by 10.204.129.8 with SMTP id m8mr3598056bks.62.1345392829818; Sun, 19 Aug 2012 09:13:49 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-065-220-164.pools.arcor-ip.net. [88.65.220.164]) by mx.google.com with ESMTPS id t23sm5120184bks.4.2012.08.19.09.13.47 (version=SSLv3 cipher=OTHER); Sun, 19 Aug 2012 09:13:49 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: =?utf-8?q?=E4=B9=94=E6=A5=9A?= Date: Sun, 19 Aug 2012 18:14:24 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.7.4; amd64; ; ) References: <201207300139326668335@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_gDRMQ8Ke5QO1Kik" Message-Id: <201208191814.24880.bschmidt@freebsd.org> X-Gm-Message-State: ALoCoQmkEV+6zQL6OYM8gpZGDK71mTYqHUYsQgMryY4k2+HuhIoRUgmTega1wv440aA0PADbDzQc Cc: freebsd-wireless Subject: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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: Sun, 19 Aug 2012 16:13:52 -0000 --Boundary-00=_gDRMQ8Ke5QO1Kik Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tuesday 14 August 2012 17:17:43 =E4=B9=94=E6=A5=9A wrote: > /8/14 Adrian Chadd : > > why is meshid reading from the HTINFO field I doesn't, it tries to interpret the "AP channel Report" and "Neighbor Repoort" elements as Mesh elements due to outdated defines. =20 > I am also confused. > How can we further debug? Can you try attached diff? This change is in head and an MFC should fix the issue. =2D-=20 Bernhard --Boundary-00=_gDRMQ8Ke5QO1Kik Content-Type: text/x-patch; charset="UTF-8"; name="r231187.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="r231187.diff" Index: sys/net80211/ieee80211.h =================================================================== --- sys/net80211/ieee80211.h (revision 231186) +++ sys/net80211/ieee80211.h (revision 231187) @@ -709,27 +709,32 @@ enum { IEEE80211_ELEMID_VENDOR = 221, /* vendor private */ /* - * 802.11s IEs based on D3.03 spec and were not assigned by - * ANA. Beware changing them because some of them are being - * kept compatible with Linux. + * 802.11s IEs + * NB: On vanilla Linux still IEEE80211_ELEMID_MESHPEER = 55, + * but they defined a new with id 117 called PEER_MGMT. + * NB: complies with open80211 */ - IEEE80211_ELEMID_MESHCONF = 51, - IEEE80211_ELEMID_MESHID = 52, - IEEE80211_ELEMID_MESHLINK = 35, - IEEE80211_ELEMID_MESHCNGST = 36, - IEEE80211_ELEMID_MESHPEER = 55, - IEEE80211_ELEMID_MESHCSA = 38, - IEEE80211_ELEMID_MESHTIM = 39, - IEEE80211_ELEMID_MESHAWAKEW = 40, - IEEE80211_ELEMID_MESHBEACONT = 41, - IEEE80211_ELEMID_MESHPANN = 48, - IEEE80211_ELEMID_MESHRANN = 49, - IEEE80211_ELEMID_MESHPREQ = 68, - IEEE80211_ELEMID_MESHPREP = 69, - IEEE80211_ELEMID_MESHPERR = 70, - IEEE80211_ELEMID_MESHPXU = 53, - IEEE80211_ELEMID_MESHPXUC = 54, - IEEE80211_ELEMID_MESHAH = 60, /* Abbreviated Handshake */ + IEEE80211_ELEMID_MESHCONF = 113, + IEEE80211_ELEMID_MESHID = 114, + IEEE80211_ELEMID_MESHLINK = 115, + IEEE80211_ELEMID_MESHCNGST = 116, + IEEE80211_ELEMID_MESHPEER = 117, + IEEE80211_ELEMID_MESHCSA = 118, + IEEE80211_ELEMID_MESHTIM = 39, /* XXX: remove */ + IEEE80211_ELEMID_MESHAWAKEW = 119, + IEEE80211_ELEMID_MESHBEACONT = 120, + /* 121-124 MMCAOP not implemented yet */ + IEEE80211_ELEMID_MESHPANN = 125, /* XXX: is GANN now, not used */ + IEEE80211_ELEMID_MESHRANN = 126, + /* 127 Extended Capabilities */ + /* 128-129 reserved */ + IEEE80211_ELEMID_MESHPREQ = 130, + IEEE80211_ELEMID_MESHPREP = 131, + IEEE80211_ELEMID_MESHPERR = 132, + /* 133-136 reserved */ + IEEE80211_ELEMID_MESHPXU = 137, + IEEE80211_ELEMID_MESHPXUC = 138, + IEEE80211_ELEMID_MESHAH = 60, /* XXX: remove */ }; struct ieee80211_tim_ie { --Boundary-00=_gDRMQ8Ke5QO1Kik-- From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 19 16:52:56 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 DCBE6106566C for ; Sun, 19 Aug 2012 16:52:56 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5B4DB8FC08 for ; Sun, 19 Aug 2012 16:52:55 +0000 (UTC) Received: by bkcje9 with SMTP id je9so2053499bkc.13 for ; Sun, 19 Aug 2012 09:52:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:message-id:x-gm-message-state; bh=pgxze8zcQz/An+uYgS+pvnEQP5pZwS3RjEhWksuFDkk=; b=kLIQZPZaZfnn+PBy2IttqxcEQb+TSN+DxRpBD1hmXAeUFyaEtBUBDGLrJHGmLPE3QT Y9ERZQXNnoGaXwrx4MsD1ekbUIowzjVFk172rl61i1gOWN4OgGWGzzqzPNmzhjjH4Z8v hJIRJFU9Ofaj2+YXR0xMZ0gq1nyl3T5lt4sZz43EsSCr+ohXoFJZoy7NJ3PafnA1pUy/ mNfwMx9MhoxGxQUQZsHNHqc+Ac4ENJgavXZuSsX3cOtsiYIz+B1Ro6wbI+hXLRJYXHsD TJrsv91Eg+vc7HthjdVAsofCOH1QD7brkgHdLWfIsEnoq591FvIN+z6OekPTGbpLhtbJ Orwg== Received: by 10.205.119.208 with SMTP id fv16mr3782145bkc.100.1345395174949; Sun, 19 Aug 2012 09:52:54 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-065-220-164.pools.arcor-ip.net. [88.65.220.164]) by mx.google.com with ESMTPS id hg13sm5142389bkc.7.2012.08.19.09.52.51 (version=SSLv3 cipher=OTHER); Sun, 19 Aug 2012 09:52:54 -0700 (PDT) From: Bernhard Schmidt To: Yuval Prag Date: Sun, 19 Aug 2012 18:53:24 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.7.4; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_FoRMQiuZfUEQNdC" Message-Id: <201208191853.25104.bschmidt@techwires.net> X-Gm-Message-State: ALoCoQkI4oHklF9paltIZQk9MKS59RoPmpIhVDnw0S/Tp8PwwTx6EWa5gZu96G9k8YLqfB9ETiKS Cc: freebsd-wireless@freebsd.org Subject: Re: Intel Pro/Wireless 2200BG crash on FreeBSD-8.3 i386 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: Sun, 19 Aug 2012 16:52:56 -0000 --Boundary-00=_FoRMQiuZfUEQNdC Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On Friday 17 August 2012 07:00:26 Yuval Prag wrote: > Hi Im looking for help and some more info on the subject. > > the only post i found is from april 2008 the post suggests to add the > capability to the driver based on or copy from a different WiFi > NIC driver and it is not working still same error > > the NIC hangs in a way ifconfig show IP address the and status = > associated, a simple ping to the router works with intermittent failures > in the form of "sento: Network is down" and than it hangs usualy afte the > 15th packet send... a restart the NIC device with "/etc/rc.d/netif restart" > will cause the system to reboot! Attached patch should fix the panic, I should push this into tree finally.. The dmesg in PR170573 shows some confusing information, the driver is iwi(4) but the firmware load is for ipw(4), is this some left over from an older setup? I so, clean up your loader.conf please. Can you please pull a 9.1-beta memstick image or something and give this a quick shot? Just so we now that issue still exists on a more recent system. The relevant part from the dmesg is basically this line: iwi0: firmware error after that, the hardware is dead. We need to figure out why this is happening, please post more details about your setup and configuration. Preferably also a the full dmesg with wlandebug 0xffffffff enabled before above error line is printed. -- Bernhard --Boundary-00=_FoRMQiuZfUEQNdC Content-Type: text/x-patch; charset="UTF-8"; name="iwi_vs_sta1.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="iwi_vs_sta1.diff" Index: sys/dev/iwi/if_iwi.c =================================================================== --- sys/dev/iwi/if_iwi.c (revision 235132) +++ sys/dev/iwi/if_iwi.c (working copy) @@ -2811,7 +2811,7 @@ iwi_auth_and_assoc(struct iwi_softc *sc, struct ie { struct ieee80211com *ic = vap->iv_ic; struct ifnet *ifp = vap->iv_ifp; - struct ieee80211_node *ni = vap->iv_bss; + struct ieee80211_node *ni; struct iwi_configuration config; struct iwi_associate *assoc = &sc->assoc; struct iwi_rateset rs; @@ -2826,6 +2826,8 @@ iwi_auth_and_assoc(struct iwi_softc *sc, struct ie return (-1); } + ni = ieee80211_ref_node(vap->iv_bss); + IWI_STATE_BEGIN(sc, IWI_FW_ASSOCIATING); error = 0; mode = 0; @@ -2982,6 +2984,8 @@ done: if (error) IWI_STATE_END(sc, IWI_FW_ASSOCIATING); + ieee80211_free_node(ni); + return (error); } --Boundary-00=_FoRMQiuZfUEQNdC-- From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 01:35:21 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 BD0B7106564A for ; Mon, 20 Aug 2012 01:35:21 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 648918FC08 for ; Mon, 20 Aug 2012 01:35:21 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q7K1ZJ0p074837 for ; Sun, 19 Aug 2012 19:35:19 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q7K1ZJIB074834 for ; Sun, 19 Aug 2012 19:35:19 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 19 Aug 2012 19:35:19 -0600 (MDT) From: Warren Block To: freebsd-wireless@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: Wireless temperature sensors 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, 20 Aug 2012 01:35:21 -0000 Does anyone have any experience using these 433MHz sensors? http://www.amazon.com/Meade-TS34C-M-Range-Temperature-TE923W-M/dp/B004K6LORS/ref=pd_ybh_5 There has apparently been some work on decoding the protocol, but first I need a receiver. I have a couple of these in 434MHz: http://shop.moderndevice.com/products/rfm12b-radio The receivers could be added to an Arduino, but there may be a more direct way to attach them to a USB port (preferably). OTOH, an Arduino isn't that big a deal, either. This may be the protocol code: http://jeelabs.org/2010/04/19/more-ook-decoders/ From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 11:08:08 2012 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 E2C44106567F for ; Mon, 20 Aug 2012 11:08:08 +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 B1CBB8FC1F for ; Mon, 20 Aug 2012 11:08:08 +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 q7KB88U4048257 for ; Mon, 20 Aug 2012 11:08:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7KB877F048238 for freebsd-wireless@FreeBSD.org; Mon, 20 Aug 2012 11:08:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Aug 2012 11:08:07 GMT Message-Id: <201208201108.q7KB877F048238@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, 20 Aug 2012 11:08:09 -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/170620 wireless [ath] LOR and deadlock when multiple vaps are used 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/169433 wireless [iwn] iwn(4) doesn't support 6235 chip. 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 123 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 12:53:02 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 014CC1065672; Mon, 20 Aug 2012 12:53:02 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id AA02D8FC0A; Mon, 20 Aug 2012 12:53:01 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3RVt-000H45-0P; Mon, 20 Aug 2012 16:55:25 +0400 Date: Mon, 20 Aug 2012 16:55:24 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Message-ID: <20120820125524.GL98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 12:53:02 -0000 On Sun, Aug 19, 2012 at 12:12:20AM -0700, Adrian Chadd wrote: > I don't see this kind of behaviour in STA mode. What are you associating to? > > What channel is it on? wlan0: link state changed to DOWN/UP -- because AP don't implement 802.11R and don't transmit WLAN_EID_TIMEOUT_INTERVAL. > > [155821] ath0: bb hang detected (0x4), resetting > > [194052] ath0: device timeout > > [202568] ath0: device timeout > > [214975] ath0: bb hang detected (0x4), resetting And time to time I need to kldunload if_ath_pci.ko kldload if_ath_pci.ko for re-enable card. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 15:25:39 2012 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 21FDD1065672; Mon, 20 Aug 2012 15:25:39 +0000 (UTC) (envelope-from honestqiao@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id A48478FC14; Mon, 20 Aug 2012 15:25:38 +0000 (UTC) Received: by qcsg15 with SMTP id g15so5610757qcs.13 for ; Mon, 20 Aug 2012 08:25:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=zkB9CWvPt7JOJ/jns3VccFF6yb2e1bdSDxhHdcKVXV8=; b=tTxlYJYGk2EiCHe118/x0G75SnhyPmakNODAdLXaDFqtyiuqjCsDX9kV+LB3YZkaiT nZqaw/5yk+kA8e3Y9aBqdo8jW+KmmAxMKz3z1j8BKsn4GVuDw2tVAa1DaWRpFr0iidw/ d2IMnIx2hJMl5zt/TQceOiGWRCRySQZjQFixALa4ps4MgpnfhDkCpuYP1Qsd8tJE+wJt F/nbGsAkNv95oX5yUDh34Zipc05bd+zspFW71ETCrT8+to1jxbnnPUcsj5idMoGZ7/Sr hscwdv6cswkPKpRqxg3ql5FWIq2qPUO5xhLAbQwTS/V1Vc9ZqG+HAaltMz7nZZFM16Ju jz7A== Received: by 10.229.147.193 with SMTP id m1mr13131180qcv.128.1345476337323; Mon, 20 Aug 2012 08:25:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.197.65 with HTTP; Mon, 20 Aug 2012 08:24:56 -0700 (PDT) In-Reply-To: <201208191814.24880.bschmidt@freebsd.org> References: <201207300139326668335@gmail.com> <201208191814.24880.bschmidt@freebsd.org> From: =?UTF-8?B?5LmU5qWa?= Date: Mon, 20 Aug 2012 23:24:56 +0800 Message-ID: To: Bernhard Schmidt Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless Subject: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 20 Aug 2012 15:25:39 -0000 2012/8/20 Bernhard Schmidt : > On Tuesday 14 August 2012 17:17:43 =E4=B9=94=E6=A5=9A wrote: >> /8/14 Adrian Chadd : >> > why is meshid reading from the HTINFO field > > I doesn't, it tries to interpret the "AP channel Report" and > "Neighbor Repoort" elements as Mesh elements due to outdated > defines. > >> I am also confused. >> How can we further debug? > > Can you try attached diff? This change is in head and an MFC > should fix the issue. > > -- > Bernhard But my src branch is stable/9. [23:15:22]root@x201i.pts/3 /usr/src # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 239433 Node Kind: directory Schedule: normal Last Changed Author: emaste Last Changed Rev: 239433 Last Changed Date: 2012-08-20 22:54:30 +0800 (Mon, 20 Aug 2012) I need switch to HEAD? From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 15:38:58 2012 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 BE2081065672 for ; Mon, 20 Aug 2012 15:38:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8F6A78FC0A for ; Mon, 20 Aug 2012 15:38:58 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so7513862pbb.13 for ; Mon, 20 Aug 2012 08:38:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0Hmzja8VIPrZcV1CmQdCyx4Cbby1ONhLi3t7OCOwBQA=; b=jeEno7Zfdab5YPEBvqqajjJffkwrnbCBfPNuZKisYnRuYPxHOhadOYKI1OHr3td6W9 mL4Jxkl01aqdvJBRma0vQbm/W9vDuE6qyQ0bDYiC9xpUqSf6si0uYoFkFaVyz6e1YFVl t8FnQ1RdJZBCvcSKh8fMvBIl0sqXKPNslSKQbQ8NZ/zKSOcL4M/+2FEa9tjHPIxuz/xn QidDXqXWUsiy/UqwtyOT4vU1SQkXeAOEopu083Z6n+74drbStAtUHRotB6FZNQG4O4l5 t9R4TxyX3Kmv22T0hRHDlJhHrGp6bHIw1Z0JKJH1zEiEmxVph2TkoLHqlbFabI0UcbXE 8wOw== MIME-Version: 1.0 Received: by 10.68.236.102 with SMTP id ut6mr35336317pbc.113.1345477137956; Mon, 20 Aug 2012 08:38:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 08:38:56 -0700 (PDT) In-Reply-To: <20120820125524.GL98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> Date: Mon, 20 Aug 2012 08:38:56 -0700 X-Google-Sender-Auth: ociYWokuwPoM9M1HBT8b8D6EGTY Message-ID: From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 15:38:58 -0000 On 20 August 2012 05:55, Slawa Olhovchenkov wrote: > wlan0: link state changed to DOWN/UP -- because AP don't implement > 802.11R and don't transmit WLAN_EID_TIMEOUT_INTERVAL. So you mean that's to be expected? There are situations where an AP will time a station out. May leave a background ping going and see if it stays associated? >> > [155821] ath0: bb hang detected (0x4), resetting >> > [194052] ath0: device timeout >> > [202568] ath0: device timeout >> > [214975] ath0: bb hang detected (0x4), resetting > > And time to time I need to > > kldunload if_ath_pci.ko > kldload if_ath_pci.ko > > for re-enable card. This is a bit more worrying. An ifconfig wlanX destroy ; ifconfig wlanX create isn't sufficient? Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:01:21 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 198DB106567A; Mon, 20 Aug 2012 16:01:21 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id BCEE38FC1F; Mon, 20 Aug 2012 16:01:20 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3US8-000Kdj-O7; Mon, 20 Aug 2012 20:03:44 +0400 Date: Mon, 20 Aug 2012 20:03:44 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Message-ID: <20120820160344.GM98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 16:01:21 -0000 On Mon, Aug 20, 2012 at 08:38:56AM -0700, Adrian Chadd wrote: > On 20 August 2012 05:55, Slawa Olhovchenkov wrote: > > > wlan0: link state changed to DOWN/UP -- because AP don't implement > > 802.11R and don't transmit WLAN_EID_TIMEOUT_INTERVAL. > > So you mean that's to be expected? There are situations where an AP > will time a station out. May leave a background ping going and see if > it stays associated? This is time for rekeing (WPA2 enterprise). AP configured for rekeing clients at 3600 seconds. But AP don't send information about rekeing interval in EAPOL packets. [277795] wlan0: link state changed to DOWN [277797] wlan0: link state changed to UP [281406] wlan0: link state changed to DOWN [281408] wlan0: link state changed to UP [292231] wlan0: link state changed to DOWN [292233] wlan0: link state changed to UP [302376] ath0: device timeout 281406-277797 = 3609 292231-281408 = 10823 = 3600*3+23 > >> > [155821] ath0: bb hang detected (0x4), resetting > >> > [194052] ath0: device timeout > >> > [202568] ath0: device timeout > >> > [214975] ath0: bb hang detected (0x4), resetting > > > > And time to time I need to > > > > kldunload if_ath_pci.ko > > kldload if_ath_pci.ko > > > > for re-enable card. > > This is a bit more worrying. An ifconfig wlanX destroy ; ifconfig > wlanX create isn't sufficient? I am not clearly remember, may be isn't sufficient. This is from old time, before introduction wlan0 (when all work on ath0 and D-Link DWL-G650). A am try at next time. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:06: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 71F65106564A for ; Mon, 20 Aug 2012 16:06:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 422AF8FC12 for ; Mon, 20 Aug 2012 16:06:07 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so7551057pbb.13 for ; Mon, 20 Aug 2012 09:06:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=iUFvqWqpIsqALCpbeYC+4LNig1zm/GG5jGvsqhi3WSE=; b=oraJCkzOo0cVkZ3ttZDvAV9Vs6h9LVpgDkuzB6aycHcoSt0tmBhk4zmxh8LxvEJ+gA D3fanltGL24YDj7uE0Ly9hzKZCxuiRsmjWVBo5voKXXxJIuUC/gCAfXy4rf1gTDeNEpG ZqzoFwxnevkilJXVURRr5WQoC8SbDSl2/0TMvFj00eEiWcixuq3/EQI5ih47oo/k9tlb zUJZ1feKNyuw0S51FvdLNYT/Nx1CVdEU98YFlUQlUQgIsBnFKNoGfx7jt3YeaasoAtfD JhBGWQCvdfNZ0eicdpalp/4UlHkE20ID99CucW8E17UP9WnM8ERjcL/V9tiA8bpfXQ6M nFTA== MIME-Version: 1.0 Received: by 10.68.136.40 with SMTP id px8mr35497582pbb.153.1345478766813; Mon, 20 Aug 2012 09:06:06 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 09:06:06 -0700 (PDT) In-Reply-To: <20120820160344.GM98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> <20120820160344.GM98910@zxy.spb.ru> Date: Mon, 20 Aug 2012 09:06:06 -0700 X-Google-Sender-Auth: -ocJ06C-yLo53yrNewoNiKwIxCc Message-ID: From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 16:06:07 -0000 Please do try again. I'd like to nail any card reset and instability issues as soon as they pop up. -HEAD should be pretty good with those NICs now. I use all of them (AR5416, AR9160, AR9220, AR9280, AR9285, AR9287, even an AR9227 where appropriate) and I've not seen any real instability issues. The main issues I see right now are very likely due to noisy environments and ANI behaving poorly. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:28: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 E653B106566B; Mon, 20 Aug 2012 16:28:55 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 9739F8FC15; Mon, 20 Aug 2012 16:28:55 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3Uso-000L8t-Ac; Mon, 20 Aug 2012 20:31:18 +0400 Date: Mon, 20 Aug 2012 20:31:18 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Message-ID: <20120820163118.GN98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> <20120820160344.GM98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 16:28:56 -0000 On Mon, Aug 20, 2012 at 09:06:06AM -0700, Adrian Chadd wrote: > Please do try again. > > I'd like to nail any card reset and instability issues as soon as they > pop up. -HEAD should be pretty good with those NICs now. > I use all of them (AR5416, AR9160, AR9220, AR9280, AR9285, AR9287, > even an AR9227 where appropriate) and I've not seen any real > instability issues. > > The main issues I see right now are very likely due to noisy > environments and ANI behaving poorly. How you detect noisy environments? (some output from athsurvey?) What level of noisy is acpetable in terms of athsurvey and in terms of physicaly units? (I can use Cisco Spectrum Expert for survey, but not simultaneously with this card). What is ANI? What I need to try in next time of lost traffic? (no messages in console in this situation, nothing about "ath0: device timeout" nor "ath0: bb hang detected (0x4), resetting"). Do I need to enable some debug? From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:30: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 366F51065670 for ; Mon, 20 Aug 2012 16:30:53 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id A5AC58FC12 for ; Mon, 20 Aug 2012 16:30:52 +0000 (UTC) Received: by bkcje9 with SMTP id je9so2445463bkc.13 for ; Mon, 20 Aug 2012 09:30:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=+n1mPlMkdukof3XLYgYxIujlc6m9nBeG0AoY8O6YDsE=; b=AjRyXAWmFmkQcypi5o+mvEgQAFErQOA1ZC0VBJfrXLJhf6cqH/ue5PBFeasuxDDzZ1 3HKV782bkAlVf5I2T586S4g1Tcz5n/IDOnVqx8OHBGeeh9RVP7g1AMUFbES5LiMi1AuI rVypJA/hxmKHNKTVYWVLi873JAQM7+/iNG6Q2XQemf5E1irKv0xvZ3SApeYclOaFOsx0 /j6QShIb+dMSxIDR2CbcOss7pOFQA6drh1G1LINWlDZ8bNNnMOy50jYMhY4+T9LuGWkN f5uWo9AE6wpzw03FRLGt21xMZ9qs7RruK4ZEfq+KB7QUwuxxWVsgXg/KVHQo9Ensx8yZ WcjQ== Received: by 10.204.148.66 with SMTP id o2mr4511549bkv.43.1345480251148; Mon, 20 Aug 2012 09:30:51 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-067-214-011.pools.arcor-ip.net. [88.67.214.11]) by mx.google.com with ESMTPS id c18sm6490122bkv.8.2012.08.20.09.30.49 (version=SSLv3 cipher=OTHER); Mon, 20 Aug 2012 09:30:50 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: =?utf-8?q?=E4=B9=94=E6=A5=9A?= Date: Mon, 20 Aug 2012 18:29:10 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.7.4; amd64; ; ) References: <201207300139326668335@gmail.com> <201208191814.24880.bschmidt@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201208201829.10554.bschmidt@freebsd.org> X-Gm-Message-State: ALoCoQkssAWXarVdxqIgY9CUkI/r5TCI9m2N7rrZyghbaHlthuYwuMj3Bkp1f78rsQc4KQteB7BT Cc: freebsd-wireless Subject: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 20 Aug 2012 16:30:53 -0000 On Monday 20 August 2012 17:24:56 =E4=B9=94=E6=A5=9A wrote: > 2012/8/20 Bernhard Schmidt : > > Can you try attached diff? This change is in head and an MFC > > should fix the issue. >=20 > But my src branch is stable/9. >=20 > I need switch to HEAD? No, the patch should apply to stable/9 just fine. =2D-=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:36:05 2012 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 D67E9106566C for ; Mon, 20 Aug 2012 16:36:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 699FA8FC0A for ; Mon, 20 Aug 2012 16:36:05 +0000 (UTC) Received: by dadr6 with SMTP id r6so2423657dad.13 for ; Mon, 20 Aug 2012 09:36:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=IaYYMqtFkR8s5e3VPnH2pkUQ8tb+vW4dhKRQ4elDRjQ=; b=w5h7E7kqfIQYygqHqkuC7RK9UbfpFJNzJ+YPR/2SIAJrq6bSN2b5W/c7TEnZxLu/93 p4quLPomTq49QJcTHl+5ulA1IxYuNz6ShYwnQzqWmUvwA0PnWx22D+JajCCIyQpqrrdH LvVjUg8Dr+XOxIREs/4ITfIcszZyxsis+aOWzCy5eCzvz27bRefQGhvuMudrLnDwl5RS e9Vark5JrUhqFlnjqoBnwq0uyoNZp7VZBVCvQ2OV788r/T6s7ULsOrK+XEE+8RAMt2uP 6oKcEqZsVo/MIea3BLYZzraIrQsVlggx1qtmimlRAiL1CdDjLbBfBp1PCQFDUep18Ngp j1Lg== MIME-Version: 1.0 Received: by 10.66.75.195 with SMTP id e3mr30932437paw.32.1345480564908; Mon, 20 Aug 2012 09:36:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 09:36:04 -0700 (PDT) In-Reply-To: <20120820163118.GN98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> <20120820160344.GM98910@zxy.spb.ru> <20120820163118.GN98910@zxy.spb.ru> Date: Mon, 20 Aug 2012 09:36:04 -0700 X-Google-Sender-Auth: znxVPG_r2YGpzve2ksCgd7U61UE Message-ID: From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 16:36:05 -0000 On 20 August 2012 09:31, Slawa Olhovchenkov wrote: >> The main issues I see right now are very likely due to noisy >> environments and ANI behaving poorly. > > How you detect noisy environments? > (some output from athsurvey?) Yup. Look at the channel busy statistics. YOur channel isn't busy at all. > What level of noisy is acpetable in terms of athsurvey and in terms of > physicaly units? (I can use Cisco Spectrum Expert for survey, but not > simultaneously with this card). Anything bursty, wide or narrow band, will cause issues. > What is ANI? Ambient/Automatic Noise Immunity. There's some code which adjusts some PHY parameters to do with signal sizing and offset; however I may have (more) broken it. I need to sit down and add some further debugging and write an inspection tool or two to figure out exactly what's going on. > What I need to try in next time of lost traffic? > (no messages in console in this situation, nothing about "ath0: device > timeout" nor "ath0: bb hang detected (0x4), resetting"). > > Do I need to enable some debug? Well, what do you mean by "lost traffic" ? I need some more information about that. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:52:12 2012 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 F302110656B1; Mon, 20 Aug 2012 16:52:11 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 851AF8FC19; Mon, 20 Aug 2012 16:52:11 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3VFL-000LVB-HA; Mon, 20 Aug 2012 20:54:35 +0400 Date: Mon, 20 Aug 2012 20:54:35 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Message-ID: <20120820165435.GO98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> <20120820160344.GM98910@zxy.spb.ru> <20120820163118.GN98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 16:52:12 -0000 On Mon, Aug 20, 2012 at 09:36:04AM -0700, Adrian Chadd wrote: > On 20 August 2012 09:31, Slawa Olhovchenkov wrote: > > >> The main issues I see right now are very likely due to noisy > >> environments and ANI behaving poorly. > > > > How you detect noisy environments? > > (some output from athsurvey?) > > Yup. Look at the channel busy statistics. YOur channel isn't busy at all. Oh, I am don't need utilise all bandwidth, typical use: ssh access to remote host and lot of web traffic. And narrow uplink (~2-5Mbit/s). Now I do test transfer from local ftp: min avg max tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% (10.8 73.8 90.5 5.1) (12.2 76.7 93.2 6.8) (13.2 81.2 94.9 9.5) (10.8 73.8 91.2 5.1) (12.2 77.0 93.3 6.6) (13.2 81.2 94.9 8.8) (11.2 74.5 91.2 5.1) (12.3 76.7 93.5 6.5) (13.2 81.2 94.9 8.8) (10.3 73.7 91.2 5.1) (12.4 76.6 93.8 6.2) (13.4 79.5 94.9 8.8) (10.3 73.6 92.4 5.1) (12.5 76.5 94.0 6.0) (13.4 79.0 94.9 7.6) (10.3 73.6 92.4 4.9) (12.5 76.5 94.0 5.9) (13.4 78.6 95.1 7.6) (11.0 72.4 92.4 4.9) (12.6 76.2 94.0 6.0) (13.5 79.2 95.1 7.6) (11.0 72.3 92.4 4.9) (12.6 76.1 94.0 6.0) (13.6 79.2 95.1 7.6) (11.0 70.8 92.6 4.9) (13.2 75.5 94.1 5.9) (16.6 79.2 95.1 7.4) (11.5 70.8 93.0 5.1) (13.3 75.2 94.1 5.9) (16.6 79.2 94.9 7.0) (11.5 70.8 92.8 5.1) (13.2 74.9 94.2 5.8) (16.6 78.9 94.9 7.2) (11.2 70.9 92.8 5.1) (12.7 75.3 94.0 6.0) (14.7 78.9 94.9 7.2) (10.7 70.9 92.4 4.4) (12.3 75.7 93.9 6.1) (13.5 79.4 95.6 7.6) ( 7.5 63.2 92.1 3.2) (12.0 75.7 93.8 6.2) (13.4 79.4 96.8 7.8) ( 7.5 63.2 92.1 3.2) (11.8 76.2 93.8 6.2) (13.3 80.2 96.8 7.8) ( 7.5 63.2 92.1 3.2) (11.9 76.4 93.8 6.2) (13.3 80.2 96.8 7.8) (10.3 71.8 92.1 5.3) (12.0 76.7 93.8 6.2) (13.3 80.2 94.7 7.8) (10.2 71.8 92.2 5.1) (12.0 76.3 93.8 6.2) (13.2 79.8 94.9 7.8) (10.2 71.8 92.2 5.0) (12.1 76.5 94.0 6.0) (13.3 79.5 95.0 7.8) (10.2 71.8 92.2 5.0) (12.2 76.2 94.1 5.8) (13.3 79.5 95.0 7.8) ( 9.2 71.0 93.2 5.0) (12.3 75.9 94.2 5.8) (13.3 79.5 95.0 6.8) ( 9.2 71.0 93.1 5.0) (12.1 75.6 94.2 5.8) (13.3 78.7 95.0 6.9) ( 9.2 71.0 92.4 5.1) (12.1 75.7 94.1 5.9) (13.2 78.4 94.9 7.6) > > What level of noisy is acpetable in terms of athsurvey and in terms of > > physicaly units? (I can use Cisco Spectrum Expert for survey, but not > > simultaneously with this card). > > Anything bursty, wide or narrow band, will cause issues. > > > > What is ANI? > > Ambient/Automatic Noise Immunity. There's some code which adjusts some > PHY parameters to do with signal sizing and offset; however I may have > (more) broken it. > I need to sit down and add some further debugging and write an > inspection tool or two to figure out exactly what's going on. > > > What I need to try in next time of lost traffic? > > > (no messages in console in this situation, nothing about "ath0: device > > timeout" nor "ath0: bb hang detected (0x4), resetting"). > > > > Do I need to enable some debug? > > Well, what do you mean by "lost traffic" ? I need some more > information about that. Sometimes (may be one in 2-3 days) receiving packets on wlan0 stoped. May be intesive traffic increase probability. No messages in dmesg. tcpdump on wlan0 show only outgoing packets. Interface is UP. No automatic recovery. For manual recovery I am need to kldunload/kldolad if_ath_pci. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 16:57: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 25A101065780 for ; Mon, 20 Aug 2012 16:57:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E66A18FC12 for ; Mon, 20 Aug 2012 16:57:54 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so7622360pbb.13 for ; Mon, 20 Aug 2012 09:57:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4isMrpTMRqR/eB2GisIa8figQtXsZFFp8ZMIPHnqVYs=; b=ahtX+QDcj3w2bVbvmO3F6cv1iuKJJ2DJ3RwAxfLTNSKJJF98JcaVLWtMtDFqv+5srf K4l/WvRNPie/QeQ5ujasV9gMY2gvu2KUJqyeyIWboqbPlq12vWSowdKOLUHA6MT6oloZ P2K9riNoO81Xak3LH26D1KrIdtY3FNb3zFGWLT9O2qkxnfxkKRQYegJqaFwJuwVpfWkJ HdoK8cx1s5pf4MIloE/1vWEVWlUb5junpqBSLEiU4EJ+T+2rnh/3oaHr697wtCTd+9bQ qvmO3c0GLAQmuvrQDiKzdruGPm/2KrnVrl3fvVy0Ju3sOOGgV14vVwira/DXByC/Ilks Dk0Q== MIME-Version: 1.0 Received: by 10.66.85.4 with SMTP id d4mr21696337paz.11.1345481874116; Mon, 20 Aug 2012 09:57:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 09:57:54 -0700 (PDT) In-Reply-To: <20120820165435.GO98910@zxy.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> <20120820160344.GM98910@zxy.spb.ru> <20120820163118.GN98910@zxy.spb.ru> <20120820165435.GO98910@zxy.spb.ru> Date: Mon, 20 Aug 2012 09:57:54 -0700 X-Google-Sender-Auth: _fFD2RIP354N-PzojTxr0CoJN-4 Message-ID: From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 16:57:55 -0000 On 20 August 2012 09:54, Slawa Olhovchenkov wrote: >> Yup. Look at the channel busy statistics. YOur channel isn't busy at all. > > Oh, I am don't need utilise all bandwidth, typical use: ssh access to remote host > and lot of web traffic. And narrow uplink (~2-5Mbit/s). > > Now I do test transfer from local ftp: Right. > min avg max > tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% > (10.8 73.8 90.5 5.1) (12.2 76.7 93.2 6.8) (13.2 81.2 94.9 9.5) Right. The rx% is high as you're receiving frames. The busy count (bc%) is high because you're actively doing work on the channel. If bc% is high but rx% and tx% is low, there's some non-decodable wifi (eg too far away, or too distorted, or collision-y) non-wifi signal that's high enough to cause issues. [snip] >> Well, what do you mean by "lost traffic" ? I need some more >> information about that. > > Sometimes (may be one in 2-3 days) receiving packets on wlan0 stoped. > May be intesive traffic increase probability. > No messages in dmesg. tcpdump on wlan0 show only outgoing packets. Interface is UP. > No automatic recovery. For manual recovery I am need to kldunload/kldolad if_ath_pci. The next time it happens: * sysctl dev.ath.0.txagg=1 (I assume your interface is ath0) - that dumps some basic information about the state of the aggregation logic _AND_ the hardware TX queues; * check dmesg; * ifconfig -v wlan0 and ifconfig -v wlan0 list sta (to see if 11n is enabled). You shouldn't have to unload/reload the driver. A simple ifconfig wlan0 down ; ifconfig wlan0 up (and restarting wpa_supplicant if it was running) should be enough. (Oh, and running dhclient.) You can also enable reset+TX debugging when things hang (sysctl dev.ath.0.debug=0x3) and then do something like 'ifconfig wlan0 down'; it will then dump out the state of the hardware/software queue(s) and hopefully give me a better idea of what state the hardware/driver is in. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 17:08:15 2012 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 07B02106566C; Mon, 20 Aug 2012 17:08:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id A91B68FC12; Mon, 20 Aug 2012 17:08:14 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3VUs-000LnN-Sx; Mon, 20 Aug 2012 21:10:38 +0400 Date: Mon, 20 Aug 2012 21:10:38 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Message-ID: <20120820171038.GP98910@zxy.spb.ru> References: <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> <20120820160344.GM98910@zxy.spb.ru> <20120820163118.GN98910@zxy.spb.ru> <20120820165435.GO98910@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 17:08:15 -0000 On Mon, Aug 20, 2012 at 09:57:54AM -0700, Adrian Chadd wrote: > >> Well, what do you mean by "lost traffic" ? I need some more > >> information about that. > > > > Sometimes (may be one in 2-3 days) receiving packets on wlan0 stoped. > > May be intesive traffic increase probability. > > No messages in dmesg. tcpdump on wlan0 show only outgoing packets. Interface is UP. > > No automatic recovery. For manual recovery I am need to kldunload/kldolad if_ath_pci. > > The next time it happens: > > * sysctl dev.ath.0.txagg=1 (I assume your interface is ath0) - that > dumps some basic information about the state of the aggregation logic > _AND_ the hardware TX queues; This is one time diagnostic, not trigger logic? > * check dmesg; > * ifconfig -v wlan0 and ifconfig -v wlan0 list sta (to see if 11n is enabled). My AP don't support 11n, only 11g. > You shouldn't have to unload/reload the driver. A simple ifconfig > wlan0 down ; ifconfig wlan0 up (and restarting wpa_supplicant if it > was running) should be enough. (Oh, and running dhclient.) > > You can also enable reset+TX debugging when things hang (sysctl > dev.ath.0.debug=0x3) and then do something like 'ifconfig wlan0 down'; > it will then dump out the state of the hardware/software queue(s) and > hopefully give me a better idea of what state the hardware/driver is > in. OK. From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 20 17:09:36 2012 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 B08D9106564A for ; Mon, 20 Aug 2012 17:09:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7CEBC8FC17 for ; Mon, 20 Aug 2012 17:09:36 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so7638196pbb.13 for ; Mon, 20 Aug 2012 10:09:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0zJIfiWP5GSwAZB6ct3lDiRVofiun21rJCI3qJT/Kiw=; b=GwYTP4/UheUedfnXWvmRwLIYXwqqSGEcfkDp9LqoBddbfRK7rdiGIs0B89R8R46q/n tyImtdAGSPM/VDPAweNTWzOJY2yki5Giut9Lr47wndDESAe54gJg9iupjvo/EIhnNlZM LKt14frRXLr9CMXQYdPiSFSZiaPZl/xSuh3YV9W1bFplc6b8s0Le7+b9T59ECQ4BqSFd +PQSeYe7d98ppX4HMuC5VbchmE2zUORHdWvpIXth99fexD3ys1jm6pRp0ho4ktnKRCEV G9dYx1qAb9sjADxrCLfUp43pA09xZSTbEdZS8fQptxZuh73F91xcZLLxuXXfG6ZFUATp A77A== MIME-Version: 1.0 Received: by 10.68.231.233 with SMTP id tj9mr35987992pbc.39.1345482575748; Mon, 20 Aug 2012 10:09:35 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 10:09:35 -0700 (PDT) In-Reply-To: <20120820171038.GP98910@zxy.spb.ru> References: <20120819071403.GF98910@zxy.spb.ru> <20120820125524.GL98910@zxy.spb.ru> <20120820160344.GM98910@zxy.spb.ru> <20120820163118.GN98910@zxy.spb.ru> <20120820165435.GO98910@zxy.spb.ru> <20120820171038.GP98910@zxy.spb.ru> Date: Mon, 20 Aug 2012 10:09:35 -0700 X-Google-Sender-Auth: PM0kQo6L7pNW6bBNPc71cZ6gFNs Message-ID: From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 20 Aug 2012 17:09:36 -0000 Yup, setting 'txagg=1' is a once-off output to dmesg. Adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 21 00:50:02 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 6265D106564A; Tue, 21 Aug 2012 00:50:02 +0000 (UTC) (envelope-from honestqiao@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id DDFB88FC08; Tue, 21 Aug 2012 00:50:01 +0000 (UTC) Received: by qatn12 with SMTP id n12so3790907qat.13 for ; Mon, 20 Aug 2012 17:50:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=08tUo57KknjY/FUh00K0VzVWjjA8Bblzc5CGqgQTfao=; b=UkOXMwrWsSBqlOBM5FX6Zxrv1x6WCm/aCWTu+TP0UaAPY2x4QT1BMWvY+s0w0EblQH 06nR1NHSBGZdKBMuz9mGCPxLbAbK2ERpdKwY0eDjILXins/J/Q6YSSaW5QCuTL/1zCAM Lp8rDtqa/A4rWqEjPi+BJCY09KFMXVVwGQKHENoY5+Jt5qazm44nMhoiGsr8JrVE3Lq2 zoeTiz1BKtIEVxAC81kKx7VWeOvCK5aAtCiq0tiHTSUdm54ri12nGNOn0p3rA+Dk7bQo PLjbxX+zcU0Kpb5y4xeJFJWvXpMqsPrBuM2sYOm80/5kZUV0gB7tjevOonZ+MTa5g9QK f0zg== Received: by 10.229.122.220 with SMTP id m28mr14039589qcr.49.1345510201243; Mon, 20 Aug 2012 17:50:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.197.65 with HTTP; Mon, 20 Aug 2012 17:49:17 -0700 (PDT) In-Reply-To: <201208201829.10554.bschmidt@freebsd.org> References: <201207300139326668335@gmail.com> <201208191814.24880.bschmidt@freebsd.org> <201208201829.10554.bschmidt@freebsd.org> From: =?UTF-8?B?5LmU5qWa?= Date: Tue, 21 Aug 2012 08:49:17 +0800 Message-ID: To: Bernhard Schmidt Content-Type: multipart/mixed; boundary=0015175734a896395004c7bc012c Cc: freebsd-wireless Subject: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 21 Aug 2012 00:50:02 -0000 --0015175734a896395004c7bc012c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2012/8/21 Bernhard Schmidt : > On Monday 20 August 2012 17:24:56 =E4=B9=94=E6=A5=9A wrote: >> 2012/8/20 Bernhard Schmidt : >> > Can you try attached diff? This change is in head and an MFC >> > should fix the issue. >> >> But my src branch is stable/9. >> >> I need switch to HEAD? > > No, the patch should apply to stable/9 just fine. > > -- > Bernhard [8:48:19]root@x201i.pts/1 /usr/src # patch -p < /home/HonestQiao/Downloads/r231187.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: sys/net80211/ieee80211.h |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |--- sys/net80211/ieee80211.h (revision 231186) |+++ sys/net80211/ieee80211.h (revision 231187) -------------------------- Patching file sys/net80211/ieee80211.h using Plan A... Hunk #1 failed at 709. 1 out of 1 hunks failed--saving rejects to sys/net80211/ieee80211.h.rej done --0015175734a896395004c7bc012c Content-Type: application/octet-stream; name="ieee80211.h.rej" Content-Disposition: attachment; filename="ieee80211.h.rej" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h64a03e70 KioqKioqKioqKioqKioqCioqKiA3MDksNzM1ICoqKioKICAJSUVFRTgwMjExX0VMRU1JRF9WRU5E T1IJCT0gMjIxLAkvKiB2ZW5kb3IgcHJpdmF0ZSAqLw0KICANCiAgCS8qDQotIAkgKiA4MDIuMTFz IElFcyBiYXNlZCBvbiBEMy4wMyBzcGVjIGFuZCB3ZXJlIG5vdCBhc3NpZ25lZCBieQ0KLSAJICog QU5BLiBCZXdhcmUgY2hhbmdpbmcgdGhlbSBiZWNhdXNlIHNvbWUgb2YgdGhlbSBhcmUgYmVpbmcN Ci0gCSAqIGtlcHQgY29tcGF0aWJsZSB3aXRoIExpbnV4Lg0KICAJICovDQotIAlJRUVFODAyMTFf RUxFTUlEX01FU0hDT05GCT0gNTEsDQotIAlJRUVFODAyMTFfRUxFTUlEX01FU0hJRAkJPSA1MiwN Ci0gCUlFRUU4MDIxMV9FTEVNSURfTUVTSExJTksJPSAzNSwNCi0gCUlFRUU4MDIxMV9FTEVNSURf TUVTSENOR1NUCT0gMzYsDQotIAlJRUVFODAyMTFfRUxFTUlEX01FU0hQRUVSCT0gNTUsDQotIAlJ RUVFODAyMTFfRUxFTUlEX01FU0hDU0EJPSAzOCwNCi0gCUlFRUU4MDIxMV9FTEVNSURfTUVTSFRJ TQk9IDM5LA0KLSAJSUVFRTgwMjExX0VMRU1JRF9NRVNIQVdBS0VXCT0gNDAsDQotIAlJRUVFODAy MTFfRUxFTUlEX01FU0hCRUFDT05UCT0gNDEsDQotIAlJRUVFODAyMTFfRUxFTUlEX01FU0hQQU5O CT0gNDgsDQotIAlJRUVFODAyMTFfRUxFTUlEX01FU0hSQU5OCT0gNDksDQotIAlJRUVFODAyMTFf RUxFTUlEX01FU0hQUkVRCT0gNjgsDQotIAlJRUVFODAyMTFfRUxFTUlEX01FU0hQUkVQCT0gNjks DQotIAlJRUVFODAyMTFfRUxFTUlEX01FU0hQRVJSCT0gNzAsDQotIAlJRUVFODAyMTFfRUxFTUlE X01FU0hQWFUJPSA1MywNCi0gCUlFRUU4MDIxMV9FTEVNSURfTUVTSFBYVUMJPSA1NCwNCi0gCUlF RUU4MDIxMV9FTEVNSURfTUVTSEFICQk9IDYwLCAvKiBBYmJyZXZpYXRlZCBIYW5kc2hha2UgKi8N CiAgfTsNCiAgDQogIHN0cnVjdCBpZWVlODAyMTFfdGltX2llIHsNCi0tLSA3MDksNzQwIC0tLS0K ICAJSUVFRTgwMjExX0VMRU1JRF9WRU5ET1IJCT0gMjIxLAkvKiB2ZW5kb3IgcHJpdmF0ZSAqLw0K ICANCiAgCS8qDQorIAkgKiA4MDIuMTFzIElFcw0KKyAJICogTkI6IE9uIHZhbmlsbGEgTGludXgg c3RpbGwgSUVFRTgwMjExX0VMRU1JRF9NRVNIUEVFUiA9IDU1LA0KKyAJICogYnV0IHRoZXkgZGVm aW5lZCBhIG5ldyB3aXRoIGlkIDExNyBjYWxsZWQgUEVFUl9NR01ULg0KKyAJICogTkI6IGNvbXBs aWVzIHdpdGggb3BlbjgwMjExDQogIAkgKi8NCisgCUlFRUU4MDIxMV9FTEVNSURfTUVTSENPTkYJ PSAxMTMsDQorIAlJRUVFODAyMTFfRUxFTUlEX01FU0hJRAkJPSAxMTQsDQorIAlJRUVFODAyMTFf RUxFTUlEX01FU0hMSU5LCT0gMTE1LA0KKyAJSUVFRTgwMjExX0VMRU1JRF9NRVNIQ05HU1QJPSAx MTYsDQorIAlJRUVFODAyMTFfRUxFTUlEX01FU0hQRUVSCT0gMTE3LA0KKyAJSUVFRTgwMjExX0VM RU1JRF9NRVNIQ1NBCT0gMTE4LA0KKyAJSUVFRTgwMjExX0VMRU1JRF9NRVNIVElNCT0gMzksIC8q IFhYWDogcmVtb3ZlICovDQorIAlJRUVFODAyMTFfRUxFTUlEX01FU0hBV0FLRVcJPSAxMTksDQor IAlJRUVFODAyMTFfRUxFTUlEX01FU0hCRUFDT05UCT0gMTIwLA0KKyAJLyogMTIxLTEyNCBNTUNB T1Agbm90IGltcGxlbWVudGVkIHlldCAqLw0KKyAJSUVFRTgwMjExX0VMRU1JRF9NRVNIUEFOTgk9 IDEyNSwgLyogWFhYOiBpcyBHQU5OIG5vdywgbm90IHVzZWQgKi8NCisgCUlFRUU4MDIxMV9FTEVN SURfTUVTSFJBTk4JPSAxMjYsDQorIAkvKiAxMjcgRXh0ZW5kZWQgQ2FwYWJpbGl0aWVzICovDQor IAkvKiAxMjgtMTI5IHJlc2VydmVkICovDQorIAlJRUVFODAyMTFfRUxFTUlEX01FU0hQUkVRCT0g MTMwLA0KKyAJSUVFRTgwMjExX0VMRU1JRF9NRVNIUFJFUAk9IDEzMSwNCisgCUlFRUU4MDIxMV9F TEVNSURfTUVTSFBFUlIJPSAxMzIsDQorIAkvKiAxMzMtMTM2IHJlc2VydmVkICovDQorIAlJRUVF ODAyMTFfRUxFTUlEX01FU0hQWFUJPSAxMzcsDQorIAlJRUVFODAyMTFfRUxFTUlEX01FU0hQWFVD CT0gMTM4LA0KKyAJSUVFRTgwMjExX0VMRU1JRF9NRVNIQUgJCT0gNjAsIC8qIFhYWDogcmVtb3Zl ICovDQogIH07DQogIA0KICBzdHJ1Y3QgaWVlZTgwMjExX3RpbV9pZSB7DQo= --0015175734a896395004c7bc012c-- From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 21 18:47:22 2012 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 74DA71065676 for ; Tue, 21 Aug 2012 18:47:22 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E2FDD8FC1A for ; Tue, 21 Aug 2012 18:47:21 +0000 (UTC) Received: by bkcje9 with SMTP id je9so88241bkc.13 for ; Tue, 21 Aug 2012 11:47:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=tpq1t6m3lGgeQvZUXMW5Ggp72ZaqoLBwabvj1YjnIPM=; b=hZu6AHId0QEQ5TTOujtacoWNM3e5HoyzmjMaRddLE6WY1xlOvO3ez67zJGi84MSYeU TGLdtT/iwEANYjtA8oKPjwEcAatVP9HLqITB7g68pI1GLObEVLAK+PpTFQgED0QMCwXB e/xj65nKRLT2/WLoMT4Ym4vZjr5UBZ97qGc4+V6ERSF5ovuQlOTXSm7wvj51Lx3j3xxJ wt/nLL90UWBVRzquABh+luTr/fMjFf1QD2aKi625fhlOr0KoDJq6c1Gl8dFZbCVhjNeP 28vur9BVF7QTXrb49FhmQR284sCgPiBafbV72W4U3cE3pz1VWTE7z+8lKKrpnGHh9jlg C+VQ== Received: by 10.204.8.84 with SMTP id g20mr822025bkg.126.1345574840422; Tue, 21 Aug 2012 11:47:20 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-067-209-170.pools.arcor-ip.net. [88.67.209.170]) by mx.google.com with ESMTPS id c18sm1369306bkv.8.2012.08.21.11.47.19 (version=SSLv3 cipher=OTHER); Tue, 21 Aug 2012 11:47:19 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: =?utf-8?q?=E4=B9=94=E6=A5=9A?= Date: Tue, 21 Aug 2012 20:47:50 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.7.4; amd64; ; ) References: <201207300139326668335@gmail.com> <201208201829.10554.bschmidt@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201208212047.50852.bschmidt@freebsd.org> X-Gm-Message-State: ALoCoQlbiwJtFGvvgSgJhazALoG2x8rPgc0oo4Mad6Vu8Oujxwz8HITXzJKqB7EedXRojXvuFXqa Cc: freebsd-wireless Subject: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 21 Aug 2012 18:47:22 -0000 On Tuesday 21 August 2012 02:49:17 =E4=B9=94=E6=A5=9A wrote: > 2012/8/21 Bernhard Schmidt : > > On Monday 20 August 2012 17:24:56 =E4=B9=94=E6=A5=9A wrote: > >> 2012/8/20 Bernhard Schmidt : > >> > Can you try attached diff? This change is in head and an MFC > >> > should fix the issue. > >> > >> But my src branch is stable/9. > >> > >> I need switch to HEAD? > > > > No, the patch should apply to stable/9 just fine. > > > > -- > > Bernhard >=20 > [8:48:19]root@x201i.pts/1 /usr/src # patch -p < > /home/HonestQiao/Downloads/r231187.diff > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |Index: sys/net80211/ieee80211.h > |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > |--- sys/net80211/ieee80211.h (revision 231186) > |+++ sys/net80211/ieee80211.h (revision 231187) > -------------------------- > Patching file sys/net80211/ieee80211.h using Plan A... > Hunk #1 failed at 709. > 1 out of 1 hunks failed--saving rejects to sys/net80211/ieee80211.h.rej > done Is your source up 2 date and clean? It applies cleanly here. Check with svn up and svn stat I guess. amy:sys/net80211% pwd /home/bschmidt/src/svn/freebsd/stable/9/sys/net80211 amy:sys/net80211% patch -p2 < ~/tmp/r231187.diff Hmm... Looks like a unified diff to me... The text leading up to this was: =2D------------------------- |Index: sys/net80211/ieee80211.h |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |--- sys/net80211/ieee80211.h (revision 231186) |+++ sys/net80211/ieee80211.h (revision 231187) =2D------------------------- Patching file ieee80211.h using Plan A... Hunk #1 succeeded at 709. done amy:sys/net80211% =2D-=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 03:38:50 2012 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 602F9106566C; Wed, 22 Aug 2012 03:38:50 +0000 (UTC) (envelope-from honestqiao@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id DD8128FC19; Wed, 22 Aug 2012 03:38:49 +0000 (UTC) Received: by qcsg15 with SMTP id g15so435602qcs.13 for ; Tue, 21 Aug 2012 20:38:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=oa922ZuEJz+nAbjAw67ycV36QUlQg17yMLk5+3xVtWw=; b=gvwgKNUyU7JTkzf8iMd+qfEV3HbHbbA6Gv/OVAdj/KtYCzhaxz4QiMcBYs+5aI2qzc QDQCMwCAdXElshGqumCdaMRZXC8Kj47PLW+2IqYZWueIE4CrtBn4ftvoibX7NSo0AUMR vGDzshEnGsPUU7++HUUIevNNmmmtpNhSqYhcgwptc1mshrVO9je3mtRyp0tHLF4nlgSs rikEb6SvvsyKC0AO17JICGKPKLW+25dXRPhmcMyao4Dw03lamp463wbpkaTGZF6vgWR7 U6uj2yQ+62trz+EBrr8CTqkC9ntzHvaOJyqXMy+AVh55II80PPDxmwDu3qcKWSy/viPd arHw== Received: by 10.224.188.76 with SMTP id cz12mr13176063qab.12.1345606723607; Tue, 21 Aug 2012 20:38:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.197.65 with HTTP; Tue, 21 Aug 2012 20:38:03 -0700 (PDT) In-Reply-To: <201208212047.50852.bschmidt@freebsd.org> References: <201207300139326668335@gmail.com> <201208201829.10554.bschmidt@freebsd.org> <201208212047.50852.bschmidt@freebsd.org> From: =?UTF-8?B?5LmU5qWa?= Date: Wed, 22 Aug 2012 11:38:03 +0800 Message-ID: To: Bernhard Schmidt Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless Subject: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 22 Aug 2012 03:38:50 -0000 2012/8/22 Bernhard Schmidt : > On Tuesday 21 August 2012 02:49:17 =C7=C7=B3=FE wrote: >> 2012/8/21 Bernhard Schmidt : >> > On Monday 20 August 2012 17:24:56 =C7=C7=B3=FE wrote: >> >> 2012/8/20 Bernhard Schmidt : >> >> > Can you try attached diff? This change is in head and an MFC >> >> > should fix the issue. >> >> >> >> But my src branch is stable/9. >> >> >> >> I need switch to HEAD? >> > >> > No, the patch should apply to stable/9 just fine. >> > >> > -- >> > Bernhard >> >> [8:48:19]root@x201i.pts/1 /usr/src # patch -p < >> /home/HonestQiao/Downloads/r231187.diff >> Hmm... Looks like a unified diff to me... >> The text leading up to this was: >> -------------------------- >> |Index: sys/net80211/ieee80211.h >> |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> |--- sys/net80211/ieee80211.h (revision 231186) >> |+++ sys/net80211/ieee80211.h (revision 231187) >> -------------------------- >> Patching file sys/net80211/ieee80211.h using Plan A... >> Hunk #1 failed at 709. >> 1 out of 1 hunks failed--saving rejects to sys/net80211/ieee80211.h.rej >> done > > Is your source up 2 date and clean? It applies cleanly here. Check > with svn up and svn stat I guess. > > amy:sys/net80211% pwd > /home/bschmidt/src/svn/freebsd/stable/9/sys/net80211 > amy:sys/net80211% patch -p2 < ~/tmp/r231187.diff > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |Index: sys/net80211/ieee80211.h > |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > |--- sys/net80211/ieee80211.h (revision 231186) > |+++ sys/net80211/ieee80211.h (revision 231187) > -------------------------- > Patching file ieee80211.h using Plan A... > Hunk #1 succeeded at 709. > done > amy:sys/net80211% > > -- > Bernhard [11:28:00]root@x201i.pts/2 /usr/src # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 239552 Node Kind: directory Schedule: normal Last Changed Author: kevlo Last Changed Rev: 239549 Last Changed Date: 2012-08-22 08:59:17 +0800 (Wed, 22 Aug 2012) [11:28:04]root@x201i.pts/2 /usr/src # svn stat [11:28:10]root@x201i.pts/2 /usr/src # svn log -r 231180:231190 ------------------------------------------------------------------------ r231188 | mav | 2012-02-08 15:30:48 +0800 (Wed, 08 Feb 2012) | 10 lines There hasn't r231186 for stable/9. The proximal version is r231188. [11:31:38]root@x201i.pts/2 /usr/src #svn up -r r231188 ...... Updated to revision 231188. [11:31:57]root@x201i.pts/2 /usr/src # cd sys/net80211 [11:31:59]root@x201i.pts/2 sys/net80211 # patch -p2 < /home/HonestQiao/Downloads/r231187.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: sys/net80211/ieee80211.h |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |--- sys/net80211/ieee80211.h (revision 231186) |+++ sys/net80211/ieee80211.h (revision 231187) -------------------------- Patching file ieee80211.h using Plan A... Hunk #1 failed at 709. 1 out of 1 hunks failed--saving rejects to ieee80211.h.rej done [11:33:43]root@x201i.pts/2 sys/net80211 # rm ieee80211.h.* remove ieee80211.h.orig? y remove ieee80211.h.rej? y [11:33:57]root@x201i.pts/2 sys/net80211 # cd /usr/src/ [11:34:09]root@x201i.pts/2 /usr/src # svn up ..... Updated to revision 239552. [11:35:46]root@x201i.pts/2 /usr/src # cd sys/net80211 [11:36:01]root@x201i.pts/2 sys/net80211 # patch -p2 < /home/HonestQiao/Downloads/r231187.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: sys/net80211/ieee80211.h |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |--- sys/net80211/ieee80211.h (revision 231186) |+++ sys/net80211/ieee80211.h (revision 231187) -------------------------- Patching file ieee80211.h using Plan A... Hunk #1 failed at 709. 1 out of 1 hunks failed--saving rejects to ieee80211.h.rej done From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 05:15: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 B8336106578A; Wed, 22 Aug 2012 05:15:05 +0000 (UTC) (envelope-from prvs=5741372ef=Brett.Wright@cooperindustries.com) Received: from cooperlighting-sw.cooperlighting.com (cooperlighting-sw.cooperlighting.com [216.130.131.68]) by mx1.freebsd.org (Postfix) with ESMTP id 1CE7C8FC08; Wed, 22 Aug 2012 05:15:04 +0000 (UTC) Authentication-Results: cooperlighting-sw.cooperlighting.com; dkim=neutral (message not signed) header.i=none X-IronPort-AV: E=Sophos;i="4.77,807,1336363200"; d="scan'208";a="66144626" Received: from cipt0174.nam.ci.root ([10.132.108.174]) by cooperlighting-sw.cooperlighting.com with ESMTP; 22 Aug 2012 01:14:57 -0400 Received: from APEVS1.AP.CI.ROOT ([10.180.2.22]) by cipt0174.NAM.CI.ROOT with Microsoft SMTPSVC(6.0.3790.4675); Wed, 22 Aug 2012 01:14:57 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable x-cr-hashedpuzzle: DpcT D9ng HDA8 HT/Q WXLv Zf7O ZoXp aWfr eHhZ erCT fwf0 f/OJ ggQm kAGb kFy9 kL4a; 3; YQBkAHIAaQBhAG4AQABmAHIAZQBlAGIAcwBkAC4AbwByAGcAOwBmAHIAZQBlAGIAcwBkAC0AdwBpAHIAZQBsAGUAcwBzAEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnADsAdwA4AGgAZABrAGkAbQBAAGcAbQBhAGkAbAAuAGMAbwBtAA==; Sosha1_v1; 7; {03B1FE79-636C-4311-8EBF-DE799D6C327A}; YgByAGUAdAB0AC4AdwByAGkAZwBoAHQAQABjAG8AbwBwAGUAcgBpAG4AZAB1AHMAdAByAGkAZQBzAC4AYwBvAG0A; Wed, 22 Aug 2012 05:14:13 GMT; UgBFADoAIABBAHQAaABlAHIAbwBzACAARABGAFMAIAByAGEAZABhAHIAIABkAGUAdABlAGMAdABpAG8AbgA= x-cr-puzzleid: {03B1FE79-636C-4311-8EBF-DE799D6C327A} Content-class: urn:content-classes:message Date: Wed, 22 Aug 2012 13:14:13 +0800 Message-ID: <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Atheros DFS radar detection Thread-Index: Ac15u1a6i/Kl33a6TICuLrtoZ0wD7QGTmgoA References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root> From: "Wright, Brett" To: "Adrian Chadd" , "Kim Culhan" X-OriginalArrivalTime: 22 Aug 2012 05:14:57.0992 (UTC) FILETIME=[12B9BC80:01CD8025] Cc: freebsd-wireless@freebsd.org Subject: RE: Atheros DFS radar detection 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, 22 Aug 2012 05:15:12 -0000 > -----Original Message----- > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf > Of Adrian Chadd >=20 > Brett, did you have any luck? >=20 > I'll be in a position to test out with some AR5212 era NICs this week. >=20 > Adrian > Hi Adrian, I have been mucking around with the radar parameters for several days now. In order to get reasonably low levels of false detects I need very aggressive (at least I *think* they are aggressive) values for the radar parameters. For example: FIRPWR: -33 RRSSI: 45 HEIGHT: 28 PRSSI: 22 INBAND: 6 However, the meaning of these parameters is still a little unclear to me. I have read the patent document many times but there is still a lot of information I do not know. I would be prepared to bet that Atheros has documentation describing the above parameters with a lot more clarity. For example , just to pick one of the parameters FIRPWR: According to the comment for this field it is a threshold that the signal power must exceed, but it's default value is -41dBm. Now -41dBm is VERY strong! Also, my experimentally derived value of -31dBm is way stronger still. Certainly in my test environment the strongest signals are around -55dBm (way weaker than either of these values). This really highlights to me that I am "missing" something... Also, the parameter I found makes the biggest difference to my false detects is RRSSI which is "the threshold that the RSSI must exceed when AGC is OK..." etc. Is this a SNR? If so 45dB (my setting for this parameter) with a noise floor around -95dBm would equate to an absolute RSSI of -50dBm. Am I reading this correctly? And if it is an SNR, then why is FIRPWR apparently an actual RSSI (i.e. absolute level). Is everything other than FIRPWR an SNR?=20 Finally, I haven't yet taken the next step of actually injecting radar pulses, but my suspicion is that with such aggressive parameters that actual radar detection according to the regulatory test patterns will fail. I do realize that the difficulties I'm having are due to my lack of information and understanding, however any light you may be able to shed would be greatly appreciated. Thanks=20 Brett From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 05:39:08 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 C90E0106566B for ; Wed, 22 Aug 2012 05:39:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 82FA98FC0A for ; Wed, 22 Aug 2012 05:39:08 +0000 (UTC) Received: by obbun3 with SMTP id un3so1122067obb.13 for ; Tue, 21 Aug 2012 22:39:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=DJN1+mmLbNzS6Y8vAqVX02us5/MXPR/xIFLLxdADWuI=; b=UyN9cbr9ASpBmbxy1CFYUCcByWeVGYzHlEhJdjvQ7Xeq8riA9qKUg9+Se9JFtFBCsz FGvqcCvRjqnr9OchQCAqXqXOGv/FEt5JOXWpiNhA5h1EG4uukX/O/vzWAi2pbyXRcPGn P0+UsqkepjhCcYX7J94TWYw5ZR1fYOKYHDqjE6Wwp2rx3b0CzLWPaTTiRSMelfVJs8Kk uwT0TPyfoLeCNwoNgkRvuoDDliwmrrSHD6ZaE/ow2eRlW2ngBfKvikf5MmX3xsDvnHEg HlwygfLY9+TUcZyUsnxiGh/qCPXN4A3IIwpoN5nR9n0djtvi2uDzApNtGxGhEtmgATCg uTkQ== MIME-Version: 1.0 Received: by 10.60.10.194 with SMTP id k2mr14628382oeb.127.1345613947688; Tue, 21 Aug 2012 22:39:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.76.8.98 with HTTP; Tue, 21 Aug 2012 22:39:07 -0700 (PDT) Received: by 10.76.8.98 with HTTP; Tue, 21 Aug 2012 22:39:07 -0700 (PDT) In-Reply-To: <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> Date: Tue, 21 Aug 2012 22:39:07 -0700 X-Google-Sender-Auth: 2hCh7YC3nL-F3arqxV2eQLQqt0s Message-ID: From: Adrian Chadd To: "Wright, Brett" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: RE: Atheros DFS radar detection 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, 22 Aug 2012 05:39:08 -0000 Oh. Disable ANI too. Adrian On Aug 21, 2012 10:15 PM, "Wright, Brett" wrote: > > -----Original Message----- > > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf > > Of Adrian Chadd > > > > Brett, did you have any luck? > > > > I'll be in a position to test out with some AR5212 era NICs this week. > > > > Adrian > > > > Hi Adrian, > > I have been mucking around with the radar parameters for several days > now. In order to get reasonably low levels of false detects I need very > aggressive (at least I *think* they are aggressive) values for the radar > parameters. For example: > > FIRPWR: -33 > RRSSI: 45 > HEIGHT: 28 > PRSSI: 22 > INBAND: 6 > > However, the meaning of these parameters is still a little unclear to > me. I have read the patent document many times but there is still a lot > of information I do not know. I would be prepared to bet that Atheros > has documentation describing the above parameters with a lot more > clarity. For example , just to pick one of the parameters FIRPWR: > According to the comment for this field it is a threshold that the > signal power must exceed, but it's default value is -41dBm. Now -41dBm > is VERY strong! Also, my experimentally derived value of -31dBm is way > stronger still. Certainly in my test environment the strongest signals > are around -55dBm (way weaker than either of these values). This really > highlights to me that I am "missing" something... > > Also, the parameter I found makes the biggest difference to my false > detects is RRSSI which is "the threshold that the RSSI must exceed when > AGC is OK..." etc. Is this a SNR? If so 45dB (my setting for this > parameter) with a noise floor around -95dBm would equate to an absolute > RSSI of -50dBm. Am I reading this correctly? And if it is an SNR, then > why is FIRPWR apparently an actual RSSI (i.e. absolute level). Is > everything other than FIRPWR an SNR? > > Finally, I haven't yet taken the next step of actually injecting radar > pulses, but my suspicion is that with such aggressive parameters that > actual radar detection according to the regulatory test patterns will > fail. > > I do realize that the difficulties I'm having are due to my lack of > information and understanding, however any light you may be able to shed > would be greatly appreciated. > > Thanks > Brett > > From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 05:50: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 6E1B61065672; Wed, 22 Aug 2012 05:50:53 +0000 (UTC) (envelope-from prvs=5741372ef=Brett.Wright@cooperindustries.com) Received: from cooperlighting-sw.cooperlighting.com (cooperlighting-sw.cooperlighting.com [216.130.131.68]) by mx1.freebsd.org (Postfix) with ESMTP id 128D48FC0A; Wed, 22 Aug 2012 05:50:52 +0000 (UTC) Authentication-Results: cooperlighting-sw.cooperlighting.com; dkim=neutral (message not signed) header.i=none X-IronPort-AV: E=Sophos;i="4.77,808,1336363200"; d="scan'208,217";a="66146049" Received: from cipt0175.nam.ci.root ([10.132.108.175]) by cooperlighting-sw.cooperlighting.com with ESMTP; 22 Aug 2012 01:50:51 -0400 Received: from APEVS1.AP.CI.ROOT ([10.180.2.22]) by cipt0175.NAM.CI.ROOT with Microsoft SMTPSVC(6.0.3790.4675); Wed, 22 Aug 2012 01:50:52 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 22 Aug 2012 13:50:48 +0800 Message-ID: <475A4E02EFF4724A9E58F55A56AC13160661E783@APEVS1.ap.ci.root> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Atheros DFS radar detection Thread-Index: Ac2AKHSyV2ZnZSYfTvaN4bWNop6UhQAAYDJQ References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root><475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> From: "Wright, Brett" To: "Adrian Chadd" X-OriginalArrivalTime: 22 Aug 2012 05:50:52.0313 (UTC) FILETIME=[16CD0890:01CD802A] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: RE: Atheros DFS radar detection 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, 22 Aug 2012 05:50:53 -0000 Yes I've had ANI disabled all along... =20 Thanks =20 From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf Of Adrian Chadd Sent: Wednesday, 22 August 2012 3:39 PM To: Wright, Brett Cc: freebsd-wireless@freebsd.org; Kim Culhan Subject: RE: Atheros DFS radar detection =20 Oh. Disable ANI too. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 10:18:57 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 9AB0B1065670 for ; Wed, 22 Aug 2012 10:18:57 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id C7A558FC16 for ; Wed, 22 Aug 2012 10:18:56 +0000 (UTC) Received: by lage12 with SMTP id e12so544307lag.13 for ; Wed, 22 Aug 2012 03:18:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=kpk0HqZB9sFVYxEwmtnKyRSN87sk0XlUZe07CfRLar0=; b=TGcFwTx53NLTLOMHEm2f4GsrNxpBVyLuzZnbkaZ0WfZYqO+LTfDy2fEUD7lMrdqe3B GRZvZGEAmTxFsfzgNsZyjNalsHwKxB7wWAzEyPn/D/klwQfywE7HTPoHJZ0BypvM5o5e SXEl58DPsLDQ9oGts8VhBONPznn2yXiqn4X3H/m4UgMdxdFS9oF3hdlJ29Sk08e4c4B8 fPRXqm5RwT+jjY/LBMU7Gh6b8QjEVw9blWBe3YwSh3DXv8OxCKEqf5F0G+JbfR+9nkBl kbqLZzBeMqBBlDHPqN8STaTcHmEjGj/MiH5NiLpZNuMoCmlVpPgoItDDfFNrwsjxzPww xSkQ== MIME-Version: 1.0 Received: by 10.112.82.42 with SMTP id f10mr9025124lby.95.1345630735348; Wed, 22 Aug 2012 03:18:55 -0700 (PDT) Sender: bschmidt@techwires.net Received: by 10.152.123.200 with HTTP; Wed, 22 Aug 2012 03:18:55 -0700 (PDT) X-Originating-IP: [79.140.39.245] In-Reply-To: References: <201207300139326668335@gmail.com> <201208201829.10554.bschmidt@freebsd.org> <201208212047.50852.bschmidt@freebsd.org> Date: Wed, 22 Aug 2012 12:18:55 +0200 X-Google-Sender-Auth: VgaXoCEoaYhznVr8IxHQGudTs4o Message-ID: From: Bernhard Schmidt To: =?UTF-8?B?5LmU5qWa?= Content-Type: multipart/mixed; boundary=f46d04016a97fab33c04c7d811ad X-Gm-Message-State: ALoCoQnO+Kzq7kpXc3yoOCbURs4DaviVZwaTqOj4l2mmywfcun+YIjLfkWNOPv9hXCmSwSa2AGz/ X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless Subject: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 22 Aug 2012 10:18:57 -0000 --f46d04016a97fab33c04c7d811ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Aug 22, 2012 at 5:38 AM, =E4=B9=94=E6=A5=9A = wrote: > [11:33:57]root@x201i.pts/2 sys/net80211 # cd /usr/src/ > [11:34:09]root@x201i.pts/2 /usr/src # svn up > ..... > Updated to revision 239552. > > [11:35:46]root@x201i.pts/2 /usr/src # cd sys/net80211 > [11:36:01]root@x201i.pts/2 sys/net80211 # patch -p2 < > /home/HonestQiao/Downloads/r231187.diff > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |Index: sys/net80211/ieee80211.h > |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > |--- sys/net80211/ieee80211.h (revision 231186) > |+++ sys/net80211/ieee80211.h (revision 231187) > -------------------------- > Patching file ieee80211.h using Plan A... > Hunk #1 failed at 709. > 1 out of 1 hunks failed--saving rejects to ieee80211.h.rej > done Is there Windows stuff involved which might change line breaks? amy:stable/9% pwd /home/bschmidt/src/svn/freebsd/stable/9 amy:stable/9% svn up Updating '.': At revision 239563. amy:stable/9% svn stat sys/net80211 amy:stable/9% md5 sys/net80211/ieee80211.h MD5 (sys/net80211/ieee80211.h) =3D f3cc66ca7ab81b3c63d1c1fd95806624 amy:stable/9% md5 ~/tmp/r231187.diff MD5 (/home/bschmidt/tmp/r231187.diff) =3D e2c5762997088ee1857983a99ddf80bc amy:stable/9% patch -p0 < ~/tmp/r231187.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: sys/net80211/ieee80211.h |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |--- sys/net80211/ieee80211.h (revision 231186) |+++ sys/net80211/ieee80211.h (revision 231187) -------------------------- Patching file sys/net80211/ieee80211.h using Plan A... Hunk #1 succeeded at 709. done I've attached the patched ieee80211.h --=20 Bernhard --f46d04016a97fab33c04c7d811ad-- From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 12:49:57 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 3D6841065673 for ; Wed, 22 Aug 2012 12:49:57 +0000 (UTC) (envelope-from dmarion.freebsd@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 BE0AE8FC1D for ; Wed, 22 Aug 2012 12:49:56 +0000 (UTC) Received: by eeke52 with SMTP id e52so360210eek.13 for ; Wed, 22 Aug 2012 05:49:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version:x-mailer; bh=AIyKLA/fBB7xBvhn4M4uNRAFgEn4+MHIdMigfeZ+ou0=; b=lqf8AzpCBQYfXrJC8P2JRG3wh2IkaaUx7+uonOcWno/Uj+MUM12n1YRQ+i6QhaHlm9 JZH726sZ6jJYDF1Tles/UPLAAY8lFJbyuwC7VjvE7jj+n6dnHGfM65WyL96QmShtUVWA GYGLX+SgX3qT0Yw14WO7sUEJIQcbN2TZOH8pFV0ZXgMsD5618Uj5BE5ZbIQktTYbeW8q y9yicH1x/9nuhaFriYSd+6QuGz8y13w6kk8XkUw+Zm5QWHiE6CmdlC0q5qH6bwhTvGT3 jaUqBEm6F98FK+tVyA+8e5EwsSb7IBLt6GSdzj2gnYq3lB11H/iWgN24KrzSLAvnGPIR MpzA== Received: by 10.14.204.200 with SMTP id h48mr18391890eeo.7.1345639795621; Wed, 22 Aug 2012 05:49:55 -0700 (PDT) Received: from [192.168.123.4] (cpe-109-60-76-181.zg3.cable.xnet.hr. [109.60.76.181]) by mx.google.com with ESMTPS id 45sm12707925eeb.8.2012.08.22.05.49.53 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2012 05:49:54 -0700 (PDT) Sender: Damjan Marion From: Damjan Marion Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <77FB5910-3BF6-4B05-83C6-37854203A798@FreeBSD.org> Date: Wed, 22 Aug 2012 14:49:51 +0200 To: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) X-Mailer: Apple Mail (2.1485) Subject: 802.15.4 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, 22 Aug 2012 12:49:57 -0000 Hi, I wonder if anybody did some work to support 802.15.4/6LoWPAN on FreeBSD. Google doesn't give any records... Damjan From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 13:32:29 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 B1821106566B for ; Wed, 22 Aug 2012 13:32:29 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2C29B8FC14 for ; Wed, 22 Aug 2012 13:32:28 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so780405lbb.13 for ; Wed, 22 Aug 2012 06:32:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=yj/wfRoCI84a45C7Z8QUbQI6XHCmwNJbKnEs0l/BxKQ=; b=KMW0Ui2GSuckBDdWdsIgWNOLXotq0/Y++Ku0HEki/uC5hAyFk75SELn9Qwo00cPxEg tJiUvuSARMhOYKeYN59pomqpxkbwgiV+H1dpZjqw4AfxzMlxLmjUUfhIRvvRtd3+FvNn 6WV8hnUNGdvjUbHEubFCNRznyUnhH7d069ySqYELgiUWpGFkNB3PUXfRxvd3k+TklK7A lUmeFdWD66JA0NSYH+IoetloStuNpG6rgknZfEkKK2DK6RJLpm4xjMgG89XpE8wG1zLW 9svhdUN0HUql8ggD2iPk7izV3pTuVkRubybGqp23XXWX8MWNvb9+UYlP3grbbFQoU8R7 E6/Q== MIME-Version: 1.0 Received: by 10.112.43.98 with SMTP id v2mr9206854lbl.1.1345642347719; Wed, 22 Aug 2012 06:32:27 -0700 (PDT) Received: by 10.152.123.200 with HTTP; Wed, 22 Aug 2012 06:32:27 -0700 (PDT) X-Originating-IP: [79.140.39.245] In-Reply-To: <77FB5910-3BF6-4B05-83C6-37854203A798@FreeBSD.org> References: <77FB5910-3BF6-4B05-83C6-37854203A798@FreeBSD.org> Date: Wed, 22 Aug 2012 15:32:27 +0200 Message-ID: From: Bernhard Schmidt To: Damjan Marion Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmhNagX+wI3a4wBQ4/NlCRgzpyPkPUgtzpY/uxZYmNgirrImyKB/ZbZ9oxVLIk17iJGf2jH Cc: freebsd-wireless@freebsd.org Subject: Re: 802.15.4 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, 22 Aug 2012 13:32:29 -0000 On Wed, Aug 22, 2012 at 2:49 PM, Damjan Marion wrote: > > > Hi, > > I wonder if anybody did some work to support 802.15.4/6LoWPAN on FreeBSD. > Google doesn't give any records... That doesn't ring a bell, ZigBee did though. But no, I'm not aware of anyone having done some work in that area. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 18:25: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 A8B8B106564A for ; Wed, 22 Aug 2012 18:25:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 768DD8FC14 for ; Wed, 22 Aug 2012 18:25:09 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so1917637pbb.13 for ; Wed, 22 Aug 2012 11:25:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PnCsNaocRWGAHItdT1lE+YXVnBGQG8Hin+jaxfeC238=; b=OHxwiwKW5IWE0JOGYEx/cYkVmbNjr7ORM4OCxSUeBsfzOoi2BQ7kgLsYcvWXbMuNdj 97Zv/MiO605fa4CRdT3luoSA5y7+AmQi2SnDmCjBdjmznOGUYzKS3CYGQlk3afONX2ol rWFSNnQ6Nnel2fjw7dhUzeo5Eyg/f5DuzZd7gVZPrIUA6cS5N7ZN48JEf0kdyHnEGvXL DUiouF3tSykOZn2iavTf29poHY9G5DWdOwpy0TavFGT7fapPrylKZQThJqHEKC+m+6sp KBzRV+zRQhv7dXr+XJ+fP/3yBCbJcOmRv3D5oW9nYbvwhkfsONMhMLkKG9hyb5hVku7G Lp+g== MIME-Version: 1.0 Received: by 10.68.236.102 with SMTP id ut6mr54866355pbc.113.1345659908886; Wed, 22 Aug 2012 11:25:08 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Wed, 22 Aug 2012 11:25:08 -0700 (PDT) In-Reply-To: <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> Date: Wed, 22 Aug 2012 11:25:08 -0700 X-Google-Sender-Auth: sI8mzNbvLWMi5o2ucbfFR3sL0Zc Message-ID: From: Adrian Chadd To: "Wright, Brett" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: Re: Atheros DFS radar detection 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, 22 Aug 2012 18:25:09 -0000 Hm, let me have a (re)-read of what we have here.. Your false detects - are they long? short? Do they have 0 or no duration? That'll at least hint at what's going on (ie, triggering on out of band or in-band stuff; whether it's triggering on 802.11 frames or not.) firpwr is the threshold for power estimation. The power estimation occurs _after_ the AGC (ie, it's the size of the signal _after_ the AGC has had a few tries at it.) rrssi is the threshold for long (ie, can do AGC changes) detection. The RSSI has to be above this for radar "signal" to be considered occuring. Decreasing it will increase false detects but allow longer, weaker radar pulses. prssi is the threshold for short (ie, can't do AGC changes) detection ("pulse"). Once there's an AGC change, the RSSI needs to be below this value for the event to be considered a pulse instead of a long radar event. The Atheros NICs use relative signal levels rather than absolute levels. It's all relative to what the noise floor is. So as long as the hardware sees a good noise floor (ie, there's no spurs, 100% congestion, etc) the RSSI will be relative to something sane (eg ~ 95dBm) and you can _almost_ treat it as an absolute level. But, you really shouldn't. It also means if the NF value is higher for some reason, the RSSI values will change and the parameters will also change. The whole point of tuning the PRSSI/RSSI/Firpwr is to try and make the hardware detect radar pulses at -62dBm at the device input. This depends upon the input antenna and any amplifiers. This is why it's tricky as hell to get right. :-) I'm going to throw an AR5212 into my laptop now and see what errors I get. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 19:28:51 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BC0E1065670; Wed, 22 Aug 2012 19:28:51 +0000 (UTC) (envelope-from bschmidt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 608078FC19; Wed, 22 Aug 2012 19:28:51 +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 q7MJSpMU055473; Wed, 22 Aug 2012 19:28:51 GMT (envelope-from bschmidt@freefall.freebsd.org) Received: (from bschmidt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7MJSpSb055469; Wed, 22 Aug 2012 19:28:51 GMT (envelope-from bschmidt) Date: Wed, 22 Aug 2012 19:28:51 GMT Message-Id: <201208221928.q7MJSpSb055469@freefall.freebsd.org> To: bschmidt@FreeBSD.org, freebsd-wireless@FreeBSD.org, bschmidt@FreeBSD.org From: bschmidt@FreeBSD.org Cc: Subject: Re: kern/169433: [iwn] iwn(4) doesn't support 6235 chip. 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, 22 Aug 2012 19:28:51 -0000 Synopsis: [iwn] iwn(4) doesn't support 6235 chip. Responsible-Changed-From-To: freebsd-wireless->bschmidt Responsible-Changed-By: bschmidt Responsible-Changed-When: Wed Aug 22 19:28:35 UTC 2012 Responsible-Changed-Why: over to me http://www.freebsd.org/cgi/query-pr.cgi?pr=169433 From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 19:36:12 2012 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 CF3121065674 for ; Wed, 22 Aug 2012 19:36:12 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4D49C8FC21 for ; Wed, 22 Aug 2012 19:36:11 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1221504bkc.13 for ; Wed, 22 Aug 2012 12:36:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:subject:date:user-agent:references:in-reply-to:cc :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=JHqHfpd8fcImfTdjtiBLL7n2OuDP5Ya7uIarIbDTa7U=; b=pnx0lOhgzaIrHxlbs/RXggheWPia6tWFHS552jVPjLw58uEkXnGiDYZFGtHFhSWy0Z 8igHrXTn0LhlQC3WiJsnKXbh5vGCqDjqDfhrqR6a5pqm42/0D8+ASgI89++i8kweWWkl CmjUHoRArs4MNNHr0oBUAIOYT5KsBsd1ydam/HSxGcxt352rCDDFDK2WzuOP8C54w6Dg JCQtNs5tMIDaJ2h7pdTbwgcTtXBhDZDvpNpymWQyn12CUiBDG+9FhpMWjH1jZItq1irI eEQi7qBZ2CV0qkedgO3zPEMjrHz1UD7dcVFkG1D6vJf7kwz2nQy3L5FqzjrWpZeHqZkX r6vQ== Received: by 10.204.130.211 with SMTP id u19mr6875969bks.24.1345664170021; Wed, 22 Aug 2012 12:36:10 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-178-002-174-033.pools.arcor-ip.net. [178.2.174.33]) by mx.google.com with ESMTPS id 14sm3375859bkq.12.2012.08.22.12.36.08 (version=SSLv3 cipher=OTHER); Wed, 22 Aug 2012 12:36:09 -0700 (PDT) From: Bernhard Schmidt To: freebsd-wireless@freebsd.org Date: Wed, 22 Aug 2012 21:36:45 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-RC1; KDE/4.7.4; amd64; ; ) References: <201208051530.q75FU5d1040895@freefall.freebsd.org> In-Reply-To: <201208051530.q75FU5d1040895@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201208222136.45637.bschmidt@techwires.net> X-Gm-Message-State: ALoCoQmNY7I2pXL9euaV7fU0Lg/CVtSF1N7IElsZyX1CGBRyeSTmPC21VBNljnrP9nCxl8mBWU03 Cc: Alexander Motin , Ron McDowell Subject: Re: kern/169433: [iwn] iwn(4) doesn't support 6235 chip. 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, 22 Aug 2012 19:36:12 -0000 On Sunday 05 August 2012 17:30:05 Ron McDowell wrote: > I have the same [I think] card in a new Samsung NP550P5C-T01US with > slightly different parameters: This chipset is available with 2 different IDs, 0x088e and 0x088f, both are handled equally though. I guess that the only difference is that one is half-size card the other full-size. -- Working on it. I should receive one of those cards by the end of this week. The issue is that simply adding the device IDs is not enough to get it going. It requires a new firmware which is incompatible to the driver in it's current state. I start asap once I've got the hardware and I hope to be able to provide a solution soon. I'll keep you posted. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 20:31:59 2012 Return-Path: Delivered-To: wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86590106566B; Wed, 22 Aug 2012 20:31:59 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5B8B48FC25; Wed, 22 Aug 2012 20:31: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 q7MKVxkD063825; Wed, 22 Aug 2012 20:31:59 GMT (envelope-from lev@freefall.freebsd.org) Received: (from lev@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7MKVxDq063821; Wed, 22 Aug 2012 20:31:59 GMT (envelope-from lev) Date: Wed, 22 Aug 2012 20:31:59 GMT Message-Id: <201208222031.q7MKVxDq063821@freefall.freebsd.org> To: lev@FreeBSD.org, freebsd-bugs@FreeBSD.org, wireless@FreeBSD.org From: lev@FreeBSD.org Cc: Subject: Re: kern/170889: [ath] ath driver uses some uninitilized memory 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, 22 Aug 2012 20:31:59 -0000 Synopsis: [ath] ath driver uses some uninitilized memory Responsible-Changed-From-To: freebsd-bugs->wireless Responsible-Changed-By: lev Responsible-Changed-When: Wed Aug 22 20:31:34 UTC 2012 Responsible-Changed-Why: To the owner http://www.freebsd.org/cgi/query-pr.cgi?pr=170889 From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 20:34:15 2012 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 0DCD1106566C for ; Wed, 22 Aug 2012 20:34:15 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id BCEE68FC0C for ; Wed, 22 Aug 2012 20:34:14 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 2E1644AC31; Thu, 23 Aug 2012 00:34:08 +0400 (MSK) Date: Thu, 23 Aug 2012 00:34:03 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <925895036.20120823003403@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <1311732708.20120815005429@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2012 20:34:15 -0000 Hello, Adrian. You wrote 19 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 2:13:05: AC> .. please file a PR? Pretty please? :0 Sorry for delay: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D170889 Also, I now have TRUE 11n client (Samsung notebook with Intel Advanced-N adapter, not loosy PlayBook with unknown adapter and capabilities) and it seems, I'll fill new bugreports in near future, as I've seen one AP stall already. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 20:45:54 2012 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 E5B8A1065688; Wed, 22 Aug 2012 20:45:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id B14708FC0A; Wed, 22 Aug 2012 20:45:53 +0000 (UTC) Received: by dadr6 with SMTP id r6so15288dad.13 for ; Wed, 22 Aug 2012 13:45:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ib3h3fm7ZAUatzyoujXTzkE8AyqexZuqtvEoOmVOT6U=; b=FZzJQ12RmUN6svb6Udg4/vewKoLauvk5QBHvQYoqg/av+KvhPrvDKXrOkr3aCtiTLv 6GosWRid1+NeYcrSP4nHXepdg/DtyRDjrtVtnX5IohgQHbD4UAnqsTZXQRRGhr0STBux L5Nvsd16+32nQM4DipJTn2iZ0MVuyW2COpmvoeOkVf9V6hZa8+Let9d10XXV3i3qRYDq Ya4+0+Q7T8wRKOagmZBYLEdGJVneeRetEBn+6JxEFYjPjbphKWNczO05CdkTIMnNe/XB lRGkrpSBQmxVrqngXFGYSicmD77lxss4jb6tdMmOPmv5CUIWKcI0+4IkB5ZfUT6FWjG7 Fb2Q== MIME-Version: 1.0 Received: by 10.66.82.167 with SMTP id j7mr14427878pay.32.1345668353069; Wed, 22 Aug 2012 13:45:53 -0700 (PDT) Received: by 10.68.36.106 with HTTP; Wed, 22 Aug 2012 13:45:53 -0700 (PDT) In-Reply-To: <925895036.20120823003403@serebryakov.spb.ru> References: <1311732708.20120815005429@serebryakov.spb.ru> <925895036.20120823003403@serebryakov.spb.ru> Date: Wed, 22 Aug 2012 13:45:53 -0700 Message-ID: From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: New ath code works well as AP 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, 22 Aug 2012 20:45:54 -0000 well, the playbook is still a good test. I bet it's exposing shortcomings in our power save handling code. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 21:30:27 2012 Return-Path: Delivered-To: wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E71A10656AA; Wed, 22 Aug 2012 21:30:27 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D54488FC0C; Wed, 22 Aug 2012 21:30:26 +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 q7MLUQMe071739; Wed, 22 Aug 2012 21:30:26 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7MLUQrv071733; Wed, 22 Aug 2012 21:30:26 GMT (envelope-from linimon) Date: Wed, 22 Aug 2012 21:30:26 GMT Message-Id: <201208222130.q7MLUQrv071733@freefall.freebsd.org> To: linimon@FreeBSD.org, wireless@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/170889: [ath] ath driver uses some uninitilized memory 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, 22 Aug 2012 21:30:27 -0000 Synopsis: [ath] ath driver uses some uninitilized memory Responsible-Changed-From-To: wireless->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 22 21:30:15 UTC 2012 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=170889 From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 22 21:30:27 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E71A10656AA; Wed, 22 Aug 2012 21:30:27 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D54488FC0C; Wed, 22 Aug 2012 21:30:26 +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 q7MLUQMe071739; Wed, 22 Aug 2012 21:30:26 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7MLUQrv071733; Wed, 22 Aug 2012 21:30:26 GMT (envelope-from linimon) Date: Wed, 22 Aug 2012 21:30:26 GMT Message-Id: <201208222130.q7MLUQrv071733@freefall.freebsd.org> To: linimon@FreeBSD.org, wireless@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/170889: [ath] ath driver uses some uninitilized memory 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, 22 Aug 2012 21:30:27 -0000 Synopsis: [ath] ath driver uses some uninitilized memory Responsible-Changed-From-To: wireless->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 22 21:30:15 UTC 2012 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=170889 From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 23 00:37: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 75EA51065689 for ; Thu, 23 Aug 2012 00:37:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 43C198FC1D for ; Thu, 23 Aug 2012 00:37:46 +0000 (UTC) Received: by dadr6 with SMTP id r6so111035dad.13 for ; Wed, 22 Aug 2012 17:37:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UJ97X/irytYw9/zPeWxfcYKT5T8uDcP+XP1gSYI6GXU=; b=VtjouXiIQSJCZFnzWxFaKaR9FyFMQ5WObx03cTCuAQRUg9uKsUjQ944ytMRl8hGH5H DXUNqfdTvgxGEXcAqbBu0xKNrsB8MHYDzwfj2LmlFTNxxYHoDITpmDuLsPKLx6+cNjXP 4GufF8DFed5JtgrMXUFEDhFs2f7vDrdqVTA+DSJuGPC7FxkATGiaMtB0X853ELtlga6T 5nZ/HkSgSVWMHSMoh/J5gaqImUw3H8X+YLUZcbLGvAgNM/Y/7lJlAkhjIB4GqrxQIkZX MTKhDUPX8HXkOz5qPPzYp/N4ovhT46RKhZOxI5VI2S7XkmKqp+qbUBUf7fHOj/LsZtg9 ScQw== MIME-Version: 1.0 Received: by 10.68.192.40 with SMTP id hd8mr106395pbc.125.1345682265570; Wed, 22 Aug 2012 17:37:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Wed, 22 Aug 2012 17:37:45 -0700 (PDT) In-Reply-To: References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> Date: Wed, 22 Aug 2012 17:37:45 -0700 X-Google-Sender-Auth: DPLjwRfyq19borZICL8fzwbhvwY Message-ID: From: Adrian Chadd To: "Wright, Brett" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: Re: Atheros DFS radar detection 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, 23 Aug 2012 00:37:46 -0000 hi, would you mind filing a couple of PRs, just so I remember to get this stuff done: * please add a HAL method to fetch the default radar parameters; * please modify the AR5212 HAL to disable some of the fast diversity stuff if radar is enabled; * please modify dfs_null to fetch the default radar parameters and disable the appropriate fast diversity stuff; * please modify the AR5212 HAL to disable 5GHz ANI operation if radar reporting is enabled. I've whacked an AR5212 reference cardbus NIC into a laptop and added the AR5212 parameters to dfs_null.c. I get around 40 false detects a second when doing around 25mbit/sec TCP iperf test. So there may be something specific about your NIC(s) and antenna setup. I'll try to setup some other 11a NICs (AR5213, AR5312, AR5413, etc) and see what the story is. I know the AR5212 parameters I have are working, but I also know the AR5413 Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 23 01:11:23 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 98065106566C; Thu, 23 Aug 2012 01:11:23 +0000 (UTC) (envelope-from prvs=575f86cc2=Brett.Wright@cooperindustries.com) Received: from cooperlighting-sw.cooperlighting.com (cooperlighting-sw.cooperlighting.com [216.130.131.68]) by mx1.freebsd.org (Postfix) with ESMTP id 405158FC15; Thu, 23 Aug 2012 01:11:22 +0000 (UTC) Authentication-Results: cooperlighting-sw.cooperlighting.com; dkim=neutral (message not signed) header.i=none X-IronPort-AV: E=Sophos;i="4.80,297,1344225600"; d="scan'208";a="66300477" Received: from cipt0175.nam.ci.root ([10.132.108.175]) by cooperlighting-sw.cooperlighting.com with ESMTP; 22 Aug 2012 21:11:22 -0400 Received: from APEVS1.AP.CI.ROOT ([10.180.2.22]) by cipt0175.NAM.CI.ROOT with Microsoft SMTPSVC(6.0.3790.4675); Wed, 22 Aug 2012 21:11:22 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 23 Aug 2012 09:09:43 +0800 Message-ID: <475A4E02EFF4724A9E58F55A56AC13160661F137@APEVS1.ap.ci.root> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Atheros DFS radar detection Thread-Index: Ac2Ak3fjs+Qfxrd6QiSTsXjXKJ/3AQAN9BSA References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root><475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> From: "Wright, Brett" To: "Adrian Chadd" X-OriginalArrivalTime: 23 Aug 2012 01:11:22.0054 (UTC) FILETIME=[355C5660:01CD80CC] Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: RE: Atheros DFS radar detection 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, 23 Aug 2012 01:11:23 -0000 Hi, > -----Original Message----- > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf > Of Adrian Chadd >=20 > Your false detects - are they long? short? Do they have 0 or no > duration? That'll at least hint at what's going on (ie, triggering on > out of band or in-band stuff; whether it's triggering on 802.11 frames > or not.) > They appear to have no duration. I only get them while transferring data (iperf). > It also means if the NF value is higher for some > reason, the RSSI values will change and the parameters will also > change. >=20 Actually the noise floor seems to be settling around -87dBm on these cards... Thanks Brett. From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 23 01:17:29 2012 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 115CC106566C; Thu, 23 Aug 2012 01:17:29 +0000 (UTC) (envelope-from prvs=575f86cc2=Brett.Wright@cooperindustries.com) Received: from cooperlighting-sw.cooperlighting.com (cooperlighting-sw.cooperlighting.com [216.130.131.68]) by mx1.freebsd.org (Postfix) with ESMTP id AD53C8FC12; Thu, 23 Aug 2012 01:17:28 +0000 (UTC) Authentication-Results: cooperlighting-sw.cooperlighting.com; dkim=neutral (message not signed) header.i=none X-IronPort-AV: E=Sophos;i="4.80,297,1344225600"; d="scan'208";a="66300760" Received: from cipt0175.nam.ci.root ([10.132.108.175]) by cooperlighting-sw.cooperlighting.com with ESMTP; 22 Aug 2012 21:17:28 -0400 Received: from APEVS1.AP.CI.ROOT ([10.180.2.22]) by cipt0175.NAM.CI.ROOT with Microsoft SMTPSVC(6.0.3790.4675); Wed, 22 Aug 2012 21:17:27 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 23 Aug 2012 09:16:34 +0800 Message-ID: <475A4E02EFF4724A9E58F55A56AC13160661F182@APEVS1.ap.ci.root> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Atheros DFS radar detection Thread-Index: Ac2AyBlhhvFHY98JQY2NEULZzot66AAA+New References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root><475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> From: "Wright, Brett" To: "Adrian Chadd" X-OriginalArrivalTime: 23 Aug 2012 01:17:27.0959 (UTC) FILETIME=[0F750270:01CD80CD] Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: RE: Atheros DFS radar detection 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, 23 Aug 2012 01:17:29 -0000 Hi Adrian, > -----Original Message----- > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf > Of Adrian Chadd >=20 > hi, >=20 > would you mind filing a couple of PRs, just so I remember to get this > stuff done: >=20 Sure. > I've whacked an AR5212 reference cardbus NIC into a laptop and added > the AR5212 parameters to dfs_null.c. I get around 40 false detects a > second when doing around 25mbit/sec TCP iperf test. That seems to be about the rate of false detects I now get without setting the parameters too aggressively... However, even with that rate of false detects and iperfing continuously, I inevitably get a radar pattern match and channel change (usually within about 20 minutes of continuous iperf). With the more aggressive parameters it is much better - but am suspicious that then real radar pulse matching will fail. Perhaps false detects causing the radar pattern to be triggered and channel change is just going to be inevitable to some degree? >=20 > Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 23 03:47:46 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96E30106566C; Thu, 23 Aug 2012 03:47:46 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6A75E8FC08; Thu, 23 Aug 2012 03:47:46 +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 q7N3lkrh022586; Thu, 23 Aug 2012 03:47:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7N3lkgs022582; Thu, 23 Aug 2012 03:47:46 GMT (envelope-from linimon) Date: Thu, 23 Aug 2012 03:47:46 GMT Message-Id: <201208230347.q7N3lkgs022582@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/170904: [ath] ath driver: configure related parameters when radar detection (DFS) is enabled 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, 23 Aug 2012 03:47:46 -0000 Synopsis: [ath] ath driver: configure related parameters when radar detection (DFS) is enabled Responsible-Changed-From-To: freebsd-net->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Thu Aug 23 03:47:27 UTC 2012 Responsible-Changed-Why: Set more canonical assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=170904 From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 23 06:27: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 EFAF0106566C for ; Thu, 23 Aug 2012 06:27:23 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6394B8FC0A for ; Thu, 23 Aug 2012 06:27:23 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so266080lbb.13 for ; Wed, 22 Aug 2012 23:27:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=hzo8auh6TJJeVAZLyHWLOIjG28xnxcNhK+F7EeXeOME=; b=IHqLp4TIMbNaol/OInk2V/Wke/lqNnsNKjDHXbHbElkeT7SIXYEv/DFqdw8f140+4U zG8TYaLgHOfYnK4+4SshoIqCnOK0Lg90j1AYouVZ5/ULcX7FlHivNh2SyrpL7AwKbyaX oDg8FF9kP0+14J/cpTuPMe/YQw67Nfqyns8STtm9mITzoeZzsfsWAI1ncdKpUdczxMTW /sJy8TFsDxL+NpXiSYGa7a2RyK+svvqFIn/zhxe4KIBbemtCWkL1hVdZVEMFCGDzAFJ2 OQfYSbhW9iZUNv/zpfegFH5HYuNvsKYNrKSEm9wRM4HnRLmvp7ld51qRjPLiLO98HUut 8yDA== MIME-Version: 1.0 Received: by 10.152.128.230 with SMTP id nr6mr481192lab.24.1345703241981; Wed, 22 Aug 2012 23:27:21 -0700 (PDT) Sender: bschmidt@techwires.net Received: by 10.152.123.200 with HTTP; Wed, 22 Aug 2012 23:27:21 -0700 (PDT) X-Originating-IP: [79.140.39.245] In-Reply-To: References: <201207300139326668335@gmail.com> <201208201829.10554.bschmidt@freebsd.org> <201208212047.50852.bschmidt@freebsd.org> Date: Thu, 23 Aug 2012 08:27:21 +0200 X-Google-Sender-Auth: 0SSE99FyI0eXDf40ufC2ObieBe8 Message-ID: From: Bernhard Schmidt To: =?UTF-8?B?5LmU5qWa?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkfbAFYXsWoHmBlJyfWezqCUoNG4KXtftvbX20ZwC6+5oSVWpnUFwl98qDaYKAEw39+BWM2 Cc: freebsd-wireless Subject: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 23 Aug 2012 06:27:24 -0000 On Wed, Aug 22, 2012 at 12:18 PM, Bernhard Schmidt w= rote: > On Wed, Aug 22, 2012 at 5:38 AM, =E4=B9=94=E6=A5=9A wrote: >> [11:33:57]root@x201i.pts/2 sys/net80211 # cd /usr/src/ >> [11:34:09]root@x201i.pts/2 /usr/src # svn up >> ..... >> Updated to revision 239552. >> >> [11:35:46]root@x201i.pts/2 /usr/src # cd sys/net80211 >> [11:36:01]root@x201i.pts/2 sys/net80211 # patch -p2 < >> /home/HonestQiao/Downloads/r231187.diff >> Hmm... Looks like a unified diff to me... >> The text leading up to this was: >> -------------------------- >> |Index: sys/net80211/ieee80211.h >> |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> |--- sys/net80211/ieee80211.h (revision 231186) >> |+++ sys/net80211/ieee80211.h (revision 231187) >> -------------------------- >> Patching file ieee80211.h using Plan A... >> Hunk #1 failed at 709. >> 1 out of 1 hunks failed--saving rejects to ieee80211.h.rej >> done > > Is there Windows stuff involved which might change line breaks? > > amy:stable/9% pwd > /home/bschmidt/src/svn/freebsd/stable/9 > amy:stable/9% svn up > Updating '.': > At revision 239563. > amy:stable/9% svn stat sys/net80211 > amy:stable/9% md5 sys/net80211/ieee80211.h > MD5 (sys/net80211/ieee80211.h) =3D f3cc66ca7ab81b3c63d1c1fd95806624 > amy:stable/9% md5 ~/tmp/r231187.diff > MD5 (/home/bschmidt/tmp/r231187.diff) =3D e2c5762997088ee1857983a99ddf80b= c > amy:stable/9% patch -p0 < ~/tmp/r231187.diff > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |Index: sys/net80211/ieee80211.h > |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > |--- sys/net80211/ieee80211.h (revision 231186) > |+++ sys/net80211/ieee80211.h (revision 231187) > -------------------------- > Patching file sys/net80211/ieee80211.h using Plan A... > Hunk #1 succeeded at 709. > done > > I've attached the patched ieee80211.h Any kind of success yet? I'll push that into the tree as soon as I have received some kind of confirmation. --=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 23 07:07:02 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 62D84106564A for ; Thu, 23 Aug 2012 07:07:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2FD268FC08 for ; Thu, 23 Aug 2012 07:07:01 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so827204pbb.13 for ; Thu, 23 Aug 2012 00:07:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=K8nxuprWYTc68j5KMSr6bupD7zklKbsEBn3ImM44ICg=; b=mVVfw55C/ECMxV+Xe2Wpt55aeYckY9UDx3uSwCKu3dYerWjFd+1U2saao8sQlNH1hi lvv8mIN1uaqpx+o98r1xTdIBorMEB4WTaCsiy3wFVBWNusLg8milEUJ4cthLNd6c71Py lXN3YKklFejwRWaoET2HgrhprFuEc3DbbvcrEhoDN2xjFLTc/CU9x7xgg41jMsqK5Ytu ZOaGi7vX91sKHKJrXGOfMIpN4193vYK4X0px6MVnLMnrsTXc1LO94IiuAJDIs9zhjeof 5nnIj2GFSvDLoc3RTTsicf/t1nrIU3iPqAkJdcfi6MnPdF/OsmSl+WLszWdQQP92fBHG 18Mg== MIME-Version: 1.0 Received: by 10.68.231.233 with SMTP id tj9mr2327637pbc.39.1345705621732; Thu, 23 Aug 2012 00:07:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Thu, 23 Aug 2012 00:07:01 -0700 (PDT) In-Reply-To: <475A4E02EFF4724A9E58F55A56AC13160661F137@APEVS1.ap.ci.root> References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661F137@APEVS1.ap.ci.root> Date: Thu, 23 Aug 2012 00:07:01 -0700 X-Google-Sender-Auth: Gz04O-3HkSGI8-1XsFsfxF8ZDo4 Message-ID: From: Adrian Chadd To: "Wright, Brett" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: Re: Atheros DFS radar detection 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, 23 Aug 2012 07:07:02 -0000 On 22 August 2012 18:09, Wright, Brett wrote: > They appear to have no duration. I only get them while transferring data > (iperf). Right. What happens when you adjust prssi by itself then? >> It also means if the NF value is higher for some >> reason, the RSSI values will change and the parameters will also >> change. > Actually the noise floor seems to be settling around -87dBm on these > cards... Right. That's going to lower the RSSI values that the hardware reports/sees and muck things up a bit. Either there's a spur somewhere, the boards are noisy, or there's some external amplifier attached on the input side. I'll ask one of the baseband guys tomorrow and see what they think. This is a really old chip though. They may not remember. :-) Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 23 06:30:24 2012 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 0745F106564A; Thu, 23 Aug 2012 06:30:24 +0000 (UTC) (envelope-from honestqiao@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id BB4D18FC12; Thu, 23 Aug 2012 06:30:23 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so771823pbb.13 for ; Wed, 22 Aug 2012 23:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:references:x-priority:x-has-attach:x-mailer :mime-version:message-id:content-type:content-transfer-encoding; bh=zBvZ5hmZppP7XQEvz46kptU8/mPwuEsqF38bDpXVdE4=; b=UXaTHL+e/PgAhEQniVjvrGa2CUjcp/C2qSFAAguYgtiUhHSGqAxLQDpFWUSKHYLVjP X0rgGiVsJk0nly/NRwwW1sTfBQngWOR0mHYbNunyPsvJPvsPxoyqjd7C3jJVZMi8KuZ1 QT+ZFS2OOKQP3/EepPP2/11l2MQTo2M6W5tdC+8zJRZUEDiEgoNqkRJGabYcQaqOOkd2 ufsFewF34KkbwfN+2TgEcX2AZcr5wn6mKF2TC6tntiRxK1Pe01YtZ1bX/6jErSFB61GW qqte6d8Je8FKjJjuekg0sZGjubGw7vpDdzepzGfH4pFNFxSHWsSY/9cc8THQf2BqT+8O Nx/w== Received: by 10.68.200.98 with SMTP id jr2mr2059323pbc.81.1345703423315; Wed, 22 Aug 2012 23:30:23 -0700 (PDT) Received: from HonestQiaoNB ([216.218.222.20]) by mx.google.com with ESMTPS id uj3sm5335411pbc.39.2012.08.22.23.30.20 (version=SSLv3 cipher=OTHER); Wed, 22 Aug 2012 23:30:21 -0700 (PDT) Date: Thu, 23 Aug 2012 14:30:18 +0800 From: =?gb2312?B?x8ez/i9Ib25lc3RRaWFv?= To: bschmidt References: <201207300139326668335@gmail.com> <201208201829.10554.bschmidt@freebsd.org> <201208212047.50852.bschmidt@freebsd.org> , X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7.0.1.91[en] Mime-Version: 1.0 Message-ID: <201208231430163933460@gmail.com> Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 X-Mailman-Approved-At: Thu, 23 Aug 2012 11:36:05 +0000 Cc: freebsd-wireless Subject: Re: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 23 Aug 2012 06:30:24 -0000 MjAxMi0wOC0yMyAxNDoyNywgQmVybmhhcmQgU2NobWlkdDxic2NobWlkdEBmcmVlYnNkLm9yZz4g d3JvdGU6DQo+T24gV2VkLCBBdWcgMjIsIDIwMTIgYXQgMTI6MTggUE0sIEJlcm5oYXJkIFNjaG1p ZHQgPGJzY2htaWR0QGZyZWVic2Qub3JnPiB3cm90ZToNCj4+IE9uIFdlZCwgQXVnIDIyLCAyMDEy IGF0IDU6MzggQU0sIMfHs/4gPGhvbmVzdHFpYW9AZ21haWwuY29tPiB3cm90ZToNCj4+PiBbMTE6 MzM6NTddcm9vdEB4MjAxaS5wdHMvMiBzeXMvbmV0ODAyMTEgIyBjZCAvdXNyL3NyYy8NCj4+PiBb MTE6MzQ6MDldcm9vdEB4MjAxaS5wdHMvMiAvdXNyL3NyYyAjIHN2biB1cA0KPj4+IC4uLi4uDQo+ Pj4gVXBkYXRlZCB0byByZXZpc2lvbiAyMzk1NTIuDQo+Pj4NCj4+PiBbMTE6MzU6NDZdcm9vdEB4 MjAxaS5wdHMvMiAvdXNyL3NyYyAjIGNkIHN5cy9uZXQ4MDIxMQ0KPj4+IFsxMTozNjowMV1yb290 QHgyMDFpLnB0cy8yIHN5cy9uZXQ4MDIxMSAjIHBhdGNoIC1wMiA8DQo+Pj4gL2hvbWUvSG9uZXN0 UWlhby9Eb3dubG9hZHMvcjIzMTE4Ny5kaWZmDQo+Pj4gSG1tLi4uICBMb29rcyBsaWtlIGEgdW5p ZmllZCBkaWZmIHRvIG1lLi4uDQo+Pj4gVGhlIHRleHQgbGVhZGluZyB1cCB0byB0aGlzIHdhczoN Cj4+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4+IHxJbmRleDogc3lzL25ldDgwMjEx L2llZWU4MDIxMS5oDQo+Pj4gfD09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCj4+PiB8LS0tIHN5cy9uZXQ4MDIxMS9pZWVl ODAyMTEuaCAgIChyZXZpc2lvbiAyMzExODYpDQo+Pj4gfCsrKyBzeXMvbmV0ODAyMTEvaWVlZTgw MjExLmggICAocmV2aXNpb24gMjMxMTg3KQ0KPj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t DQo+Pj4gUGF0Y2hpbmcgZmlsZSBpZWVlODAyMTEuaCB1c2luZyBQbGFuIEEuLi4NCj4+PiBIdW5r ICMxIGZhaWxlZCBhdCA3MDkuDQo+Pj4gMSBvdXQgb2YgMSBodW5rcyBmYWlsZWQtLXNhdmluZyBy ZWplY3RzIHRvIGllZWU4MDIxMS5oLnJlag0KPj4+IGRvbmUNCj4+DQo+PiBJcyB0aGVyZSBXaW5k b3dzIHN0dWZmIGludm9sdmVkIHdoaWNoIG1pZ2h0IGNoYW5nZSBsaW5lIGJyZWFrcz8NCj4+DQo+ PiBhbXk6c3RhYmxlLzklIHB3ZA0KPj4gL2hvbWUvYnNjaG1pZHQvc3JjL3N2bi9mcmVlYnNkL3N0 YWJsZS85DQo+PiBhbXk6c3RhYmxlLzklIHN2biB1cA0KPj4gVXBkYXRpbmcgJy4nOg0KPj4gQXQg cmV2aXNpb24gMjM5NTYzLg0KPj4gYW15OnN0YWJsZS85JSBzdm4gc3RhdCBzeXMvbmV0ODAyMTEN Cj4+IGFteTpzdGFibGUvOSUgbWQ1IHN5cy9uZXQ4MDIxMS9pZWVlODAyMTEuaA0KPj4gTUQ1IChz eXMvbmV0ODAyMTEvaWVlZTgwMjExLmgpID0gZjNjYzY2Y2E3YWI4MWIzYzYzZDFjMWZkOTU4MDY2 MjQNCj4+IGFteTpzdGFibGUvOSUgbWQ1IH4vdG1wL3IyMzExODcuZGlmZg0KPj4gTUQ1ICgvaG9t ZS9ic2NobWlkdC90bXAvcjIzMTE4Ny5kaWZmKSA9IGUyYzU3NjI5OTcwODhlZTE4NTc5ODNhOTlk ZGY4MGJjDQo+PiBhbXk6c3RhYmxlLzklIHBhdGNoIC1wMCA8IH4vdG1wL3IyMzExODcuZGlmZg0K Pj4gSG1tLi4uICBMb29rcyBsaWtlIGEgdW5pZmllZCBkaWZmIHRvIG1lLi4uDQo+PiBUaGUgdGV4 dCBsZWFkaW5nIHVwIHRvIHRoaXMgd2FzOg0KPj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N Cj4+IHxJbmRleDogc3lzL25ldDgwMjExL2llZWU4MDIxMS5oDQo+PiB8PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KPj4g fC0tLSBzeXMvbmV0ODAyMTEvaWVlZTgwMjExLmggICAocmV2aXNpb24gMjMxMTg2KQ0KPj4gfCsr KyBzeXMvbmV0ODAyMTEvaWVlZTgwMjExLmggICAocmV2aXNpb24gMjMxMTg3KQ0KPj4gLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4+IFBhdGNoaW5nIGZpbGUgc3lzL25ldDgwMjExL2llZWU4 MDIxMS5oIHVzaW5nIFBsYW4gQS4uLg0KPj4gSHVuayAjMSBzdWNjZWVkZWQgYXQgNzA5Lg0KPj4g ZG9uZQ0KPj4NCj4+IEkndmUgYXR0YWNoZWQgdGhlIHBhdGNoZWQgaWVlZTgwMjExLmgNCj4NCj5B bnkga2luZCBvZiBzdWNjZXNzIHlldD8NCj4NCj5JJ2xsIHB1c2ggdGhhdCBpbnRvIHRoZSB0cmVl IGFzIHNvb24gYXMgSSBoYXZlIHJlY2VpdmVkIHNvbWUga2luZCBvZg0KPmNvbmZpcm1hdGlvbi4N Cj4NCj4tLSANCj5CZXJuaGFyZA0KDQpJJ2xsIHRlc3QgaXQgdG9kYXkgbmlnaHQuDQo= From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 23 13:52:52 2012 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 7AE4E1065674; Thu, 23 Aug 2012 13:52:52 +0000 (UTC) (envelope-from honestqiao@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id F20B38FC23; Thu, 23 Aug 2012 13:52:51 +0000 (UTC) Received: by qatn12 with SMTP id n12so539580qat.13 for ; Thu, 23 Aug 2012 06:52:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=KCrH1dY13hR2eHtdSkV3/3TSQieB2vfPFXdeO52D/AQ=; b=bdL6odXtHrCZPjv2r+7PjZ86kb/gCZ/6rTZnsOm6PjNg0ZkmWaxW6PnC1hkJzxrgpH xpRaPmx/ueGAat2R5Faw2sSg0bY7IFR2uXS5kjABPqB37U04YHlAdPm68XhGCsLlQidf QRsgFJNQiw1qDbg4LVUwHm+41sFsPJXbQ38xdO8432PX1hgpS2yPlzlD9gourcX+7vuI id8isKGMMMjTISNJOrHYVRCLkgVlortY9yNT4NDTgxMaiDVbIAj7NKBRQxLPjFVBfPxA kHHmQLiMO2AR4vLmjtGTzAfdXKvq9Vk3F9UXI0ExDw6UeOvGJ11TDdHfuTWuaf9+R38f mLIw== Received: by 10.229.122.220 with SMTP id m28mr711984qcr.49.1345729970844; Thu, 23 Aug 2012 06:52:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.197.65 with HTTP; Thu, 23 Aug 2012 06:52:10 -0700 (PDT) In-Reply-To: <201208231430163933460@gmail.com> References: <201207300139326668335@gmail.com> <201208201829.10554.bschmidt@freebsd.org> <201208212047.50852.bschmidt@freebsd.org> <201208231430163933460@gmail.com> From: =?UTF-8?B?5LmU5qWa?= Date: Thu, 23 Aug 2012 21:52:10 +0800 Message-ID: To: bschmidt Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless Subject: Re: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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, 23 Aug 2012 13:52:52 -0000 2012/8/23 =C7=C7=B3=FE/HonestQiao : > 2012-08-23 14:27, Bernhard Schmidt wrote: >>On Wed, Aug 22, 2012 at 12:18 PM, Bernhard Schmidt = wrote: >>> On Wed, Aug 22, 2012 at 5:38 AM, =C7=C7=B3=FE wr= ote: >>>> [11:33:57]root@x201i.pts/2 sys/net80211 # cd /usr/src/ >>>> [11:34:09]root@x201i.pts/2 /usr/src # svn up >>>> ..... >>>> Updated to revision 239552. >>>> >>>> [11:35:46]root@x201i.pts/2 /usr/src # cd sys/net80211 >>>> [11:36:01]root@x201i.pts/2 sys/net80211 # patch -p2 < >>>> /home/HonestQiao/Downloads/r231187.diff >>>> Hmm... Looks like a unified diff to me... >>>> The text leading up to this was: >>>> -------------------------- >>>> |Index: sys/net80211/ieee80211.h >>>> |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> |--- sys/net80211/ieee80211.h (revision 231186) >>>> |+++ sys/net80211/ieee80211.h (revision 231187) >>>> -------------------------- >>>> Patching file ieee80211.h using Plan A... >>>> Hunk #1 failed at 709. >>>> 1 out of 1 hunks failed--saving rejects to ieee80211.h.rej >>>> done >>> >>> Is there Windows stuff involved which might change line breaks? >>> >>> amy:stable/9% pwd >>> /home/bschmidt/src/svn/freebsd/stable/9 >>> amy:stable/9% svn up >>> Updating '.': >>> At revision 239563. >>> amy:stable/9% svn stat sys/net80211 >>> amy:stable/9% md5 sys/net80211/ieee80211.h >>> MD5 (sys/net80211/ieee80211.h) =3D f3cc66ca7ab81b3c63d1c1fd95806624 >>> amy:stable/9% md5 ~/tmp/r231187.diff >>> MD5 (/home/bschmidt/tmp/r231187.diff) =3D e2c5762997088ee1857983a99ddf8= 0bc >>> amy:stable/9% patch -p0 < ~/tmp/r231187.diff >>> Hmm... Looks like a unified diff to me... >>> The text leading up to this was: >>> -------------------------- >>> |Index: sys/net80211/ieee80211.h >>> |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> |--- sys/net80211/ieee80211.h (revision 231186) >>> |+++ sys/net80211/ieee80211.h (revision 231187) >>> -------------------------- >>> Patching file sys/net80211/ieee80211.h using Plan A... >>> Hunk #1 succeeded at 709. >>> done >>> >>> I've attached the patched ieee80211.h >> >>Any kind of success yet? >> >>I'll push that into the tree as soon as I have received some kind of >>confirmation. >> >>-- >>Bernhard > > I'll test it today night. Good news. Nothing changed on My AP, My FreeBSD can connect to My AP with your patched file. [21:51:10]root@x201i.pts/1 /usr/src # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 239552 Node Kind: directory Schedule: normal Last Changed Author: kevlo Last Changed Rev: 239549 Last Changed Date: 2012-08-22 08:59:17 +0800 (Wed, 22 Aug 2012) [21:51:13]root@x201i.pts/1 /usr/src # svn stat M sys/net80211/ieee80211.h [21:51:19]root@x201i.pts/1 /usr/src # ifconfig -v wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 8c:21:0a:43:ef:d4 4 11 54M 24.0 0 903 13920 EPS AQEHTRS SSID RATES DSPARMS<11> ERP<0x0> RSN XRATES<48,72,96,108> HTCAP ???<331aef1103ffff00000000000000000000-> HTINFO ???<34160b0715000000000000000000000000-> WME ATH<0x7fff> WPS [21:51:28]root@x201i.pts/1 /usr/src # [21:51:28]root@x201i.pts/1 /usr/src # uname -a FreeBSD x201i.honestqiao 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r239552M: Thu Aug 23 12:36:01 CST 2012 root@x201i.honestqiao:/usr/obj/usr/src/sys/HonestQiaoKernel amd64 From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 01:40:09 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10295106566B for ; Fri, 24 Aug 2012 01:40:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DCCC08FC0A for ; Fri, 24 Aug 2012 01:40:08 +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 q7O1e8ac009003 for ; Fri, 24 Aug 2012 01:40:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7O1e8k2009002; Fri, 24 Aug 2012 01:40:08 GMT (envelope-from gnats) Date: Fri, 24 Aug 2012 01:40:08 GMT Message-Id: <201208240140.q7O1e8k2009002@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/170904: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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, 24 Aug 2012 01:40:09 -0000 The following reply was made to PR kern/170904; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/170904: commit references a PR Date: Fri, 24 Aug 2012 01:29:58 +0000 (UTC) Author: adrian Date: Fri Aug 24 01:29:46 2012 New Revision: 239638 URL: http://svn.freebsd.org/changeset/base/239638 Log: Implement an API to fetch the default DFS parameters for the given chip. The only chip this is currently implemented for is the AR5416 HAL family. A follow-up commit will add AR5212 support. PR: kern/170904 Modified: head/sys/dev/ath/ath_hal/ah.h head/sys/dev/ath/ath_hal/ar5416/ar5416.h head/sys/dev/ath/ath_hal/ar5416/ar5416_attach.c head/sys/dev/ath/ath_hal/ar5416/ar5416_radar.c Modified: head/sys/dev/ath/ath_hal/ah.h ============================================================================== --- head/sys/dev/ath/ath_hal/ah.h Fri Aug 24 01:14:00 2012 (r239637) +++ head/sys/dev/ath/ath_hal/ah.h Fri Aug 24 01:29:46 2012 (r239638) @@ -1223,6 +1223,8 @@ struct ath_hal { HAL_PHYERR_PARAM *pe); void __ahdecl(*ah_getDfsThresh)(struct ath_hal *ah, HAL_PHYERR_PARAM *pe); + HAL_BOOL __ahdecl(*ah_getDfsDefaultThresh)(struct ath_hal *ah, + HAL_PHYERR_PARAM *pe); HAL_BOOL __ahdecl(*ah_procRadarEvent)(struct ath_hal *ah, struct ath_rx_status *rxs, uint64_t fulltsf, const char *buf, HAL_DFS_EVENT *event); Modified: head/sys/dev/ath/ath_hal/ar5416/ar5416.h ============================================================================== --- head/sys/dev/ath/ath_hal/ar5416/ar5416.h Fri Aug 24 01:14:00 2012 (r239637) +++ head/sys/dev/ath/ath_hal/ar5416/ar5416.h Fri Aug 24 01:29:46 2012 (r239638) @@ -253,6 +253,8 @@ extern HAL_BOOL ar5416SetRifsDelay(struc const struct ieee80211_channel *chan, HAL_BOOL enable); extern void ar5416EnableDfs(struct ath_hal *ah, HAL_PHYERR_PARAM *pe); +extern HAL_BOOL ar5416GetDfsDefaultThresh(struct ath_hal *ah, + HAL_PHYERR_PARAM *pe); extern void ar5416GetDfsThresh(struct ath_hal *ah, HAL_PHYERR_PARAM *pe); extern HAL_BOOL ar5416ProcessRadarEvent(struct ath_hal *ah, struct ath_rx_status *rxs, uint64_t fulltsf, const char *buf, Modified: head/sys/dev/ath/ath_hal/ar5416/ar5416_attach.c ============================================================================== --- head/sys/dev/ath/ath_hal/ar5416/ar5416_attach.c Fri Aug 24 01:14:00 2012 (r239637) +++ head/sys/dev/ath/ath_hal/ar5416/ar5416_attach.c Fri Aug 24 01:29:46 2012 (r239638) @@ -156,6 +156,7 @@ ar5416InitState(struct ath_hal_5416 *ahp /* DFS Functions */ ah->ah_enableDfs = ar5416EnableDfs; ah->ah_getDfsThresh = ar5416GetDfsThresh; + ah->ah_getDfsDefaultThresh = ar5416GetDfsDefaultThresh; ah->ah_procRadarEvent = ar5416ProcessRadarEvent; ah->ah_isFastClockEnabled = ar5416IsFastClockEnabled; Modified: head/sys/dev/ath/ath_hal/ar5416/ar5416_radar.c ============================================================================== --- head/sys/dev/ath/ath_hal/ar5416/ar5416_radar.c Fri Aug 24 01:14:00 2012 (r239637) +++ head/sys/dev/ath/ath_hal/ar5416/ar5416_radar.c Fri Aug 24 01:29:46 2012 (r239638) @@ -29,6 +29,51 @@ #include "ah_eeprom_v14.h" /* for owl_get_ntxchains() */ /* + * These are default parameters for the AR5416 and + * later 802.11n NICs. They simply enable some + * radar pulse event generation. + * + * These are very likely not valid for the AR5212 era + * NICs. + * + * Since these define signal sizing and threshold + * parameters, they may need changing based on the + * specific antenna and receive amplifier + * configuration. + */ +#define AR5416_DFS_FIRPWR -33 +#define AR5416_DFS_RRSSI 20 +#define AR5416_DFS_HEIGHT 10 +#define AR5416_DFS_PRSSI 15 +#define AR5416_DFS_INBAND 15 +#define AR5416_DFS_RELPWR 8 +#define AR5416_DFS_RELSTEP 12 +#define AR5416_DFS_MAXLEN 255 + +HAL_BOOL +ar5416GetDfsDefaultThresh(struct ath_hal *ah, HAL_PHYERR_PARAM *pe) +{ + + /* + * These are general examples of the parameter values + * to use when configuring radar pulse detection for + * the AR5416, AR91xx, AR92xx NICs. They are only + * for testing and do require tuning depending upon the + * hardware and deployment specifics. + */ + pe->pe_firpwr = AR5416_DFS_FIRPWR; + pe->pe_rrssi = AR5416_DFS_RRSSI; + pe->pe_height = AR5416_DFS_HEIGHT; + pe->pe_prssi = AR5416_DFS_PRSSI; + pe->pe_inband = AR5416_DFS_INBAND; + pe->pe_relpwr = AR5416_DFS_RELPWR; + pe->pe_relstep = AR5416_DFS_RELSTEP; + pe->pe_maxlen = AR5416_DFS_MAXLEN; + + return (AH_TRUE); +} + +/* * Get the radar parameter values and return them in the pe * structure */ _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 06:39:01 2012 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 92A14106566B; Fri, 24 Aug 2012 06:39:01 +0000 (UTC) (envelope-from prvs=576e6f874=Brett.Wright@cooperindustries.com) Received: from cooperlighting-sw.cooperlighting.com (cooperlighting-sw.cooperlighting.com [216.130.131.68]) by mx1.freebsd.org (Postfix) with ESMTP id 225B58FC0A; Fri, 24 Aug 2012 06:39:00 +0000 (UTC) Authentication-Results: cooperlighting-sw.cooperlighting.com; dkim=neutral (message not signed) header.i=none X-IronPort-AV: E=Sophos;i="4.80,302,1344225600"; d="scan'208";a="66479581" Received: from cipt0174.nam.ci.root ([10.132.108.174]) by cooperlighting-sw.cooperlighting.com with ESMTP; 24 Aug 2012 02:38:54 -0400 Received: from APEVS1.AP.CI.ROOT ([10.180.2.22]) by cipt0174.NAM.CI.ROOT with Microsoft SMTPSVC(6.0.3790.4675); Fri, 24 Aug 2012 02:38:54 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 24 Aug 2012 14:38:37 +0800 Message-ID: <475A4E02EFF4724A9E58F55A56AC131606667F85@APEVS1.ap.ci.root> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Atheros DFS radar detection Thread-Index: Ac2A/hLkCkFa4dvGTj2/or9DyI+qnQAxGlTg References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root><475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root><475A4E02EFF4724A9E58F55A56AC13160661F137@APEVS1.ap.ci.root> From: "Wright, Brett" To: "Adrian Chadd" X-OriginalArrivalTime: 24 Aug 2012 06:38:54.0434 (UTC) FILETIME=[21814C20:01CD81C3] Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: RE: Atheros DFS radar detection 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: Fri, 24 Aug 2012 06:39:01 -0000 > -----Original Message----- > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf > Of Adrian Chadd > Sent: Thursday, 23 August 2012 5:07 PM >=20 > Right. What happens when you adjust prssi by itself then? >=20 Adjusting prrsi by itself doesn't do much. Adjusting rrssi seems to help the most - but I have to push it right up to about 40 to 45. >=20 > I'll ask one of the baseband guys tomorrow and see what they think. > This is a really old chip though. They may not remember. :-) >=20 Thanks Brett From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 07:40:05 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 733AA106564A for ; Fri, 24 Aug 2012 07:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 585208FC08 for ; Fri, 24 Aug 2012 07:40:05 +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 q7O7e5Em063564 for ; Fri, 24 Aug 2012 07:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7O7e5TS063563; Fri, 24 Aug 2012 07:40:05 GMT (envelope-from gnats) Date: Fri, 24 Aug 2012 07:40:05 GMT Message-Id: <201208240740.q7O7e5TS063563@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/170904: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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, 24 Aug 2012 07:40:05 -0000 The following reply was made to PR kern/170904; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/170904: commit references a PR Date: Fri, 24 Aug 2012 07:32:51 +0000 (UTC) Author: adrian Date: Fri Aug 24 07:32:35 2012 New Revision: 239642 URL: http://svn.freebsd.org/changeset/base/239642 Log: Add the method to fetch the default DFS parameters for the AR5212 PHY. I need to check whether new parameters were added for the AR5413 NIC. PR: kern/170904 Modified: head/sys/dev/ath/ath_hal/ar5212/ar5212.h head/sys/dev/ath/ath_hal/ar5212/ar5212_attach.c head/sys/dev/ath/ath_hal/ar5212/ar5212_misc.c Modified: head/sys/dev/ath/ath_hal/ar5212/ar5212.h ============================================================================== --- head/sys/dev/ath/ath_hal/ar5212/ar5212.h Fri Aug 24 06:56:44 2012 (r239641) +++ head/sys/dev/ath/ath_hal/ar5212/ar5212.h Fri Aug 24 07:32:35 2012 (r239642) @@ -633,6 +633,8 @@ extern void ar5212AniReset(struct ath_ha extern HAL_BOOL ar5212IsNFCalInProgress(struct ath_hal *ah); extern HAL_BOOL ar5212WaitNFCalComplete(struct ath_hal *ah, int i); extern void ar5212EnableDfs(struct ath_hal *ah, HAL_PHYERR_PARAM *pe); +extern HAL_BOOL ar5212GetDfsDefaultThresh(struct ath_hal *ah, + HAL_PHYERR_PARAM *pe); extern void ar5212GetDfsThresh(struct ath_hal *ah, HAL_PHYERR_PARAM *pe); extern HAL_BOOL ar5212ProcessRadarEvent(struct ath_hal *ah, struct ath_rx_status *rxs, uint64_t fulltsf, const char *buf, Modified: head/sys/dev/ath/ath_hal/ar5212/ar5212_attach.c ============================================================================== --- head/sys/dev/ath/ath_hal/ar5212/ar5212_attach.c Fri Aug 24 06:56:44 2012 (r239641) +++ head/sys/dev/ath/ath_hal/ar5212/ar5212_attach.c Fri Aug 24 07:32:35 2012 (r239642) @@ -137,6 +137,7 @@ static const struct ath_hal_private ar52 /* DFS Functions */ .ah_enableDfs = ar5212EnableDfs, .ah_getDfsThresh = ar5212GetDfsThresh, + .ah_getDfsDefaultThresh = ar5212GetDfsDefaultThresh, .ah_procRadarEvent = ar5212ProcessRadarEvent, .ah_isFastClockEnabled = ar5212IsFastClockEnabled, .ah_get11nExtBusy = ar5212Get11nExtBusy, Modified: head/sys/dev/ath/ath_hal/ar5212/ar5212_misc.c ============================================================================== --- head/sys/dev/ath/ath_hal/ar5212/ar5212_misc.c Fri Aug 24 06:56:44 2012 (r239641) +++ head/sys/dev/ath/ath_hal/ar5212/ar5212_misc.c Fri Aug 24 07:32:35 2012 (r239642) @@ -1163,6 +1163,35 @@ ar5212EnableDfs(struct ath_hal *ah, HAL_ OS_REG_WRITE(ah, AR_PHY_RADAR_0, val | AR_PHY_RADAR_0_ENA); } +/* + * Parameters for the AR5212 PHY. + * + * TODO: figure out what values were added for the AR5413 and later + * PHY; update these here. + */ +#define AR5212_DFS_FIRPWR -41 +#define AR5212_DFS_RRSSI 12 +#define AR5212_DFS_HEIGHT 20 +#define AR5212_DFS_PRSSI 22 +#define AR5212_DFS_INBAND 6 + +HAL_BOOL +ar5212GetDfsDefaultThresh(struct ath_hal *ah, HAL_PHYERR_PARAM *pe) +{ + + pe->pe_firpwr = AR5212_DFS_FIRPWR; + pe->pe_rrssi = AR5212_DFS_RRSSI; + pe->pe_height = AR5212_DFS_HEIGHT; + pe->pe_prssi = AR5212_DFS_PRSSI; + pe->pe_inband = AR5212_DFS_INBAND; + /* XXX look up what is needed for the AR5413 */ + pe->pe_relpwr = 0; + pe->pe_relstep = 0; + pe->pe_maxlen = 0; + + return (AH_TRUE); +} + void ar5212GetDfsThresh(struct ath_hal *ah, HAL_PHYERR_PARAM *pe) { @@ -1250,7 +1279,7 @@ ar5212Get11nExtBusy(struct ath_hal *ah) } /* - * There's no channel survey support for the AR5211. + * There's no channel survey support for the AR5212. */ HAL_BOOL ar5212GetMibCycleCounts(struct ath_hal *ah, HAL_SURVEY_SAMPLE *hsample) _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 14:57:56 2012 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 CFFAC106566B for ; Fri, 24 Aug 2012 14:57:56 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 436038FC16 for ; Fri, 24 Aug 2012 14:57:55 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so1408737lbb.13 for ; Fri, 24 Aug 2012 07:57:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=FDTA24TOG0WHSlJf2MKObbueWbgTPdkafAT1Ihe1p70=; b=EN9yNvZtnAFwZJL8hRLuLrR18QOpO15FMRav19UNwDqGOPeJKbRFStLD4tKt04TRub Rf7RXItvwG0ne7KmBvZsLLzjgSX5zG/nuOh5xkyPwClGKQ3HnjKWuCSApeIysATLf5sb AN5BbHHdJEjvfAAA90YWmQWXFf9+NskkKQho7PG0hmqdpu++kiam1HETBmYenRdMNIJM bABRiLm0ZO6bmehM4ub7/jtPW9WMWUmzurljJjHujsbHasKeEL307JWmJa3nso0MZuJw Fs8YmsXzzH6W5QfeEhiGnsUeWiCPv+1VLqrulTq+nCyP5qYYbe3WQNNU8M7X8VjVz+xq vuIQ== MIME-Version: 1.0 Received: by 10.152.103.146 with SMTP id fw18mr6158693lab.30.1345820274292; Fri, 24 Aug 2012 07:57:54 -0700 (PDT) Sender: bschmidt@techwires.net Received: by 10.152.123.200 with HTTP; Fri, 24 Aug 2012 07:57:54 -0700 (PDT) X-Originating-IP: [79.140.39.245] In-Reply-To: References: <201207300139326668335@gmail.com> <201208201829.10554.bschmidt@freebsd.org> <201208212047.50852.bschmidt@freebsd.org> <201208231430163933460@gmail.com> Date: Fri, 24 Aug 2012 16:57:54 +0200 X-Google-Sender-Auth: 6AHm7jQGRNYeY76_4Fn6yDFIdOQ Message-ID: From: Bernhard Schmidt To: =?UTF-8?B?5LmU5qWa?= Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlPAPaEbZDoKAc6WLn7oFboyMqkvHZv1Fhk7BfbsQ3snbwr/c3yZaPokLSda2or8D4B/r1E Cc: freebsd-wireless Subject: Re: Re: iwn0/wlan0 scan WPA2-PSK/AES as WEP on freebsd9 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: Fri, 24 Aug 2012 14:57:56 -0000 On Thu, Aug 23, 2012 at 3:52 PM, =C7=C7=B3=FE wrote: > 2012/8/23 =C7=C7=B3=FE/HonestQiao : >> I'll test it today night. > > Good news. > Nothing changed on My AP, My FreeBSD can connect to My AP with your > patched file. Thanks. Change is in tree now, also in the next 9.1 build. --=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 16:22: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 3076E106566B for ; Fri, 24 Aug 2012 16:22:03 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id BE9738FC17 for ; Fri, 24 Aug 2012 16:22:02 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:b893:d73f:3750:2064]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 5C1754AC2D for ; Fri, 24 Aug 2012 20:22:01 +0400 (MSK) Date: Fri, 24 Aug 2012 20:21:55 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <199007581.20120824202155@serebryakov.spb.ru> To: freebsd-wireless MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Fri, 24 Aug 2012 16:22:03 -0000 Hello, freebsd-wireless. hostapd and wpa_supplicat have support for many compile-time options, most of which are disabled (not enabled) by FreeBSD build system. 802.11w, 802.11r and WPS support are most notable ones. Is it intentional, or ``by chance''? Does these features support by FreeBSD 802.11 stack (and does special support from drivers needed for them), and these options could be enabled, or they needed more kernel-side code? -- // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 16:46:24 2012 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 BCC46106568F; Fri, 24 Aug 2012 16:46:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 865DD8FC1A; Fri, 24 Aug 2012 16:46:24 +0000 (UTC) Received: by dadr6 with SMTP id r6so1065851dad.13 for ; Fri, 24 Aug 2012 09:46:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qxMWxAJyTGgSGyTpFnxkASKNTM09FxC09DzycSShhQQ=; b=aBqg75/9ctn3BFCrdv1kcHYUKHLe84i7iV8OGLJ817HFn/49nf2ZCVSG0Kfbb2obzB sa4dN2Jvrl9LNWNbjCxiMNauv4UE8+6mM2+97BsUXQKeREG+HJus7VFZiROvFdYoqPRR f/VutlDqRn+zlDIVXFr6jjtg520hXL7YO0KE8UHXZRPvhAKPxiiSI09jPDpBNP0H+VpE kLA71ElIg45OYbrHVPf9/jVa5ilEKFtyYI8jzh1o962799pq+iYXUWEsgUA2dOFO0q6O EePPSgpVm+HIUNTE1rHEGJeRbRvob0owMmeQAICIoIqKbF/DVkJr34G1/EIPCZ7UQPq7 Wjjg== MIME-Version: 1.0 Received: by 10.68.231.233 with SMTP id tj9mr14306058pbc.39.1345826783919; Fri, 24 Aug 2012 09:46:23 -0700 (PDT) Received: by 10.68.36.106 with HTTP; Fri, 24 Aug 2012 09:46:23 -0700 (PDT) Received: by 10.68.36.106 with HTTP; Fri, 24 Aug 2012 09:46:23 -0700 (PDT) In-Reply-To: <199007581.20120824202155@serebryakov.spb.ru> References: <199007581.20120824202155@serebryakov.spb.ru> Date: Fri, 24 Aug 2012 09:46:23 -0700 Message-ID: From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Fri, 24 Aug 2012 16:46:24 -0000 Enable, play and see? On Aug 24, 2012 9:22 AM, "Lev Serebryakov" wrote: > Hello, freebsd-wireless. > > hostapd and wpa_supplicat have support for many compile-time > options, most of which are disabled (not enabled) by FreeBSD build > system. 802.11w, 802.11r and WPS support are most notable ones. > > Is it intentional, or ``by chance''? Does these features support by > FreeBSD 802.11 stack (and does special support from drivers needed > for them), and these options could be enabled, or they needed more > kernel-side code? > > -- > // Black Lion AKA Lev Serebryakov > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:15:11 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 3DA7E106566B; Fri, 24 Aug 2012 17:15:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0523B8FC16; Fri, 24 Aug 2012 17:15:10 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so3926916pbb.13 for ; Fri, 24 Aug 2012 10:15:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mS+PvY8wrhpO0I9KzCCUY/oVYCHQUXtCA1hHjldO2wk=; b=0BOI/ST9X5qLYrjRT2vnVtHBSARRJMFcMZMxnmnBiWsCxOgVzi3+evMoW2DVHm61nC RXVCHNeAyNHjsg/VYDRaCOyNmInXiNOLLHEcxa9iupm0OLsgcK7Rr5mQwlVD4Pr6h4T/ CVjptItedzmC5c8CGUWJep4A28Ue0BLCzMfSPukRwwfG1AsUmuae1xNhxPJrKuflKx3C vvziXXroXMoAeC/j6E3e1riT7sM1C7L75CmYOCwskBfv6ibfVFa3mP0KtAsJ/YgWDW4z J5vUgrt9nvm1xUR+qEo52yJDYXBRzyAVWogKZc+n16ki9Ee4G12Y8OpjT4dm9VOiYHU0 4RCQ== MIME-Version: 1.0 Received: by 10.66.85.4 with SMTP id d4mr12265696paz.11.1345828510244; Fri, 24 Aug 2012 10:15:10 -0700 (PDT) Received: by 10.68.36.106 with HTTP; Fri, 24 Aug 2012 10:15:10 -0700 (PDT) In-Reply-To: <201208241910.35576.bschmidt@techwires.net> References: <199007581.20120824202155@serebryakov.spb.ru> <201208241910.35576.bschmidt@techwires.net> Date: Fri, 24 Aug 2012 10:15:10 -0700 Message-ID: From: Adrian Chadd To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Fri, 24 Aug 2012 17:15:11 -0000 On 24 August 2012 10:10, Bernhard Schmidt wrote: > On Friday 24 August 2012 18:46:23 Adrian Chadd wrote: >> Enable, play and see? > > ACK. :) > There is more interesting stuff available which needs someone to look > into, eg. briding support and VLANs. I guess the bridging stuff is > required to get 11r running. 11w though requires hardware support if > I'm not totally of. > > There are even a lot of 11n options available which are currently not > supported nor in any other way tunable, this requires stack work, not > only for the supplicant but also for ifconfig. There's also likely a whole bunch of driver and stack things we need. Eg, we need correct VLAN handling (which is fine, we SHOULD have it in net80211, I just don't think it's been tested in a long time.) There's also off-channel traffic support which I know we don't currently do. I have a looong list of 802.11n things to add to the ath driver and debug (correct LDPC/STBC negotiation and driver handling, rate control stuff, AP power save, STA power save, background scanning and off-channel traffic, MIMO power save negotiation and support, correct PS-POLL handling, looking at uAPSD STA/AP handling, adhoc, TDMA...) before I even begin to look at that more fun stuff. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:16:46 2012 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 E2E32106572D for ; Fri, 24 Aug 2012 17:16:44 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 250AA8FC12 for ; Fri, 24 Aug 2012 17:16:43 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1334433bkc.13 for ; Fri, 24 Aug 2012 10:16:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=akA6i7frMqslmKEYdLS09tRDDfJ7P0z5DVMX2v+Pb/E=; b=I7u3EJqsged/9NODz4hxajB8CApfQdV9V8vC6LoO/a3aRaSktemxJ0T0sYves0kad2 Zg8HWKlJ2tjZXQBt/N4uJBLOfo0QQQ2Ppw2ZNE7UG0fe5XdF7k/5vo3SrjFoCUf/TqVB 0T39h8vYXKW/N74xqtatk3/qAkephVbTLk/txnNaJMcN4fzLtkCkFEqfkkBiT8R21UJp b0ifpYMf50j6o4SZo4AICqBr6D/a+kebRHMxp3Bug7Z4wOVtOsq4Kx/WQ5NgymoJqrt+ bWQvtBtllvIMeNznNybtH/sLJQETc7CA4IBPV62nOSyzo09G7k1rCX5531jacZU2u7+C wvvg== Received: by 10.205.129.10 with SMTP id hg10mr2238398bkc.78.1345828200350; Fri, 24 Aug 2012 10:10:00 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-067-209-027.pools.arcor-ip.net. [88.67.209.27]) by mx.google.com with ESMTPS id fu8sm6737151bkc.5.2012.08.24.10.09.59 (version=SSLv3 cipher=OTHER); Fri, 24 Aug 2012 10:09:59 -0700 (PDT) From: Bernhard Schmidt To: freebsd-wireless@freebsd.org Date: Fri, 24 Aug 2012 19:10:35 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-RC1; KDE/4.7.4; amd64; ; ) References: <199007581.20120824202155@serebryakov.spb.ru> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208241910.35576.bschmidt@techwires.net> X-Gm-Message-State: ALoCoQnXHsPl3ktIbTzzR+us+Vh/84KWXECja3YVUXxGn3ro3vFv2oUrw+EqQiawjRfXC8v3pAPW Cc: Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Fri, 24 Aug 2012 17:16:47 -0000 On Friday 24 August 2012 18:46:23 Adrian Chadd wrote: > Enable, play and see? ACK. > On Aug 24, 2012 9:22 AM, "Lev Serebryakov" wrote: > > > Hello, freebsd-wireless. > > > > hostapd and wpa_supplicat have support for many compile-time > > options, most of which are disabled (not enabled) by FreeBSD build > > system. 802.11w, 802.11r and WPS support are most notable ones. > > > > Is it intentional, or ``by chance''? Does these features support by > > FreeBSD 802.11 stack (and does special support from drivers needed > > for them), and these options could be enabled, or they needed more > > kernel-side code? There is more interesting stuff available which needs someone to look into, eg. briding support and VLANs. I guess the bridging stuff is required to get 11r running. 11w though requires hardware support if I'm not totally of. There are even a lot of 11n options available which are currently not supported nor in any other way tunable, this requires stack work, not only for the supplicant but also for ifconfig. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:40:19 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 72B331065767 for ; Fri, 24 Aug 2012 17:40:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1C75E8FC20 for ; Fri, 24 Aug 2012 17:40:04 +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 q7OHe3tp048470 for ; Fri, 24 Aug 2012 17:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7OHe3aB048469; Fri, 24 Aug 2012 17:40:03 GMT (envelope-from gnats) Date: Fri, 24 Aug 2012 17:40:03 GMT Message-Id: <201208241740.q7OHe3aB048469@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/170904: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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, 24 Aug 2012 17:40:19 -0000 The following reply was made to PR kern/170904; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/170904: commit references a PR Date: Fri, 24 Aug 2012 17:37:26 +0000 (UTC) Author: adrian Date: Fri Aug 24 17:37:12 2012 New Revision: 239656 URL: http://svn.freebsd.org/changeset/base/239656 Log: Add an accessor macro for getting access to the default DFS parameters. PR: kern/170904 Modified: head/sys/dev/ath/if_athvar.h Modified: head/sys/dev/ath/if_athvar.h ============================================================================== --- head/sys/dev/ath/if_athvar.h Fri Aug 24 17:08:02 2012 (r239655) +++ head/sys/dev/ath/if_athvar.h Fri Aug 24 17:37:12 2012 (r239656) @@ -1185,6 +1185,8 @@ void ath_intr(void *); ((*(_ah)->ah_enableDfs)((_ah), (_param))) #define ath_hal_getdfsthresh(_ah, _param) \ ((*(_ah)->ah_getDfsThresh)((_ah), (_param))) +#define ath_hal_getdfsdefaultthresh(_ah, _param) \ + ((*(_ah)->ah_getDfsDefaultThresh)((_ah), (_param))) #define ath_hal_procradarevent(_ah, _rxs, _fulltsf, _buf, _event) \ ((*(_ah)->ah_procRadarEvent)((_ah), (_rxs), (_fulltsf), \ (_buf), (_event))) _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:40:19 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 76249106576E for ; Fri, 24 Aug 2012 17:40:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 523858FC22 for ; Fri, 24 Aug 2012 17:40:06 +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 q7OHe6gx048475 for ; Fri, 24 Aug 2012 17:40:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7OHe6Ai048474; Fri, 24 Aug 2012 17:40:06 GMT (envelope-from gnats) Date: Fri, 24 Aug 2012 17:40:06 GMT Message-Id: <201208241740.q7OHe6Ai048474@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/170904: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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, 24 Aug 2012 17:40:19 -0000 The following reply was made to PR kern/170904; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/170904: commit references a PR Date: Fri, 24 Aug 2012 17:38:05 +0000 (UTC) Author: adrian Date: Fri Aug 24 17:37:51 2012 New Revision: 239657 URL: http://svn.freebsd.org/changeset/base/239657 Log: Correctly handle the "pe_enabled" flag - both when configuring DFS and fetching the current DFS configuration. PR: kern/170904 Modified: head/sys/dev/ath/ath_hal/ar5212/ar5212_misc.c Modified: head/sys/dev/ath/ath_hal/ar5212/ar5212_misc.c ============================================================================== --- head/sys/dev/ath/ath_hal/ar5212/ar5212_misc.c Fri Aug 24 17:37:12 2012 (r239656) +++ head/sys/dev/ath/ath_hal/ar5212/ar5212_misc.c Fri Aug 24 17:37:51 2012 (r239657) @@ -1160,7 +1160,12 @@ ar5212EnableDfs(struct ath_hal *ah, HAL_ val &= ~AR_PHY_RADAR_0_INBAND; val |= SM(pe->pe_inband, AR_PHY_RADAR_0_INBAND); } - OS_REG_WRITE(ah, AR_PHY_RADAR_0, val | AR_PHY_RADAR_0_ENA); + if (pe->pe_enabled) + val |= AR_PHY_RADAR_0_ENA; + else + val &= ~ AR_PHY_RADAR_0_ENA; + + OS_REG_WRITE(ah, AR_PHY_RADAR_0, val); } /* @@ -1206,6 +1211,7 @@ ar5212GetDfsThresh(struct ath_hal *ah, H pe->pe_height = MS(val, AR_PHY_RADAR_0_HEIGHT); pe->pe_prssi = MS(val, AR_PHY_RADAR_0_PRSSI); pe->pe_inband = MS(val, AR_PHY_RADAR_0_INBAND); + pe->pe_enabled = !! (val & AR_PHY_RADAR_0_ENA); pe->pe_relpwr = 0; pe->pe_relstep = 0; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:50:03 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9556106564A for ; Fri, 24 Aug 2012 17:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BE4F38FC08 for ; Fri, 24 Aug 2012 17:50:03 +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 q7OHo305049218 for ; Fri, 24 Aug 2012 17:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7OHo3xP049217; Fri, 24 Aug 2012 17:50:03 GMT (envelope-from gnats) Date: Fri, 24 Aug 2012 17:50:03 GMT Message-Id: <201208241750.q7OHo3xP049217@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/170904: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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, 24 Aug 2012 17:50:03 -0000 The following reply was made to PR kern/170904; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/170904: commit references a PR Date: Fri, 24 Aug 2012 17:40:21 +0000 (UTC) Author: adrian Date: Fri Aug 24 17:39:57 2012 New Revision: 239658 URL: http://svn.freebsd.org/changeset/base/239658 Log: Remove the hard-coded AR5416-series parameters and instead use the DFS parameters fetched from the HAL. Check whether the specific chipset supports RADAR reporting before enabling DFS; or some of the (unset) DFS methods may fail. Tested: * AR5210 (correctly didn't enable radar PHY reporting) * AR5212 (correctly enabled radar PHY reporting w/ the correct default parameters.) TODO: * Now that I have this capability check in place, I could remove the (empty) DFS methods from AR5210/AR5211. * Test on AR5416, AR9160, AR9280. PR: kern/170904 Modified: head/sys/dev/ath/ath_dfs/null/dfs_null.c Modified: head/sys/dev/ath/ath_dfs/null/dfs_null.c ============================================================================== --- head/sys/dev/ath/ath_dfs/null/dfs_null.c Fri Aug 24 17:37:51 2012 (r239657) +++ head/sys/dev/ath/ath_dfs/null/dfs_null.c Fri Aug 24 17:39:57 2012 (r239658) @@ -72,28 +72,6 @@ __FBSDID("$FreeBSD$"); #include /* - * These are default parameters for the AR5416 and - * later 802.11n NICs. They simply enable some - * radar pulse event generation. - * - * These are very likely not valid for the AR5212 era - * NICs. - * - * Since these define signal sizing and threshold - * parameters, they may need changing based on the - * specific antenna and receive amplifier - * configuration. - */ -#define AR5416_DFS_FIRPWR -33 -#define AR5416_DFS_RRSSI 20 -#define AR5416_DFS_HEIGHT 10 -#define AR5416_DFS_PRSSI 15 -#define AR5416_DFS_INBAND 15 -#define AR5416_DFS_RELPWR 8 -#define AR5416_DFS_RELSTEP 12 -#define AR5416_DFS_MAXLEN 255 - -/* * Methods which are required */ @@ -125,30 +103,27 @@ ath_dfs_radar_enable(struct ath_softc *s #if 0 HAL_PHYERR_PARAM pe; + /* Check if the hardware supports radar reporting */ + /* XXX TODO: migrate HAL_CAP_RADAR/HAL_CAP_AR to somewhere public! */ + if (ath_hal_getcapability(sc->sc_ah, + HAL_CAP_PHYDIAG, 0, NULL) != HAL_OK) + return (0); + /* Check if the current channel is radar-enabled */ if (! IEEE80211_IS_CHAN_DFS(chan)) return (0); + /* Fetch the default parameters */ + memset(&pe, '\0', sizeof(pe)); + if (! ath_hal_getdfsdefaultthresh(sc->sc_ah, &pe)) + return (0); + /* Enable radar PHY error reporting */ sc->sc_dodfs = 1; - /* - * These are general examples of the parameter values - * to use when configuring radar pulse detection for - * the AR5416, AR91xx, AR92xx NICs. They are only - * for testing and do require tuning depending upon the - * hardware and deployment specifics. - */ - pe.pe_firpwr = AR5416_DFS_FIRPWR; - pe.pe_rrssi = AR5416_DFS_RRSSI; - pe.pe_height = AR5416_DFS_HEIGHT; - pe.pe_prssi = AR5416_DFS_PRSSI; - pe.pe_inband = AR5416_DFS_INBAND; - pe.pe_relpwr = AR5416_DFS_RELPWR; - pe.pe_relstep = AR5416_DFS_RELSTEP; - pe.pe_maxlen = AR5416_DFS_MAXLEN; + /* Tell the hardware to enable radar reporting */ pe.pe_enabled = 1; - + /* Flip on extension channel events only if doing HT40 */ if (IEEE80211_IS_CHAN_HT40(chan)) pe.pe_extchannel = 1; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:50:33 2012 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 A10241065670 for ; Fri, 24 Aug 2012 17:50:33 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 24FC68FC0C for ; Fri, 24 Aug 2012 17:50:32 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1350008bkc.13 for ; Fri, 24 Aug 2012 10:50:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=VhJAdwpD3x7SOuIgJrX9Drygo/mvwM//dCNJiuthTVE=; b=aeeS72CA/ensljVYC2A+MTG2Fzt5GYBCuC66vIXiyTf+WWehHPCOj4tye1gc4eFhQT 5Km53v+x9lKtC7rjJfm609rITmARbOf8HXJNnGin0zqP6mCsT2pj6urXdcxn6ytvxq9X NOlZ3ltDkXLhUhdnW7NAvoJgYfOySBAh5hHApxZEiqpDQVorGIgPoARnf04qVHjHTNCa 2yznlfkRm2/JqrZ3W5WOTF0B+vOQnexIh37Zg6rA5g3LwwS55CU0I++2PukqrsxwWVsk QTu+FJpkLWMGPc9zSf3Yik4+KUKzYU+9N/jfA+esRF5Iq/67zTZ66Uvl0WCcWsyIh/6h pmbw== Received: by 10.204.148.12 with SMTP id n12mr936225bkv.6.1345830631733; Fri, 24 Aug 2012 10:50:31 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-067-209-027.pools.arcor-ip.net. [88.67.209.27]) by mx.google.com with ESMTPS id gq2sm6779995bkc.13.2012.08.24.10.50.30 (version=SSLv3 cipher=OTHER); Fri, 24 Aug 2012 10:50:31 -0700 (PDT) From: Bernhard Schmidt To: Adrian Chadd Date: Fri, 24 Aug 2012 19:51:06 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-RC1; KDE/4.7.4; amd64; ; ) References: <199007581.20120824202155@serebryakov.spb.ru> <201208241910.35576.bschmidt@techwires.net> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208241951.06694.bschmidt@techwires.net> X-Gm-Message-State: ALoCoQmnmmCilPu7cMD0ZqrGhEgvb/qwbs31rqhkumY/8AuGHiZ+XgFXjYNJBeVDB+GHQMvUIGft Cc: freebsd-wireless@freebsd.org Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Fri, 24 Aug 2012 17:50:33 -0000 On Friday 24 August 2012 19:15:10 Adrian Chadd wrote: > On 24 August 2012 10:10, Bernhard Schmidt wrote: > > There is more interesting stuff available which needs someone to look > > into, eg. briding support and VLANs. I guess the bridging stuff is > > required to get 11r running. 11w though requires hardware support if > > I'm not totally of. > > > > There are even a lot of 11n options available which are currently not > > supported nor in any other way tunable, this requires stack work, not > > only for the supplicant but also for ifconfig. > > There's also likely a whole bunch of driver and stack things we need. > Eg, we need correct VLAN handling (which is fine, we SHOULD have it in > net80211, I just don't think it's been tested in a long time.) There's > also off-channel traffic support which I know we don't currently do. Na.. not VLAN over WLAN (well, yeah, that needs to be looked into also), hostapd is able to shove STAs into different VLANs (on the wired interface) based on Radius rules. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:52:00 2012 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 2138F1065673 for ; Fri, 24 Aug 2012 17:52:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E104D8FC0C for ; Fri, 24 Aug 2012 17:51:59 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so3985166pbb.13 for ; Fri, 24 Aug 2012 10:51:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=tVpul+8VPvKS7gXeEv9fwGH6BGu5LhBwr15EgVrm/bc=; b=s9a6rxkjbxGWqzcYw5nn/QPBgwE1pKOdHB9liqSN4RSRpvUxANWi1dLTsoDH0MNfoq fUHkLoDgujPrM3wIhVCQQ4j8E7GZmji0Z6IWdPXusyQqBPZocZEkMuXmyMLyC/efUCKt cX7JxohJhvsW8xM1r4+eVaDVhKIJhhXYzbmFxf4GtXDFvjGpGt2uH+kOY9bzHrXup07a TUcjARj4RhQ2GRr/pucLR0gke2sz2RrrPBy/y54OAkDRxhOmVsvRNmJf8qIS6hLba8vF 2p2TzbI96ZAmR4Z/49mwVR82ZEinB+ptd5NOS8BpsvcAdM6NQ9sbrDqRitvuxKogi+aI JUAQ== MIME-Version: 1.0 Received: by 10.66.76.227 with SMTP id n3mr12297443paw.53.1345830719530; Fri, 24 Aug 2012 10:51:59 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Fri, 24 Aug 2012 10:51:59 -0700 (PDT) In-Reply-To: <475A4E02EFF4724A9E58F55A56AC131606667F85@APEVS1.ap.ci.root> References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661F137@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC131606667F85@APEVS1.ap.ci.root> Date: Fri, 24 Aug 2012 10:51:59 -0700 X-Google-Sender-Auth: zKMLi9GwGpvGJ11zTb3FfoIjkEY Message-ID: From: Adrian Chadd To: "Wright, Brett" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: Re: Atheros DFS radar detection 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: Fri, 24 Aug 2012 17:52:00 -0000 Hi Brett, I've been productive! * I've added a default radar parameter method to the AR5212 and AR5416 HALs, so now the default parameters are stored there; * I've extended dfs_null (behind #if 0 for now) to fetch these parameters and program them in - as well as only doing it for NICs where DFS is supported. * I've taught my pktlog/libradarpkt code (in user/adrian/ath_radar_stuff) to parse the AR5212 records - so all you need to do is set dev.ath.X.monpass=0xff, then run my pktlog program to see what's going on I haven't yet sat down and done actual radar pulse train detection with the AR5212 and I know it's just going to plain suck at doing chirps in a busy environment (as they just look like long pulses; there's no FFT data to assist the software in decoding what's going on) but it should be enough to get you started. Have you tried these NICs on different hardware? I wonder if you're seeing some kind of spur or board noise that's contributing to both the false detections and the high noise floor calibration value. I don't have an SR-5 here to test against I'm afraid.. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:52:18 2012 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 C2FEB106564A for ; Fri, 24 Aug 2012 17:52:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8D5318FC18 for ; Fri, 24 Aug 2012 17:52:18 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp2so3985166pbb.13 for ; Fri, 24 Aug 2012 10:52:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Ys7gkXSJwzgZi82iWpgD2QVRCjzW1hgQ2EBpIiwwOUk=; b=qIYOlzGzLEu5Czx7K+1LwNtUkhdDf9q6eSAdbC8gov9ViHa8wIkvZ3NiUi/sEZsvYc zA/flaWvm7Jiei0TzFbuClp3bBfPc5i2URb/ZzyHwluegR0wXP4WE28ql9hRWf+fRcK8 UzLH82FblB1cQhhK7cp6DKVqp9Y+0T6tINXnO0zHWkFY9LjxS+SvTgdlwVkeK8wh5Okj YGLCb1VtdUg1x8GDn7pAuCtPmUxRTbU9Kj3P7xFii/X4kfhvL1cMdJ5mzMMDT+zPP2VJ aN3zCxTX5/B6S4FB7r0Lh1UrIuDu3AvlyJYfFO6d18M+SNSwu6jbbPEz21HGf7wpTnUK u9lw== MIME-Version: 1.0 Received: by 10.68.236.102 with SMTP id ut6mr14592344pbc.113.1345830738421; Fri, 24 Aug 2012 10:52:18 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Fri, 24 Aug 2012 10:52:18 -0700 (PDT) In-Reply-To: References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC13160661F137@APEVS1.ap.ci.root> <475A4E02EFF4724A9E58F55A56AC131606667F85@APEVS1.ap.ci.root> Date: Fri, 24 Aug 2012 10:52:18 -0700 X-Google-Sender-Auth: aKN0shhOglfYSqh0Fqnd8rwNaOk Message-ID: From: Adrian Chadd To: "Wright, Brett" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: Re: Atheros DFS radar detection 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: Fri, 24 Aug 2012 17:52:18 -0000 .. oh, and I haven't yet added the diversity change to the AR5212 HAL when doing radar. I'll add that shortly. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 17:54:27 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 0756B106564A; Fri, 24 Aug 2012 17:54:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C80B58FC0C; Fri, 24 Aug 2012 17:54:26 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so3988882pbb.13 for ; Fri, 24 Aug 2012 10:54:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RIxhkqU3dxI0SwIa2RVPjj9sZQ8wNF+kgHq6WuSNT/Y=; b=04g2aqrcqAc1cdHX/dElofgXiKFN66J7ko5FbYbO8BXJUMXIOuii4sf9hPvSXb1Nzu saEH6cDGGZT60j+JQXUIU3Qh4AszuFnR1GIBafqIXh7NIoxe7zwC374CrDwiciJS7dJ8 f7gmyOOMv4ZPh1V7fCfiIr8XCDSfWXFY34xVxhrjpG7H0NGz8Z+5tg/VcGGjjDA9+oZ4 53m8Mp9r7WFtdMvM9odnhbssSmQtQscH6e50hRmUqKMlHpIJTQOGtlvTDw7vw3gJYWJd GOfqntCCwPf7P2f/b2V1nIbbzBDASzQhu/lqFTf5ixnwnEiuEJr5RuTXbYcwba5g0tiQ Aa6w== MIME-Version: 1.0 Received: by 10.66.85.4 with SMTP id d4mr12480199paz.11.1345830866371; Fri, 24 Aug 2012 10:54:26 -0700 (PDT) Received: by 10.68.36.106 with HTTP; Fri, 24 Aug 2012 10:54:26 -0700 (PDT) In-Reply-To: <201208241951.06694.bschmidt@techwires.net> References: <199007581.20120824202155@serebryakov.spb.ru> <201208241910.35576.bschmidt@techwires.net> <201208241951.06694.bschmidt@techwires.net> Date: Fri, 24 Aug 2012 10:54:26 -0700 Message-ID: From: Adrian Chadd To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Fri, 24 Aug 2012 17:54:27 -0000 On 24 August 2012 10:51, Bernhard Schmidt wrote: >> There's also likely a whole bunch of driver and stack things we need. >> Eg, we need correct VLAN handling (which is fine, we SHOULD have it in >> net80211, I just don't think it's been tested in a long time.) There's >> also off-channel traffic support which I know we don't currently do. > > Na.. not VLAN over WLAN (well, yeah, that needs to be looked into > also), hostapd is able to shove STAs into different VLANs (on the wired > interface) based on Radius rules. Right. I wonder what the "vlan" tag in the net80211 node is for. Is that for VLAN over WLAN? Yeah, being able to map a STA into a VLAN would be cool, but then we'd have to figure out where to do the bridging and how to tell net80211 to do that mapping to vlan subinterfaces.. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 20:42: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 9445D106566B for ; Fri, 24 Aug 2012 20:42:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 537778FC1D for ; Fri, 24 Aug 2012 20:42:35 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:b893:d73f:3750:2064]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id CEA534AC2D for ; Sat, 25 Aug 2012 00:42:28 +0400 (MSK) Date: Sat, 25 Aug 2012 00:42:22 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1086983773.20120825004222@serebryakov.spb.ru> To: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Administrative question to whom is responsible for wireless@ settings. 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: Fri, 24 Aug 2012 20:42:36 -0000 Hello, Freebsd-wireless. Now list differs in settings with (most?) other FreeBSD lists. Id doesn't sent messages, which was Replied To All to receiver via list itself. It is very inconvenient, as e-mail client filters, tuned for "List-Id:" header could not put answers to list (and me at same time) properly and threads in list's folder becomes broken. Any other list I'm subscribed (current@, net@, hackers@, developers@) sent message to me in such case (with all List-XXX: headers and footer), but wireless@ don't -- I get only direct messages, as CC'ed person. Could it be fixed, please? -- // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 20:43:24 2012 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 9AF4D106566B for ; Fri, 24 Aug 2012 20:43:24 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 323918FC17 for ; Fri, 24 Aug 2012 20:43:24 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:b893:d73f:3750:2064]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id E016B4AC2D; Sat, 25 Aug 2012 00:43:22 +0400 (MSK) Date: Sat, 25 Aug 2012 00:43:16 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <122600912.20120825004316@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <199007581.20120824202155@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Fri, 24 Aug 2012 20:43:24 -0000 Hello, Adrian. You wrote 24 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 20:46:23: AC> Enable, play and see? Most of these features needs more hardware than I have. Roaming between BSS? I need second AP... --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 20:45:05 2012 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 6FB961065670 for ; Fri, 24 Aug 2012 20:45:05 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 206B68FC19 for ; Fri, 24 Aug 2012 20:45:04 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:b893:d73f:3750:2064]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 6B4B34AC2D; Sat, 25 Aug 2012 00:45:03 +0400 (MSK) Date: Sat, 25 Aug 2012 00:44:57 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <517967128.20120825004457@serebryakov.spb.ru> To: Bernhard Schmidt In-Reply-To: <201208241910.35576.bschmidt@techwires.net> References: <199007581.20120824202155@serebryakov.spb.ru> <201208241910.35576.bschmidt@techwires.net> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Fri, 24 Aug 2012 20:45:05 -0000 Hello, Bernhard. You wrote 24 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 21:10:35: BS> There is more interesting stuff available which needs someone to look BS> into, eg. briding support and VLANs. I guess the bridging stuff is BS> required to get 11r running. 11w though requires hardware support if BS> I'm not totally of. BS> There are even a lot of 11n options available which are currently not BS> supported nor in any other way tunable, this requires stack work, not BS> only for the supplicant but also for ifconfig. Where could I read about all this stuff? Standards? And is here any source but sources (;-)) to understand wha is implemented now and what is not? --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 24 20:45:17 2012 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 0022A106566C for ; Fri, 24 Aug 2012 20:45:16 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id A4ADE8FC08 for ; Fri, 24 Aug 2012 20:45:16 +0000 (UTC) Received: by vbmv11 with SMTP id v11so3292358vbm.13 for ; Fri, 24 Aug 2012 13:45:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fXtMWjyoGQ8WtdWy34g+7RKr+IPKbBeJxmDLYRSZtcI=; b=aiRWvK5smxuGhJezgem2A1faEAlbzkzvg5zsrS0BJEGTU/lB8dtcIVaRES98Q+dC7U 9MCtf+qvWsl59AQTdgaYezR2dkhqtv/Iw3KRph2zZ8LkfZ76z+ZiRqjS3rYghzt+I3vs rlSpQgkJJIKWVwC2f90FYbD9FEVG8RVg3m0iM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=fXtMWjyoGQ8WtdWy34g+7RKr+IPKbBeJxmDLYRSZtcI=; b=cpLT5SC8CZriOWGTnoAi63GLpfyNJiOXHPah7TR66uun2OVk5wOpvsKbKZgddDS6bp EwnNstqySbefcYdVrQj1TTRyvdWPjQgA3dEMqq0X0PTi1+NZ3rjQV9458Wrc1hx1zw5d BizMnadVxyq/4PYilYBxiYXvYzrDucyG8vH63AHQz3KCAVMlPSgC0rgiHq71Vawj6Sjh WjxFT8s/b3qyy/ZCa2i0tT1d22myCx2jpY1MG1Qy3SJXoJAIJTDfWQ8oQlvvi2hwcKJq qC82NisyDEbrmuP3VvK6auK6nypUvZU7E7o1xH2SWc9/mcr6QCQrkj2q9vbF4X8Ja9Gc lHnw== Received: by 10.220.141.208 with SMTP id n16mr5742970vcu.22.1345841115861; Fri, 24 Aug 2012 13:45:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.190.227 with HTTP; Fri, 24 Aug 2012 13:44:44 -0700 (PDT) In-Reply-To: <1086983773.20120825004222@serebryakov.spb.ru> References: <1086983773.20120825004222@serebryakov.spb.ru> From: Eitan Adler Date: Fri, 24 Aug 2012 16:44:44 -0400 Message-ID: To: postmaster Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlwXscCrqRJn1pLGmRBMipFylJIDA8OebPQbs5iTtze9WznGIws/fQaI3rijPi4a8qLQPuk Cc: freebsd-wireless@freebsd.org Subject: Re: Administrative question to whom is responsible for wireless@ settings. 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: Fri, 24 Aug 2012 20:45:17 -0000 sending this to the mailing list administrators On 24 August 2012 16:42, Lev Serebryakov wrote: > Hello, Freebsd-wireless. > > Now list differs in settings with (most?) other FreeBSD lists. Id > doesn't sent messages, which was Replied To All to receiver via list > itself. It is very inconvenient, as e-mail client filters, tuned for > "List-Id:" header could not put answers to list (and me at same time) > properly and threads in list's folder becomes broken. > > Any other list I'm subscribed (current@, net@, hackers@, > developers@) sent message to me in such case (with all List-XXX: > headers and footer), but wireless@ don't -- I get only direct > messages, as CC'ed person. > > Could it be fixed, please? > > -- > // Black Lion AKA Lev Serebryakov > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" -- Eitan Adler From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 25 06:12: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 686C11065670 for ; Sat, 25 Aug 2012 06:12:03 +0000 (UTC) (envelope-from sven@hazejager.nl) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 205F78FC0A for ; Sat, 25 Aug 2012 06:12:02 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so3695485vcb.13 for ; Fri, 24 Aug 2012 23:12:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=ImkoQ1XVhLzPVFzBFm8VC48irRDFqnbcCTwtUcMU1ZI=; b=TYM0cvniX37wnrDqRuqvI83VS8Ebn/cyiT33BiVqzCG364oH57W9ovoew4yzCgncaM TqLh9EIJJOZzBBXEoSCSD9TQXRrTFyVBumntrv4CYLI8ICyHuShY8jY5QZhcYEcTnAt/ 9JOSPrSMdsUw1aBc1d9c9LUXY89aeqa8QSJdChMxQIKwrDZJAaeFJCzi6TfZ5JXt0QhD PADV6UH2YsKvO+oTGLWma/19bChmd3aHkDAhgjGfzn0ROIJ3dPuuwp8BLQ9+Xy8aFRNf 3bMxR/cfqtMB+kRw4XXEELzyg7OOUJ/qCmolDax3OYefD8X1CUPjIefUteBk5JYxbU51 qdag== MIME-Version: 1.0 Received: by 10.221.13.78 with SMTP id pl14mr5647879vcb.35.1345875122014; Fri, 24 Aug 2012 23:12:02 -0700 (PDT) Received: by 10.220.172.68 with HTTP; Fri, 24 Aug 2012 23:12:01 -0700 (PDT) X-Originating-IP: [212.123.177.47] Date: Sat, 25 Aug 2012 08:12:01 +0200 Message-ID: From: Sven Hazejager To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnFul3reJ/oEv3Qu8yD2DuOPDFJS6GOpEkLclSfXwmziEk/HCnzM8M9sF0r5XEsFKR8ocGc Subject: "Best" wireless MiniPCI card? 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: Sat, 25 Aug 2012 06:12:03 -0000 I am looking to upgrade my ALIX based router/AP with a stable MiniPCI 802.11n card that works "best". According to http://wiki.freebsd.org/dev/ath_hal%284%29/HardwareSupport, the AR9227 would make me happy, but I cannot find any NICs that have it. I can get a AR5008-based NIC for next to nothing, but it seems to have a list of issues...? Any suggestions? Thanks! From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 25 07:13:16 2012 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 C4028106566B for ; Sat, 25 Aug 2012 07:13:16 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 405698FC14 for ; Sat, 25 Aug 2012 07:13:14 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1553701bkc.13 for ; Sat, 25 Aug 2012 00:13:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=UfooMrjoKciTiiuvE4zMeMo4lhRmiMa+0WO4Q5X8Gy0=; b=FFM+2QefLwkaUIN/2veeRJjS7CBJycQs8nyT6OuXqHu1l16scaeTKQfbL38D36dfTm Bw+sn3rEkVB+Aob4MwoLs8T0Snc7vSbfu7qFMVlT2FwxG804JFl8aPWiNjbDGYO3Awex sCaruQ525EoLLU7LB9n0V99I8NQAPfO4BcM75KKfchmD7OAfF5EuVEfCanvlwCY/pZHE s29kTUaprXWpwYlj0UDzzGrJJfSw+4v/qlzN6KbXGUw62v5e2/qqy98UvgobcXaWbKhO 0rE+zhVt6BAYB3iwiFaT64xF0xlhrkf1rtFJuyv1YIfFQGlvEp0EsJBw+eCLjIcnvNQe qd5Q== Received: by 10.205.134.139 with SMTP id ic11mr2653842bkc.40.1345878793658; Sat, 25 Aug 2012 00:13:13 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-065-055-063.pools.arcor-ip.net. [88.65.55.63]) by mx.google.com with ESMTPS id y20sm7341552bkv.11.2012.08.25.00.13.11 (version=SSLv3 cipher=OTHER); Sat, 25 Aug 2012 00:13:12 -0700 (PDT) From: Bernhard Schmidt To: Lev Serebryakov Date: Sat, 25 Aug 2012 09:13:48 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-RC1; KDE/4.7.4; amd64; ; ) References: <199007581.20120824202155@serebryakov.spb.ru> <201208241910.35576.bschmidt@techwires.net> <517967128.20120825004457@serebryakov.spb.ru> In-Reply-To: <517967128.20120825004457@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Message-Id: <201208250913.48946.bschmidt@techwires.net> X-Gm-Message-State: ALoCoQnqlaGxJ9Mx06Y+57/GLrt9q6zyYW2tvYxVnE2LFca2sh0j/ODJcs2UnbgLWYsnvoDfhpvU Cc: freebsd-wireless@freebsd.org Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? 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: Sat, 25 Aug 2012 07:13:16 -0000 On Friday 24 August 2012 22:44:57 Lev Serebryakov wrote: > Hello, Bernhard. > You wrote 24 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 21:10:35: >=20 > BS> There is more interesting stuff available which needs someone to look > BS> into, eg. briding support and VLANs. I guess the bridging stuff is > BS> required to get 11r running. 11w though requires hardware support if > BS> I'm not totally of. >=20 > BS> There are even a lot of 11n options available which are currently not > BS> supported nor in any other way tunable, this requires stack work, not > BS> only for the supplicant but also for ifconfig. > Where could I read about all this stuff? Standards? And is here any > source but sources (;-)) to understand wha is implemented now and > what is not? I don't think that anyone made a list of supported supplicant or hostapd features yet. There is a list of wireless related "ideas" on the wiki which at least mentions one hostapd feature. Well, there are 2 kinds of settings, those which configure 802.11 features as defined in the standards (eg. ht_capab), and those which are plan stack stuff, as in multi-VAP support or VLANS. The later might have howtos or something available. However, there's now way around reading at least the source, the supplicant source, the stack source and anything in between. =2D-=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 25 11:19:08 2012 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 48F0C1065670 for ; Sat, 25 Aug 2012 11:19:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1D65E8FC1A for ; Sat, 25 Aug 2012 11:19:07 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so5010295pbb.13 for ; Sat, 25 Aug 2012 04:19:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=t60ZBTD4dscoF6OsUnem7Putd4IBs25Hhpn4y6dai88=; b=rH5T0B9vm99KgqjEfhd14y9k0gQZUClBskpPCXCfqXAczeLLwsYiQ2zh1cPtBB5Wjn wWD+oMVKyb9L1L6c3kCAM6ZoPvTi8CTAAEwg+h/4UFQTgmEONTFhD3/nU8tHX1b57dhc Oj22db2e+2IgLDeyeLv1gelSR9rsNFllOBDiwl51WLNFEnrlSsKKpBQ3nUW7dnSoqF7W zbZhKuCakbZUUZ8N1ZLc/KqqMb0r0F4hkajJptOkN3gVCqjZ3N8iLMlZ+SVmGHJCU9J9 klvMBzkXE4w6+8eJfoUaGLWEsi+Hh1sZiReIbhABgB3d12IHoLQaHCudJ8t2ZRmiwpgS 5rOw== MIME-Version: 1.0 Received: by 10.68.227.233 with SMTP id sd9mr5078979pbc.48.1345893547531; Sat, 25 Aug 2012 04:19:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Sat, 25 Aug 2012 04:19:07 -0700 (PDT) In-Reply-To: References: Date: Sat, 25 Aug 2012 04:19:07 -0700 X-Google-Sender-Auth: tzghSL72VviJXTpjaLfABXJd5GA Message-ID: From: Adrian Chadd To: Sven Hazejager Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: "Best" wireless MiniPCI card? 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: Sat, 25 Aug 2012 11:19:08 -0000 AR5416 is fine; the basic work arounds are in place. I suggest the AR9160. Adrian On 24 August 2012 23:12, Sven Hazejager wrote: > I am looking to upgrade my ALIX based router/AP with a stable MiniPCI > 802.11n card that works "best". According to > http://wiki.freebsd.org/dev/ath_hal%284%29/HardwareSupport, the AR9227 > would make me happy, but I cannot find any NICs that have it. I can > get a AR5008-based NIC for next to nothing, but it seems to have a > list of issues...? Any suggestions? Thanks! > _______________________________________________ > 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 Aug 25 18:45:34 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 C1A4F106564A for ; Sat, 25 Aug 2012 18:45:34 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4B9C18FC0A for ; Sat, 25 Aug 2012 18:45:34 +0000 (UTC) Received: by eaak11 with SMTP id k11so901702eaa.13 for ; Sat, 25 Aug 2012 11:45:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=6XwyxYQ0QdusbWqa+LY7F3DyXYcP3pUlAaFr+b0Bm1k=; b=Imi+Bmk5DbyqunxUMUyWiHjgPiGpsM7M5svy91cpb1xMO4LZc9u/uMBiq5gedoDbwX 8XuwdC9wJULnXpyED2O/t3ZWWa1Ddlr3SpDN11D8L44g/hlxt2dXnbLY2degOBvrV3aX JG+dp8WAIUqLRZG2s7+HOTUiWR2nU53Ep/+DiSYkcue+7xgmsVDRDNcQP/EnzJTr7b6h g/J81PQyeZcZ83vDLOuM5f6R5eEG/L5AYqCvQItFAeHNBeCwtHqpO3uju1wgEIgLvdxU gMmANi/id9Y6vGA0WsvzoP0dn7mtnccbeIjftr6qg6hSKDeFvsX+G5htvNnB6SQQfKP5 Mm1g== Received: by 10.14.203.73 with SMTP id e49mr11739229eeo.27.1345919853747; Sat, 25 Aug 2012 11:37:33 -0700 (PDT) Received: from mini.office.venture37.com (mini.office.venture37.com. [2001:4b10:101a:2::10]) by mx.google.com with ESMTPS id m45sm38858739eep.16.2012.08.25.11.37.32 (version=SSLv3 cipher=OTHER); Sat, 25 Aug 2012 11:37:32 -0700 (PDT) Message-ID: <50391B6A.5010302@gmail.com> Date: Sat, 25 Aug 2012 19:37:30 +0100 From: Sevan / Venture37 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Content-Type: multipart/mixed; boundary="------------060400090309000706020004" Subject: ath(4) error: array index 21 is past the end of the array (which contains, 21 elements) 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: Sat, 25 Aug 2012 18:45:34 -0000 This is a multi-part message in MIME format. --------------060400090309000706020004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, On -CURRENT buildkernel fails when WITH_CLANG_IS_CC declared with: /usr/src/sys/modules/ath/../../dev/ath/if_ath_debug.c:184:24: error: array index 21 is past the end of the array (which contains 21 elements) [-Werror,-Warray-bounds] eds->ds_hw[20], eds->ds_hw[21]); ^ ~~ @/dev/ath/ath_hal/ah_desc.h:229:2: note: array 'ds_hw' declared here uint32_t ds_hw[21]; /* includes buf/len */ ^ 1 error generated. *** [if_ath_debug.o] Error code 1 Attached patch bumps array size to 22 in decleration which stops the error. Sevan --------------060400090309000706020004 Content-Type: text/plain; charset=UTF-8; name="ath_patch.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ath_patch.txt" Index: sys/dev/ath/ath_hal/ah_desc.h =================================================================== --- sys/dev/ath/ath_hal/ah_desc.h (revision 239685) +++ sys/dev/ath/ath_hal/ah_desc.h (working copy) @@ -226,7 +226,7 @@ struct ath_desc_txedma { uint32_t ds_info; uint32_t ds_link; - uint32_t ds_hw[21]; /* includes buf/len */ + uint32_t ds_hw[22]; /* includes buf/len */ }; struct ath_desc_status { --------------060400090309000706020004--