ok guys. Thanks for the feedback and i will search for a professional. Cheers.

Hi folks, I have the same problem now for an PFSense installation on a Lenovo desktop rtl8821ae not being detected on a 2.4.3-RELEASE, how can I install a driver?

My question is, if someone has expirience if that is working. I have no stick right now So nothing to post

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? Greetings

pfSense = 10.0.0.1 – set as a static in interfaces AP = 10.0.0.2 -- set in dhcp on pfsense and static on AP Subnet = 255.255.255.128 or /25

The controller needs to be on an untagged port The AP's need to to be in a trunk with the native vlan the same as the controller, the vlans for the SSIDS 310, 320 & 330 need to be tagged. Here is what my Linksys switch looks like, my untagged vlan is 4093. GE1 Trunk 4093 Admit All Enabled 2T, 3T, 4T, 5T, 6T, 7T, 4093UP GE2 Trunk 4093 Admit All Enabled 2T, 3T, 4T, 7T, 4093UP GE3 Access 4093 Admit All Enabled 4093UP GE8 Trunk 4093 Admit All Enabled 2T, 3T, 4T, 5T, 6T, 7T, 4093UP GE1 >> pfSense GE2 >> AP GE3 >> Controller GE8 >> interlink to other switch You need to carry the vlans across all the interlinks if you want them on an edge port. I'd be tempted to set up an edge port in vlan 310, 320 & 330 as a normal port and check the vlans are being carried correctly, working your way back to the Cisco to check. You could also check the ports are configured correctly by connecting up a laptop to the trunks and filtering on vlan.id that should display ports that are vlan tagged. [image: 1.jpg] [image: 1.jpg_thumb] [image: 2.jpg] [image: 2.jpg_thumb] [image: 3.jpg] [image: 3.jpg_thumb] [image: 4.jpg] [image: 4.jpg_thumb]

Sounds like you are on the right track. https://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSense [image: pfSense+wifi.jpg] [image: pfSense+wifi.jpg_thumb]

Thanks gjaltemba and Chris! 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. Nat

You have Client isolation Enabled in your AP (access point)

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.

Fair enough… If its something that is in a home/lab for a while waiting for the new switch to get here is one thing.  Making compromise after it works and never updating is another ;)

Duh ;)  Not sure where you got the idea that freebsd was choice for wifi… If you need wifi connectivity use external AP or if you need to connect to some wisp or something use their device or get a wifi ethernet bridge, etc.

@WiFivomFranMan: @nazar-pc: 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. ifconfig run0_wlan0 list chan: Channel  1 : 2412  MHz 11g          Channel  11 : 2462  MHz 11g Channel  2 : 2417  MHz 11g          Channel  36 : 5180  MHz 11a Channel  3 : 2422  MHz 11g          Channel  40 : 5200  MHz 11a Channel  4 : 2427  MHz 11g          Channel  44 : 5220  MHz 11a Channel  5 : 2432  MHz 11g          Channel  48 : 5240  MHz 11a Channel  6 : 2437  MHz 11g          Channel 149 : 5745  MHz 11a Channel  7 : 2442  MHz 11g          Channel 153 : 5765  MHz 11a Channel  8 : 2447  MHz 11g          Channel 157 : 5785  MHz 11a Channel  9 : 2452  MHz 11g          Channel 161 : 5805  MHz 11a Channel  10 : 2457  MHz 11g          Channel 165 : 5825* MHz 11a 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.

hmmm looks like this setting is in the GUI too… doh

Turns out that this is a bug in Windows that was introduced by the 1709 feature update. I found a laptop that hadn't been used for a few months, so started installing Windows updates and testing the Wi-Fi disconnect after each update. No issues until the 1709 update is installed. So I am now able to reproduce this on 4 laptops. Is there anything in PFSense that was updated since 2.3.4-Release-p1 that might fix this? I'm wary of updating to 2.4.0 in case it breaks my OpenVPN setup (which took a week to get working on all clients).

Thanks for the information guys. I have just ran around the house sorting it out, I have plugged in an AP that I had laying around, if it improves I will look into getting a better AP. Thanks for the help!

@kcallis: Any pointers would be greatly appreciated! Ask here: http://www.linksysinfo.org/index.php?forums/tomato-firmware.33/ this is not a pfSense problem.

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." Keep your front door security separate from WIFI.