I would, personally, not put the AP on OPT1 but on one of the SG-3100 switch ports so you can put SSIDs on the same broadcast domains as the remaining switch ports if you wish.

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.

Potentially that may be better. The best option is to use an external 3G/4G modem that provides Ethernet such as the Netgear LBxxxx devices.

pfSense may support USB tethering from the Jetpack, it depends how it appears when connected. However it will have issues if that interface is assigned and then disconnected.

Steve

Late reply but…

We can't actually see if it's running in hostap mode from that, it's just off the screenshot on the 'media' line.

The interface settings page would be more useful there. Check the system log for errors.

Steve

Cheers. This was actually very helpful, thanks for taking the time.

@Birke:

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.

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.

1.jpg
1.jpg_thumb
2.jpg
2.jpg_thumb
3.jpg
3.jpg_thumb
4.jpg
4.jpg_thumb

Sounds like you are on the right track.

https://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSense

pfSense+wifi.jpg
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 ;)