From owner-freebsd-wireless@FreeBSD.ORG Mon Jun 22 20:02:38 2015 Return-Path: Delivered-To: freebsd-wireless@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A953B43D for ; Mon, 22 Jun 2015 20:02:38 +0000 (UTC) (envelope-from zsolty_szasz@yahoo.com) Received: from nm40-vm4.bullet.mail.bf1.yahoo.com (nm40-vm4.bullet.mail.bf1.yahoo.com [72.30.239.212]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 65C78A73 for ; Mon, 22 Jun 2015 20:02:38 +0000 (UTC) (envelope-from zsolty_szasz@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1435003021; bh=CuRVX3+xQwP4x/8W0+N6oN6ybx9maoUSdq4RWzBJUsA=; h=Date:From:To:Subject:References:In-Reply-To:From:Subject; b=bD/EtR1xOYC7Q/Y8qztjg9ZxzK94VR4RPAHqhYCvQORfsfEDYpnGGUrGjmUm39bhlqKvuUACOrBqQJzsQS5amSxNFzUXYLK62QwguRAvV7xlQ533dJHOJZFe7OXWwl/N1i18EfXRyI4Tpc3b0j9qZn2VPUa9rtahatGS6auB53LnT6xde5eUJCIEnCOn2SyQVwSyXIfB4J8wBOsRhnX32UX0hALQYIONBCKuMsqmPiBWcRHKk/Hbjwxlb/M/nRqk4rJOPLClZl8KiA+n8+9uVr0EzcZ/sHqUF2UEA21wmqdMoAT8E28vIzyxi4LcpA8eLDXeD8TldihSPQhfExB4/g== Received: from [66.196.81.173] by nm40.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2015 19:57:01 -0000 Received: from [98.139.213.8] by tm19.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2015 19:57:01 -0000 Received: from [127.0.0.1] by smtp108.mail.bf1.yahoo.com with NNFMP; 22 Jun 2015 19:57:01 -0000 X-Yahoo-Newman-Id: 397222.92173.bm@smtp108.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 2b_OSWgVM1lFcZoz4xtlwXekB5Bb9lcfmJffPgF88PS5cO7 YvQwJY7PZoB4s.lv.UEtgWtxirDIvEoD.ZR36.fY6Xesdh3Bjp_jj1pZFmZo WggfgfKspr7HcbYdGtXXaDQmbig6F9l2ZzUaSw4QuyM8I4H3qOVf00M2FEu8 8R82MD3w7Ndhep2xQwayT9klEYrIqNgBa2GGzKDYoRtbxU340Sa5szrXiTNs HlEnhr6y.PqRGh9kjVG3ymMcggGuYoTJCpwLN07coqaN7lKKp4nYS17ahiKq nPRuHlpF1aw2Rk540nXn.ufVl6DGY.gh4Kf01tCas7eq1Jc5gb_DrVt09u1k wQrWTz0ILZ6tGtGePiwD11lNiDy5XoT.TtZ_LJ2sHFfQs9DKyR2M9kLNPq27 PBFouE9CpuXfO6n3MZQ7vJGD7wyhJjLy5ucmqpXGT3m.pGauUUVNHWeJkIO3 4IFnWqmH9qmWCyjqTZRjd1VORfROVCMc1Fyx0J4UxrwZWI1IEzFTaNjCy3HI b7aEzq2.SKK2mu0bMYMeuO5vLbNt_bESNJNua4Ag- X-Yahoo-SMTP: 5y9VXDCswBBSOv5OTvOKSRzDQZXeB9iZDw-- Message-ID: <5588688C.2070900@yahoo.com> Date: Mon, 22 Jun 2015 22:57:00 +0300 From: Zsolt SZASZ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd , "freebsd-wireless@freebsd.org" Subject: Re: trouble connecting to wifi References: <716422696.1187863.1434616682661.JavaMail.yahoo@mail.yahoo.com> <55846575.8000501@yahoo.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: Mon, 22 Jun 2015 20:02:38 -0000 Hi, After 2 days of testing with ifconfig ath0_wlan0 -ampdutx I must say that the situation has not improved. The system is running exactly the same way like before which regards the stability. I have a lot of stuck beacon messages as well. When normally WiFi is not working then from my laptop I can see the ssid, I can connect (but it always connect with 15mbps) and disconnect from it but by pinging the router I am not receiving reply. I think the WiFi became unstable after I generate a heavy traffic by my torrent client from my laptop. On 6/20/2015 6:00 PM, Adrian Chadd wrote: > Hi, > > yes - this'll hurt performance, but I'm more interested in whether > disabling ampdutx affects performance/stability. If disabling AMPDU TX > (but leaving AMPDU RX enabled) reduces the instability/stuck beacons > then I have more useful information. > > > -adrian > > > On 19 June 2015 at 14:54, Zsolt SZASZ wrote: >> Hi, >> >> * dev.ath.0.hal.force_full_reset=1 <- its already setup, this is nothing to >> do with the ability to connect with my devices to the wifi, but it helps me >> to have a smoother download - without this I have interruptions (spikes) >> when I download - so its a good thing. >> >> Then I tried: >> # ifconfig ath0_wlan0 -ampdutx but it hurts my download speeds. Without this >> I achieve download speeds like 15-17MB/sec but when this is active I've got >> only 3MB/sec. Also, I don't know if my wifi is stable with this setting on, >> I need more days to check :) >> >> >> >> On 6/18/2015 4:12 PM, Adrian Chadd wrote: >>> On 18 June 2015 at 01:38, zsolty szasz via freebsd-wireless >>> wrote: >>>> Hi, >>>> >>>> I am using pfsense 2.2.2 at home. I have a computer dedicated to be a >>>> home router which contains a PCI slot wireless adapter with Atheros 9227 >>>> chipset. The model of the wireless adapter is TP-Link TL-WN51ND and it has >>>> two antennas. This comply with IEEE 802.11n, and provides wireless speed up >>>> to 300Mbps according to the manufacturer. >>>> This adapter was recognized well by pfsense and I have setup with ease in >>>> "N" using channel 3 - I live in a crowded neighborhood and I saw that nobody >>>> is using channel 3. With this settings the wifi is working fine one or two >>>> days but after that I have to do something like "ifconfig ath0 down | >>>> ifconfig ath0 up" to work again a couple of days more. The issue is that >>>> from my laptop or phones I can see my wifi but I cant connect. I also >>>> receive a lot of "ath0 stuck beacon resetting" messages in pfsense. For a >>>> couple of weeks I changed back to "G" mode to see if its stable and its >>>> working perfectly stable with no ath0 stuck beacon messages at all! >>>> I really would like to use in "N" because of greater download speeds but >>>> I'm lazy to go every time in front of the router and type ifconfig ath0 >>>> down/up every time. So please advise me what can I do, or check or setup. >>>> Kind regards, >>> Hi, >>> >>> So: >>> >>> * Set dev.ath.0.hal.force_full_reset=1 ; see if that helps >>> * Since 11n is not working but 11g does, it may be something to do >>> with using 11n features. 11n is always /configured/ in the NIC. So, >>> try doing this: >>> >>> # ifconfig wlan0 -ampdutx >>> >>> .. to disable AMPDU transmit. See if that makes it behave differently. >>> >>> >>> >>> -adrian >>