Wifi performance
-
This is for 3 users the case.
But at the time of testing I was testing it with one user online (me).
Other users were offline.I have tried all 13 channels already.
Giving me the same problems on all 13.I'm using WPA2 personal. Unfortunately it's no option to use Radius as I have a few devices (printer, Squeezebox, etc) that are not capable of using WPA(2) Enterprise.
I don't have a default SSID name, no one else is using it for sure.
The wifi is running in AP mode and the connection is bridged with my LAN so wifi connections are in the same subnet (192.168.10.0/24) as my LAN.When I connect an external wifi ap I do not have such problems.
The main problem I have is that the connection does not stay connected on my iOS devices after you lock the screen.
On other wireless aps I do not have this problem.I recently tried another firewall distro "ZeroShell" which is based on Linux instead of (Free)BSD and with this distro I did not have the problem of disconnecting iOS devices after they are locked/standby for 10 minutes.
-
I recently tried another firewall distro "ZeroShell" which is based on Linux instead of (Free)BSD and with this distro I did not have the problem of disconnecting iOS devices after they are locked/standby for 10 minutes.
This could be for sure as the same as with other Linux based distros, because of the better hardware and driver
support under Linux. ZeroShell is really good but more wide spread in Italy and Spain or Portugal and not
here in Germany where I live. It comes also with a very strong encrypting Rasius Server and is actual
maintained and gets support over a forum or directly from Fulvio. nice appliance but nothing really that
should be compared to pfSense, but with his own charm and skills.For WiFi & pfSense it is only to say about, when is runs smooth it runs, if not it is running not with smooth.
If you need urgent a WLAN AP you could also insert your card inside of an smaller MikroTik with RouterOS
and turn it into a WLAN AP running in AP mode. It will be much better then all other things. -
@Panja, my guess is that the hostapd is using the default inactivity timeout of 5 minutes, and kicking off your device too soon. Other devices typically use 15 or 30 minutes inactivity timeout.
You would probably have to manually edit the /var/etc/hostapd_xxx.conf config file to test this, and your changes would be lost anytime you make a change on pfSense web GUI as it will require the file.
From hostapd defualt config file, we find this:Station inactivity limit
If a station does not send anything in ap_max_inactivity seconds, an
empty data frame is sent to it in order to verify whether it is
still in range. If this frame is not ACKed, the station will be
disassociated and then deauthenticated. This feature is used to
clear station table of old entries when the STAs move out of the
range.
The station can associate again with the AP if it is still in range;
this inactivity poll is just used as a nicer way of verifying
inactivity; i.e., client will not report broken connection because
disassociation frame is not sent immediately without first polling
the STA with a data frame.
default: 300 (i.e., 5 minutes)
#ap_max_inactivity=300
In the end, as others have stated, a DD-WRT device or any other device that is dedicated to wifi (and the requisite code development went into it) will probably work better.
-
@awebster.
Thanks!
Unfortunately in my .conf file there is no "ap_max_inactivity=300" so I cant change it.
But can I add this to my config file?@BlueKobold
Thanks. I won't be running ZeroShell but just tested it because of the wireless drivers.Probably just have to accept that the wireless on (Free)BSD is sh*t. :o
-
Just made up my mind and I will buy an additional wireless access point. :o
-
Probably just have to accept that the wireless on (Free)BSD is sh*t. :o
I wouldn't go that far to call it that.
First: that card you are using utilizes the AR9280 chipset. Which is known to have low level hardware issues if you read the FreeBSD ATH driver maintainer's pages on freebsd.org or out on google. Based on my experience with trying to use that chipset with pfsense for the past few years, I can see why some think that way.
Second: given the limitations of what that ATH maintainer has to do to reverse engineer the HAL for Atheros chipsets, it's amazing what he has been able to do and I give him props for that.
Third: try the newer rev of that chipset series. AR9380. The ATH maintainer's wiki page indicates fewer or no low level hardware issues with the newer chipsets. After I swapped out a bunch of AR9280 over to AR9380 in my pfsense deployments, hostap is now actually usable. Specifically I saw a significant reduction of dropped connections, especially during WPA2 AES rekeys. That's also probably tied in with the last round of ATH driver updates back in 2.2.3 or 2.2.4 I believe.
-
Thanks for the clearing that up!
Did not know that.Cheers
-
Thanks. I won't be running ZeroShell but just tested it because of the wireless drivers.
For sure likes we all do this for testing, I really often use OpenWRT or also ZeroShell for these things.
Probably just have to accept that the wireless on (Free)BSD is sh*t. :o
Perhaps to hard as i see it right. If you got it running smooth and liquid it will be a fine thing
but if it will permanently not running or matching your needs, it sometimes is a really point that
can´t be changed. -
@Panja Change this as a system tuneable
-
@Panja What kind of dbi is your antena? 7, 8 or 10?
https://dongknows.com/wi-fi-dbi-and-high-gain-antennas-explained/
