Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Jun 2015 22:57:00 +0300
From:      Zsolt SZASZ <zsolty_szasz@yahoo.com>
To:        Adrian Chadd <adrian@freebsd.org>,  "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Subject:   Re: trouble connecting to wifi
Message-ID:  <5588688C.2070900@yahoo.com>
In-Reply-To: <CAJ-Vmo=eRrv60Oei3gKa2N2gZxFUQ4qfZGt5MjuECTvWHRWg1A@mail.gmail.com>
References:  <716422696.1187863.1434616682661.JavaMail.yahoo@mail.yahoo.com>	<CAJ-Vmon-f5gowp3qxXOba4KoO33bGWSQQ_YE4MiPrLNYbp8R=A@mail.gmail.com>	<55846575.8000501@yahoo.com> <CAJ-Vmo=eRrv60Oei3gKa2N2gZxFUQ4qfZGt5MjuECTvWHRWg1A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <zsolty_szasz@yahoo.com> 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
>>> <freebsd-wireless@freebsd.org> 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
>>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5588688C.2070900>