From owner-freebsd-wireless@freebsd.org Wed Jul 1 15:17:27 2015 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8330F9913C5 for ; Wed, 1 Jul 2015 15:17:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EDC01F76 for ; Wed, 1 Jul 2015 15:17:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iecuq6 with SMTP id uq6so36939453iec.2 for ; Wed, 01 Jul 2015 08:17:26 -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=G1Gb5uiHOChj7MjyKixHQ42FoNKrtyiaFUPaHUTiWUg=; b=IC0loZlvA0nh66X6yoXVCFXEml7cGf4SqjCIFpm71y+x8m+4/VdY2RkRIAS6hdaXfd ZltHPVcrPWstt1cYHs+KZX+drWWYQapMvgSLvVjyP556VkqRJ1L3QOEb7I+rj00rR9xk KUrWNGa9lwcA0R3Lrq1dzk4Kr0K3mZxy4Mi2QXKZJpzZazWZL8rJZRSON8fIo8OahtDY tsz4UrbxAqHE3qUG9XZBrXxL1Em/hQhAgMRqaDwKE4YVzKCho1S0x/asVZuPRXTTRhZ1 A3y3opprBgK87akShUWGahTJTSEcANsaqS3Jyo7Put8Sptf2AiuVMCwmJCtzEF79VYDQ Okhg== MIME-Version: 1.0 X-Received: by 10.107.155.74 with SMTP id d71mr38206128ioe.29.1435763846585; Wed, 01 Jul 2015 08:17:26 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Wed, 1 Jul 2015 08:17:26 -0700 (PDT) In-Reply-To: <559397C4.6000700@yahoo.com> References: <40578426.2258333.1435608895736.JavaMail.yahoo@mail.yahoo.com> <559397C4.6000700@yahoo.com> Date: Wed, 1 Jul 2015 08:17:26 -0700 X-Google-Sender-Auth: 4K2fb8a18qVaU6ww_-Dk7-SvTUg Message-ID: Subject: Re: trouble connecting to wifi From: Adrian Chadd To: Zsolt SZASZ Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 01 Jul 2015 15:17:27 -0000 Let me go and see what the erm, "blessed" way in net80211 is to disable ht40, then we can go from there. (I really should default 2GHz to HT/20..) -adrian On 1 July 2015 at 00:33, Zsolt SZASZ wrote: > Its working stable! > I try to contact the pfsense core team about this option to be added in the > future. > Shall I install 11-Current and continue from there with the testing? > > > On 6/30/2015 12:19 AM, Adrian Chadd wrote: >> >> hi, >> >> you can do that. but I'm surprised there's no way in pfsense to >> explicitly configure the channel as being ht/20 only. >> >> You may find some devices won't let you tune to channel 13. It's all >> very regulatory-y restricted. >> >> >> -a >> >> >> On 29 June 2015 at 13:14, zsolty szasz wrote: >>> >>> I checked all the wireless channels which my adapter supports. >>> >>> #ifconfig -v ath0_wlan0 list channel >>> Channel 1 : 2412 MHz 11b Channel 7 : 2442 MHz >>> 11g >>> Channel 1 : 2412 MHz 11g Channel 7 : 2442 MHz >>> 11g >>> ht/20 >>> Channel 1 : 2412 MHz 11g ht/20 Channel 7 : 2442 MHz 11g >>> ht/40+ >>> Channel 1 : 2412 MHz 11g ht/40+ Channel 7 : 2442 MHz 11g >>> ht/40- >>> Channel 2 : 2417 MHz 11b Channel 8 : 2447 MHz >>> 11b >>> Channel 2 : 2417 MHz 11g Channel 8 : 2447 MHz >>> 11g >>> Channel 2 : 2417 MHz 11g ht/20 Channel 8 : 2447 MHz 11g >>> ht/20 >>> Channel 2 : 2417 MHz 11g ht/40+ Channel 8 : 2447 MHz 11g >>> ht/40- >>> Channel 3 : 2422 MHz 11b Channel 9 : 2452 MHz >>> 11b >>> Channel 3 : 2422 MHz 11g Channel 9 : 2452 MHz >>> 11g >>> Channel 3 : 2422 MHz 11g ht/20 Channel 9 : 2452 MHz 11g >>> ht/20 >>> Channel 3 : 2422 MHz 11g ht/40+ Channel 9 : 2452 MHz 11g >>> ht/40- >>> Channel 4 : 2427 MHz 11b Channel 10 : 2457 MHz >>> 11b >>> Channel 4 : 2427 MHz 11g Channel 10 : 2457 MHz >>> 11g >>> Channel 4 : 2427 MHz 11g ht/20 Channel 10 : 2457 MHz 11g >>> ht/20 >>> Channel 4 : 2427 MHz 11g ht/40+ Channel 10 : 2457 MHz 11g >>> ht/40- >>> Channel 5 : 2432 MHz 11b Channel 11 : 2462 MHz >>> 11b >>> Channel 5 : 2432 MHz 11g Channel 11 : 2462 MHz >>> 11g >>> Channel 5 : 2432 MHz 11g ht/20 Channel 11 : 2462 MHz 11g >>> ht/20 >>> Channel 5 : 2432 MHz 11g ht/40+ Channel 11 : 2462 MHz 11g >>> ht/40- >>> Channel 5 : 2432 MHz 11g ht/40- Channel 12 : 2467 MHz 11b >>> Channel 6 : 2437 MHz 11b Channel 12 : 2467 MHz >>> 11g >>> Channel 6 : 2437 MHz 11g Channel 12 : 2467 MHz >>> 11g >>> ht/20 >>> Channel 6 : 2437 MHz 11g ht/20 Channel 13 : 2472 MHz 11b >>> Channel 6 : 2437 MHz 11g ht/40+ Channel 13 : 2472 MHz 11g >>> Channel 6 : 2437 MHz 11g ht/40- Channel 13 : 2472 MHz 11g >>> ht/20 >>> Channel 7 : 2442 MHz 11b >>> >>> I changed my settings to channel 13 since that is using only ht/20. Is >>> that >>> ok for further testing? >>> >>> #ifconfig >>> ath0_wlan0: flags=8843 metric 0 >>> mtu >>> 1500 >>> ether 30:b5:c2:63:51:77 >>> inet6 fe80::32b5:c2ff:fe63:5177%ath0_wlan0 prefixlen 64 scopeid >>> 0x8 >>> inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 >>> nd6 options=21 >>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng >>> >>> status: running >>> ssid freebsdap channel 13 (2472 MHz 11g ht/20) bssid >>> 30:b5:c2:63:51:77 >>> regdomain ETSI country RO indoor ecm authmode WPA2/802.11i >>> privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 scanvalid >>> 60 >>> protmode OFF ampdulimit 64k ampdudensity 8 shortgi wme burst >>> -apbridge >>> dtimperiod 1 -dfs >>> >>> >>> >>> >>> On Monday, June 29, 2015 12:45 AM, Adrian Chadd >>> wrote: >>> >>> >>> no, you'll have to ask the pfsense people if they provided a UI to set >>> the channel to HT/20 only. >>> >>> >>> -a >>> >>> >>> On 28 June 2015 at 14:37, Zsolt SZASZ wrote: >>>> >>>> with ifconfig ath0_wlan0 -ampdu ? or default? >>>> >>>> >>>> On 6/28/2015 11:41 PM, Adrian Chadd wrote: >>>>> >>>>> Ok, it's doing HT/40 in 11n mode, and you're on channel 3. >>>>> >>>>> Try HT/20. >>>>> >>>>> >>>>> -a >>>>> >>>>> >>>>> On 28 June 2015 at 13:37, Zsolt SZASZ wrote: >>>>>> >>>>>> ifconfig returns this (ifconfig ath0_wlan0 -ampdu is setup): >>>>>> >>>>>> ath0: flags=8843 metric 0 mtu >>>>>> 2290 >>>>>> ether 30:b5:c2:63:51:77 >>>>>> nd6 options=21 >>>>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng >>>>>> >>>>>> status: running >>>>>> >>>>>> ath0_wlan0: flags=8843 metric >>>>>> 0 >>>>>> mtu >>>>>> 1500 >>>>>> ether 30:b5:c2:63:51:77 >>>>>> inet6 fe80::32b5:c2ff:fe63:5177%ath0_wlan0 prefixlen 64 >>>>>> scopeid >>>>>> 0x8 >>>>>> inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 >>>>>> nd6 options=21 >>>>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng >>>>>> >>>>>> status: running >>>>>> ssid freebsdap channel 3 (2422 MHz 11g ht/40+) bssid >>>>>> 30:b5:c2:63:51:77 >>>>>> regdomain ETSI country RO indoor ecm authmode WPA2/802.11i >>>>>> privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit >>>>>> txpower 30 scanvalid 60 protmode OFF -ampdu ampdulimit 64k >>>>>> ampdudensity 8 shortgi wme burst -apbridge dtimperiod 1 -dfs >>>>>> >>>>>> stable 11g is: >>>>>> >>>>>> ath0: flags=8843 metric 0 mtu >>>>>> 2290 >>>>>> ether 30:b5:c2:63:51:77 >>>>>> nd6 options=21 >>>>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >>>>>> >>>>>> status: running >>>>>> >>>>>> ath0_wlan0: flags=8843 metric >>>>>> 0 >>>>>> mtu >>>>>> ether 30:b5:c2:63:51:77 >>>>>> inet6 fe80::32b5:c2ff:fe63:5177%ath0_wlan0 prefixlen 64 >>>>>> scopeid >>>>>> 0x8 >>>>>> inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 >>>>>> nd6 options=21 >>>>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >>>>>> >>>>>> status: running >>>>>> ssid freebsdap channel 3 (2422 MHz 11g) bssid >>>>>> 30:b5:c2:63:51:77 >>>>>> regdomain ETSI country RO indoor ecm authmode WPA2/802.11i >>>>>> privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 30 >>>>>> scanvalid >>>>>> 60 >>>>>> protmode OFF wme burst -apbridge dtimperiod 1 -dfs >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 6/27/2015 8:28 PM, Adrian Chadd wrote: >>>>>>> >>>>>>> ok, so you have to use no-11n in order for it to be tsable, ok. >>>>>>> >>>>>>> when you test, can you just verify that it's always using the same >>>>>>> channel? >>>>>>> >>>>>>> are you using HT/20 or HT/40 when you're in 11n mode? >>>>>>> >>>>>>> >>>>>>> -a >>>>>>> >>>>>>> >>>>>>> On 25 June 2015 at 08:10, zsolty szasz >>>>>>> wrote: >>>>>>>> >>>>>>>> No joy! >>>>>>>> Besides that I had also a lot of these: ath0_wlan0: discard frame >>>>>>>> w/o >>>>>>>> leading ethernet header (len 6 pkt len 6). >>>>>>>> >>>>>>>> One night when WiFi stopped working then I came with my laptop in my >>>>>>>> hand >>>>>>>> to >>>>>>>> sit in front of my router to do the usual ifconfig ath0 down/up but >>>>>>>> before >>>>>>>> doing that I observed that while I was near to the wifi antenna with >>>>>>>> my >>>>>>>> laptop the wifi started to work fine again without doing anything >>>>>>>> (on >>>>>>>> laptop >>>>>>>> the connection went from 15Mbps to 280Mbps automatically). I don't >>>>>>>> know >>>>>>>> it >>>>>>>> this information is usefully to you. Of course this happened only >>>>>>>> one >>>>>>>> time, >>>>>>>> I tried next day the same and it wasn't enough. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Monday, June 22, 2015 11:07 PM, Adrian Chadd >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> That's fine. Ok, try this: >>>>>>>> >>>>>>>> ifconfig ath0_wlan0 -ampdu >>>>>>>> >>>>>>>> .. then reassociate evryone. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -adrian >>>>>>>> >>>>>>>> >>> >