Setting for Seperate AP
-
I've been having intermittent problems with my wireless access point on my home network. The AP will work fine for days, then it will seem like the whole TCPIP stack on it will stop working. I will still stay connected to the SSID, but I can communicate with any other devices on the network (including the AP itself) or the Internet. Wired devices continue to work fine. The only fix I can have is to reboot the AP where it'll be fine for a few days till it happens again.
The AP has a static IP outside of my DHCP range. Are there any other settings on my pfSense firewall that I should look into that could help this problem?
-
Sounds like your AP is broken.
If you can communicate with the AP can you log into it and look at things such as associated clients, etc?
-
The AP has a static IP outside of my DHCP range. Are there any other settings on my pfSense firewall that I should look into that could help this problem?
Is this a so called "bridged port" to that WiFi AP? I mean is that one big LAN with WiFi and wired clients?
Did you thought about that it will be perhaps better to set up one LAN with 192.xx.xx. and one WLAN with
172.xx.xx and let the pfSense route between that both networks? At last DHCP and DNS leases must be
cached for storing them and it would be perhaps a nice idea to high up the RAM inside of your pfSense
firewall, or am I wrong with that. -
The AP is an Amped Wireless model APA20, I bought brand new. Running the latest firmware.
I thought the AP was just acting as a wireless bridge to my wired network, DHCP/DNS is being handled by pfSense and the AP just passes that through to the clients.
Last night I tried isolating 802.11B/G/N to the 2.4ghz and 802.11.AC to 5ghz. I noticed that even though all my devices are AC capable, they were connecting to the AP in N mode on 5ghz. Curious to see if that helps at all.
I'm really hoping that this isn't a problem with pfSense at all…
-
Likely not.
-
I guess I just wasn't sure if there were some settings on the firewall that I was missing when having bridges on the network.
-
The AP is an Amped Wireless model APA20, I bought brand new. Running the latest firmware.
Would be even the best if the latest WiFi standards are a so called "must be".
I thought the AP was just acting as a wireless bridge to my wired network, DHCP/DNS is being handled by pfSense and the AP just passes that through to the clients.
In normal, or in common cases when all is running well, this might be not a real problem, but if
there are problems mostly they could not so easy solved out then.Last night I tried isolating 802.11B/G/N to the 2.4ghz and 802.11.AC to 5ghz. I noticed that even though all my devices are AC capable, they were connecting to the AP in N mode on 5ghz. Curious to see if that helps at all.
As told before and a couple lines above this would be the best way to get the newest WiFI standards
in usage inside of the network.I'm really hoping that this isn't a problem with pfSense at all…
No, not really with pfSense.
I guess I just wasn't sure if there were some settings on the firewall that I was missing when having bridges on the network.
That´s easy to answer, if it works you are the lucky one and if not it is often better to go with an external
WiFi AP likes you have done. If this is only for the private usage no worry, but if also for the public usage
you should be activating perhaps the client isolation inside the SSIDs or separate VLANs.Last night I tried isolating 802.11B/G/N to the 2.4ghz and 802.11.AC to 5ghz.
You can also try out to put them in separate VLANs with different SSIDs.
