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.

@monstermania:

Hi,
the stick should be supportes by the urtwn(4) driver.
https://www.freebsd.org/cgi/man.cgi?query=urtwn&sektion=4

But be aware that only 11b/g are supported by FreeBSD.

best regards
Dirk

Hello,
Yes it is supported by the urtwn(4) driver.
I am using V2.1 model

Regards

Capture.PNG
Capture.PNG_thumb

Does that eeebox PC B202 have enough specs to run FreeNAS?
I thought you need lotsa RAM min 8G.

I am interested as I want to setup a Webdav NAS behind my pfsense.

VLANs are supported by Merlin firmware. One of the guides is here.

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:

https://www.pfsense.org/products/#requirements

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..

Find a USB WiFi adaptor that will work with FreeBSD / pfSense or use the LAN port on the XPS.

Try looking on the FreeBSD web site.

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.

"Do all router have the option to be an AP?"

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 ;)

This is getting a bit overblown. Especially as, while we don't always agree 100%, I think you (johnpoz), and Derelict are two of the most helpful people on the board. Yes, I suggested a user contact the reseller- for a hardware issue.
The point I was trying to make, is that a wireless board exists, where people can presumably ask questions about using wireless cards in the actual firewall. Telling them it is not best practice is fine. What I thought was out of line was (and perhaps I was reading too much into it) that a new user was being told that he was not deserving of help because he bought some hardware that a mod did not approve of. I have lots of 'official' hardware, and have in the past told people that they should get some decent hardware (like an adi) when they were running on flaky garbage. The OP had a configuration question. I don't like the implication that if you don't have approved hardware, you are not welcome to ask questions. I don't think Derelict meant that, but his response was not in his usual character. How about I buy the fist round of  Old Man Grumpy Ale http://www.gooseisland.com/our-beers/old-man-grumpy and we can all get back to normally scheduled programming?

Is this AP you going to be using a wifi client itself, ie wireless uplink vs a wire?

AP are only open to this krack is if they are using wireless uplink, ie they are a wifi client themselves.  If your AP is connected to the network with a wire - and not acting as a wifi "client" then it is not open to this problem..

You need to make sure all your wifi clients are patched..

When using a AP, pfsense has zero to do with wireless.  A wireless extender is something that would be open because it has a wireless uplink.. If you are using any of those in your wifi then yes they should be patched.

"Its stopping the users from accessing key systems in timely fashion."

So these key systems on on the internet or your network?

"Override for DNS, from general setup is on."

That doesn't really tell us what the client is using.. Out of the box pfsense would be using unbound - resolver and not forwarding.  Letting your dhcp override what pfsense uses for its dns wouldn't have anything to do with what clients use for dns.  Which normally would be unbound running on pfsense, which would then resolver and not forward.

tmaan222 question number 2 would be of interest for sure. Use your fav dns client nslookup, dig, host, etc.  Try and resolve something www.google.com… After you get a response what was the time?  Do it again you should get it cached answer that should be at most a few ms..