… second SSID ... different WPA2 password, however I could not put it on a different frequency ... which is super annoying.
I think this is either a hardware limitation with the PCIe card, an OS limitation in BSD, or a driver limitation of sorts.
Technical suggestion: it's a limitation of the admin to understand how WiFi with multiple SSIDs on the same wireless NIC works.
Multi-SSIDs will always be the same channel. It just broadcasts a different SSID simultaneously, which obviously happens on the same frequency/channel.
You have already been told that FreeBSD's support for WiFi is "minimal" at best. Keep that in mind before posting something about limited wireless config options or less than expected WiFi throughput and such.
Best option is to buy a used Ruckus 7372/7982 on eBay for $40 and forget about all WiFi troubles. Even though you don't wanna hear that.
Sorry for the late reply, work has been crazy busy and I just had a chance to try this. Set up the NAT in about 5 minutes and it worked perfectly. Also your explanation made perfect sense why it wasnt working and how NAT will make it work. Thanks for your time!
Seems to work fine but the main installation I am using is pretty small and all devices can pretty much see both APs all the time.
The last WiFi work I did was in a large warehouse a few months ago. There were 6 APs throughout the building. There's no way you'd see the APs at one end of the building, from the other. The place was so large we had to use fibre to connect parts of it. They have Cisco APs and switches.
did you assign only the vlans as interfaces in pfsense or did you assign the re1 itself too?
the unifi-ap uses the settings of the re1-interface for management. means you need to assign an interface to re1 and set up the dhcp for that too. after that you should be able to do a layer3 adoption
This is not necessary in the newest controller. You don't need a native vlan. You can assign management vlan in settings for AP without having to assign a native vlan to it. It takes some planning and basic vlan knowledge to configure.
Hello, I have the same problem. Did you find the answer for this issue? In my case It seems because I am not authenticating, so my phone disconnected every 2 minutes.., But my computer does not have problem If I authenticate or not. Any ideas?
I swapped the routers and found the AP on OPT1 was not working under LAN too. I checked the AP setting where I had configured for static ip, 192.168.50.2 and the gateway as 192.168.50.1 and primary DNS was 192.168.50.1. I thought this could have caused issue and made it as auto IP. To be safe I reset the router.
The two settings, I guess, would have caused the issue are:
1. Primary DNS was 192.168.50.1
2. Wireless Isolation (checked) in the wireless settings.
However the issue is resolved. I appreciate your help. You made me think and try different options.
No luck with the WRT54GL either so lead me to believe it was the set up.
Had both interfaces bridged between the lan port and the one leading to the Access point.
Ended up removing the bridge, setting the Port for the AP to another subnet with its own DHCP server and now I am able to connect with any wireless device when they access the AP.
Made some firewall rules and now everything on wifi can access the lan, and vice versa. Not sure if this was the most efficient way to do this, but it is working without any issues with the Asus RT-n56u. So far.
I've got Trenda W522U bual band Wi-Fi adapter with RT3572 chipset that is capable of 802.11n at 300Mbps (theoretically).
But when configuring access point in pfSense UI I can only select between 802.11b, 802.11g and 802.11a (5GHz).
What should I do to get 802.11n working and why it doesn't work out of the box?
I suspect driver on Linux is similar, since it also shows the same standards in Network Manager GUI.
I am seeing the same thing. No 802.11n :( it has have a ton of problems joining 5GHz 802.11ac or 802.11n networks
I ended up installing Alpine Linux on my router machine, then installed pfSense and LEDE in VMs under KVM and configured some networking.
pfSense controls everything and LEDE is a dumb AP. This way it works fine, I even got 802.11ac mini PCIe adapter that is assigned to LEDE and it works great too.
I'd like to have just pfSense without extra hassle, but it is not possible any time soon.
God I hope not. Pfsense is first and foremost a firewall, and an industrial strength at that and does that job well. It has some routing functionality because well, there could be multi-WAN and multi-LAN to deal with, but now u want to throw WIFI at it, like the rest of the world are selling you these all-in-one boxes, Jack of all Trades and Master of None?
In a robust environment, a box should do a specific job, I would rather have pfSense extend to layer-4, layer-5 processing etc. WIFI to me is really an ancillary function and needs to be deployed, physically, often, away from the "closet."
Trunk would be used to your AP with the management vlan being the native or untagged traffic.. General would allow for more than 1 untagged vlan, while a trunk really has an enforced filter and only allows the 1 single untagged vlan, etc.
General gives you a bit more flexibility for doing odd stuff.. But to unifi AP if all your SSIDs are on vlans with only 1 of them untagged and the same as your management network your using to talk to the AP on then trunk would be correct cisco setting..
Either general or trunk would work as long as you setup the correct tagging for your vlans.
No AP does this - when you move between AP that are using the same SSID.. WDS or not…
You really should get a switch... The interfaces are router interfaces they are not switch interfaces.. While you could bridge them to be in the same vlan.. Its not an optimal sort of setup.. Just get a smart switch connect your AP to it.. Could be something as cheap as a $30 smart switch... Connect your interfaces in from your different networks/vlans from pfsense to the same switch..Now any wireless client be on any network you want it to be on.
okay then the rule of using freebsd hardware documentation isn't valid, as stated here that all freebsd hardware is supported in pfsense:
Hardware Compatibility List
As pfSense is based on FreeBSD, its hardware compatibility list is the same as FreeBSD's. The pfSense kernel includes all FreeBSD drivers.
. I am only wanting to use this as a client, not as an AP. Is there a way to load the driver other than recompiling the kernel? Also, do you plan to add it to pfsense at any point in the future? If not do you have a list of wifi devices supported by pfsense?
If you want help with openwrt - go there… Not going to waste my time sorry, its been over 10 years since used it.. Back when put it on a wrt54g... How to setup eap-tls with freerad on pfsense has been gone over multiple times.. I have posted config I use multiple times.. If you want me to post it again sure..
"I need to ask what are their pros and cons?"
Running you authentication on your AP.. Might be fine if you had 1 AP... After that it doesn't scale at all.. Have you run it on your switch? Its PITA to configure such stuff..
Yes pfsense would be your router/firewall - doesn't matter how you get your clients on the network via wire or wireless.. It would route all your traffic.
"Wifi rules separately into the AP itself?[/"
Your confusing what a AP does with some wifi router device - your stuck in the openwrt mindset where everything is done on the little box... a AP does nothing more than bridge the wifi client to the wired network.. It does not route, it does not filter it does not do anything but bridge the wireless devices to the network..
And there is no integration… pfsense doesn't give 2 shits what your AP does.. Or how it does it... There is ZERO to do with pfsense...
Pfsense doesn't know if wifi client or wired - doesn't know what SSID you connected to, be it 2.4 or 5ghz, etc..
There is ZERO to do on pfsense to get your AP to work... The only thing you would have to know is if your going to use vlan and what the IDs are so you could setup those networks on pfsense.. But that is more on your AP then pfsense.
Pfsense would do the same setting be it wired vlan or wireless vlan, etc.
Yes… Since they are actually an AP with a switch and router function.. Any wifi router as AP is as simple as connect it to your network via one of the lan ports, turn off its dhcpd - there you go AP.. You will prob want to set its lan IP to be on your network your connecting it to so its easier to configure ;)
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.