From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 17 03:58:53 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2644273E for ; Sun, 17 Aug 2014 03:58:53 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 078AC20DB for ; Sun, 17 Aug 2014 03:58:53 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7H3wqH8092574 for ; Sun, 17 Aug 2014 03:58:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 185478] [iwi] [panic] panic in iwi0 driver Date: Sun, 17 Aug 2014 03:58:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: break19@gmail.com X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 17 Aug 2014 03:58:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185478 break19@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |break19@gmail.com --- Comment #2 from break19@gmail.com --- I, too, am having this issue. Unread portion of the kernel message buffer: wlan0: ieee80211_new_state_locked: pending SCAN -> AUTH transition lost panic: vm_fault: fault on nofault entry, addr: c8032000 cpuid = 0 KDB: stack backtrace: #0 0xc0b3a082 at kdb_backtrace+0x52 #1 0xc0afce11 at panic+0x121 #2 0xc0d9863a at vm_fault_hold+0x1a4a #3 0xc0d96bb2 at vm_fault+0x82 #4 0xc0ff36bb at trap_pfault+0x1bb #5 0xc0ff2f07 at trap+0x677 #6 0xc0fdca4c at calltrap+0x6 #7 0xc07636fe at iwi_auth_and_assoc+0x4be #8 0xc076304b at iwi_newstate+0x15b #9 0xc0c112c5 at ieee80211_newstate_cb+0x175 #10 0xc0b482da at taskqueue_run_locked+0xea #11 0xc0b48e77 at taskqueue_thread_loop+0xc7 #12 0xc0acbef3 at fork_exit+0xa3 #13 0xc0fdcaf4 at fork_trampoline+0x8 Uptime: 7h14m2s Physical memory: 2014 MB Dumping 156 MB: 141 125 109 93 77 61 45 29 13 Reading symbols from /boot/kernel/aio.ko.symbols...done. Loaded symbols for /boot/kernel/aio.ko.symbols Reading symbols from /boot/kernel/acpi_video.ko.symbols...done. Loaded symbols for /boot/kernel/acpi_video.ko.symbols Reading symbols from /boot/kernel/sem.ko.symbols...done. Loaded symbols for /boot/kernel/sem.ko.symbols Reading symbols from /boot/kernel/i915kms.ko.symbols...done. Loaded symbols for /boot/kernel/i915kms.ko.symbols Reading symbols from /boot/kernel/iicbb.ko.symbols...done. Loaded symbols for /boot/kernel/iicbb.ko.symbols Reading symbols from /boot/kernel/iicbus.ko.symbols...done. Loaded symbols for /boot/kernel/iicbus.ko.symbols Reading symbols from /boot/kernel/iic.ko.symbols...done. Loaded symbols for /boot/kernel/iic.ko.symbols Reading symbols from /boot/kernel/drm2.ko.symbols...done. Loaded symbols for /boot/kernel/drm2.ko.symbols Reading symbols from /boot/kernel/apm_saver.ko.symbols...done. Loaded symbols for /boot/kernel/apm_saver.ko.symbols Reading symbols from /boot/kernel/apm.ko.symbols...done. Loaded symbols for /boot/kernel/apm.ko.symbols Reading symbols from /boot/kernel/fdescfs.ko.symbols...done. Loaded symbols for /boot/kernel/fdescfs.ko.symbols Reading symbols from /boot/kernel/iwi_bss.ko.symbols...done. Loaded symbols for /boot/kernel/iwi_bss.ko.symbols Reading symbols from /boot/kernel/ums.ko.symbols...done. Loaded symbols for /boot/kernel/ums.ko.symbols Reading symbols from /boot/kernel/uhid.ko.symbols...done. Loaded symbols for /boot/kernel/uhid.ko.symbols #0 doadump (textdump=-957650816) at pcpu.h:233 233 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=-957650816) at pcpu.h:233 #1 0xc0afca89 in kern_reboot (howto=260) at kern_shutdown.c:452 #2 0xc0afce4f in panic (fmt=) at kern_shutdown.c:759 #3 0xc0d9863a in vm_fault_hold (vaddr=3242895516, fault_type=1 '\001', fault_flags=, m_hold=) at vm_fault.c:283 #4 0xc0d96bb2 in vm_fault (map=0xc1ec1000, vaddr=, fault_type=0 '\0', fault_flags=) at vm_fault.c:224 #5 0xc0ff36bb in trap_pfault (frame=, usermode=0, eva=3243337188) at trap.c:914 #6 0xc0ff2f07 in trap (frame=0xeb166ad8) at trap.c:532 #7 0xc0fdca4c in calltrap () at /usr/src/sys/i386/i386/exception.s:170 #8 0xc0c06786 in node_getrssi (ni=0xc8032000) at ieee80211_node.c:1100 #9 0xc07636fe in iwi_auth_and_assoc () at if_iwi.c:2910 #10 0xc076304b in iwi_newstate (vap=, nstate=) at if_iwi.c:997 #11 0xc0c112c5 in ieee80211_newstate_cb (xvap=0xc7e5d000, npending=1) at ieee80211_proto.c:1756 #12 0xc0b482da in taskqueue_run_locked (queue=0xc7ad2480) at subr_taskqueue.c:342 #13 0xc0b48e77 in taskqueue_thread_loop (arg=0xc7ad50a4) at subr_taskqueue.c:563 #14 0xc0acbef3 in fork_exit (callout=0xc0b48db0 ) at kern_fork.c:995 #15 0xc0fdcaf4 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:279 Current language: auto; currently minimal FreeBSD keyhole 10.0-STABLE FreeBSD 10.0-STABLE #0 r269844: Tue Aug 12 15:30:35 CDT 2014 root@keyhole:/usr/obj/usr/src/sys/GENERIC i386 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 17 07:47:40 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5A5AB14D; Sun, 17 Aug 2014 07:47:40 +0000 (UTC) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17FA82584; Sun, 17 Aug 2014 07:47:39 +0000 (UTC) Received: from [93.104.25.142] (helo=localhost.my.domain) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XIvBb-0000nI-6f; Sun, 17 Aug 2014 09:47:31 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.my.domain (8.14.7/8.14.3) with ESMTP id s7H7lTdK001528; Sun, 17 Aug 2014 09:47:29 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.7/8.14.3/Submit) id s7H7lS4T001527; Sun, 17 Aug 2014 09:47:28 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Sun, 17 Aug 2014 09:47:28 +0200 From: Matthias Apitz To: freebsd-wireless@freebsd.org, freebsd-current@freebsd.org Subject: Re: Broadcom BCM4312 802.11b/g in 11-CURRENT r269739 Message-ID: <20140817074728.GA1495@La-Habana> Reply-To: Matthias Apitz References: <20140816152509.GA1529@La-Habana> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20140816152509.GA1529@La-Habana> X-Operating-System: FreeBSD 9.0-CURRENT r214444 (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 93.104.25.142 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 17 Aug 2014 07:47:40 -0000 El día Saturday, August 16, 2014 a las 05:25:09PM +0200, Matthias Apitz escribió: > > Hello, > > I have a 11-CURRENT from August 8, and ports from the day after: > > FreeBSD tiny-r269739 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r269739M: Fri Aug 15 18:07:41 CEST 2014 guru@vm-tiny-r269739:/usr/obj/usr/src/sys/GENERIC i386 > > The configuration used for the Wifi card is: > > rc.conf: > > wlans_bwn0="wlan0" > ifconfig_wlan0="WPA DHCP" > > loader.conf > > if_bwn_load="YES" > bwn_v4_lp_ucode_load="YES" > > The Wifi comes up fine on boot with WPA and DHCP assigns IP addr and > routing: > > wlan0: flags=8843 metric 0 mtu 1500 > ether 90:4c:e5:00:06:ce > inet 192.168.2.100 netmask 0xffffff00 broadcast 192.168.2.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g > status: associated > ssid tarara channel 7 (2442 MHz 11g) bssid 00:13:f7:0d:08:48 > country US authmode WPA2/802.11i privacy ON deftxkey UNDEF > AES-CCM 4:128-bit txpower 30 bmiss 7 scanvalid 60 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS > wme roaming MANUAL > > I even can do a DNS lookup and transfer some ~10 PING to Internet, but > after this it gets stuck. Below is a 'dmesg | fgrep -i bwn'. Let me know > if someone needs a complete dmesg output. > I have recompiled if_bwn.c with -DBWN_DEBUG and set hw.bwn.debug=15 in /boot/loader.conf; an output of 'dmesg | fgrep bwn' is attached. IP addr gets assigned via DHCP and some 20 IMCP packages can be sent. After this, the traffic gets stuck. If someone (the author of the driver or the port of net/bwn*) is willing to guide my through the debugging, here I am. Thanks matthias Preloaded elf module "/boot/kernel/if_bwn.ko" at 0xc183d8e8. Preloaded elf module "/boot/kernel/siba_bwn.ko" at 0xc183dc6c. Preloaded elf module "/boot/modules/bwn_v4_lp_ucode.ko" at 0xc183e01c. firmware: 'bwn_v4_lp_ucode' version 0: 0 bytes loaded at 0xc1811084 firmware: 'bwn_v4_lp_ucode5' version 0: 22264 bytes loaded at 0xc1811084 firmware: 'bwn_v4_lp_ucode11' version 0: 32776 bytes loaded at 0xc181677c firmware: 'bwn_v4_lp_ucode13' version 0: 31440 bytes loaded at 0xc181e784 firmware: 'bwn_v4_lp_ucode14' version 0: 31000 bytes loaded at 0xc1826254 firmware: 'bwn_v4_lp_ucode15' version 0: 34672 bytes loaded at 0xc182db6c firmware: 'bwn_v4_lp_pcm5' version 0: 1320 bytes loaded at 0xc18362dc firmware: 'bwn_v4_lp_a0g1initvals5' version 0: 1848 bytes loaded at 0xc1836804 firmware: 'bwn_v4_lp_a0g0initvals5' version 0: 1848 bytes loaded at 0xc1836f3c firmware: 'bwn_v4_lp_b0g0initvals5' version 0: 1848 bytes loaded at 0xc1837674 firmware: 'bwn_v4_lp_b0g0initvals13' version 0: 2126 bytes loaded at 0xc1837dac firmware: 'bwn_v4_lp_a0g1bsinitvals5' version 0: 178 bytes loaded at 0xc18385fa firmware: 'bwn_v4_lp_a0g0bsinitvals5' version 0: 178 bytes loaded at 0xc18386ac firmware: 'bwn_v4_lp_b0g0bsinitvals5' version 0: 178 bytes loaded at 0xc183875e firmware: 'bwn_v4_lp_lp0initvals13' version 0: 3664 bytes loaded at 0xc1838810 firmware: 'bwn_v4_lp_lp0initvals14' version 0: 2110 bytes loaded at 0xc1839660 firmware: 'bwn_v4_lp_lp0initvals15' version 0: 2282 bytes loaded at 0xc1839e9e firmware: 'bwn_v4_lp_lp0bsinitvals13' version 0: 178 bytes loaded at 0xc183a788 firmware: 'bwn_v4_lp_lp0bsinitvals14' version 0: 178 bytes loaded at 0xc183a83a firmware: 'bwn_v4_lp_lp0bsinitvals15' version 0: 178 bytes loaded at 0xc183a8ec firmware: 'bwn_v4_lp_n0bsinitvals11' version 0: 178 bytes loaded at 0xc183a99e siba_bwn0: mem 0x57100000-0x57103fff irq 16 at device 0.0 on pci1 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) bwn0: DMA (64 bits) bwn0: MSI count : 1 siba_bwn0: attempting to allocate 1 MSI vectors (1 supported) siba_bwn0: using IRQ 257 for MSI bwn0: Using 1 MSI messages bwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps bwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps bwn_init: if_flags 0x8803 bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn_newstate: INIT -> SCAN bwn_newstate: SCAN -> AUTH bwn_newstate: AUTH -> ASSOC bwn_newstate: ASSOC -> RUN bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: need multicast update callback bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) bwn0: RX decryption attempted (old 0 keyidx 0x2) -- Matthias Apitz | /"\ ASCII Ribbon Campaign: E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 17 14:52:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3AF8980A for ; Sun, 17 Aug 2014 14:52:41 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A264E20F0 for ; Sun, 17 Aug 2014 14:52:39 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s7HEhe0D062018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 17 Aug 2014 22:43:41 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s7HEhdlA062017; Sun, 17 Aug 2014 22:43:39 +0800 (CST) (envelope-from kevlo) Date: Sun, 17 Aug 2014 22:43:37 +0800 From: Kevin Lo To: Miguel Clara Subject: Re: FreeBSD current RT3071 can't connect to 5G network Message-ID: <20140817144336.GA62005@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> <20140815030631.GA36062@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 17 Aug 2014 14:52:41 -0000 On Sat, Aug 16, 2014 at 09:07:29PM +0100, Miguel Clara wrote: > > On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo wrote: > > > All USB wifi dongles in FreeBSD don't support 11n yet. > > > > Kevin > > > > > I was not aware of that, is this really true for all USB wifi dongles or > do you mean ralink only? It's true for all USB wifi dongles in *BSD... Kevin From owner-freebsd-wireless@FreeBSD.ORG Sun Aug 17 16:04:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13159CC7; Sun, 17 Aug 2014 16:04:14 +0000 (UTC) Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6ED872763; Sun, 17 Aug 2014 16:04:13 +0000 (UTC) Received: by mail-we0-f177.google.com with SMTP id w62so3966664wes.8 for ; Sun, 17 Aug 2014 09:04:11 -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=XiYnQQ0eZcpzbaW1sjzUjFFEybTDQ5IAz6CzT12VplM=; b=Sw5wFihdzarJUo0ISCu7UHiXvzmzFhX2OtC/JlWWR9EI4udx9FkuR/vqE3UqC/ZDth DfD0Fgpn2mizGnsAyu6uY2EG7HgB8AEg3ZrOeyheT9TxN+B+wq9B2SS9syoLUZ7FrTkg f7qSquf+t4qfGhSoIBEM5G3KZOcam6enEui/sXta8iy9FNvva88a7sW5g4t4M2Sqo7Eh Tpg8JOWMphVqmMhJDAP8MaUEA7LuFVUv7N9l+ofhVuko1Orgid30iMILKMpURrrhyHKa 0qxTasZOVwXt7mDI3zufYra9vRhH1Xume03O0iKt2tOECOlrfvk9S8q6Ui64+09A4en/ aSBw== X-Received: by 10.194.71.52 with SMTP id r20mr2032254wju.113.1408291451707; Sun, 17 Aug 2014 09:04:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.121.37 with HTTP; Sun, 17 Aug 2014 09:03:50 -0700 (PDT) In-Reply-To: <20140817144336.GA62005@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> <20140815030631.GA36062@ns.kevlo.org> <20140817144336.GA62005@ns.kevlo.org> From: Miguel Clara Date: Sun, 17 Aug 2014 17:03:50 +0100 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network To: Kevin Lo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 17 Aug 2014 16:04:14 -0000 Thanks for clarifying Kevin. I wonder whats the reason for this? Since its in all I guess something in the kernel makes this harder? or is it just lack of time/resources? thanks Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Sun, Aug 17, 2014 at 3:43 PM, Kevin Lo wrote: > On Sat, Aug 16, 2014 at 09:07:29PM +0100, Miguel Clara wrote: > > > > On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo wrote: > > > > > All USB wifi dongles in FreeBSD don't support 11n yet. > > > > > > Kevin > > > > > > > > I was not aware of that, is this really true for all USB wifi dongles or > > do you mean ralink only? > > It's true for all USB wifi dongles in *BSD... > > Kevin > From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 18 08:00:22 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 505284E8 for ; Mon, 18 Aug 2014 08:00:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3262E37AA for ; Mon, 18 Aug 2014 08:00:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7I80Mnd090272 for ; Mon, 18 Aug 2014 08:00:22 GMT (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201408180800.s7I80Mnd090272@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 18 Aug 2014 08:00:22 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 18 Aug 2014 08:00:22 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (7 bugs) Bug 140567: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140567 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] [patch] ath is not worked on my notebook PC Bug 154598: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154598 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] Atheros 5424/2424 can't connect to WPA network Bug 163312: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163312 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [panic] [ath] kernel panic: page fault with ath0 taskq Bug 166190: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166190 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] TX hangs and frames stuck in TX queue Bug 166357: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166357 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] 802.11n TX stall when the first frame in the BAW is in the software queue Bug 166642: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166642 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. Bug 169362: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169362 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-wireless@FreeBSD.org Status: Needs MFC Resolution: Summary: [ath] AR5416: radar pulse PHY errors sometimes include the CRC Error bit set as well as the PHY errors From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 18 08:50:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D9383AD for ; Mon, 18 Aug 2014 08:50:08 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 10BD33BFF for ; Mon, 18 Aug 2014 08:50:07 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s7I8nX3P031773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Aug 2014 16:49:34 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s7I8nXu1031772; Mon, 18 Aug 2014 16:49:33 +0800 (CST) (envelope-from kevlo) Date: Mon, 18 Aug 2014 16:49:32 +0800 From: Kevin Lo To: Miguel Clara Subject: Re: FreeBSD current RT3071 can't connect to 5G network Message-ID: <20140818084932.GA31760@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> <20140815030631.GA36062@ns.kevlo.org> <20140817144336.GA62005@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 18 Aug 2014 08:50:08 -0000 Since there is no data sheets available, looking throught the source code from the vendor makes slower development and is very time-consuming, at least in my case. Kevin On Sun, Aug 17, 2014 at 05:03:50PM +0100, Miguel Clara wrote: > > Thanks for clarifying Kevin. > > I wonder whats the reason for this? Since its in all I guess something in > the kernel makes this harder? or is it just lack of time/resources? > > thanks > > > > > Melhores Cumprimentos // Best Regards > ----------------------------------------------- > *Miguel Clara* > *IT - Sys Admin & Developer* > *E-mail: *miguelmclara@gmail.com > www.linkedin.com/in/miguelmclara/ > > > On Sun, Aug 17, 2014 at 3:43 PM, Kevin Lo wrote: > > > On Sat, Aug 16, 2014 at 09:07:29PM +0100, Miguel Clara wrote: > > > > > > On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo wrote: > > > > > > > All USB wifi dongles in FreeBSD don't support 11n yet. > > > > > > > > Kevin > > > > > > > > > > > I was not aware of that, is this really true for all USB wifi dongles or > > > do you mean ralink only? > > > > It's true for all USB wifi dongles in *BSD... > > > > Kevin > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 19 19:53:14 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6BD75437 for ; Tue, 19 Aug 2014 19:53:14 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EAF9B3904 for ; Tue, 19 Aug 2014 19:53:13 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id 10so5830269lbg.40 for ; Tue, 19 Aug 2014 12:53:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=5pus3W2JrdJjK5pRkmhSP/C/vQNcjv8mjcbinPhoQTw=; b=mqB5tyR5hUCCJdScBoFlvSD0I1qbDBRgNMO+SciCeXoCE30GCCD8r+l5r5oEEwoiyL oWFx47myTVY5qA5SzYYtTylyJiNtxR2IzwGR9vna6KTSfj6bmvVmN2krMbelIgpvWl4Z vZCUVtlSRgSfP8jv17BOp2mA40WEGAS2pskEcluOx0wZblN3uRxrsxdv6IaOoCrC/RNu dJsqvYeD/TqrU6eR2U6y0+A1O0JazUhK+ElE28tTQ2wLl2GDu5xuW5q5xvXl9X8vdzfr majt16mKLizcZi7uvnzpjYLKY6uMdzSmM2gzqJ2WWdEZLdtPKOUk12vIO7ZVSUtSIXaf xQBg== MIME-Version: 1.0 X-Received: by 10.112.5.170 with SMTP id t10mr26085795lbt.64.1408477991703; Tue, 19 Aug 2014 12:53:11 -0700 (PDT) Received: by 10.114.29.200 with HTTP; Tue, 19 Aug 2014 12:53:11 -0700 (PDT) Date: Tue, 19 Aug 2014 21:53:11 +0200 Message-ID: Subject: iwn: Intel Centrino 6205 bad 11n performance From: Johannes Dieterich To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 19 Aug 2014 19:53:14 -0000 Dear all, I have a Intel Centrino Advanced-N 6205 WLAN NIC in my Thinkpad using iwn. iwn0@pci0:3:0:0: class=0x028000 card=0x13118086 chip=0x00858086 rev=0x34 hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Advanced-N 6205 [Taylor Peak]' class = network Unfortunately, I only get a rather bad speed using CURRENT (r270098) out of the chip. It is connected to an 11n (on the 2.4 GHz band) network: wlan0: flags=8843 metric 0 mtu 1500 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid XXXXX channel 4 (2427 MHz 11g ht/20) bssid XXXXXXXXXX country US authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 15 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme roaming MANUAL I get a maximum of 900 KB/s of throughput (both in/out, approximated by copying a large file using scp), within the network and to the outside world. Running SuSE Linux on the notebook allows me to easily saturate my uplink at > 3MB/s, didn't then further check within the network. I get no log messages on FBSD from iwn and I am not located in a particularly noisy neighborhood. The only performance issue I can find with this chip is one old report on Ubuntu (http://ubuntuforums.org/showthread.php?t=1949571), where the 11n seemed to be the culprit in the driver/firmware. Could this be an issue for us as well (firmware problem?)? As my workhorse is FreeBSD, I'd love to fix this issue. How can I further debug this issue and/or provide more data? I know that the status of iwn in FBSD is difficult ATM but maybe there is hope? Best Johannes From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 19 22:30:55 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 037E08D2 for ; Tue, 19 Aug 2014 22:30:55 +0000 (UTC) Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B89843794 for ; Tue, 19 Aug 2014 22:30:54 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id j7so6358912qaq.28 for ; Tue, 19 Aug 2014 15:30:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=njg15VnrEMpLviLKPzyjWpypHu1DklDIsC4y/yvXWCg=; b=VxswctPBSdEKrTcMEPgGyeghSpPv7142K84WYic5vLilYAgOGkVXCHpZwb27GJxpVH BroKiun5MkQoe5q1ksJfQDBu1a/xMaVqi24y5E9kUq7nKP20ELG2ELpMi8LqeK38P7kP SUZzMOuv2gvoPFG2Vt0HSyM5Jt/qomrwI1h+ZAmIo+xdzAUpqAyJhpud6LbEL+h6AKvj wB7hMrAg4aODcjvGc5YGv2ofN882EEAr68aQycw6huQPRKjyrktNPwFrWbobSgnQ6ran H7YBt+Wd14wJgoMr7NajSN5Ge2dzo6xNu139i3yuFBotqp08h3Bj9Y1pES+obdHSgCZM jFpw== MIME-Version: 1.0 X-Received: by 10.140.90.40 with SMTP id w37mr67129572qgd.52.1408487453754; Tue, 19 Aug 2014 15:30:53 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Tue, 19 Aug 2014 15:30:53 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Aug 2014 15:30:53 -0700 X-Google-Sender-Auth: 6SxLaG4ZndBU8TMNPxiz1PW2Wis Message-ID: Subject: Re: iwn: Intel Centrino 6205 bad 11n performance From: Adrian Chadd To: Johannes Dieterich Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 19 Aug 2014 22:30:55 -0000 Hi, You can try disabling 11n (ifconfig -ht) but besides that, there's no real iwn maintainer or anyone who wants to get really nitty gritty into what the driver is doing. So until that happens, I think we're short of luck. :( -a On 19 August 2014 12:53, Johannes Dieterich wrote: > Dear all, > > I have a Intel Centrino Advanced-N 6205 WLAN NIC in my Thinkpad using iwn. > > iwn0@pci0:3:0:0: class=0x028000 card=0x13118086 chip=0x00858086 rev=0x34 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Centrino Advanced-N 6205 [Taylor Peak]' > class = network > > Unfortunately, I only get a rather bad speed using CURRENT (r270098) out of > the chip. It is connected to an 11n (on the 2.4 GHz band) network: > > wlan0: flags=8843 metric 0 mtu 1500 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > status: associated > ssid XXXXX channel 4 (2427 MHz 11g ht/20) bssid XXXXXXXXXX > country US authmode WPA2/802.11i privacy ON deftxkey UNDEF > TKIP 2:128-bit txpower 15 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 > bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 64k > ampdudensity 8 -amsdutx amsdurx shortgi wme roaming MANUAL > > I get a maximum of 900 KB/s of throughput (both in/out, approximated by > copying a large file using scp), within the network and to the outside > world. Running SuSE Linux on the notebook allows me to easily saturate my > uplink at > 3MB/s, didn't then further check within the network. I get no > log messages on FBSD from iwn and I am not located in a particularly noisy > neighborhood. > > The only performance issue I can find with this chip is one old report on > Ubuntu (http://ubuntuforums.org/showthread.php?t=1949571), where the 11n > seemed to be the culprit in the driver/firmware. Could this be an issue for > us as well (firmware problem?)? > > As my workhorse is FreeBSD, I'd love to fix this issue. How can I further > debug this issue and/or provide more data? I know that the status of iwn in > FBSD is difficult ATM but maybe there is hope? > > Best > > Johannes > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 19 23:42:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37E7C736; Tue, 19 Aug 2014 23:42:58 +0000 (UTC) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FF773E3A; Tue, 19 Aug 2014 23:42:57 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id w61so7046132wes.23 for ; Tue, 19 Aug 2014 16:42:54 -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=LFLd4QwVwBuVjpOy4r31bv1Ej2gXZRCvwLoOp4oylxQ=; b=IgRMZkmTZ++ge8mmNX0xEVSUqE86LzUalN5AuUxmy0rENnzqsAZ83h+QZyM1e+a8v4 hvYbNkV4wK8pk2XHj/o5Im96B55NGx20BItO+r0dXV+CdubAT0m22N1SMsDy6z/6IZ6a /hMBp57oAYHJkzpcRvv5rono+JOlNhuEu0b5AYHRLoGOlrepKaMPHPopjMsYD6Dr0IsQ mFPcfK4KjKt9pbVN0USwVLbHSV8jfS4q5lYxmSxWGdzHFWokyqGB98COBwGbJJVS3A7e xS8Tk0UJKQ9DLk6bmwYag3EHSDz3hGfDRVgu8CnElAflZ+ViomwHY8Nr3wTRh/muFkit N4bg== X-Received: by 10.180.104.163 with SMTP id gf3mr10524489wib.24.1408491774806; Tue, 19 Aug 2014 16:42:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.121.37 with HTTP; Tue, 19 Aug 2014 16:42:34 -0700 (PDT) In-Reply-To: <20140818084932.GA31760@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> <20140815030631.GA36062@ns.kevlo.org> <20140817144336.GA62005@ns.kevlo.org> <20140818084932.GA31760@ns.kevlo.org> From: Miguel Clara Date: Wed, 20 Aug 2014 00:42:34 +0100 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network To: Kevin Lo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 19 Aug 2014 23:42:58 -0000 Would hardware donation help? At least in you're case I mean :) Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer* *E-mail: *miguelmclara@gmail.com www.linkedin.com/in/miguelmclara/ On Mon, Aug 18, 2014 at 9:49 AM, Kevin Lo wrote: > Since there is no data sheets available, looking throught the source code > from the vendor makes slower development and is very time-consuming, > at least in my case. > > Kevin > > On Sun, Aug 17, 2014 at 05:03:50PM +0100, Miguel Clara wrote: > > > > Thanks for clarifying Kevin. > > > > I wonder whats the reason for this? Since its in all I guess something in > > the kernel makes this harder? or is it just lack of time/resources? > > > > thanks > > > > > > > > > > Melhores Cumprimentos // Best Regards > > ----------------------------------------------- > > *Miguel Clara* > > *IT - Sys Admin & Developer* > > *E-mail: *miguelmclara@gmail.com > > www.linkedin.com/in/miguelmclara/ > > > > > > On Sun, Aug 17, 2014 at 3:43 PM, Kevin Lo wrote: > > > > > On Sat, Aug 16, 2014 at 09:07:29PM +0100, Miguel Clara wrote: > > > > > > > > On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo wrote: > > > > > > > > > All USB wifi dongles in FreeBSD don't support 11n yet. > > > > > > > > > > Kevin > > > > > > > > > > > > > > I was not aware of that, is this really true for all USB wifi > dongles or > > > > do you mean ralink only? > > > > > > It's true for all USB wifi dongles in *BSD... > > > > > > Kevin > > > > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to " > freebsd-wireless-unsubscribe@freebsd.org" > > > From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 20 08:27:05 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CC96D07 for ; Wed, 20 Aug 2014 08:27:05 +0000 (UTC) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F401C3DC4 for ; Wed, 20 Aug 2014 08:27:04 +0000 (UTC) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.14.8/8.14.8) with ESMTP id s7K8QGgp055133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Aug 2014 16:26:16 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.14.8/8.14.8/Submit) id s7K8QFYC055132; Wed, 20 Aug 2014 16:26:15 +0800 (CST) (envelope-from kevlo) Date: Wed, 20 Aug 2014 16:26:14 +0800 From: Kevin Lo To: Patrick Powell Subject: Re: FreeBSD current RT3071 can't connect to 5G network Message-ID: <20140820082614.GA55123@ns.kevlo.org> References: <53DE4FD2.8050309@FreeBSD.org> <20140805092636.GA41308@ns.kevlo.org> <20140815030631.GA36062@ns.kevlo.org> <53EE0B83.8020404@astart.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53EE0B83.8020404@astart.com> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 20 Aug 2014 08:27:05 -0000 Wireless drivers on FreeBSD have a manual page which lists the hardware supported by that driver. For example: https://www.freebsd.org/cgi/man.cgi?query=run&apropos=0&sektion=0&manpath=FreeBSD+10.0-RELEASE&arch=default&format=html#HARDWARE Does this help you? Thanks. Kevin On Fri, Aug 15, 2014 at 06:30:43AM -0700, Patrick Powell wrote: > > Is it possible to provide a SHORT list of a COUPLE that do, and are > either supported > out of the box or with a few simple mods to the driver (patch?). And > perhaps a link to > a site where they might be purchased? > > On 08/14/14 20:06, Kevin Lo wrote: > > All USB wifi dongles in FreeBSD don't support 11n yet. > > > > Kevin > > > > On Thu, Aug 14, 2014 at 03:09:23PM +0100, Miguel Clara wrote: > >> Duh, I figured it out... by default the Asus Guest netwroks are created in > >> "auto" mode, so both N and legacy, while my 5G network was set to N only > >> (2.4 is set to auto too). > >> > >> This also explain the poor performance now... for some reason 11n is not > >> working only 11g/a. > >> > >> ifconfig wlan0 mode 11na or 11ng gives me device is not configured (This > >> works fine for the ath card tough)! > >> > >> > >> Melhores Cumprimentos // Best Regards > >> ----------------------------------------------- > >> *Miguel Clara* > >> *IT - Sys Admin & Developer* > >> *E-mail: *miguelmclara@gmail.com > >> www.linkedin.com/in/miguelmclara/ > >> > >> > >> On Thu, Aug 14, 2014 at 2:13 PM, Miguel Clara > >> wrote: > >> > >>> > >>> On Wed, Aug 13, 2014 at 7:10 PM, Miguel Clara > >>> wrote: > >>> > >>>> Hi, just wanted to report that the patch made no difference. > >>>> > >>>> However I created a guest network in my router with the same password and > >>>> also using WPA2, and it connects to it. > >>>> > >>>> the only difference is the BSSID, so I wonder if this is a issue with wpa > >>>> and nothing to to with the driver? > >>>> > >>> NOTE: it works well if using ath driivers so the problem is probably in > >>> the driver indeed! > >>> > >>> > >>>> But the performance is still horrible! > >>>> > >>>> > >>>> > >>>> > >> _______________________________________________ > >> freebsd-wireless@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > >> > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 20 10:22:15 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0FADF5C2; Wed, 20 Aug 2014 10:22:15 +0000 (UTC) Received: from marge.meraka.csir.co.za (marge.meraka.csir.co.za [IPv6:2001:4200:7000:3::1]) by mx1.freebsd.org (Postfix) with ESMTP id 1823C3B92; Wed, 20 Aug 2014 10:22:14 +0000 (UTC) Received: from [IPv6:2001:4200:7000:3:223:aeff:fea7:a3c2] (unknown [IPv6:2001:4200:7000:3:223:aeff:fea7:a3c2]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by marge.meraka.csir.co.za (Postfix) with ESMTPSA id BFC07D0CC47; Wed, 20 Aug 2014 12:21:53 +0200 (SAST) Message-ID: <53F476C1.5040608@meraka.csir.co.za> Date: Wed, 20 Aug 2014 12:21:53 +0200 From: Johann Hugo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Ath - clients with weak signals not working after upgrade to FreeBSD 11.0 References: <5520556.ca3p8qHkHk@jeep> <2355251.gdJNgdnIzD@jeep> <1495468.yhTHqENs3S@jeep> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 20 Aug 2014 10:22:15 -0000 Ok, it's working fine with freebsd-9 Did some more tests with FreeBSD 11.0-CURRENT. I think the ANI problem is only there when the nodes are in ADHOC mode (default mode for our mesh). The same hardware setup works fine if the nodes are in AP/Client mode. Johann On 08/01/2014 19:56, Adrian Chadd wrote: > Well, step #1 would be to run the freebsd-9 ath(4) driver in the later > freebsd version. If you're able to shoehorn that in, let's see if > that's the case. > > > > -a > > > On 1 August 2014 02:20, Johann Hugo wrote: >> Hi >> >> >> >> Is it possible to disable ANI ? >> >> >> >> How should we go about to narrow down the problem ? >> >> >> >> -------------------------------------------- >> >> >> >> FreeBSD 11.0-CURRENT (Looks like crcerr is not updating) >> >> >> >> mesh-6c9a:~ # athstats -i ath1 anistats -o ani 1 >> >> input output altrate short long xretry crcerr crypt phyerr rssi rate >> >> 2994 248 0 0 18 3 0 0 0 44 54M >> >> 11 1 0 0 0 0 0 0 0 44 54M >> >> 11 0 0 0 0 0 0 0 0 42 54M >> >> 11 1 0 0 0 0 0 0 0 44 54M >> >> 11 0 0 0 0 0 0 0 0 44 54M >> >> 11 1 0 0 0 0 0 0 0 43 54M >> >> 11 0 0 0 0 0 0 0 0 44 54M >> >> 10 1 0 0 0 0 0 0 0 45 54M >> >> 12 1 0 0 0 0 0 0 0 44 54M >> >> 11 1 0 0 0 0 0 0 0 42 54M >> >> 11 1 0 0 0 0 0 0 0 44 54M >> >> 12 0 0 0 0 0 0 0 0 42 54M >> >> 11 1 0 0 0 0 0 0 0 43 54M >> >> 11 0 0 0 0 0 0 0 0 44 54M >> >> 12 1 0 0 0 0 0 0 0 42 54M >> >> 11 1 0 0 13 1 0 0 0 43 36M >> >> 10 1 0 0 0 0 0 0 0 44 36M >> >> 12 1 0 0 0 0 0 0 0 43 36M >> >> 10 1 0 0 13 1 0 0 0 44 54M >> >> 11 1 0 0 0 0 0 0 0 44 54M >> >> 12 2 0 0 11 1 0 0 0 43 12M >> >> input output altrate short long xretry crcerr crypt phyerr rssi rate >> >> 3230 272 0 0 66 7 0 0 0 44 9M >> >> 12 2 0 0 13 1 0 0 0 43 24M >> >> 11 1 0 0 0 0 0 0 0 42 24M >> >> 12 2 0 0 0 0 0 0 0 43 54M >> >> 11 1 0 0 0 0 0 0 0 43 54M >> >> 12 1 0 0 0 0 0 0 0 42 54M >> >> 11 0 0 0 0 0 0 0 0 43 54M >> >> 10 1 0 0 0 0 0 0 0 43 54M >> >> 11 1 0 0 0 0 0 0 0 42 54M >> >> 9 0 0 0 0 0 0 0 0 43 54M >> >> 11 1 0 0 0 0 0 0 0 43 54M >> >> 14 3 0 0 0 0 0 0 0 37 54M >> >> 11 0 0 0 0 0 0 0 0 42 54M >> >> 10 1 0 0 0 0 0 0 0 44 54M >> >> 11 0 0 0 0 0 0 0 0 44 54M >> >> 10 1 0 0 0 0 0 0 0 44 54M >> >> 11 0 0 0 0 0 0 0 0 44 54M >> >> 10 1 0 0 0 0 0 0 0 45 54M >> >> 11 1 0 0 0 0 0 0 0 45 54M >> >> 11 0 0 0 0 0 0 0 0 45 54M >> >> 10 1 0 0 0 0 0 0 0 45 54M >> >> input output altrate short long xretry crcerr crypt phyerr rssi rate >> >> 3460 290 0 0 79 8 0 0 0 44 54M >> >> 10 1 0 0 0 0 0 0 0 44 54M >> >> 11 0 0 0 0 0 0 0 0 41 54M >> >> 11 1 0 0 0 0 0 0 0 43 54M >> >> 10 1 0 0 0 0 0 0 0 44 54M >> >> 11 0 0 0 0 0 0 0 0 44 54M >> >> 12 2 0 0 0 0 0 0 0 42 54M >> >> 11 0 0 0 0 0 0 0 0 43 54M >> >> 11 1 0 0 0 0 0 0 0 43 54M >> >> 12 0 0 0 0 0 0 0 0 42 54M >> >> >> >> ----------------------------------------- >> >> >> >> FreeBSD 9.0-STABLE >> >> >> >> mesh-6c9a:~ # athstats -i ath1 anistats -o ani 1 >> >> input output altrate short long xretry crcerr crypt phyerr rssi rate >> >> 1315335 48744 431 0 10204 865 630698 0 0 27 12M >> >> 38 0 0 0 0 0 13 0 0 21 12M >> >> 34 1 0 0 0 0 14 0 0 24 12M >> >> 28 0 0 0 0 0 14 0 0 27 12M >> >> 44 8 0 0 1 0 13 0 0 23 12M >> >> 43 1 0 0 0 0 9 0 0 23 12M >> >> 33 1 0 0 0 0 11 0 0 27 12M >> >> 36 1 0 0 0 0 16 0 0 22 12M >> >> 30 0 0 0 0 0 21 0 0 26 12M >> >> 42 5 0 0 1 0 18 0 0 23 12M >> >> 34 3 0 0 0 0 9 0 0 23 12M >> >> 32 0 0 0 0 0 20 0 0 23 12M >> >> 31 3 0 0 0 0 18 0 0 25 12M >> >> 27 1 0 0 0 0 18 0 0 29 54M >> >> 40 2 0 0 0 0 16 0 0 23 54M >> >> 40 3 0 0 0 0 12 0 0 21 54M >> >> 37 2 0 0 0 0 15 0 0 24 54M >> >> 34 1 0 0 0 0 12 0 0 26 54M >> >> 44 2 0 0 0 0 7 0 0 24 54M >> >> 60 1 0 0 0 0 19 0 0 24 54M >> >> 41 0 0 0 0 0 11 0 0 24 54M >> >> input output altrate short long xretry crcerr crypt phyerr rssi rate >> >> 1316118 48780 431 0 10206 865 630996 0 0 23 54M >> >> 39 1 0 0 0 0 12 0 0 21 54M >> >> 42 2 0 0 0 0 10 0 0 22 6M >> >> 36 2 0 0 2 0 15 0 0 21 6M >> >> 41 0 0 0 0 0 9 0 0 23 6M >> >> 34 1 0 0 0 0 7 0 0 26 6M >> >> 30 0 0 0 0 0 16 0 0 26 6M >> >> 36 3 0 0 0 0 15 0 0 22 6M >> >> 45 0 0 0 0 0 26 0 0 26 6M >> >> 38 3 0 0 2 0 18 0 0 21 6M >> >> 38 1 0 0 0 0 13 0 0 25 6M >> >> 36 0 0 0 0 0 13 0 0 20 6M >> >> 27 2 0 0 0 0 20 0 0 24 6M >> >> 39 1 0 0 0 0 15 0 0 21 6M >> >> 40 2 0 0 0 0 13 0 0 23 6M >> >> 38 0 0 0 0 0 8 0 0 24 6M >> >> 35 3 0 0 6 1 18 0 0 23 6M >> >> 34 1 0 0 0 0 11 0 0 22 6M >> >> 48 0 0 0 0 0 23 0 0 24 6M >> >> 35 1 0 0 0 0 8 0 0 24 6M >> >> 34 2 0 0 0 0 14 0 0 20 6M >> >> input output altrate short long xretry crcerr crypt phyerr rssi rate >> >> 1316889 48805 431 0 10216 866 631303 0 0 27 6M >> >> 41 1 0 0 0 0 15 0 0 24 6M >> >> 28 0 0 0 0 0 13 0 0 24 6M >> >> 36 3 0 0 0 0 12 0 0 23 6M >> >> 27 1 0 0 0 0 12 0 0 25 6M >> >> 26 0 0 0 0 0 12 0 0 28 6M >> >> 20 1 0 0 0 0 15 0 0 29 6M >> >> 40 0 0 0 0 0 28 0 0 27 6M >> >> >> >> On Thursday 31 July 2014 16:01:56 Adrian Chadd wrote: >> >>> On 31 July 2014 14:56, Johann Hugo wrote: >>>> On Thursday 31 July 2014 14:29:55 Adrian Chadd wrote: >>>>> Hi, >>>>> Yeah, run athstats 1 on both to see what kind of difference(s) there >>>>> are in transmit/receive statistics. >>>>> I wonder if it's changes in the ANI code. >>>> Forgot to mention that I only see the problem on cards with an Atheros >>>> 9220 >>>> chipset and not on older ones with an Atheros 5413 chipset. >>> Right, but the main changes to the ANI code occured with the 11n HAL, >>> not with the pre-11n chips. >>> There's also changes to the initval arrays used in chip >>> initailisation. That may have changed things. >>> -a > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 20 19:14:15 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C90EE471 for ; Wed, 20 Aug 2014 19:14:15 +0000 (UTC) Received: from nm3-vm0.bullet.mail.bf1.yahoo.com (nm3-vm0.bullet.mail.bf1.yahoo.com [98.139.212.154]) by mx1.freebsd.org (Postfix) with ESMTP id 75F3E3B62 for ; Wed, 20 Aug 2014 19:14:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s2048; t=1408561920; bh=2rc72sVtrLt/oIL3VYOZUYjypVCP3AjK59LiR0ztZZQ=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:Date:Message-ID:Subject:From:To:Cc:Content-Type:From:Subject; b=cZPUAgxdUWUoM8xZy2m7fuHUAh86z0YRxaCFCc7KVnim4dO6E5d9UR405tlxpKuYb4JVzbn4G+KOgRr6x/ovOT9tGoS00YzGoBul+7R7qy7xFyeUUN1XSwAPLIYBrQevQSYHcTP68fkppYrn3yXaGc3DmuawjDW7puhEUPiGN1dYVii7Is77fEMrLgXBEghTvhnzXFYvXvSEvf+agoxXOXd6452bb8spgFDioQm68QvbF01zC3cC/F0f9/OSCWvJqzu1Su0OGs+7FG26tQy/a2Uaf0/Rda4aEESDeYiS2f8duxU7O1NTe/SoyGcwSo9yIOa0u6S4WRK3D8FA6NXTbQ== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.ca; b=LlU/1YUaDd0amknju1SnU7eG+B0mFJzjX51YnlCQ2Y17//wwK5BD5HH93s3XcfBEH57ybsaJQGU3i0KQIWAfSQmJM09AXVs/zX9AF/IgeyuF3lBrKQBTqgPTDPagK2TrQG3Qglajpr0Ww2LsBvJRyWnqSzHwgOG9ncACJjmpeMgEl9vINn0CY7AoH/CS6PEbYU8G1YWFY9l6dO67clGUCAlzomgPLAxv0Le0OgFSv6UH2W5E+7j84WSHgOBt/viJm8ot5M3D289D5KtOEyCEAeUpZl8eq9RQ6/NlEEzvB7E+b9PvgRe8W4T3BVqzGeGQMe4Zo0I28C81rzZHi/gO/w==; Received: from [98.139.215.140] by nm3.bullet.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 19:12:00 -0000 Received: from [68.142.230.65] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 19:12:00 -0000 Received: from [127.0.0.1] by smtp222.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 19:12:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1408561920; bh=2rc72sVtrLt/oIL3VYOZUYjypVCP3AjK59LiR0ztZZQ=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=OuJqWqipXgaFkgIWZUTPd+Rh3biZVxjc9jQpxZpgOSAmb3jnqQR+N2xLXFZsIo2jhUW7DvlXGVonAQNN6kxdx3XNMKM4tJaTUj3LGTmNHRRWLGT9W/g8+zRuH8mhTzIl8BQdhu2gFqWzcqR2zU8rXdHpzLL1lrOsZ+2SQHGtTCM= X-Yahoo-Newman-Id: 924456.75661.bm@smtp222.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 76no6HoVM1mzyi4aKNw2UoU7Kl3aLXwT6zq6avwS.x4CXGs nMoKBcKqK7KE72oDB5cAJZ9Tlrdvfk4lUIdXTlQrVAGNKDzJb0RBZcuOgW52 2EV4p9PL3JffzM1R_WjNSef1YLjHKlncoxZFGABKBkQ5pnDj5p.uij_Ibs8O NvlmouxDUdXVhHI4jIxieX2c7.SEm.rHGW70xXkeb_8geTqxZTAG4MqxI9cr qYYNVvkUWQHS.0oNZEquQ_wbynonAxT1TqALtcPFV9U5Pi1Tck5W30xZhxDK h2RfuKY9OsmyIt2KhaWGpfvfSFPsqhtKnHr3vPmqY5uBoZ6dYtHHblcSBWaq Zl6y9vg8bmBYvnCeJ3lyrjPPniQ83aaaugjT0esmL.PLktEg_YOAKI1UmfOY c0d4Uy3jNhpG5zXCMZBz.iMeRGIcTVfwp39xSPvlL5ma52nlSXqpZGIGF2n6 co23BzXw2H3Gh6G3G5bfk8w3hH9cZDX_vYRRIYwhIimZLqQyFSAt8CN.ZZyT jHMJpzZtc0.V.QPtM5X7sgGUMNHzXHnd6HzPIefOscBVDfQ70N7COwdcNLph qx4OyEtMM8ZmzaqELuWv9urHIdAoqde9SjBQxZPOvx4UbGpRvywWcl0lR X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: by mail-lb0-f178.google.com with SMTP id c11so7149838lbj.23 for ; Wed, 20 Aug 2014 12:11:59 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.255.36 with SMTP id an4mr42617937lbd.31.1408561919280; Wed, 20 Aug 2014 12:11:59 -0700 (PDT) Received: by 10.112.230.9 with HTTP; Wed, 20 Aug 2014 12:11:59 -0700 (PDT) Date: Wed, 20 Aug 2014 13:11:59 -0600 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network From: PseudoCylon To: Kevin Lo , Miguel Clara Content-Type: text/plain; charset=UTF-8 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 20 Aug 2014 19:14:15 -0000 > Message: 4 > Date: Mon, 18 Aug 2014 16:49:32 +0800 > From: Kevin Lo > To: Miguel Clara > Cc: freebsd-wireless@freebsd.org > Subject: Re: FreeBSD current RT3071 can't connect to 5G network > Message-ID: <20140818084932.GA31760@ns.kevlo.org> > Content-Type: text/plain; charset=us-ascii Adding 11n support to run is pretty much done. But, run (either stock or with 11n) generates lots of rx crc errors. I do not have datasheets neither, so I kinda gave up. If some one fix it, the driver is ready to go. Otherwise, the performance sucks. > > Since there is no data sheets available, looking throught the source code > from the vendor makes slower development and is very time-consuming, > at least in my case. > > Kevin > > On Sun, Aug 17, 2014 at 05:03:50PM +0100, Miguel Clara wrote: >> >> Thanks for clarifying Kevin. >> >> I wonder whats the reason for this? Since its in all I guess something in >> the kernel makes this harder? or is it just lack of time/resources? >> >> thanks >> >> >> >> >> Melhores Cumprimentos // Best Regards >> ----------------------------------------------- >> *Miguel Clara* >> *IT - Sys Admin & Developer* >> *E-mail: *miguelmclara@gmail.com >> www.linkedin.com/in/miguelmclara/ >> >> >> On Sun, Aug 17, 2014 at 3:43 PM, Kevin Lo wrote: >> >> > On Sat, Aug 16, 2014 at 09:07:29PM +0100, Miguel Clara wrote: >> > > >> > > On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo wrote: >> > > >> > > > All USB wifi dongles in FreeBSD don't support 11n yet. >> > > > >> > > > Kevin >> > > > >> > > > >> > > I was not aware of that, is this really true for all USB wifi dongles or >> > > do you mean ralink only? >> > >> > It's true for all USB wifi dongles in *BSD... >> > >> > Kevin >> > >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" >> > > From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 20 19:29:29 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4627BAC5; Wed, 20 Aug 2014 19:29:29 +0000 (UTC) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA5F13CB0; Wed, 20 Aug 2014 19:29:28 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id m20so8347507qcx.10 for ; Wed, 20 Aug 2014 12:29:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=nlQ+5Df5ANHHwon8UQNIgklkQDck2rOhaRKPNLt7hKU=; b=Ds1ZkGgDXH9LMo+uWMR3kQiZyBBtMN/KTi264GIlS9i6eyi8sFozNz4KAyPNrDuF0q teKCOKLbcMDfLlbqu54IgC5yyukuLD5WVD6J6iSt8l6jpSCl4U692PipuZmsf9OhqeMD WqFUYG1rN4owSeSi83nPaj+R5LZhzsBMPfMzwDw2kxKeuxTrWHjeEbvteC8pmxFTB43K 1fTF3nu8OidC7YMWT89wMYeJDrgL8goKWvb6bwnj7QUbFJnCDwYsN223q4HAu1EAnc83 DAo/w1LH6EzXGBoUaGjjmGXZnHfWZb3udIRwvotf81GQEy1728HATZsSbp2UZnMrPE94 8l6g== MIME-Version: 1.0 X-Received: by 10.224.75.73 with SMTP id x9mr43697927qaj.63.1408562967804; Wed, 20 Aug 2014 12:29:27 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Wed, 20 Aug 2014 12:29:27 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 12:29:27 -0700 X-Google-Sender-Auth: dbJH5Sc362_1lGJvg5mTktnb6Go Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=UTF-8 Cc: Kevin Lo , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 20 Aug 2014 19:29:29 -0000 Are you seeing RX CRC errors for all rates? CCK? OFDM? HT? At all distances? There's a handful of things we can look at to see what's causing it once some more digging is done. (Eg, HT? could be guard interval. OFDM has similar issues, there's typically ways to configure how much time between each symbol is left before transmitting the next one. It may not be doing CTS-to-self, or it may not be advertising the right thing via NAV, or it may be ignoring CCK, or the receive gain tables are all messed up, etc.) -a From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 20 23:34:05 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13EE8C8 for ; Wed, 20 Aug 2014 23:34:05 +0000 (UTC) Received: from nm14-vm0.bullet.mail.bf1.yahoo.com (nm14-vm0.bullet.mail.bf1.yahoo.com [98.139.213.164]) by mx1.freebsd.org (Postfix) with ESMTP id A316233E3 for ; Wed, 20 Aug 2014 23:34:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s2048; t=1408577637; bh=wn+zq/yUns5CLNYtH7t1IYoEqiTsuMz/XNfPL5I7qZo=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type:From:Subject; b=hBRzfzpkiQnLYis/N0Sp6zzUCKD9a/9HPnGgFoIB/oyb24Wnrz12v/Prbo93+Zv6f8zxUVhg821lnw8DsxoIfU8oVjCXTzseG8JVRArK4Ad9WBJWEKlpA6aoAmKoKrxORX7w869Oir0opnpvS0O29BzS/z9MOTl3YN4tuof91WGVhjt8SLrV6h4oH3GRoMokOSUtsGusjpe0YLg40Zy3/WNHUUlSxS1P/uy6Esg1UwpkFJ6LII5+lY2/p4KUI2FWj4ovEhHjVbcil7e30ywE3aPa20/3e5UMJurFjNCj/eIjkEpkz3Rwh2JRg1DioTPT3SvXjuxlB7bVlEpH6G+oSA== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.ca; b=swtHo38kmJg5pG0VUTVQik2N+3GQYSw7w+xH3+zJc4isaD5BMQrKA1HWILtA1GV2JUgWlbwgFRGYW8OtHl64kvElnbrxT0RzL5TC4L2A6CBSciCbrh8LL2HpSgQVh5BNKSTbMBCyCbh62XCJFOV0Krk2UTjP+7M6wr4bKhQNqjlkcvuDU9WiGTI6sn6yhtAHtrFM49AhRumpORuYy6wOP2YPiaEu2DbyuhYB2gO9W/Otxm2TWoUjHFuHAjxyUDZxhWJ/oRAvQNFkNfwntOLXTaeuaF631SitNByLGoa/ttted5tTznxYy5r07uNs+kiz+YbahDF8YvPmMB5OJL0Eww==; Received: from [98.139.215.140] by nm14.bullet.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 23:33:57 -0000 Received: from [68.142.230.77] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 23:33:57 -0000 Received: from [127.0.0.1] by smtp234.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 23:33:57 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1408577637; bh=wn+zq/yUns5CLNYtH7t1IYoEqiTsuMz/XNfPL5I7qZo=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=wjYPLprxrt1nnVdv8KNR/CTOseKU+9O7jM7/bB1pIUIR4Mu/WmA1vil2RZxZxoOU+cFDgiP/0zCw+aPN6ezYwGGfAjdgeivzH27iKxtYns8x83mGJV0qFFY0LFfTiXXkwDgS7pFM/cn5blvBFbOg+9SaZjNZf4kV4UKNrDiQl0w= X-Yahoo-Newman-Id: 17487.32792.bm@smtp234.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: pSm.02kVM1nyL9vbsnxQ_bCwgvtcCtabGVjslHCLDwYmss0 1UKIirGh88gVQLJArK0tYdo0TN5zeUDRgKqNqQS8eSRCsfIIM3IGFTs7Hl8y 9Cd5D3_SF2EHbulB0hMhnPFMwbH.J4rPelCQJEBevYGbYpeUc2OPTI2SGdhf fc4xlH2bGh3juU8ZnV7sGY3.BIXppirHTk8.N77gPQbZjvTfVcl9EoYywytX NxNnrR12RmPZajwIwxEgpXQRi7jPaUQXfuHmKBdtqlhWh6FYCQf4BYG3k7G. 5XLQVQYX9K0q0KnVtNdsHTJqsXSvjJFSybJNo3ieWHDTo4uWd_TP8bDwikI7 6RMQK2vr6TP7bDnEQvyHdVOtskTtZLgs28TxcnsWbVxQ_Tt62BCQQEnMR8iX XaTCWZBUy75P7uYUbcv62ITbYznHmCobX406bk77RXCl6GqPR1KWahgc9ige CcFZ9hoL9JtNJyFuDzhWz0NTbhkDCaQDlwmzacpsNcj_PlyohocSCRvpTNmA 6b38bIHo6dH_kYVtsNnsP2ra92K7w8oFDmEdgkMV0 X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: by mail-la0-f48.google.com with SMTP id gl10so7671309lab.7 for ; Wed, 20 Aug 2014 16:33:53 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.27.134 with SMTP id t6mr36275060lag.56.1408577633007; Wed, 20 Aug 2014 16:33:53 -0700 (PDT) Received: by 10.112.230.9 with HTTP; Wed, 20 Aug 2014 16:33:52 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 17:33:52 -0600 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: Kevin Lo , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 20 Aug 2014 23:34:05 -0000 On Wed, Aug 20, 2014 at 1:29 PM, Adrian Chadd wrote: > Are you seeing RX CRC errors for all rates? CCK? OFDM? HT? At all distances? CCK not sure, OFDM and HT yes. And at wide range of distances. (Tx rates usually hit mcs 12 to 14 with 2s ht20 ap) > > There's a handful of things we can look at to see what's causing it > once some more digging is done. > > (Eg, HT? could be guard interval. OFDM has similar issues, there's > typically ways to configure how much time between each symbol is left > before transmitting the next one. It may not be doing CTS-to-self, or > it may not be advertising the right thing via NAV, or it may be > ignoring CCK, or the receive gain tables are all messed up, etc.) I have looked into stuff I was able to dig out from other src codes, ie protection, ifs, nav, bk slot. (Because I do not have datasheet, every thing is based on my guesses.) One thing I could not figure out is if on-chip memory is properly allocated for rx pkt. (It seems memory can be allocated for different things, ie beacon, enc keys). > > > -a From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 20 23:55:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B56B6BFF; Wed, 20 Aug 2014 23:55:08 +0000 (UTC) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 647D435BE; Wed, 20 Aug 2014 23:55:08 +0000 (UTC) Received: by mail-qg0-f49.google.com with SMTP id j107so7976864qga.8 for ; Wed, 20 Aug 2014 16:55: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:message-id:subject :from:to:cc:content-type; bh=UARrdg1tP5tdhtGWYTH4BRv+aHLsdr4WXKa3pSL2WtQ=; b=D2/jimhBpsomkUIg5bzHm9s+87KXWrU3mDoF9U+d137X5bS0h79fTNXl9y2RmO7rUF 8OG+Nj6TO8szEIOV2+p1Z9Or9kApj0HfsH6hAiXIiqAIpydpwfqQ9fsdNAZFIZqK1dxi dJpnvgrUu+OQlDWzfZJ1lg9WMb7HpPblFmQo25IjvSchAkO2+WB2+iIUVKp2BgX6X0IG 4p+I1g4g4HS2RC4U0WVFp1kpO8oMzC2LLJqHYITSszfn18W8dr19GjdiTRfQ/Lb87SZQ CkVLmQhkZnyO+H2mkEu1ylI+iSLxda8PyH/Enm+y7Ts4NOYITbQ2v+9g3bYU3JIG5fau baaA== MIME-Version: 1.0 X-Received: by 10.224.75.73 with SMTP id x9mr45870275qaj.63.1408578907625; Wed, 20 Aug 2014 16:55:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Wed, 20 Aug 2014 16:55:07 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 16:55:07 -0700 X-Google-Sender-Auth: ZZGnLwYWzEx3sysy8sKCauQOdiI Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=UTF-8 Cc: Kevin Lo , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 20 Aug 2014 23:55:08 -0000 On 20 August 2014 16:33, PseudoCylon wrote: > On Wed, Aug 20, 2014 at 1:29 PM, Adrian Chadd wrote: >> Are you seeing RX CRC errors for all rates? CCK? OFDM? HT? At all distances? > > CCK not sure, OFDM and HT yes. And at wide range of distances. (Tx > rates usually hit mcs 12 to 14 with 2s ht20 ap) > >> >> There's a handful of things we can look at to see what's causing it >> once some more digging is done. >> >> (Eg, HT? could be guard interval. OFDM has similar issues, there's >> typically ways to configure how much time between each symbol is left >> before transmitting the next one. It may not be doing CTS-to-self, or >> it may not be advertising the right thing via NAV, or it may be >> ignoring CCK, or the receive gain tables are all messed up, etc.) > > I have looked into stuff I was able to dig out from other src codes, > ie protection, ifs, nav, bk slot. (Because I do not have datasheet, > every thing is based on my guesses.) One thing I could not figure out > is if on-chip memory is properly allocated for rx pkt. (It seems > memory can be allocated for different things, ie beacon, enc keys). > So CRC errors are pretty normal with wifi. Even a tiny bit of interference generates CRC errors. That's why there's an ACK and retry mechanism. :P If you're hitting MCS 12 then you're doing pretty well. A-MPDU will see lots of CRC errors just because of how long the transmissions are and how easily corrupted things can get. That's again why there's a quick retry mechanism for things. What %age errors are you seeing? -a From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 09:43:53 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46EC351E for ; Thu, 21 Aug 2014 09:43:53 +0000 (UTC) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B3DD3EE6 for ; Thu, 21 Aug 2014 09:43:53 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id rp18so4237259iec.5 for ; Thu, 21 Aug 2014 02:43:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=BDjjTahcov663voXK+UnVMZV/4w3EOgktnwiAtW3iRQ=; b=SIb3Yjo4vWmI4lif6DE3IhpSfliTHb9p2SxxTBWhAXrYhnfwAedKFBF9vDePbF9MC+ t9yhFrMLC5cMT2yduATwAsJnvbm8Ki3FZtESqfGviLG0V3CWPSSfXhOwc9XQmEC67h+0 zdVESFyczG6Y6HOF/cKB/qCS37NGRBbtaQs2+W/hiJbyqNmVddEhEqYL/m3KHoV/jktR bvXNEMb++sx5Y0UrpI8PU0mrVWHqdZAVlKlJ9OQF/i6SpjYw87jmY+ZarrOcXo0Bfn+u 4sNZwxNtP5rzHwwN1finXRVREsJez+Q1lzdN06r36OE8KxIRsv5uVBTai2hGuv2ji5Xm KYjg== MIME-Version: 1.0 X-Received: by 10.42.60.211 with SMTP id r19mr2440972ich.64.1408614232466; Thu, 21 Aug 2014 02:43:52 -0700 (PDT) Received: by 10.107.153.208 with HTTP; Thu, 21 Aug 2014 02:43:52 -0700 (PDT) Date: Thu, 21 Aug 2014 05:43:52 -0400 Message-ID: Subject: How do I ALTQ hostap interface? From: Peter Lai To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 09:43:53 -0000 How do I ALTQ my wireless (hostap mode) interface in 10.0-R? If I try to add a queue to wlan0, pf complains that wlan0 has no ALTQ support (even though it is an ath(4) interface and ath(4) is supposed to be supported by ALTQ). ALTQ is already setup and working with my wired ethernet over em(4). Am I supposed to specify ath0 as the interface for the pf queue? What if I want to bridge my wireless and wired networks? I thought the bridge would consist of em0 and wlan0 members, and pf will not like that (claiming that bridge0 has no ALTQ driver...but I don't know if that is pf reacting to if_bridge(4) itself not having altq support or the wlan0 member of it... From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 14:38:25 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FF15FEA for ; Thu, 21 Aug 2014 14:38:25 +0000 (UTC) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E558B3DA3 for ; Thu, 21 Aug 2014 14:38:24 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id s7so8474440qap.9 for ; Thu, 21 Aug 2014 07:38:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=SO+pZ3skrQqLLAfJcoWrXE72qpASFkj1LWv95PkdSTk=; b=UGdZewYTSn0tGpbBoA8DbBSNfNHRH3M4bPzMy/i1mH+h76UpPB3t0a5Tz6uUr+Hvjk 6GIXUihMY/LtRXmxxSexeolo3Z55JudQrLf8ZqSLDXTGNDL+g/WpSOjXKeul3UdkOjHG lrAQtbcRaHhpwXzTUckQgE6mWCeQXyS9H7Ei5EoBv5JG3IVo9c78Ffk2qJKs5hHGxlDi EGys1XGNV2DP2L56O5R1Zw5M7pVdG7okvwdPhltdYnmojFAl4Aft40Ft7T0V465Y6f3Y d1xvu05bPOrOsgbgbm/cmPWVODHniw1Z37Q5cxi3l48IkkHGoYtaIKcIC+YpX3vV3y8f +t1A== MIME-Version: 1.0 X-Received: by 10.140.104.69 with SMTP id z63mr84542571qge.81.1408631903980; Thu, 21 Aug 2014 07:38:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Thu, 21 Aug 2014 07:38:23 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 07:38:23 -0700 X-Google-Sender-Auth: -5k7STODdz98s9A9xCjUgXzCV6I Message-ID: Subject: Re: How do I ALTQ hostap interface? From: Adrian Chadd To: Peter Lai Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 14:38:25 -0000 Hi, ath(4) now uses if_transmit() and thus there's no ALTQ support at the moment. Sorry. -a On 21 August 2014 02:43, Peter Lai wrote: > How do I ALTQ my wireless (hostap mode) interface in 10.0-R? If I try > to add a queue to wlan0, pf complains that wlan0 has no ALTQ support > (even though it is an ath(4) interface and ath(4) is supposed to be > supported by ALTQ). ALTQ is already setup and working with my wired > ethernet over em(4). > > Am I supposed to specify ath0 as the interface for the pf queue? > > What if I want to bridge my wireless and wired networks? I thought the > bridge would consist of em0 and wlan0 members, and pf will not like > that (claiming that bridge0 has no ALTQ driver...but I don't know if > that is pf reacting to if_bridge(4) itself not having altq support or > the wlan0 member of it... > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 15:53:12 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 089BA9DC for ; Thu, 21 Aug 2014 15:53:12 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD43C3603 for ; Thu, 21 Aug 2014 15:53:11 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id lx4so4893381iec.31 for ; Thu, 21 Aug 2014 08:53:11 -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 :content-type; bh=aN+ofhxq6vYUtYZJ1H1yv7PXCx7clrSDQhOQ4CRphDw=; b=QfHK8ryVykyd9k4ZD+QWC/HQbmNYo9oB5npGN0S9EBtT9/XetqSHwjhTcGzx8C5rWr 3F5H812Lrgzn42FVE/vfgMgr5BizcuHGogd33hJTkKn/fTsgYp9UfVI1AZPLOW9Ar1JC qKiB9MZzvgSrXuGuYVvCknLTus81YIlze0eRDzuCUqu5rvM/QuRcFyoqXk9KeFw9yTAQ OVMGOWM9b/1+bi7SxgsItqJw6zCvoqdVfsvFLFltolB7yToVdumF9QLQAJhMDOjvuclB VdEYSDYAcWr9PHtoqYg+LClzPr0DJX4iiNYM8ebrzDSRNy23JvwFD7pZBExNblXV7un8 r58g== MIME-Version: 1.0 X-Received: by 10.50.32.2 with SMTP id e2mr20473907igi.33.1408636391074; Thu, 21 Aug 2014 08:53:11 -0700 (PDT) Received: by 10.107.153.208 with HTTP; Thu, 21 Aug 2014 08:53:11 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 11:53:11 -0400 Message-ID: Subject: Re: How do I ALTQ hostap interface? From: Peter Lai To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 15:53:12 -0000 Does 9-STABLE support ath(4) and ALTQ? thanks On Thu, Aug 21, 2014 at 10:38 AM, Adrian Chadd wrote: > Hi, > > ath(4) now uses if_transmit() and thus there's no ALTQ support at the > moment. Sorry. > > > -a > > > On 21 August 2014 02:43, Peter Lai wrote: >> How do I ALTQ my wireless (hostap mode) interface in 10.0-R? If I try >> to add a queue to wlan0, pf complains that wlan0 has no ALTQ support >> (even though it is an ath(4) interface and ath(4) is supposed to be >> supported by ALTQ). ALTQ is already setup and working with my wired >> ethernet over em(4). >> >> Am I supposed to specify ath0 as the interface for the pf queue? >> >> What if I want to bridge my wireless and wired networks? I thought the >> bridge would consist of em0 and wlan0 members, and pf will not like >> that (claiming that bridge0 has no ALTQ driver...but I don't know if >> that is pf reacting to if_bridge(4) itself not having altq support or >> the wlan0 member of it... >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 17:43:52 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BDB3185B for ; Thu, 21 Aug 2014 17:43:52 +0000 (UTC) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A1B63226 for ; Thu, 21 Aug 2014 17:43:52 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id dc16so8603054qab.36 for ; Thu, 21 Aug 2014 10:43: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:message-id:subject :from:to:cc:content-type; bh=QAShXvYGbj2niWisBA6JwtthQ6aLP1cz0KOvuetsEZ4=; b=GqTHfeRuUYL5Eub9qJctqtBv6ToWiM++4bGE1l5yKgLzzQjHIhjvRSCNpya6ja6WhZ 27P55n1QJcUM/WTkIqQRvD8SRZeSrD0KCN4YQTfh16gfBDR5O/WoGHCAbvVXIolyGWN9 tExWDWeLAMq8k/3RTFrKM4AcYxZ6Z7U8Kcfhgb6Vetvd43TWmH+Y2VwssvFMMkb/4hcV LF1MNKdKUNRzUI0Z8BVp7VjVMV8jg9LoNTPT3KT+uksbfhc3As9Mcvv806ix4N2eKQqM LnA37DM5vruJG5UOjEuWheTtSic86/yIxOSsVQ9MLF3OyknlaBzSTYrVLc862Qmm81wC OHow== MIME-Version: 1.0 X-Received: by 10.140.27.144 with SMTP id 16mr338975qgx.18.1408643031625; Thu, 21 Aug 2014 10:43:51 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Thu, 21 Aug 2014 10:43:51 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 10:43:51 -0700 X-Google-Sender-Auth: 26IsAxbygQOba0eVv3YkFbi2dSo Message-ID: Subject: Re: How do I ALTQ hostap interface? From: Adrian Chadd To: Peter Lai Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 17:43:52 -0000 I've no idea. Sorry, I've kept asking those who are interested in altq to figure out how to do it for drivers with if_transmit() and so far it's been crickets/silence. -a On 21 August 2014 08:53, Peter Lai wrote: > Does 9-STABLE support ath(4) and ALTQ? > > thanks > > On Thu, Aug 21, 2014 at 10:38 AM, Adrian Chadd wrote: >> Hi, >> >> ath(4) now uses if_transmit() and thus there's no ALTQ support at the >> moment. Sorry. >> >> >> -a >> >> >> On 21 August 2014 02:43, Peter Lai wrote: >>> How do I ALTQ my wireless (hostap mode) interface in 10.0-R? If I try >>> to add a queue to wlan0, pf complains that wlan0 has no ALTQ support >>> (even though it is an ath(4) interface and ath(4) is supposed to be >>> supported by ALTQ). ALTQ is already setup and working with my wired >>> ethernet over em(4). >>> >>> Am I supposed to specify ath0 as the interface for the pf queue? >>> >>> What if I want to bridge my wireless and wired networks? I thought the >>> bridge would consist of em0 and wlan0 members, and pf will not like >>> that (claiming that bridge0 has no ALTQ driver...but I don't know if >>> that is pf reacting to if_bridge(4) itself not having altq support or >>> the wlan0 member of it... >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 17:46:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EAEB99B3 for ; Thu, 21 Aug 2014 17:46:30 +0000 (UTC) Received: from nm46-vm10.bullet.mail.bf1.yahoo.com (nm46-vm10.bullet.mail.bf1.yahoo.com [216.109.114.203]) by mx1.freebsd.org (Postfix) with ESMTP id 913B0325D for ; Thu, 21 Aug 2014 17:46:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s2048; t=1408643014; bh=QygiCgvSDhJSiogf+q6AOGVPekj5+ohaIiD3APwpJfQ=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type:From:Subject; b=an2vZnuXCHe9PPHsQMTAeFJJaGwLIFIUhj3jTs8xy38hd+1c2rwk1BL4pD+o3G0CK2JwsnWtgm+kz9fqJBZFsoYlsExMWxhVk8avn5N4cd0zg1koaKoO6I0uAgZJoy4N0tNNaUtveYuTJGQb6+MSta/OLxia7pKiMuKUGA6ujpaTFKGL1BtwwDGTPqB+E078FWVXXdK9dsKac/77g6SG4I8rHqSrY8KrtD5BXMm5loLhh0tLWo2zEdnKu1mN5Cr9IgRNzJAB9jRftI4TnSL9JLO2XaoJATG1VjGcNXHhHv8Jr6Vtf3Wk2pHUHTlRf7kNP0we4ha5DO8aU2/K9bwN7w== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.ca; b=rNFN0rGSWv1IxVCO2SjGZdmqQh4MABhySI7WOdR5xdPAE5j/XbJ9NGRPieDVgTgYE5lodWdHv0TaI7SKUoNj8R9UIO8Xq1/pJsqpp4T8vgM/db23qn/71ZV+eQGGyDfSXi5Z0EnPgTdDneieVNTeAp5PnsqFgvqTpSwzllmMT+gGDVRH52o9eBYXr/RfAGfw3RDrhrUo7Rz2+kycF69DvaTPlSlwBNTvuc32jc1COsbekMCPaZNWW11ggusmsbkcFARqCJ8uKsRxEBXvOM7ExtYVBTt0OKqpVAj4Nn1V9E9/NMxUp214ihAetYSnGTjzOWPPQhjbBxR5Cjy03IKqWw==; Received: from [98.139.212.151] by nm46.bullet.mail.bf1.yahoo.com with NNFMP; 21 Aug 2014 17:43:34 -0000 Received: from [98.139.213.9] by tm8.bullet.mail.bf1.yahoo.com with NNFMP; 21 Aug 2014 17:43:34 -0000 Received: from [127.0.0.1] by smtp109.mail.bf1.yahoo.com with NNFMP; 21 Aug 2014 17:43:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1408643014; bh=QygiCgvSDhJSiogf+q6AOGVPekj5+ohaIiD3APwpJfQ=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=jl6ho2IlyG1VY7D559VoWf5ORWJH9l/7NTEwQd0N813TcgxIgyc6hk96FlOsDLr+XgxRS0jsINEUrxFc3nnlAjECpwJdUmDHzvNVAZxG/aLh8tUakXalG98XKL+M3jqt9TgokHUiHZzX3e6LFTLchxKKcWhJNSMUeADfufnaKyA= X-Yahoo-Newman-Id: 461933.62812.bm@smtp109.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: sOdV7DQVM1l0Ts0FQ4ZlOa8w9uvnN3dsKvsu0VAPF4Umc0T nOx42F.bzHjJ4scuTF9984Yeeu.jDcgrCvGhYJfAfpzr1qbfd_QNv3GGLk78 MNhsi3Zy4f1SJHVX2Tq8E9D8zsNzOpqglHkO7LRM5FKY29sdG59pfIBRj00B vPPEpaxKt_q82QN_FLzTymFI5DViicl2CzMtzG_iw6nJ.faWnnWf4vFXwDRE h2IW9BoADVzppGiXLuaKzNCp64Akmb8tFuyVxX5aZS8a7nEFPs_BPR0eKdJi t9FkBXPIACiTs862UzXKlZ.qOPw3X9eC1GjbZV8rQgGCvHTT2w8TB57iHEpQ oBnU5W9.Fn0qf13.Cjh7OqTas7s_vzl8iwlD7yBvSFjPfSflPOwNk9RUuTzp OnoH3fr4uXQtdUgjTlGi1s_0l5w5B_YsyZux5.UNymaUFDOK3r6Pabh5Iabn 8aPglYxW8.phWWNJUAMSLymDB5CuMA20b5pZvh7q_CT5GsJU9lLv5MFHkg8u THJ1Wvfm8LxP0i1DZcIss5VrlJiCO9ySzFWKmBA-- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: by mail-la0-f54.google.com with SMTP id hz20so9018671lab.13 for ; Thu, 21 Aug 2014 10:43:32 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.4.70 with SMTP id i6mr125953lbi.54.1408643012844; Thu, 21 Aug 2014 10:43:32 -0700 (PDT) Received: by 10.112.230.9 with HTTP; Thu, 21 Aug 2014 10:43:32 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 11:43:32 -0600 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: Kevin Lo , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 17:46:31 -0000 On Wed, Aug 20, 2014 at 5:55 PM, Adrian Chadd wrote: > On 20 August 2014 16:33, PseudoCylon wrote: >> On Wed, Aug 20, 2014 at 1:29 PM, Adrian Chadd wrote: >>> Are you seeing RX CRC errors for all rates? CCK? OFDM? HT? At all distances? >> >> CCK not sure, OFDM and HT yes. And at wide range of distances. (Tx >> rates usually hit mcs 12 to 14 with 2s ht20 ap) >> >>> >>> There's a handful of things we can look at to see what's causing it >>> once some more digging is done. >>> >>> (Eg, HT? could be guard interval. OFDM has similar issues, there's >>> typically ways to configure how much time between each symbol is left >>> before transmitting the next one. It may not be doing CTS-to-self, or >>> it may not be advertising the right thing via NAV, or it may be >>> ignoring CCK, or the receive gain tables are all messed up, etc.) >> >> I have looked into stuff I was able to dig out from other src codes, >> ie protection, ifs, nav, bk slot. (Because I do not have datasheet, >> every thing is based on my guesses.) One thing I could not figure out >> is if on-chip memory is properly allocated for rx pkt. (It seems >> memory can be allocated for different things, ie beacon, enc keys). >> > > So CRC errors are pretty normal with wifi. Even a tiny bit of > interference generates CRC errors. That's why there's an ACK and retry > mechanism. :P > > If you're hitting MCS 12 then you're doing pretty well. A-MPDU will > see lots of CRC errors just because of how long the transmissions are > and how easily corrupted things can get. That's again why there's a > quick retry mechanism for things. To clarify, tx on run hits mcs 12 to 14. I assume tx on run is working. But, tx on ap can hit 39mbps at the best, most likely due to high rx crc error rates on run. > > What %age errors are you seeing? Constantly 70 to 80 rx crc errors/sec during active downloads. (h/w does not count total rx, so cannot tell the %.) > > > > > -a From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 18:59:40 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A18A353E for ; Thu, 21 Aug 2014 18:59:40 +0000 (UTC) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 63C2339E5 for ; Thu, 21 Aug 2014 18:59:40 +0000 (UTC) Received: by mail-qa0-f52.google.com with SMTP id j15so8574892qaq.39 for ; Thu, 21 Aug 2014 11:59:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Fq48ssWwKagWfDeKtFzGUegkti+aRS2+wbpEJfBSQCU=; b=tYP4ZLUK/gbILCYkXyKSDbAbUwwK/Rw7cz/Nu6zxjoJ5eM7cKsXyJEAdQ5H1XF1H6n /Lei2NtZ3Qb6kTkvltqa2POAFpmiUB+UOxyYpqMnj58uVtrQWt5k9haNeXA+k5pQcUbV GReKmgW91u2HBytYnHSCXqNkt2fdi8JuxFMEVUtyHoN9jbd1GSbCcpbUUoSDsrR6tAkb MAbKn3ptBkKsxuoWq1hw7xJHOzi1MoGrwwRbYSlg3rqkWBhq6jddElbnrNkvH82Urfvc UvRL04+NZzYrCUzoCST2RgqLk2noSfNiISGoniUKt7ULs0KoYvRA9KjD0iqxhpru55ae sJJw== MIME-Version: 1.0 X-Received: by 10.140.46.55 with SMTP id j52mr683360qga.27.1408647578780; Thu, 21 Aug 2014 11:59:38 -0700 (PDT) Received: by 10.140.18.137 with HTTP; Thu, 21 Aug 2014 11:59:38 -0700 (PDT) Date: Thu, 21 Aug 2014 13:59:38 -0500 Message-ID: Subject: Is there anyone who can look at, and possibly fix this? From: Chuck Burns To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 18:59:40 -0000 There was a bug filed about 7 months ago, with iwi crashing under heavy usage. I am also hitting this bug under 10-stable. Things that trigger the bug are heavy two-way usage, such as bittorrent/aria2c and X11-forwarding over my LAN. bug#185478 The original reporter had this bug under 10.0-RELEASE, and I was under 10-stable. Took several reboots (and quite a bit of $HOME corruption as well) to track down a semi-reliable way to reproduce the bug. It does not always trigger a kernel panic, but iwi will always die with "iwi0: Firmware Error" and usually, attempting to restart netif will cause the panic. Even restarting netif will not bring the system back. I've got a urtw0 usb dongle that I can sometimes get to work after the iwi0 goes belly up, but not always.... (and for the record, I had tons of trouble with urtw0 back in 9-current, and it was -never- made stable for me...) With that said, however, iwi0 seems to be perfectly stable under OpenBSD and various Linux distros, which makes me wonder if A) do we need a different firmware version? or B) is there a problem with our implementation of the driver? I'm happy to provide as much more information as I can (I'm currently not running FreeBSD on this machine, but that is easily, and quickly remedied if anyone wants to attempt a fix with me) Thanks, Chuck Burns From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 19:03:24 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB077917 for ; Thu, 21 Aug 2014 19:03:24 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B4DE3A8F for ; Thu, 21 Aug 2014 19:03:24 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id a108so9206159qge.16 for ; Thu, 21 Aug 2014 12:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Km3tY6gmLIyORBkPfy1wZ3lOZdejXBQxVyI/L/wxPbI=; b=l++yXo6z2DjC51cuADOUULUTmEyxyqGg2vhDPGvSGjfZFHVDNiqywUc3xpoyis1yPD LulRaez5WKKunDL2W1slFobFj9a/IMqn3N7wznZdeG4toykON08PBoyqAsBnQl586BW3 /pQJRL0dht39I40gprjCgOLhJnHOTWr+kZSXTv9TDG1jvC1FLKlF4OU53alFFs514frv QC2NqdqoRWu4I1r9DYPKZBfxBa4Kj+sJ4VVroxlBwATG/4oTdUEuIC25IVxseAi5FlSH WOWDcHuI3fAdxCWdy0Df4Wpl7R8zTV3VijGdoCmHWxInDdICVj6j/k2lzsM6AH0Bhino Jg/A== MIME-Version: 1.0 X-Received: by 10.140.80.167 with SMTP id c36mr909001qgd.52.1408647803634; Thu, 21 Aug 2014 12:03:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Thu, 21 Aug 2014 12:03:23 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 12:03:23 -0700 X-Google-Sender-Auth: mLs4lc-mdFhYT_23yVngsqiq3Ts Message-ID: Subject: Re: Is there anyone who can look at, and possibly fix this? From: Adrian Chadd To: Chuck Burns Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 19:03:24 -0000 Hi! Neither of those drivers have active maintainers in FreeBSD. I'm sorry. :( -a On 21 August 2014 11:59, Chuck Burns wrote: > There was a bug filed about 7 months ago, with iwi crashing under heavy > usage. I am also hitting this bug under 10-stable. > > Things that trigger the bug are heavy two-way usage, such as > bittorrent/aria2c and X11-forwarding over my LAN. > > bug#185478 > > The original reporter had this bug under 10.0-RELEASE, and I was under > 10-stable. > > Took several reboots (and quite a bit of $HOME corruption as well) to track > down a semi-reliable way to reproduce the bug. > > It does not always trigger a kernel panic, but iwi will always die with > "iwi0: Firmware Error" and usually, attempting to restart netif will cause > the panic. Even restarting netif will not bring the system back. > > I've got a urtw0 usb dongle that I can sometimes get to work after the iwi0 > goes belly up, but not always.... (and for the record, I had tons of > trouble with urtw0 back in 9-current, and it was -never- made stable for > me...) > > With that said, however, iwi0 seems to be perfectly stable under OpenBSD > and various Linux distros, which makes me wonder if A) do we need a > different firmware version? or B) is there a problem with our > implementation of the driver? > > I'm happy to provide as much more information as I can (I'm currently not > running FreeBSD on this machine, but that is easily, and quickly remedied > if anyone wants to attempt a fix with me) > > Thanks, > Chuck Burns > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 21:13:52 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B9087841; Thu, 21 Aug 2014 21:13:52 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C4EA382D; Thu, 21 Aug 2014 21:13:52 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id h3so237761igd.3 for ; Thu, 21 Aug 2014 14:13: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:date:message-id:subject:from:to :content-type; bh=JizofC+tXfN41s2ij4vXvxltHoma/7P/qfVQ7rwO2zI=; b=AJRCaYbwRudKJut4y5QdwYLMJY39pesZ88WD6huaewRDP//ofynIinpEcKkybOewcQ 2/mRSib1Rk60F6TRjiqsetwIrmQMGw492Tb8Shx+QbjaK/C1xoGUbd19IRaf5cBK4JwY mLVGnSosCVubZAPTSAjG0qf/a8CwG0zeKQGWN0pnt/IQOv6Nh1eCgxMbynew1wuOnFzd bz5ACIqLmO4HV0Wn1Hd0ObZwYLtGwTIq2/U9R0dClAOorEQuuuTeUIgkf7e3tYy5IzMF I3UiB3n8mP05fy+YVhEnPMn7TIjNl+4CrC4Q3vmH+yiWv8t5kdrFk4F/GDsSHB3v2YYm 3ioQ== MIME-Version: 1.0 X-Received: by 10.42.107.145 with SMTP id d17mr5625566icp.61.1408655631822; Thu, 21 Aug 2014 14:13:51 -0700 (PDT) Received: by 10.107.153.208 with HTTP; Thu, 21 Aug 2014 14:13:51 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 17:13:51 -0400 Message-ID: Subject: Re: How do I ALTQ hostap interface? From: Peter Lai To: freebsd-wireless@freebsd.org, Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 21:13:52 -0000 Looking on the freebsd-net list it seems like a "we don't know how to hack altq to work with multiqueues" problem, but supposedly it's been solved with em(4) (since it works fine with altq) , (but not necessarily with igb)? OpenBSD is of course no longer useful here since they have removed ALTQ. Perhaps it's time to revisit Dummynet/IPFW for shaping (it was just nice having an easily unified NAT and shaping ruleset). On Thu, Aug 21, 2014 at 1:43 PM, Adrian Chadd wrote: > I've no idea. > > Sorry, I've kept asking those who are interested in altq to figure out > how to do it for drivers with if_transmit() and so far it's been > crickets/silence. > > > > -a > > > On 21 August 2014 08:53, Peter Lai wrote: >> Does 9-STABLE support ath(4) and ALTQ? >> >> thanks >> >> On Thu, Aug 21, 2014 at 10:38 AM, Adrian Chadd wrote: >>> Hi, >>> >>> ath(4) now uses if_transmit() and thus there's no ALTQ support at the >>> moment. Sorry. >>> >>> >>> -a >>> >>> >>> On 21 August 2014 02:43, Peter Lai wrote: >>>> How do I ALTQ my wireless (hostap mode) interface in 10.0-R? If I try >>>> to add a queue to wlan0, pf complains that wlan0 has no ALTQ support >>>> (even though it is an ath(4) interface and ath(4) is supposed to be >>>> supported by ALTQ). ALTQ is already setup and working with my wired >>>> ethernet over em(4). >>>> >>>> Am I supposed to specify ath0 as the interface for the pf queue? >>>> >>>> What if I want to bridge my wireless and wired networks? I thought the >>>> bridge would consist of em0 and wlan0 members, and pf will not like >>>> that (claiming that bridge0 has no ALTQ driver...but I don't know if >>>> that is pf reacting to if_bridge(4) itself not having altq support or >>>> the wlan0 member of it... >>>> _______________________________________________ >>>> freebsd-wireless@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 22:37:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1BBE371A for ; Thu, 21 Aug 2014 22:37:10 +0000 (UTC) Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE4093F9E for ; Thu, 21 Aug 2014 22:37:09 +0000 (UTC) Received: by mail-qc0-f171.google.com with SMTP id r5so9962286qcx.16 for ; Thu, 21 Aug 2014 15:37: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:message-id:subject :from:to:cc:content-type; bh=7C4BaKYPYjNJGaCTl/0IeKddXGdjSAKBZVP9AaiH8Jo=; b=reh3jpL77jpf4Ufl3gcQ8d2g9gW9R0t9IwURx47Pm7UveNr5C5h3mgaaaJPI11DgU7 D9jCbECqjiTRReIxpXi5qQal1gL/XnSsklbcBRVYyemciBW4wBDnERgoBKXKO9STS+Rf L7kQSiNUxfnnaS8SqTAOc+ocdXedAbUwnBoPA0FRQQ91rjU9QAY2HF7S5BZSYP5VuCk4 06USUDfT4wNMRlyZP0oPnvF8iPp4fMlT6/0XUa3iiShCO0ykEdDGs3bJkQ9UKHRoxXuf zcaOk9WttN0oDhu8aZtJyUSnRZcq6aaQX7QrlSInOURB70hJkknO6j9ee7cWwMSDV8k+ AiWg== MIME-Version: 1.0 X-Received: by 10.140.19.201 with SMTP id 67mr2492836qgh.28.1408660629061; Thu, 21 Aug 2014 15:37:09 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Thu, 21 Aug 2014 15:37:09 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 15:37:09 -0700 X-Google-Sender-Auth: plDyDILIzaM2DksJAHjtj6xjguI Message-ID: Subject: Re: How do I ALTQ hostap interface? From: Adrian Chadd To: Peter Lai Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Aug 2014 22:37:10 -0000 On 21 August 2014 14:13, Peter Lai wrote: > Looking on the freebsd-net list it seems like a "we don't know how to > hack altq to work with multiqueues" problem, but supposedly it's been > solved with em(4) (since it works fine with altq) , (but not > necessarily with igb)? It's a solvable problem. It's just not solvable with the kinds of hacks that stuck ALTQ in there the way it is in the first place. For em, igb, etc they solved it by having a legacy "hey implement the old network transmit interface" thing stick around. -a From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 22 15:40:27 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B7DB1EB for ; Fri, 22 Aug 2014 15:40:27 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F7D130FA for ; Fri, 22 Aug 2014 15:40:27 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id h3so1339191igd.5 for ; Fri, 22 Aug 2014 08:40:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=kSq7FxV+v555lN1tcq90nlSu0TeF4LOqEJ+iTBmG8KA=; b=jWgpPomJI38oxDbZmOWK8lwgxLn77ahq58kdPX3FAJxgk9DM8tRLgfwyaBfT5NBVEv yM/VGmVWL1pz44xcDoQ6Uc0DwFC2JEtt8lD2Wm9AL9Dofa73RSXZaEapnjb0eddHpPv+ /CSVJi/8U0TNyv/InupG9uR7eRQoub7uPbGfuAPccd9DpQukCndFtT90m12On2hXg/cd Cg8lIFiOFKXj4ZY5OG6HHYVIhRtFHG2FbGBo3AiIc/LE5M+ka/NDrVA6y/XHgfqtADTO m66MobRAiYuY8f4uj26ewfhZwFswSoFrzM1E/sNFckaNbLkNmzernBj2QXq11Rg5SYP2 ITJg== MIME-Version: 1.0 X-Received: by 10.43.107.133 with SMTP id dy5mr10250721icc.14.1408722026710; Fri, 22 Aug 2014 08:40:26 -0700 (PDT) Received: by 10.107.153.208 with HTTP; Fri, 22 Aug 2014 08:40:26 -0700 (PDT) Date: Fri, 22 Aug 2014 11:40:26 -0400 Message-ID: Subject: enabling HT mode on ath 938x and WPA question From: Peter Lai To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Aug 2014 15:40:27 -0000 What is the correct way to invoke HT (ng) mode on 938x cards? I have a TP LINK WDN4800, and it seems to require 2 invocations of ifconfig mode 11g to put it into ng mode. The first invocation sets it to 11g then the second one turns on 11ng/HT40+ (according to the output of ifconfig). It seems that when the card is first initialized/booted it randomly picks a band. Is there a way in rc.conf to specify this behavior? Also, when I am using hostapd, my wireless clients see the BSSID as WPA-enabled whereas yonder generic routers (linksys, 2wire, etc.) show up as WPA/WPA2 (but I only tested this with Android clients). My hostapd.conf: interface=wlan0 debug=2 #doesn't seem to do anything, how do I turn on logging to /var/log/messages ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=myssid wpa=1 wpa_passphrase=mysekret wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 22 17:45:25 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99B2220B for ; Fri, 22 Aug 2014 17:45:25 +0000 (UTC) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B1533FD5 for ; Fri, 22 Aug 2014 17:45:25 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id m20so10989742qcx.24 for ; Fri, 22 Aug 2014 10:45:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ZvFH7cWRCRDcPy0jya70y3KlHWSAfhjIU84vhAJ7/Fk=; b=XKGvRK0vhciDfDc2qzMOv47lR83OJx6bDMiPT5GRcmJ0ZV7ZkqPDraLngHh1xtPBzC EbVWLtz6BCWAxxLlEF/qW8zafSo85BtX8EcfLnzByiuHG1leE3OfyXUX+HHXDshPaXHV DbbWMoKu91catmxOy6iAuJnPd572C+tqpUQ0gWlcVhhAf4Y/4QWI53mGm0fPXhYH2PYl gzJYaGy4XSFZ+v3la7OokX4S0FkWiaY+P0LrC1SN+khQmLrZSLkjFVFwHClQ0yWA3R01 R6X1WBBdtlnySPEkAyjeDtWpmHvYB0uaG6z4SEq8MeWIneeDm5zgW//bP7j3h3n0zYri fU2g== MIME-Version: 1.0 X-Received: by 10.224.36.4 with SMTP id r4mr6157544qad.69.1408729524400; Fri, 22 Aug 2014 10:45:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Fri, 22 Aug 2014 10:45:24 -0700 (PDT) In-Reply-To: References: Date: Fri, 22 Aug 2014 10:45:24 -0700 X-Google-Sender-Auth: WYGYfRpuO-CltQtHfVEZDT5FRxI Message-ID: Subject: Re: enabling HT mode on ath 938x and WPA question From: Adrian Chadd To: Peter Lai Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Aug 2014 17:45:25 -0000 Hi, I'm confused. It should just default to 11n. Are you actually setting a channel when you create the VAP, or are you leaving it blank so it picks a channel? -a On 22 August 2014 08:40, Peter Lai wrote: > What is the correct way to invoke HT (ng) mode on 938x cards? I have a > TP LINK WDN4800, and it seems to require 2 invocations of ifconfig > mode 11g to put it into ng mode. The first invocation sets it to 11g > then the second one turns on 11ng/HT40+ (according to the output of > ifconfig). It seems that when the card is first initialized/booted it > randomly picks a band. > > Is there a way in rc.conf to specify this behavior? > > Also, when I am using hostapd, my wireless clients see the BSSID as > WPA-enabled whereas yonder generic routers (linksys, 2wire, etc.) show > up as WPA/WPA2 (but I only tested this with Android clients). > > My hostapd.conf: > interface=wlan0 > debug=2 > #doesn't seem to do anything, how do I turn on logging to /var/log/messages > ctrl_interface=/var/run/hostapd > ctrl_interface_group=wheel > ssid=myssid > wpa=1 > wpa_passphrase=mysekret > wpa_key_mgmt=WPA-PSK > wpa_pairwise=CCMP > _______________________________________________ > 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 23 10:34:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DF0D3444 for ; Sat, 23 Aug 2014 10:34:29 +0000 (UTC) Received: from wilson.telenet-ops.be (wilson.telenet-ops.be [195.130.132.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7C46C3691 for ; Sat, 23 Aug 2014 10:34:28 +0000 (UTC) Received: from andre.telenet-ops.be (andre.telenet-ops.be [195.130.132.53]) by wilson.telenet-ops.be (Postfix) with ESMTP id 3889E3481E4 for ; Sat, 23 Aug 2014 12:22:40 +0200 (CEST) Received: from [192.168.0.95] ([141.134.88.3]) by andre.telenet-ops.be with bizsmtp id iANY1o00X04KsaM01ANYcp; Sat, 23 Aug 2014 12:22:32 +0200 Message-ID: <53F86B75.8030702@telenet.be> Date: Sat, 23 Aug 2014 12:22:45 +0200 From: Chris Van Steenlandt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: WPI (Intel wireless 3945ABG) strange behaviour Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 10:34:30 -0000 Hello everyone, I'm doing my first FreeBSD install (10.0) on an old laptop with an Intel 3945 interface. During the install I already noticed strange behaviour since the installer gave me a "DHCP lease failed". The second time it passed. FWIW, I installed with root on ZFS and the laptop has 1GB of internal memory. When I then rebooted I noticed my wireless did not connect to the SSID via wpa authentication. My wifi kept on scanning on other ssid's except the one I wanted. After reading quite some man pages, I finally have my laptop set up as follows : /etc/rc.conf : ifconfig_wlan0 =" ssid myssid" ifconfig_wlan0 ="mode 11g" ifconfig_wlan0 ="-bgscan" ifconfig_wlan0 = "WPA DHCP" and my /etc/wpa_supplicant.conf showed : network={ ssid="mysid" psk="mysecrepassword" priority=5 } When I boot, my wifi connects correct the first time but after a minute or so, I loose connection again. What is strange, is that ifconfig still tells me that wlan0 is associated ot the correct ssid ... I also regularly get the message : 'dhclient[1005] : send_packet : No buffer space available" (and "wpi0 : need mulitcast update callback" but I know this one can't hurt) Chris From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 12:38:41 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4144AEBD for ; Sat, 23 Aug 2014 12:38:41 +0000 (UTC) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C47153051 for ; Sat, 23 Aug 2014 12:38:39 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBEAB0.dip0.t-ipconnect.de [217.251.234.176]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id s7NCaPUq044753; Sat, 23 Aug 2014 12:36:25 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id s7NCcQRZ032713; Sat, 23 Aug 2014 14:38:26 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id s7NCc8ME057766; Sat, 23 Aug 2014 14:38:20 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201408231238.s7NCc8ME057766@fire.js.berklix.net> To: Chris Van Steenlandt Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sat, 23 Aug 2014 12:22:45 +0200." <53F86B75.8030702@telenet.be> Date: Sat, 23 Aug 2014 14:38:07 +0200 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 12:38:41 -0000 Hi Chris cc wireless@ > After reading quite some man pages, I finally have my laptop set up as > follows : > /etc/rc.conf : > ifconfig_wlan0 =" ssid myssid" > ifconfig_wlan0 ="mode 11g" > ifconfig_wlan0 ="-bgscan" > ifconfig_wlan0 = "WPA DHCP" ( I prefer wired nets & only fumble with wireless when I must, but ) The above has multiple Bourne shell syntax errors. > ifconfig_wlan0 =" ssid myssid" ................^..^ delete spaces > ifconfig_wlan0 ="mode 11g" ................^ delete space > ifconfig_wlan0 ="-bgscan" ................^ delete space > ifconfig_wlan0 = "WPA DHCP" ................^.^ delete spaces a test live with with /bin/sh: ifconfig_wlan0="ssid myssid" ifconfig_wlan0="mode 11g" ifconfig_wlan0="-bgscan" ifconfig_wlan0="WPA DHCP" echo $ifconfig_wlan0 & see 3 previous assertions overwritten by the fourth. So try either ifconfig_wlan0="ssid myssid" ifconfig_wlan0="$ifconfig_wlan0 mode 11g" ifconfig_wlan0="$ifconfig_wlan0 -bgscan" ifconfig_wlan0="$ifconfig_wlan0 WPA DHCP" or ifconfig_wlan0="ssid myssid mode 11g -bgscan WPA DHCP" Cheers, Julian -- Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com Interleave replies Below, like a play script. From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 19:19:43 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4A2DF5; Sat, 23 Aug 2014 19:19:43 +0000 (UTC) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2F89343B; Sat, 23 Aug 2014 19:19:42 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id s7so10747128lbd.14 for ; Sat, 23 Aug 2014 12:19:40 -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=jMw5O86vz0h9NaFbGZdq8w90SmSEUtiypdR0W1O/Jlg=; b=CVjtUV7/uFUYL9HvORUqcwTwop/jEMiDQEIMTNqPFJ+Cfg7Q84KhO2YKycRsDCjlXs 4hN6bygx9o619vtaHYQp7FiZ9JLhH5+V/IVg7uoERxKroluB52j39Fb/GGUbLcC90zPo yKMY2eM7DcWF6GlztBO9VZHuHIT936W4S6hgFeBKY4IkTffWpHMZN561FOiU6i6JuHJo Qi7PpjO1rOJ7tHvR0o1ewzlJj0ia0HBuI+hsfH3Rr17b1dbQn7WYLJp4RpjlCoieNUAo ImA8fBOcY4O4EUrHwUFD8VieYQcVj+yCvj3FSbpGbwOyR/ygoqA11X9E3F/hNBiN+3R6 CJUw== MIME-Version: 1.0 X-Received: by 10.153.4.39 with SMTP id cb7mr11422734lad.19.1408821580683; Sat, 23 Aug 2014 12:19:40 -0700 (PDT) Received: by 10.114.29.200 with HTTP; Sat, 23 Aug 2014 12:19:40 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Aug 2014 21:19:40 +0200 Message-ID: Subject: Re: iwn: Intel Centrino 6205 bad 11n performance From: Johannes Dieterich To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 19:19:43 -0000 Dear Adrian thanks a lot for the suggestion! Removing ht indeed improves the throughput to 1.7 MB/s. Still far from the maximum of my uplink but sufficient for the time being and much improved. Concerning the non-existing maintainer: does it in this case even make sense to file a PR? Given how common the Intel WLAN NICs (unfortunately) are and how some notebooks have white lists making a change to e.g. ath impossible, it is a real bummer that nobody maintains it. Thanks for your work on ath, btw, those NICs are working great nowadays! Thanks again for the help! Johannes On Wed, Aug 20, 2014 at 12:30 AM, Adrian Chadd wrote: > Hi, > > You can try disabling 11n (ifconfig -ht) but besides that, there's no > real iwn maintainer or anyone who wants to get really nitty gritty > into what the driver is doing. So until that happens, I think we're > short of luck. :( > > > -a > > > On 19 August 2014 12:53, Johannes Dieterich > wrote: > > Dear all, > > > > I have a Intel Centrino Advanced-N 6205 WLAN NIC in my Thinkpad using > iwn. > > > > iwn0@pci0:3:0:0: class=0x028000 card=0x13118086 chip=0x00858086 > rev=0x34 > > hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'Centrino Advanced-N 6205 [Taylor Peak]' > > class = network > > > > Unfortunately, I only get a rather bad speed using CURRENT (r270098) out > of > > the chip. It is connected to an 11n (on the 2.4 GHz band) network: > > > > wlan0: flags=8843 metric 0 mtu > 1500 > > nd6 options=29 > > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > > status: associated > > ssid XXXXX channel 4 (2427 MHz 11g ht/20) bssid XXXXXXXXXX > > country US authmode WPA2/802.11i privacy ON deftxkey UNDEF > > TKIP 2:128-bit txpower 15 bmiss 10 scanvalid 60 bgscan bgscanintvl > 300 > > bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 64k > > ampdudensity 8 -amsdutx amsdurx shortgi wme roaming MANUAL > > > > I get a maximum of 900 KB/s of throughput (both in/out, approximated by > > copying a large file using scp), within the network and to the outside > > world. Running SuSE Linux on the notebook allows me to easily saturate my > > uplink at > 3MB/s, didn't then further check within the network. I get no > > log messages on FBSD from iwn and I am not located in a particularly > noisy > > neighborhood. > > > > The only performance issue I can find with this chip is one old report on > > Ubuntu (http://ubuntuforums.org/showthread.php?t=1949571), where the 11n > > seemed to be the culprit in the driver/firmware. Could this be an issue > for > > us as well (firmware problem?)? > > > > As my workhorse is FreeBSD, I'd love to fix this issue. How can I further > > debug this issue and/or provide more data? I know that the status of iwn > in > > FBSD is difficult ATM but maybe there is hope? > > > > Best > > > > Johannes > > _______________________________________________ > > 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 23 19:23:48 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EAD8433B for ; Sat, 23 Aug 2014 19:23:48 +0000 (UTC) Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9E213501 for ; Sat, 23 Aug 2014 19:23:48 +0000 (UTC) Received: by mail-qg0-f44.google.com with SMTP id e89so11619090qgf.17 for ; Sat, 23 Aug 2014 12:23:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zD1eERdg7gFutZwm2YYE/a2hpx2x7hl1EGzcYp1AD3A=; b=nyqBcRwCq82UOHvVvmplyVepQH4Yf2hQBOL4zhHGFYIyDy9mxaVoMI9MAmfURQOXAW S/7R6C6daoc3IA8ftWVjx2ZuRwCfXchO4kCaCZTyhY/aYWjw4EBYzZbd4lOLhFFa07Ac Rk4ghkl99XA2cTVMlbARQR2TwXegEAFw/uaurep/+vQn4abSVQvRw7HJBTEGmQ9sZ1VL 3BXEvZlSupDal7YerosD8Cip70hlz7GJO2CH684L77KrUSKUtWj/k2aUBHIFqDpwStPQ cU1zaEiOMAidDgqYsjcPlzwm/HPkl8ECEjoH2Y+s+UlaSOnGmE4VGvgW+0yCbNhe1MN/ F0oQ== MIME-Version: 1.0 X-Received: by 10.224.86.5 with SMTP id q5mr20989824qal.36.1408821827712; Sat, 23 Aug 2014 12:23:47 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sat, 23 Aug 2014 12:23:47 -0700 (PDT) In-Reply-To: References: Date: Sat, 23 Aug 2014 12:23:47 -0700 X-Google-Sender-Auth: QBF-cpjfDtkBHl-TFkxkpNEptX8 Message-ID: Subject: Re: iwn: Intel Centrino 6205 bad 11n performance From: Adrian Chadd To: Johannes Dieterich Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 19:23:49 -0000 Please file a PR. I may end up getting around to it. I don't know whether it's 11n TX or 11n RX, but we should really debug it. -a On 23 August 2014 12:19, Johannes Dieterich wrote: > Dear Adrian > > thanks a lot for the suggestion! Removing ht indeed improves the throughput > to 1.7 MB/s. Still far from the maximum of my uplink but sufficient for the > time being and much improved. > > Concerning the non-existing maintainer: does it in this case even make sense > to file a PR? > > Given how common the Intel WLAN NICs (unfortunately) are and how some > notebooks have white lists making a change to e.g. ath impossible, it is a > real bummer that nobody maintains it. Thanks for your work on ath, btw, > those NICs are working great nowadays! > > Thanks again for the help! > > Johannes > > > On Wed, Aug 20, 2014 at 12:30 AM, Adrian Chadd wrote: >> >> Hi, >> >> You can try disabling 11n (ifconfig -ht) but besides that, there's no >> real iwn maintainer or anyone who wants to get really nitty gritty >> into what the driver is doing. So until that happens, I think we're >> short of luck. :( >> >> >> -a >> >> >> On 19 August 2014 12:53, Johannes Dieterich >> wrote: >> > Dear all, >> > >> > I have a Intel Centrino Advanced-N 6205 WLAN NIC in my Thinkpad using >> > iwn. >> > >> > iwn0@pci0:3:0:0: class=0x028000 card=0x13118086 chip=0x00858086 >> > rev=0x34 >> > hdr=0x00 >> > vendor = 'Intel Corporation' >> > device = 'Centrino Advanced-N 6205 [Taylor Peak]' >> > class = network >> > >> > Unfortunately, I only get a rather bad speed using CURRENT (r270098) out >> > of >> > the chip. It is connected to an 11n (on the 2.4 GHz band) network: >> > >> > wlan0: flags=8843 metric 0 mtu >> > 1500 >> > nd6 options=29 >> > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng >> > status: associated >> > ssid XXXXX channel 4 (2427 MHz 11g ht/20) bssid XXXXXXXXXX >> > country US authmode WPA2/802.11i privacy ON deftxkey UNDEF >> > TKIP 2:128-bit txpower 15 bmiss 10 scanvalid 60 bgscan bgscanintvl >> > 300 >> > bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 64k >> > ampdudensity 8 -amsdutx amsdurx shortgi wme roaming MANUAL >> > >> > I get a maximum of 900 KB/s of throughput (both in/out, approximated by >> > copying a large file using scp), within the network and to the outside >> > world. Running SuSE Linux on the notebook allows me to easily saturate >> > my >> > uplink at > 3MB/s, didn't then further check within the network. I get >> > no >> > log messages on FBSD from iwn and I am not located in a particularly >> > noisy >> > neighborhood. >> > >> > The only performance issue I can find with this chip is one old report >> > on >> > Ubuntu (http://ubuntuforums.org/showthread.php?t=1949571), where the 11n >> > seemed to be the culprit in the driver/firmware. Could this be an issue >> > for >> > us as well (firmware problem?)? >> > >> > As my workhorse is FreeBSD, I'd love to fix this issue. How can I >> > further >> > debug this issue and/or provide more data? I know that the status of iwn >> > in >> > FBSD is difficult ATM but maybe there is hope? >> > >> > Best >> > >> > Johannes >> > _______________________________________________ >> > 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 23 19:31:34 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 370EE839 for ; Sat, 23 Aug 2014 19:31:34 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1D8E53557 for ; Sat, 23 Aug 2014 19:31:34 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7NJVX9g049719 for ; Sat, 23 Aug 2014 19:31:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] New: [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sat, 23 Aug 2014 19:31:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dieterich.joh@gmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 19:31:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 Bug ID: 192950 Summary: [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: dieterich.joh@gmail.com Above mentioned WLAN NIC only manages a maximum upload of 900 kB/s on an 11n network on the 2.4 GHz band in my tests. By recommendation of adrian@, removing ht and falling back to 11g mode improves the upload speed to 1.9 MB/s and download to 2.9 MB/s. Please see the thread on freebsd-wireless at http://lists.freebsd.org/pipermail/freebsd-wireless/2014-August/004907.html for a more detailed description of the problem. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 19:49:26 2014 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D141CEF for ; Sat, 23 Aug 2014 19:49:26 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B7E3536F9 for ; Sat, 23 Aug 2014 19:49:26 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7NJnQ4J082999 for ; Sat, 23 Aug 2014 19:49:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 192950] [iwn] Centrino Advanced-N 6205 slow on 11n, better on 11g Date: Sat, 23 Aug 2014 19:49:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 19:49:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192950 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@freebsd.org --- Comment #1 from Adrian Chadd --- Ok, I'll start adding some more debugging to iwn(4) in HEAD and let you know when I'm ready to debug this. If I forget / move onto something else, here's what I'm going to look at (in order): * RXON config - antennas, MIMO, etc; * TX config - link quality setup, PLCP antenna config; There's other mismatches I've found in the way the antennas are setup and .. well, it's still a mess. Sigh. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 19:50:21 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 450AC118 for ; Sat, 23 Aug 2014 19:50:21 +0000 (UTC) Received: from andre.telenet-ops.be (andre.telenet-ops.be [195.130.132.53]) by mx1.freebsd.org (Postfix) with ESMTP id D770B3704 for ; Sat, 23 Aug 2014 19:50:19 +0000 (UTC) Received: from [192.168.0.95] ([141.134.88.3]) by andre.telenet-ops.be with bizsmtp id iKqH1o00E04KsaM01KqHiD; Sat, 23 Aug 2014 21:50:17 +0200 Message-ID: <53F8F086.1070207@telenet.be> Date: Sat, 23 Aug 2014 21:50:30 +0200 From: Chris Van Steenlandt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: "Julian H. Stacey" Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> In-Reply-To: <201408231238.s7NCc8ME057766@fire.js.berklix.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 19:50:21 -0000 Julian, I was not aware rc.conf was so sensitive to white space ... I even think it shouldn't. Anyhow the blanks were not really there in my rc.conf. I had to retype everything in my mail (since my laptop's network doesn't work :) and I made a few typo's. But what I did do is try to put everything on one line (see last line in your mail) and for some reason my wireless behaves better now. If it still does not work correctly, I will use the DLINK DWA 140 dongle I still have. I already plugged it in and tested it and it seems more stable (based on RALINK chip). Chris On 23-08-14 14:38, Julian H. Stacey wrote: > Hi Chris cc wireless@ > >> After reading quite some man pages, I finally have my laptop set up as >> follows : >> /etc/rc.conf : >> ifconfig_wlan0 =" ssid myssid" >> ifconfig_wlan0 ="mode 11g" >> ifconfig_wlan0 ="-bgscan" >> ifconfig_wlan0 = "WPA DHCP" > ( I prefer wired nets & only fumble with wireless when I must, but ) > The above has multiple Bourne shell syntax errors. > >> ifconfig_wlan0 =" ssid myssid" > ................^..^ delete spaces >> ifconfig_wlan0 ="mode 11g" > ................^ delete space >> ifconfig_wlan0 ="-bgscan" > ................^ delete space >> ifconfig_wlan0 = "WPA DHCP" > ................^.^ delete spaces > > a test live with with /bin/sh: > > ifconfig_wlan0="ssid myssid" > ifconfig_wlan0="mode 11g" > ifconfig_wlan0="-bgscan" > ifconfig_wlan0="WPA DHCP" > echo $ifconfig_wlan0 > > & see 3 previous assertions overwritten by the fourth. So try either > > ifconfig_wlan0="ssid myssid" > ifconfig_wlan0="$ifconfig_wlan0 mode 11g" > ifconfig_wlan0="$ifconfig_wlan0 -bgscan" > ifconfig_wlan0="$ifconfig_wlan0 WPA DHCP" > > or > > ifconfig_wlan0="ssid myssid mode 11g -bgscan WPA DHCP" > > Cheers, > Julian From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 19:53:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EB0433C6 for ; Sat, 23 Aug 2014 19:53:30 +0000 (UTC) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB527379F for ; Sat, 23 Aug 2014 19:53:30 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id j15so11090389qaq.29 for ; Sat, 23 Aug 2014 12:53:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=S4f28wpIIwP7WdsVpso71DNdtm/wF9r9FEb794uAK8E=; b=z64cHOari22VMK5kEulmMiwx8KwwbvbMkVujFJKd0Z4ebtWnx/t1RZpp+GDPoMotgr NSDz1RAIgMJrNSpKg9fe3ogKdB9qMuReDUyDkAIZ5992jq8uMfEpQIBxPWrMK+Vs2p6H BYeHEHBc89bd761eUmn1HtvCYjlrbfLmj3Qz55fzgeX7KeCZMBY/oO6GQ5zj/N9gJipG SA/7RDIUW5DfUEfkfYteXhci+7zOP63t6VxR8+gLHS21WMaxqj0H9HoQ62lSooCXSvjz JAp/JAbqcGiSwu+S30vycKmgd9UErG6gfKbQ7XVwnFPgF6QtNwZ0W4+1whrI443mp1l+ LMqA== MIME-Version: 1.0 X-Received: by 10.229.136.133 with SMTP id r5mr19964960qct.31.1408823609839; Sat, 23 Aug 2014 12:53:29 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sat, 23 Aug 2014 12:53:29 -0700 (PDT) In-Reply-To: <53F8F086.1070207@telenet.be> References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> Date: Sat, 23 Aug 2014 12:53:29 -0700 X-Google-Sender-Auth: rZjWi-eMqYhQ_oudwaf9WEexl1g Message-ID: Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour From: Adrian Chadd To: Chris Van Steenlandt Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 19:53:31 -0000 Hi! It's a shell script config file. You have multiple lines, they're evaluated in order. so effectively what you've put in is: ifconfig_wlan0 = "WPA DHCP" .. now, I suggest you just do that. Ie, you don't need the rest of them anyway at least to get it working. What's in the kernel log? Type 'dmesg', look for messgaes from the wifi driver. -a From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 20:13:46 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B0550ED5 for ; Sat, 23 Aug 2014 20:13:46 +0000 (UTC) Received: from andre.telenet-ops.be (andre.telenet-ops.be [195.130.132.53]) by mx1.freebsd.org (Postfix) with ESMTP id 4C7363978 for ; Sat, 23 Aug 2014 20:13:45 +0000 (UTC) Received: from [192.168.0.95] ([141.134.88.3]) by andre.telenet-ops.be with bizsmtp id iLDk1o00C04KsaM01LDkzL; Sat, 23 Aug 2014 22:13:44 +0200 Message-ID: <53F8F605.80006@telenet.be> Date: Sat, 23 Aug 2014 22:13:57 +0200 From: Chris Van Steenlandt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 20:13:46 -0000 Adrian, now I understand why I have to put everything on one line :) I tried what you suggested (only "WPA DHCP") and that what's the intial install generated too. But in that case my wireless does not connect to my ssid and keeps on scanning all channels and never connects ... That's why I started to add extra parameters untill I got a connection. dmesg gives nothing special with regard to my wifi driver(execpt for the messages I mentioned in my first post). Regards, Chris On 23-08-14 21:53, Adrian Chadd wrote: > Hi! > > It's a shell script config file. You have multiple lines, they're > evaluated in order. > > so effectively what you've put in is: > > ifconfig_wlan0 = "WPA DHCP" > > .. now, I suggest you just do that. Ie, you don't need the rest of > them anyway at least to get it working. > > What's in the kernel log? Type 'dmesg', look for messgaes from the wifi driver. > > > -a From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 20:19:34 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AABC01DC for ; Sat, 23 Aug 2014 20:19:34 +0000 (UTC) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A81339A9 for ; Sat, 23 Aug 2014 20:19:34 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id x13so12237565qcv.40 for ; Sat, 23 Aug 2014 13:19:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xh9IjB8TyBg6Qe5U4jMMa63n3FIltgdUmwSk3HsF5v4=; b=iEKx8Yz7Uiq6DK+n4xxsUNUMurJjg1JRkZVimwGOWBhlEDE2ubP4lDyA1xohGGUpNf babFW8Ofmx8C5hZx3NXMeQo+U7kLPOvkPYKUuATgfUous5U6LSiHETWMK1PueD7RMzJB pHcGccFtRRe6JU5OMB2oTcXIWqu+f6EzAWNikxNwpSwUAyqorwm1+lkPhn8FvivcMSLk HT6D9LLHtYKfZ5fvFAyCXnrxACYJe78Mm8RWu1haqEFzuViXBr9QO5/iZx1zJGAFxsQn wY9nnTr7x6BSKDt9ym+9lAmCkL1HrGpaBrEWKzHUaQMlIyqEStIx/895fb0aGGVhQ5Nf iY6w== MIME-Version: 1.0 X-Received: by 10.140.23.37 with SMTP id 34mr19162593qgo.2.1408825173528; Sat, 23 Aug 2014 13:19:33 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sat, 23 Aug 2014 13:19:33 -0700 (PDT) In-Reply-To: <53F8F605.80006@telenet.be> References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> Date: Sat, 23 Aug 2014 13:19:33 -0700 X-Google-Sender-Auth: 39QnQQ8rXyrtLKl5NBeuza5DFP4 Message-ID: Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour From: Adrian Chadd To: Chris Van Steenlandt Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 20:19:34 -0000 Ok. Just try it manually - * comment out stuff from /etc/rc.conf and reboot * ifconfig wlan0 create wlandev wpi0 -bgscan * wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf & * ifconfig wlan0 list scan - you haven't pasted that here, so we have no idea what APs it is seeing then see. If you compiled in IEEE80211_DEBUG in your kernel config, then 'wlandebug +scan' and see what is spat out to the kernel config. From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 20:59:07 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7EA9A574 for ; Sat, 23 Aug 2014 20:59:07 +0000 (UTC) Received: from wilson.telenet-ops.be (wilson.telenet-ops.be [195.130.132.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1096C3D03 for ; Sat, 23 Aug 2014 20:59:06 +0000 (UTC) Received: from albert.telenet-ops.be (albert.telenet-ops.be [195.130.137.90]) by wilson.telenet-ops.be (Postfix) with ESMTP id 8C86B35375 for ; Sat, 23 Aug 2014 22:59:04 +0200 (CEST) Received: from [192.168.0.95] ([141.134.88.3]) by albert.telenet-ops.be with bizsmtp id iLyx1o00B04KsaM06Lyxdp; Sat, 23 Aug 2014 22:58:58 +0200 Message-ID: <53F9009F.2020603@telenet.be> Date: Sat, 23 Aug 2014 22:59:11 +0200 From: Chris Van Steenlandt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 20:59:07 -0000 Adrian, - ifconfig step (creation of pseudo device) completed successfully - wpa_supplicant gives the following type of output (I can't paste it here, but I'll describe the structure of the output) : 1st message : Initialization successfull Then the following blocks of messages (they alternate or repeat) Block 1 : Trying to associate with (SSID='myssid' freq=5180 Mhz) wlan0 : Authentication with timed out. wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=3 locally_generated=1 ioctl[SIOCS80211, op=20, val=0, arg_len=7] : Can't assign requested adress Block 2 : Trying to associate with (SSID='myssid' freq=2412 Mhz) wlan0 : Associated with wlan0 : WPA: Key negotiation completed with [PTK=CMP GTK=TKIP] wlan0 : CTRL_EVENT_CONNECTED - Connection to completed [id=0 id_str=] Block 2 is sometines followed by : wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=0 and then followed by block 1 For as far as I understand, the driver switches between the 2.4 GHz and 5 Ghz band of my wireless network. Indeed my wifi router is configured to support both bands but apparently my wifi driver can only handle the 2.4Ghz one. On 23-08-14 22:19, Adrian Chadd wrote: > Ok. > > Just try it manually - > > * comment out stuff from /etc/rc.conf and reboot > * ifconfig wlan0 create wlandev wpi0 -bgscan > * wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf & > * ifconfig wlan0 list scan - you haven't pasted that here, so we have > no idea what APs it is seeing > > then see. > > If you compiled in IEEE80211_DEBUG in your kernel config, then > 'wlandebug +scan' and see what is spat out to the kernel config. From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 21:02:29 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FF08601 for ; Sat, 23 Aug 2014 21:02:29 +0000 (UTC) Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DF913D96 for ; Sat, 23 Aug 2014 21:02:28 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id cm18so10789118qab.4 for ; Sat, 23 Aug 2014 14:02:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=kypnNu434xMdjfevzt9fWDrGjZ2BTp5bnC96G9RLtYg=; b=Lrl4U3LGbr5+V+K91V2DJIRHpHwcMBz68qsg2JDzy+iLBtSllj7MqOvVaMVOvWTqS6 eL7Vibsk3jRD8LvTb6jf5AhKSTA66IhzM5pGdH/6NmUeqwZLUTEgMidSm/j4mq4lFWLB ar8AKK7HF6ALnF7OoE1KS3cZHTHbFBj5h/T8T4JmVgHKzodX00YKzgoA1dIoNTOCmdDN XjT5/cXwSnjmQo4OFv7EsAI58ZpQ1gpYGohSyI0MAjq6L+Vm6xV2mX9VRks+dy9FUXPh dQamtnQMbGK9ZH0Kk1ST5pxRPnCbotenwpFxb4SPzcAr5GxuH22pi0XG0Rs2Ay87tlfD domw== MIME-Version: 1.0 X-Received: by 10.224.36.4 with SMTP id r4mr11495194qad.69.1408827748178; Sat, 23 Aug 2014 14:02:28 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sat, 23 Aug 2014 14:02:28 -0700 (PDT) In-Reply-To: <53F9009F.2020603@telenet.be> References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> <53F9009F.2020603@telenet.be> Date: Sat, 23 Aug 2014 14:02:28 -0700 X-Google-Sender-Auth: R5RSDocCkP4Ai1ihygGzZYpdZY8 Message-ID: Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour From: Adrian Chadd To: Chris Van Steenlandt Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 21:02:29 -0000 Yeah, that's the same problem at iwn - the firmware rejects any frames being transmitted to 5ghz passive channels until a beacon is received. It's likely some buffering in net80211 and/or the driver(s) is required. It's not breaking regulatory - the NIC already scanned the channel and heard a beacon. But then the firmware is reset to associate to the channel (rather than scan) and it "loses" knowledge that the channel is fine to transmit on. So net80211 associating with one frame which is instantly rejected by the firmware. Something needs to buffer that and other frames until the firmware sees a beacon - then if it retries the frame(s), it'll successfully be transmitted. I've known about the problem for a while. I've just been too busy / distracted to sit down and fix it. It's not a conceptually difficult thing to fix - someone just has to do it. :P -a On 23 August 2014 13:59, Chris Van Steenlandt wrote: > Adrian, > > - ifconfig step (creation of pseudo device) completed successfully > - wpa_supplicant gives the following type of output (I can't paste it here, > but I'll describe the structure of the output) : > > 1st message : Initialization successfull > > Then the following blocks of messages (they alternate or repeat) > Block 1 : > > Trying to associate with (SSID='myssid' freq=5180 Mhz) > wlan0 : Authentication with timed out. > wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=3 > locally_generated=1 > ioctl[SIOCS80211, op=20, val=0, arg_len=7] : Can't assign requested adress > > Block 2 : > Trying to associate with (SSID='myssid' freq=2412 Mhz) > wlan0 : Associated with > wlan0 : WPA: Key negotiation completed with [PTK=CMP > GTK=TKIP] > wlan0 : CTRL_EVENT_CONNECTED - Connection to completed [id=0 > id_str=] > > > Block 2 is sometines followed by : > wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=0 > and then followed by block 1 > > For as far as I understand, the driver switches between the 2.4 GHz and 5 > Ghz band of my wireless network. Indeed my wifi router is configured to > support both bands but apparently my wifi driver can only handle the 2.4Ghz > one. > > > On 23-08-14 22:19, Adrian Chadd wrote: > > Ok. > > Just try it manually - > > * comment out stuff from /etc/rc.conf and reboot > * ifconfig wlan0 create wlandev wpi0 -bgscan > * wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf & > * ifconfig wlan0 list scan - you haven't pasted that here, so we have > no idea what APs it is seeing > > then see. > > If you compiled in IEEE80211_DEBUG in your kernel config, then > 'wlandebug +scan' and see what is spat out to the kernel config. > > From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 21:18:51 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 79D2BA10 for ; Sat, 23 Aug 2014 21:18:51 +0000 (UTC) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 35D4D3EBF for ; Sat, 23 Aug 2014 21:18:51 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id w7so12372608qcr.32 for ; Sat, 23 Aug 2014 14:18:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=2HBwrTLbzL/hM0RsumXX6OX+kvJsgN8VczZzFjNasjY=; b=nnWB1QI9+Twtq6g+kT3I4+Vpyqr6Od4nBN4QpCYfcrmcswNUDsLdaQg4pSaYW4U3xy NcLxoetUGSPIrgUKRulu8sU+SB8r7jzbIgWCKQ6YXpl1kECKJAlu/FjtWyVroqmRgQIp O/68iAuYBOTAasZBK/gPs6qqZGvo0xgaxTMfYwsiI0VnZ6WVR44wcBagHSfG+g+mFhdb PrO84HUL66I2Urgfl6n7Flj5YaLkTo3e2tlglP/Al8DLdVdBzVsYZn7R0rcaAWszqI9c XrOVHDAEKmsKxYUdh/33fQUEUCntsRxab8P3q+lhOaheIuYCAwWfyINmkk8h9d+3QE+w 5fbA== MIME-Version: 1.0 X-Received: by 10.224.86.5 with SMTP id q5mr21668592qal.36.1408828730240; Sat, 23 Aug 2014 14:18:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sat, 23 Aug 2014 14:18:50 -0700 (PDT) In-Reply-To: References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> <53F9009F.2020603@telenet.be> Date: Sat, 23 Aug 2014 14:18:50 -0700 X-Google-Sender-Auth: p9Oz42xQPy57muec1SlL4tORKt8 Message-ID: Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour From: Adrian Chadd To: Chris Van Steenlandt Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 21:18:51 -0000 (and please file a separate bug for the 5ghz problem with wpi, so I can dump this into the bug.0 thanks! -a On 23 August 2014 14:02, Adrian Chadd wrote: > Yeah, that's the same problem at iwn - the firmware rejects any frames > being transmitted to 5ghz passive channels until a beacon is received. > > It's likely some buffering in net80211 and/or the driver(s) is required. > > It's not breaking regulatory - the NIC already scanned the channel and > heard a beacon. But then the firmware is reset to associate to the > channel (rather than scan) and it "loses" knowledge that the channel > is fine to transmit on. So net80211 associating with one frame which > is instantly rejected by the firmware. Something needs to buffer that > and other frames until the firmware sees a beacon - then if it retries > the frame(s), it'll successfully be transmitted. > > I've known about the problem for a while. I've just been too busy / > distracted to sit down and fix it. It's not a conceptually difficult > thing to fix - someone just has to do it. :P > > > -a > > > > On 23 August 2014 13:59, Chris Van Steenlandt > wrote: >> Adrian, >> >> - ifconfig step (creation of pseudo device) completed successfully >> - wpa_supplicant gives the following type of output (I can't paste it here, >> but I'll describe the structure of the output) : >> >> 1st message : Initialization successfull >> >> Then the following blocks of messages (they alternate or repeat) >> Block 1 : >> >> Trying to associate with (SSID='myssid' freq=5180 Mhz) >> wlan0 : Authentication with timed out. >> wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=3 >> locally_generated=1 >> ioctl[SIOCS80211, op=20, val=0, arg_len=7] : Can't assign requested adress >> >> Block 2 : >> Trying to associate with (SSID='myssid' freq=2412 Mhz) >> wlan0 : Associated with >> wlan0 : WPA: Key negotiation completed with [PTK=CMP >> GTK=TKIP] >> wlan0 : CTRL_EVENT_CONNECTED - Connection to completed [id=0 >> id_str=] >> >> >> Block 2 is sometines followed by : >> wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=0 >> and then followed by block 1 >> >> For as far as I understand, the driver switches between the 2.4 GHz and 5 >> Ghz band of my wireless network. Indeed my wifi router is configured to >> support both bands but apparently my wifi driver can only handle the 2.4Ghz >> one. >> >> >> On 23-08-14 22:19, Adrian Chadd wrote: >> >> Ok. >> >> Just try it manually - >> >> * comment out stuff from /etc/rc.conf and reboot >> * ifconfig wlan0 create wlandev wpi0 -bgscan >> * wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf & >> * ifconfig wlan0 list scan - you haven't pasted that here, so we have >> no idea what APs it is seeing >> >> then see. >> >> If you compiled in IEEE80211_DEBUG in your kernel config, then >> 'wlandebug +scan' and see what is spat out to the kernel config. >> >> From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 21:58:21 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8ABB1633 for ; Sat, 23 Aug 2014 21:58:21 +0000 (UTC) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4663E31EC for ; Sat, 23 Aug 2014 21:58:21 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id j15so10952808qaq.15 for ; Sat, 23 Aug 2014 14:58:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=+ACuQF26yvJHxSgLSK2/P2zu9DDLKWxemjD+rdbHStI=; b=pvdvdH6HxvEhbfHaZnxyTiW3S+Zs+fpKbv/zerORSXWYji9x8r7KDTecxAHRg1trJy qwXAZAaYJZbtkuIC2u27EsOhMtn3Y/vvDUy1qQrI2O+pW8GryGU9tFytGfTcrcYJcDeL kl4DRmBS8QWlekKzLxDaxW1izngOLb80LjTisux4m8Mp7DC7/ZPl/NdTn8fInRygLjoJ Qw1Bm6C6twsmVpgsong2a195PkPL5G9LBY9c8f/3g7gDFYK/nTCIuSAoKMFQc2eC0Zqr b3dL+FpStBcfRe7/mFGiltfxuUXFmLxoXDn2yTg3xaDHAVCmiSuEZ+AZRRCahA0pMdte ZXpg== MIME-Version: 1.0 X-Received: by 10.140.22.19 with SMTP id 19mr15474841qgm.18.1408831100454; Sat, 23 Aug 2014 14:58:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sat, 23 Aug 2014 14:58:20 -0700 (PDT) In-Reply-To: <53F90E0A.3060800@telenet.be> References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> <53F9009F.2020603@telenet.be> <53F90E0A.3060800@telenet.be> Date: Sat, 23 Aug 2014 14:58:20 -0700 X-Google-Sender-Auth: YbRBIxxHfwpuSB7rV8xNutQerGI Message-ID: Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour From: Adrian Chadd To: Chris Van Steenlandt Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 21:58:21 -0000 Hi, Ther'es two separate problems; 5ghz transmit, and your connectivity Oh, the third thing to try after all that manual stuff? dhclient wlan0 Then see if it successfully gets an IP address. -a From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 22:08:03 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ADDC3D5E for ; Sat, 23 Aug 2014 22:08:03 +0000 (UTC) Received: from winston.telenet-ops.be (winston.telenet-ops.be [195.130.137.75]) by mx1.freebsd.org (Postfix) with ESMTP id 303E532C8 for ; Sat, 23 Aug 2014 22:08:02 +0000 (UTC) Received: from michel.telenet-ops.be (michel.telenet-ops.be [195.130.137.88]) by winston.telenet-ops.be (Postfix) with ESMTP id 070371BC418 for ; Sat, 23 Aug 2014 23:56:21 +0200 (CEST) Received: from [192.168.0.95] ([141.134.88.3]) by michel.telenet-ops.be with bizsmtp id iMwD1o00C04KsaM06MwDHy; Sat, 23 Aug 2014 23:56:13 +0200 Message-ID: <53F90E0A.3060800@telenet.be> Date: Sat, 23 Aug 2014 23:56:26 +0200 From: Chris Van Steenlandt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> <53F9009F.2020603@telenet.be> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 22:08:03 -0000 Adrian, I'll file a bug but I do not know if this is only related to the 5ghz band. I reconfigured my NIC and added the parameter "mode 11g" to the ifconfig command. If I'm correct only the 2.4 Ghz band is used then. Even in this scenario my NIC looses connection and then reconnects. Ifconfig shows me my NIC is associated to my ssid and that everything should be ok. However, a ping to another computer on my local network says 'No route to host' ... Regards, Chris On 23-08-14 23:18, Adrian Chadd wrote: > (and please file a separate bug for the 5ghz problem with wpi, so I > can dump this into the bug.0 > > thanks! > > -a > > > On 23 August 2014 14:02, Adrian Chadd wrote: >> Yeah, that's the same problem at iwn - the firmware rejects any frames >> being transmitted to 5ghz passive channels until a beacon is received. >> >> It's likely some buffering in net80211 and/or the driver(s) is required. >> >> It's not breaking regulatory - the NIC already scanned the channel and >> heard a beacon. But then the firmware is reset to associate to the >> channel (rather than scan) and it "loses" knowledge that the channel >> is fine to transmit on. So net80211 associating with one frame which >> is instantly rejected by the firmware. Something needs to buffer that >> and other frames until the firmware sees a beacon - then if it retries >> the frame(s), it'll successfully be transmitted. >> >> I've known about the problem for a while. I've just been too busy / >> distracted to sit down and fix it. It's not a conceptually difficult >> thing to fix - someone just has to do it. :P >> >> >> -a >> >> >> >> On 23 August 2014 13:59, Chris Van Steenlandt >> wrote: >>> Adrian, >>> >>> - ifconfig step (creation of pseudo device) completed successfully >>> - wpa_supplicant gives the following type of output (I can't paste it here, >>> but I'll describe the structure of the output) : >>> >>> 1st message : Initialization successfull >>> >>> Then the following blocks of messages (they alternate or repeat) >>> Block 1 : >>> >>> Trying to associate with (SSID='myssid' freq=5180 Mhz) >>> wlan0 : Authentication with timed out. >>> wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=3 >>> locally_generated=1 >>> ioctl[SIOCS80211, op=20, val=0, arg_len=7] : Can't assign requested adress >>> >>> Block 2 : >>> Trying to associate with (SSID='myssid' freq=2412 Mhz) >>> wlan0 : Associated with >>> wlan0 : WPA: Key negotiation completed with [PTK=CMP >>> GTK=TKIP] >>> wlan0 : CTRL_EVENT_CONNECTED - Connection to completed [id=0 >>> id_str=] >>> >>> >>> Block 2 is sometines followed by : >>> wlan0 : CTRL_EVENT_DISCONNECTED bssid = reason=0 >>> and then followed by block 1 >>> >>> For as far as I understand, the driver switches between the 2.4 GHz and 5 >>> Ghz band of my wireless network. Indeed my wifi router is configured to >>> support both bands but apparently my wifi driver can only handle the 2.4Ghz >>> one. >>> >>> >>> On 23-08-14 22:19, Adrian Chadd wrote: >>> >>> Ok. >>> >>> Just try it manually - >>> >>> * comment out stuff from /etc/rc.conf and reboot >>> * ifconfig wlan0 create wlandev wpi0 -bgscan >>> * wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf & >>> * ifconfig wlan0 list scan - you haven't pasted that here, so we have >>> no idea what APs it is seeing >>> >>> then see. >>> >>> If you compiled in IEEE80211_DEBUG in your kernel config, then >>> 'wlandebug +scan' and see what is spat out to the kernel config. >>> >>> From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 22:15:18 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A78E288 for ; Sat, 23 Aug 2014 22:15:18 +0000 (UTC) Received: from albert.telenet-ops.be (albert.telenet-ops.be [195.130.137.90]) by mx1.freebsd.org (Postfix) with ESMTP id 95B7333A4 for ; Sat, 23 Aug 2014 22:15:16 +0000 (UTC) Received: from [192.168.0.95] ([141.134.88.3]) by albert.telenet-ops.be with bizsmtp id iNFE1o00604KsaM06NFErn; Sun, 24 Aug 2014 00:15:14 +0200 Message-ID: <53F9127F.9090602@telenet.be> Date: Sun, 24 Aug 2014 00:15:27 +0200 From: Chris Van Steenlandt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> <53F9009F.2020603@telenet.be> <53F90E0A.3060800@telenet.be> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 22:15:18 -0000 Indeed, I forgot about dhcp :( If I do that, it works ok. What I did notice after 'dhclient wlan0' is after a while the message : dhclient [2628]: send_packet : No buffer space available Chris On 23-08-14 23:58, Adrian Chadd wrote: > Hi, > > Ther'es two separate problems; 5ghz transmit, and your connectivity > > Oh, the third thing to try after all that manual stuff? > > dhclient wlan0 > > Then see if it successfully gets an IP address. > > > > -a From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 23 22:17:03 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0115E42B for ; Sat, 23 Aug 2014 22:17:02 +0000 (UTC) Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B076333C4 for ; Sat, 23 Aug 2014 22:17:02 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id m5so10968855qaj.21 for ; Sat, 23 Aug 2014 15:17: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:message-id:subject :from:to:cc:content-type; bh=74uVxlwLlIxQVoG8KkXkKtCew3p/dqSkvW3bvd/CPfY=; b=DADu5maF3X6qXaHyKEHQkJdviBQyEf2MT8sETBdm9oIK98B9KbpdO8kqa7c+a9oA3C 2FwpfivdaHNgpiRT4984r8aDOE8tkN1f8HsFcXcjS60T/CITt+gu3r/Ulntz/cMNBI9z 3G5oBh/iXPPNifVZs9W4jfyjee5OUGPdU3fLOicR1D/tfnANxpxC0NMBSUxcieWgu0+C 9qFxcq+b4YTZez0Fh6MiweOSx9+Swx+DjeQvKIKz6QKk77DZMkk10La+2m9Uve13OBYM 7B/JUNoGIh4Bd0XvRDj7TYTApMDe9b0RlcK6Zeyfr9u179wOcTkfpuCeLFLenMqskfCT zibQ== MIME-Version: 1.0 X-Received: by 10.140.23.37 with SMTP id 34mr19737803qgo.2.1408832221731; Sat, 23 Aug 2014 15:17:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Sat, 23 Aug 2014 15:17:01 -0700 (PDT) In-Reply-To: <53F9127F.9090602@telenet.be> References: <201408231238.s7NCc8ME057766@fire.js.berklix.net> <53F8F086.1070207@telenet.be> <53F8F605.80006@telenet.be> <53F9009F.2020603@telenet.be> <53F90E0A.3060800@telenet.be> <53F9127F.9090602@telenet.be> Date: Sat, 23 Aug 2014 15:17:01 -0700 X-Google-Sender-Auth: QcbUeR_njRffkA8996rjKCLwyOw Message-ID: Subject: Re: WPI (Intel wireless 3945ABG) strange behaviour From: Adrian Chadd To: Chris Van Steenlandt Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Aug 2014 22:17:03 -0000 Ok, so when that happens, check dmesg. See if anything is logged. Do an ifconfig -a and paste it here - before and after it fails. i wonder if it's bad OACTIVE flag handling.) -a On 23 August 2014 15:15, Chris Van Steenlandt wrote: > Indeed, > > I forgot about dhcp :( > If I do that, it works ok. What I did notice after 'dhclient wlan0' is after > a while the message : > dhclient [2628]: send_packet : No buffer space available > > Chris > > On 23-08-14 23:58, Adrian Chadd wrote: > > Hi, > > Ther'es two separate problems; 5ghz transmit, and your connectivity > > Oh, the third thing to try after all that manual stuff? > > dhclient wlan0 > > Then see if it successfully gets an IP address. > > > > -a > >