@jimp:

Might be similar to mine:
https://redmine.pfsense.org/issues/4722

maybe, but different chip, the idProduct of my ASUS (idVendor 0b05) USB-N53 is 179d, MAC/BBP RT3572, RF RT3052, firmware RT3071

It works with extra debugging options in the kernel that slow other parts down, but not with our "optimized" kernel. You can read in the redmine entry that it happens on FreeBSD also with a pared-down kernel.

If/when OPNsense removes WITNESS and other debugging from their kernels it will likely start crashing there also until the driver is fixed in FreeBSD.

as is, it has been working fine since the release of FreeBSD-10.0, so for more than one year. No troubles no crashes as wireless AP. As I have never experienced slow performances nor stability issues with FreeBSD I just stay there.

Until I downloaded the source from the ESF portal, I didn't realize that pfSense is not just a configuration GUI like basically OPNSense, but also a partial kernel fork of FreeBSD.

There are multiple versions of these as well for different carriers. There is an ATT version and a Verizon version. The ATT using the MC7700 and the Verizon version using an MC7750 module. The label on the bottom tells all the details. The Wifi module is an option they call X-Card. I was able to swap the module between Verizon version and ATT version. The firmware picks it up automatically.
I was  hoping on crossflashing the firmware&modules between ATT and Verizon versions but that don't work. Circuit Board does has same model number and revision. The Sierra flash rom is a bin file when expanded looks like Linux with uboot file..

The device has a very nice interface and it has the best information about cellular signals and tower data I have ever seen. Very useful in pointing directional antennas.

"Using linux and screen shots take multiple monitors and dont know how to edit them."

What?? Are you using a desktop, console - what flavor of linux what desktop? Gnome, KDE, ?

When it's not detected and available for assignment, it's not supported. Do yourself a favour and get a supported miniPCI card instead or plug an AP into the ethernet port.

Oh I see, thanks for the information. If I don't have any spare PCI, PCI-e, or mPCI-e slots left and USB is out of the picture; would my only option left be an access point?

What AP would be the best in terms of compatibility & security? I have heard Ubiquiti or Xclaim works well?

Is this a wise method? If bus wasn't a limitation, which option would be the best? Thanks.

No,  I never did.  I'm at 2.2.1 now,  but I can upgrade again and try rebooting the switch.  I'm ok testing now that I now I can get it fixed easily.

Thanks,

I have found that the half sized modules don't seem to perform as well as the full length modules. I don't think the radio puts out as much power. My AP clients connection speeds are consistently lower with half sized modules. Not unusable but defiantly noticeable.
I still need to checkout  the Dell/Bigfoot Networks half sized Atheros AR9380 with 3XMIMO-AR5BHB112. It should be best in class…Have just received one, they are costly at 30 bucks used...I am only expecting so much from a half card..

What I said was…

"I can't imagine that an internal card would function as well (range, stability, config options, etc.) as a mid-range access point or router"

That statement doesn't say that it "won't" or "can't" work in the right situation or that it can't be setup to be stable. However, it is completely illogical to argue that an internal wireless card purposed as an access point will EVER function as well as a quality, purpose built wireless access point. In addition, in older versions, I personally experienced situations where changing values in the pfSense GUI caused kernel core dumps - and I was using wireless cards recommended on these forums…

So... say what you want. I'll stand by my statement.

Brilliant, thanks for the replies, guys.

Back to the drawing board for me…

And your right - i got rid of all the bridges and used the firewall. everything works perfectly and less complicated

It ended up being a problem with the wireless card.

@ak:

When I setup the bridge - I found I couldn't do that (assign bridge to the LAN) as the LAN was part of the Bridge. Guess I have to start from scratch and not assign a interface to the LAN at the start.

I think you more likely couldn't make LAN a bridge member because it was assigned to LAN.  Easiest thing is to make the bridge from a completely unrelated interface.

Yes. You need to assign the interface as already noted in my very first reply. (There's really no need to clone it unless you need multiple SSIDs.)

uniquiti

Here are links for the MC7700 DIP mode tools needed in Windows to flash for use in pfSense:

firmware:
http://source.sierrawireless.com/resources/airprime/software/mc7700-att-approved-firmware-swi9200x_03,-d-,05,-d-,20,-d-,03_dip/

watcher 3830:
http://www.sierrawireless.com/developer-zone/resources/airprime/development_kits/airprime-mc-series-connection-manager-dip-build-3830/

drivers 3795
http://www.sierrawireless.com/developer-zone/resources/airprime/software/airprime-mc-series-windows-drivers-dip-build-3795/

pfSense can be used for a great many things.  There are plenty of ways to shoot yourself in the foot.  Doesn't mean the option shouldn't be there.  One person's OPT1 is another person's Multi-WAN, for example.

I ended up going back to seperate SSID's on my test rig. Seems connection speeds dropped back a good bit. So tried to tweak and I found all my wireless devices were using OPT1/BGN and nothing on OPT2/ABGN. So i swapped ABGN to OPT1 and that helped with some. I also went to my Windows device manager and forced wifi to use 5ghz. That worked OK but still slow connection speeds all over. descided to revert back to original setup.
Still nice proof of concept. It does work. If you were using it for a sensor net or something low bandwidth it would work fine.

That all looks fine.

I guess when it stops working you need to look at exactly what's happening.  It's either losing association with the wireless, or something else.  You can look at things like whether or not you still have good ARP from the client on pfSense and from pfSense on the client, etc.