Built this on last  weeks 2.2 beta builds. The Sierra MC7700 supported out of the box now. Good LTE support works with both Tmobile and ATT. I see the newer Sierra Modules are now a funky new slot..NGFF… Why change? To screw you better... How about a low dough 3G version MIFI, i have in the cookbook to try: Total cost around 100 bucks Routerboard RB230 with cardbus AC875U modem.... They are dog slow w/Geode-i586 but at $15 bucks new/ebay with wide input power range(1A max)/poe i am liking them. I got one running Pfsense beta running AP mode with MIKROTIK R52Hn onboard. The GUI is brutal to use -But pfsense routes fine with light use once setup..

My test setup used the wireless to connect to an existing AP, with a traditional natted LAN on the ethernet. I thought that was the OP's desired configuration, but he seems to have wandered off. Mine worked fine until the 'bb hang' error. I only did the test because of another post suggested I shouldn't have tried to help the OP by telling him how it should work if I hadn't tried the configuration myself.

Bump? Anyone any ideas on how or has seen a tut online somewhere? Cheers

Wait.  Now I see it.  It's your NAT rules. You should just leave them at AUTO until you need something specific. Clicked the NAT AUTO then saved, working fine, Thank you.

You can control Ubiquiti UniFi from Windows, Mac, or Linux, but not FreeBSD, unfortunately. http://www.ubnt.com/enterprise/#unifi

https://forum.pfsense.org/index.php?topic=81014.0

Hey there, I think you will faceing a lot of trouble with this. Was looking for the same thing for a kind of acceesspoint virtualization… kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005256 For VMware here they describe that u are able to send traffic to the wireless device and back. But the Host will only recognize a wired connection. So one solution could be, to make all settings for the wireless card on the virtualization server (would mean to configure the server as a Access Point) and bridge all traffic to the host. According to this, you need to do all the hostapd configuration on your own… Really a pain in the a**... So pfsense will not recognize, that you attached an wireless adapter but another wired connection. The same goes for proxmox and KVM. If you have a working solution, I really would appreciate if you could give us a little how to. Edit Found some blogs where people tried to achieve our goal with XEN an PCI Passthrough to HVM's. But therefore you would need hardware supporting VT-d

HI, I didn't understand really well.  ??? Do you mean that you WIFI device is trying to get an IP, but it doesn't get one?

Obviously those Latvians know how to market to us Yankees….Slap a heatsink on it and sold. As a side note i see they just released an 802.11AC version.. R11e-5HacD

Did you end up doing the cable swap version? If you need more help just yell.

You'd be surprised.

I also have the WLE200NX  and am haveing the same issue I did the tuning but still noting.  I am using both antennias

@lsf: Its a wifi option only. It tells the driver that no client should talk to another directly on L2. To op: this functionality is not possible on L2 if you want to seperate the clients. You cant have both. This needs to be changed on a frebsd wireless level. On the top of my head it would require a mac filter list and would make client isolation prone to security issues. In other words a ugly flawed hack. Looks like they can't use their Roku app then. I'm not going to turn it off considering any device can get on the guest wireless.

What types of nics do you have?  If you add a device serviced, say, by the em driver, the operating system might assign the new device as em0 and push your existing devices from em0 and em1 to em1 and em2.  You'll probably need to look at the MAC addresses and use the CLI menu's (1) Assign Interfaces to straighten it out. Before you start, take a backup in Diagnostics->Backup/Restore and worst case you should be able to pull the new card, restore from the backup, and be back where you were.