Wondering if my issue is related.  I have an MC7700 and trying to get GPS to work with the NTP server on pfSense.  I dont seem to be able to get NTP to see GPS data on any of the ports.  LTE on 0.3 works fine.  Nothing else though.

"to use at tradeshows or to use as an emergency internet connection for customers." Why and the F would you need a transparent proxy for such a connection.. Cradlepoint would be a perfect solution for these sorts of things btw!!!  We have been playing with some of their hardware at work for an upcoming project.  They are slick ;)

its an android app called iperf, you can run it with whatever options you like.

Hi Johnpoz, It's a typo, my humble excuse, it should have read ''we have two (2) SSid, one for staff and one for clients'' Sorry, anyway… I haven't solve the issue yet, but you know how Boss's are, I am implementing another FW in a remote location, etc etc... I'll be back... Thanks for all the efforts and pardon my misunderstanding...

Thanks for the suggestion.  I will unbridge and give that a try to see if things improve.

Thanks, that pretty well confirms my suspicions. Clearly it's in the best interests of the community for those interested to get results without the heartache of wireless nic incompatibility. If my problem solution to find and use a standard router in AP mode is  o.k, I wonder why there are so many discussion threads and a wiki on compatible wireless nic drivers which don't cover latest enhancements anyway? Surely if you are going to start with pfSense you get a pc host with at least 3/4 configureable lan ports and use a remote wi-fi AP?  I haven't worked through the pfSense port and firewall setup yet, but I gather I can put the external AP on a port with an IP address outside the local network but still restrict access to websites and block ports on the Wlan. Now I've realized an inferior wireless nic that might work in the box with pfsense probably costs about the same as using a fast 2 channel beam forming router in AP mode, there is no contest. However, I haven't yet got answers to the question of port speeds. Most wi-fi routers claiming 800Mbps on 5Ghz band only have 10/100 lan ports. Perhaps I'm an idiot and don't understand yet why they aren't spec'd as Gigabit lan?

Ah, I did do that with an R7800 but I was hoping to see if I could get the inbuilt wifi chip to work for the heck of it. Thanks all :D

Post your rules. The block would need to be above the pass, just block them first regardless of schedule, then try and get the schedule working.

If you install it on hyper-v it should come up as a network and you should be able to see it in virtual network manager in hyper-v.  Maybe try creating a new network and attaching pfsense with that network.

What radius?  I am using domain connected windows 10 with radius on windows no issue.  Not sure of radius on pfsense.

I'd be willing to bet you can't use an internal wireless adapter as an access point with a virtual pfsense unless using pcie passthrough.

Hi, did you find a solutioin ? I think that the probleme can be the ldap configuration , if you look at your logg you'll see that the bind to the ldap can't be done. Maybe there is a probleme of certificate too.

I report the solution: https://forums.freebsd.org/threads/39557/ # cat /etc/wpa_supplicant.conf network={   ssid="NETWORK"   scan_ssid=1   key_mgmt=WPA-EAP   identity="USERNAME"   password="PASSWORD"   eap=PEAP   phase1="peaplabel=0"   phase2="auth=MSCHAPV2" } and this command to connect # wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf

Thanks NogBadTheBad! That did the trick sir!

I have the same exact setup as you. Down to the same wifi cards and processor. I know the wifi works because it's seen and worked in Ubuntu. I could plug in a Nighthawk router but that defeats the purpose of why I bought the card that was on the card list.

I continued to try different things and the solution was this: Keep messing with settings, while restarting the interface, and eventually it will start working… In my specific case, it seemed that dumbing down the network standard to 802.11b, and then reverting it to the existing standard, 802.11ng, was the magic bullet. Go figure.

The run driver does not do 802.11n. Check out the caveats: https://www.freebsd.org/cgi/man.cgi?run%284%29

@AW_sensepf: I have a nano USB wireless N adpater TP-Link TL-WN725N ver. 2.1 on pfSense 2.3. Driver URTWN(4) https://www.freebsd.org/cgi/man.cgi?query=urtwn&sektion=4&manpath=freebsd-release-ports supports Realtek RTL8188CU/RTL8188RU/RTL8188EU/RTL8192CU based USB IEEE 802.11b/g/n wireless network adapters, including my TP-LINK TL-WN725N. dmesg tells this: ugen0.3: <realtek>at usbus0 urtwn0: <realtek 0="" 3="" 802.11n="" nic,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus0 urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R wlan0: Ethernet address: f4:f2:6d:0c:xxxx wlan0: changing name to 'urtwn0_wlan0' re0: link state changed to DOWN re0: link state changed to UP re1: link state changed to DOWN urtwn0: timeout waiting for firmware readiness re1: link state changed to UP urtwn0: timeout waiting for firmware readiness urtwn0: timeout waiting for firmware readiness pflog0: promiscuous mode enabled urtwn0: timeout waiting for firmware readiness ifconfig: urtwn0: flags=8803 <up,broadcast,simplex,multicast>metric 0 mtu 2290 ether f4:f2:6d:0c:fxxxxx nd6 options=21 <performnud,auto_linklocal>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated urtwn0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 ether f4:f2:6d:0cxxxxxx inet6 fe80::xxxxx:6dff:fe0c:fa07%urtwn0_wlan0 prefixlen 64 scopeid 0x8 nd6 options=21 <performnud,auto_linklocal>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: no carrier ssid xxxxx channel 3 (2422 MHz 11g) regdomain ETSI country CH authmode WPA1+WPA2/802.11i privacy MIXED deftxkey UNDEF txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 pureg protmode OFF roaming MANUAL Named as urtwn0 status is associated. As 'urtwn0_wlan0' is no carrier. Is this because of changing name? Only? Does "urtwn0: timeout waiting for firmware readiness" mean that firmware or specific kernel module must be loaded? Or is this only, because after renaming urtwn0 doesn't exist anymore? I have ver. 2.1, but driver URTWN supports TP-LINK TL-WN725N v2 only. Does this matter? Rgds AW</performnud,auto_linklocal></up,broadcast,running,simplex,multicast></performnud,auto_linklocal></up,broadcast,simplex,multicast></realtek></realtek> news??