From owner-freebsd-wireless@freebsd.org Sun Jun 28 21:45:28 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 4A93798F423 for ; Sun, 28 Jun 2015 21:45:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (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 14E4A1E91 for ; Sun, 28 Jun 2015 21:45:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igblr2 with SMTP id lr2so41858314igb.0 for ; Sun, 28 Jun 2015 14:45: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=5kQ49c7QTvxBvZD1fNr+0KsY6Z7EuIb/20kl77NUb0w=; b=YjNv2v/oZChWXaB4jM2qbJ9al6Qdd1k6LNmnwMLuiDpQGgrRnWzrA93yIL+wEdyGKC v9rgf3afuobrLv3ej7Auu+CbjR8SthIpXSbv6N6vOFFb25LshgQJNALvlVppilkQcdB/ J8OGOvkCRaVKSG10zT1BJ3HvSWku+tP6Z3/QPCm0TKnSnvMSTed83C1yowNB86Z/mutd 5h3DQ2o4Nz2CFNMYLjRVKFMeKsfr2K4dDVcN5GEd4wHD3CQMvtNjlhRsv67Om3hD/cgX x1BZVm5AyKxCcSjEl1TuA3lBUAGEoLeE9TNUur8OAVJtZrEnQMlmaHGPA4056seqrD8/ d3/g== MIME-Version: 1.0 X-Received: by 10.107.11.169 with SMTP id 41mr16327355iol.8.1435527927076; Sun, 28 Jun 2015 14:45:27 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Sun, 28 Jun 2015 14:45:27 -0700 (PDT) In-Reply-To: <559068FF.9080004@yahoo.com> References: <72168917.1307646.1435245008197.JavaMail.yahoo@mail.yahoo.com> <55905B1A.2030803@yahoo.com> <559068FF.9080004@yahoo.com> Date: Sun, 28 Jun 2015 14:45:27 -0700 X-Google-Sender-Auth: ZL5Vy2_aiV9pNJjzk7XysKy3fPQ 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: Sun, 28 Jun 2015 21:45:28 -0000 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 >>>>> >>>>> >