That Ethernet card will probably work fine.

The wifi card will not work at all. There isn't any 802.11AC support in FreeBSD/pfSense, yet, let alone .AX.
https://docs.netgate.com/pfsense/en/latest/wireless/hardware.html#recommended-wireless-hardware

Steve

Thanks both!

I've set an ASUS Router I had to AP mode and put it behind pfSense. My exact setup looks like this:
Provider Router - pfSense - Switch - AP. QNAP is connected to the switch and I can access it with my mobile phone.

Yeah, same here: https://forum.netgate.com/topic/158771/netgate-3100-and-crypto-accelerator-in-openvpn

-Rico

Yeah most likely... Lets see if he still tries it after we have called him out..

Yeah actually it is all on the same subnet, per I think the easiest way is to disable the wireless traffic on the Unifi's scheduler, thanks for your input.

Generally you do not need to install drivers. Hardware is either already supported or it isn't.

What device do you have?

What do you see in the system logs when you connect it?

What does usbconfig dump_all_desc show?

Steve

Yeah there are probably better supported wifi modules out there, also for the cabled ethernet. But for $35 i cant complain. Linux is probably a good option too as it has a bit better hardware support.

Agree with your assessment.

While true you can take any old soho wifi router and just use its AP features... soho wifi routers, include a routing function, switch ports and a AP in 1 box..

The switch is dumb, and therefor almost always the AP is dumb.. Or atleast configured that way via the native firmware. Other then allowing "guest" ssid that is not bridged to the switch ports.

While the hardware quite often, but not always does support doing vlans. I have never seen the native firmware leverage them for anything other than maybe the "guest" network most of them allow you to create, which really is just not bridged to the switch ports vlan.

Normally they do actual use vlans, this is how they isolate the wan and the lan. But the interface doesn't allow the user to change or manipulate them really in any way.

So simple way to just use them as a dumb AP is just turn off dhcp on them, and connect them to your network via one of the lan ports. Now anything on wifi (not guest ssid) is bridged to your switch ports = AP..

So if you want to actual do vlans, either put 3rd party firmware on the device to expose way to configure the vlans. Or get an actual AP, then yes normally would support vlans..

Finally got a time window over the weekend to reinstall the pfSense. This time, I went through the process as suggested by DAVe3283 and akuma1x. The details are below.

First, on the pfSense, I setup DHCP static addresses for the AP's and the controller PC using their MAC addresses.

Next, prior to shutting down the Untangle Firewall, I factory defaulted all of the AP's from the Unifi Controller software. Once they were all defaulted, I removed power from the AP's and also removed power from the ethernet switch they were connected to. Not sure if removing power was necessary, but, wanted to make sure the AP's would boot up and get a new IP from the pfSense with no issues.

On the controller PC, In the Unifi Controller software, made sure the gateway setting and network settings reflected the new network information: 192.168.14.1 and 192.168.14.x/23. Powered down the Unifi Controller PC.

Shutdown the Untangle Firewall and connected the pfSense Firewall in its place and powered it and the ethernet switch up. Used my laptop to connect to the webUI of pfSense via the ethernet switch. After the pfSense Firewall powered up and I could see that all interfaces were up from my laptop, I powered up the Unifi Controller PC.

The Unifi Controller PC booted up and got its new IP. In the Unifi Controller software, I adopted all the AP's one by one and verified they received the correct IPs and were "Connected". They were consistently connected for over an hour with no further issues as I'd had in the previous install attempt.

Verified client PCs were connecting the the APs and passing traffic successfully.

Started fail-over testing by disconnecting WAN1. Made sure internet traffic was flowing through WAN2 and then back through WAN1 when I reconnected WAN1. It did, and I was impressed at how fast and seamless the transition was!

After a couple of days, everything is still working great. Thanks to all who submitted suggestions - this one is solved!

@prayongssx001 said in wireless disconect .:

Hello, I Prayut
My wireless at home dropped off a lot. I don't know why Open and close several times, it still does not disappear. Thank you for the good answer.

If you're running pfSense 2.4.5-p1 with a wireless card, check freebsd 11.3 hardware compatibility list.
https://www.freebsd.org/releases/11.3R/hardware.html#wlan

My memory from hanging out in these forums is that wifi cards are generally are not going to work great with pfSense. I don't know the technical reasons but if I had to take a guess, a wireless card plugged into a PC running pfSense (freebsd) is generally going to be a card meant for a client PC to connect to a wireless access point. Whereas with pfSense, you're asking this client card to BE the access point for potentially many clients. This card's typical job is to handle a single connection, not ten different connections.

The most common recommendation is to use a dedicated wireless access point connected to pfsense via ethernet. If you have an old wireless router, disable DHCP on it and use the LAN interface on that to connect to pfSense.

Edit: More information,
https://docs.netgate.com/pfsense/en/latest/book/wireless/pfsense-as-an-access-point.html

@Moonbiter said in Multiple vlans for wireless:

I also tried throwing up a guest network, but again there doesn't appear to be a way to pass a tag along to pfsense. It doesn't appear to see it any different than my main SSID.

Pfsense definitely supports VLAN tags. Configure a VLAN interface on pfsense and AP with the same tag. Then, if you have a managed switch between them, you will have to configure it to pass the tagged frames.

Yeah, 'bridge mode' there looks like a WAN setting. 'wireless bridge' is probably wifi as WAN in that context.

You may just need to do it manually. Disable DHCP on the device and connect pfSense to one of it's LAN ports. It should already have LAN and wifi bridged at layer 2 internally.

Steve

@akuma1x said in Pfsense + WAP, IP Address Whitelisting:

Like make it hurt to have to enter that password on new devices... :)

I use 63 random character strings, from www.grc.com, for my passwords. The only exception is for my guest WiFi, which has a simple password. However, anything connected to the guest network is blocked from accessing anything else on my network, including pfSense.

@JND8

As for only one device connecting, that can be configured in the DHCP server. You can create a rule to allow only certain IP addresses to connect to the management. Also, you should have a password on it and you can use a key for ssh.

You should try to define your needs, before trying to come up with a solution.

@JKnott said in Pfsense + External Wireless Access Point, Grayed out SSID:

@JND8 said in Pfsense + External Wireless Access Point, Grayed out SSID:

AP is set to WPA3.

Try WPA2. WPA3 is fairly new and many devices don't support it.

What do you know... WPA3 was the issue :)

Thanks for your help

Yup, looks like dhcpd was borking on it. I have no idea how that would affect only wireless clients though.