Very unstable wifi on TL-WDN4800

chemicstry

Hello, I have set up pfsense as wifi AP with TL-WDN4800 card and I have very dodgy connection.

All computer disconnect randomly, ping goes anywhere between 2ms and 2000ms (even to local address), takes a while to load a page.
On android browser stucks for like 6 seconds and then almost instantly loads the page. Would look like a dns problem, but that would not explain ping and disconnection problems.

Signal strength is good and there aren't much interference (my AP is red):

I tried switching channels and even 5ghz range where I have 0 interference but I got the same problems.

pfSense version:
2.2-RELEASE (amd64)
built on Thu Jan 22 14:03:54 CST 2015
FreeBSD 10.1-RELEASE-p4

My current settings are as follows:
Standard: 802.11ng (smae thing happens with na)
802.11g OFDM Protection Mode: off (tried RTS and CTS)
Transmit power: 99
Channel: 6 (tried various channels and auto)
Antenna settings: all default (I tried changing some of these but it didn't seem to make a difference)
Regulatory settings: FCC, US, Default (also tried ETSI)
Mode: Access Point
SSID: TuRgElIs
Enable WME: true (tried both)
WPA: enabled with key
WPA Mode: WPA2
WPA Key Management Mode: Pre-Shared key
Authentication: Open System Authentication
WPA Pairwise: AES

All other settings are default.

Maybe this will help

Does anyone see what I did wrong here? Or maybe could point me where to start diagnosing such problems.

Also, is it possible to setup dual band wifi on both 2.4 ghz and 5 ghz range with single NIC? My NIC says that it's dual band but I don't know if that means that it can work on both bands simultaneously.

Thank you.

dotdash

First thing to do is to update to 2.2.1- the wireless drivers are more stable.

chemicstry

@dotdash:

First thing to do is to update to 2.2.1- the wireless drivers are more stable.

Just did it and I've got a strange crash after updating and it said something about ath interface so I sent the crash report. I haven't got any more crashes so far but the problem is still there :(

dotdash

Might be worth it to try doing a fresh install and restoring the config.

@chemicstry:

Also, is it possible to setup dual band wifi on both 2.4 ghz and 5 ghz range with single NIC? My NIC says that it's dual band but I don't know if that means that it can work on both bands simultaneously.

The card is dual band in that it can operate at 2.4 or 5Ghz. It doesn't have two radios.

cmb

First, yes, make sure you're on 2.2.1. The crash report could have been from before the upgrade and you just didn't notice it until afterwards (or it could have happened as it was rebooting post-upgrade still on the old kernel potentially).

After upgrading, make sure your wireless config is acceptable by 2.2.1's input validation. Just go to Interfaces>(wireless interface name) and hit Save. If it doesn't kick back any errors you're fine. If it does, fix what it's rejecting so you end up with no errors after saving, then apply changes.

If all that checks out, the only outstanding issue I'm aware of is some kind of problem with power save. It's not universal, and we haven't exactly tracked down the specific cause yet, but it seems to exhibit itself similarly to what you're describing. One device I've found problematic in general is Apple TV. Phones and tablets may cause similar issues, though my iPhone and iPad seem to work just fine.

Derelict

CGATES-E0C84E should move to channel 11.

The only channels available are 1, 6, and 11. It is better to have two stations on 11 than one on 6 and one on 8. That way they can demodulate each others traffic and work together as best as possible. When you overlap like that they just look like noise to each other.

If it were me I'd move to Channel 1 if I can't get that AP moved.

Not that it will fix your issues. Just sayin'.

I also think the further you drift from the Atheros reference design the more problems you have.
Take a look at the HP-WPEA-113N. It is a Atheros AR5BXB92 reference design module and it works well. The best desktop adapter i have found infact.

https://wikidevi.com/wiki/Gemtek_WPEA-113N
Some come with u.fl instead of rp-sma so check your pictures on ebay.

TP-link is not the best choice for wireless adapters in my opinion. Been there and wasted my time.

chemicstry

@cmb:

First, yes, make sure you're on 2.2.1. The crash report could have been from before the upgrade and you just didn't notice it until afterwards (or it could have happened as it was rebooting post-upgrade still on the old kernel potentially).

After upgrading, make sure your wireless config is acceptable by 2.2.1's input validation. Just go to Interfaces>(wireless interface name) and hit Save. If it doesn't kick back any errors you're fine. If it does, fix what it's rejecting so you end up with no errors after saving, then apply changes.

If all that checks out, the only outstanding issue I'm aware of is some kind of problem with power save. It's not universal, and we haven't exactly tracked down the specific cause yet, but it seems to exhibit itself similarly to what you're describing. One device I've found problematic in general is Apple TV. Phones and tablets may cause similar issues, though my iPhone and iPad seem to work just fine.

I did everything you mentioned above and it didn't have any effect. The save didn't give any errors.
Is the power save issue only related to my card? If so, are there any cards that are 100% proven to work with pfsense and could make a decent AP? I'm looking for something in a consumer price range.

@Phishfry:

I also think the further you drift from the Atheros reference design the more problems you have.
Take a look at the HP-WPEA-113N. It is a Atheros AR5BXB92 reference design module and it works well. The best desktop adapter i have found infact.

https://wikidevi.com/wiki/Gemtek_WPEA-113N
Some come with u.fl instead of rp-sma so check your pictures on ebay.

TP-link is not the best choice for wireless adapters in my opinion. Been there and wasted my time.

Have you tested it with pfsense?

Have you tested it with pfsense?

Yes i have –posting with it right now as a matter of fact...