It's probably in the wrong usb composition mode. Some modes only present MBIM or QMI interfaces which pfSense has no driver for. Since there is no way for pfSense so connect to it you would have to change the mode under Windows or maybe Linux.
I used a script to do that on the 7455 I have, linked as option 3 here:
https://github.com/danielewood/sierra-wireless-modems#create-accessible-com-port

Steve

You must explicitly trust a CA for 802.1X.

It is not a web browser.

This is generally done by pushing a policy to the device with a group policy object or similar.

I would not trust a public CA for this purpose or the devices will trust any authentication server with a certificate signed by that CA.

Are you forwarding all DNS requests to Unbound in pfSense or just handing the pfSense interface IP to clients via DHCP?

Steve

For small deployments I like ruckus unleashed. the controller is in the APs. Ubiquiti cloud keys work too with minimal infrastructure needed. What bugs me about ubnt is you have to have a controller for just one AP.

The wireless tab is for wifi hardware in the pfSense box, yes.

It depends what the Fritzbox can do. If you can set that up to use a VLAN directly that traffic will probably pass your unmanaged switch and you can then connect to it using a VLAN interface in pfSense.

You could do something even more unconventional like setup a tunnel of some sort between the Fritzbox and pfSence to separate the traffic that way. A VPN if it can do that or even PPPoE can work.

A managed switch is a better way to do it but it depends how much you want to save money or like playing with network config. 😉

Steve

Mmm, some maybe. A lot are using exactly same drivers OpenWRT uses. Some are just using OpenWRT directly!

The problem I was facing was really about the firewall rule.
I created a new firewall rule for WLAN. I selected "WLAN net" for Source. Of course, I also selected "WLAN" for the interface. I also selected "any" as the protocol.

I made the settings for Captive Portal. From the DHCP Leases page, I have defined an IP address outside the DHCP range to my mobile phone. I added the static IP of my mobile phone on the Allowed IP Addresses tab from the Captive Portal Zone page.

I can connect to wireless internet automatically through Captive Portal.

Thanks for everything!

Definitely use a separate box for server like services such as that.

The best you can manage for wifi in pfSense directly is 3x3 802.11n which will give you a theoretical link speed of 450Mbps.

I have a Sparklan card that works but any similar Atheros chipset based card will likely work.
https://wikidevi.com/wiki/SparkLAN_WPEA-127N

Steve

OpenWRT looks like a decent workaround if the factory firmware is not sufficient. Thank you both for the updates on this.

So the R7500 directly connected to pfSense is in Access Point mode? And the other one is in wifi client mode?

There is just one layer 2 network here, neither R7500 is routing or NATing?

If the second R7500 has a statically mapped dhcp lease is it pulling that from pfSense? Or is it just using a static IP?

Steve

Status > Wireless will show all the connected clients.

Steve

@JKnott Thank you for the answer. As I said earlier, I changed the channel to "2" as you suggested (lower). The problem seems to be solved.

Now (today) I changed "bgn" to "n only". I will pay attention if there will be a better performance.

That^ exactly. 😉

While it's running as a router pfSense will only ever see all traffic from it as one IP.

It looks like those devices have an Access Point mode though so use that. It also looks like they have a guest wifi option that might be usable here.

Depending on the hardware version you might be able to put OpenWRT on them and then you can do pretty much whatever you want.

Steve

Some of those Realtek device should be supported:
https://www.freebsd.org/cgi/man.cgi?query=rtwn_usb&apropos=0&sektion=4&manpath=FreeBSD+12.0-RELEASE&arch=default&format=html

You might find they work OK. You alreadt have them so nothing but time to lose by testing them.

Steve

well if anyone is wondering
etsi 2 -> <!-- ETSI w/o HT40 in 5GHz -->
etsi 3 -> <!-- ETSI minus channel 36 -->
there are probably some place in eu where u can't use HT40 or channel 36
in any case they are commented inside /etc/regdomain.xml

idk but i think you need to enable WPA to use 802.11n and i never used the "outdoor" settings. You probably had the interface up but hostapd is not starting for some misconfiguration, the SSID should not be a problem couse i have something very similar and i don't have any problem with it

Yes, that card should definitely work I use that myself.

Steve

Does it show from the command line in ifconfig -a or pciconf -lv?

Steve

@tman222 said in 802.11ac support:

However, if you want to keep things simple, you can put your WiFi and LAN clients on the same local subnet by using e.g. the router I linked to, turning it into AP, and then enabling the guest network on it for guest clients (which will only have access to the internet but not the local subnet).

Strictly speaking, you can use VLANs with an unmanaged switch, with pfSense and the AP configured to support the VLANs. Other devices on the network will just ignore the VLAN tagged frames. However, for a business installation, a managed switch is always a good idea and the proper way to do this in that environment.

I assume you do see some things listed by pciconf though? On a standard x86 box I expect to see a large number of PCI devices.

You need to check the card works at all in something else.

Then test the slot with another card if you can.

Steve