Usually it means the frame it received was malformed. It could have been sent by the client incorrectly, or it could have encountered a problem processing the frame in the hardware or driver.

well yeah a mask of /32 is not correct for sure on your lan…  How is anything going to connect to that, that should most likely be /24 and also your wifi shows no carrier.

A little more information:  Using the TetherMe app on the iPhone.  Very little information available about the app.  Best I can tell it uses WPA2 (CCMP), no configurable settings.  The Wireless page under Status shows the iPhone SSID but the CAPS settings do not show WPA.  I know it uses WPA because my computers and iPad require it to connect.  Is it possible that pfSense (ath0 driver) does not try to connect because it does not see WPA as an option?  Of course, it does not connect if I de-select WPA.

1.) In the interface assign menu click on the "+"  and then the interface adding as OPT2 . Then you should see the new interface that owns a iwn name then it was recognized correctly by pfSense. 2.) In the interface setup the OPT2 must be activated then, set on static and configuring the IP address and mask. Please without building a bridge because this should be a own network for it self and the name is optional then. 3.) Set the WiFi interface in the mode "hostap" for runing an "WiFi accesspoint".

Sorry i don't have that "model" of wireless adapter I only have an old Tenda W311U  to test… and it had worked OK when i tested (some time ago).. One difference i have noticed is i have used (as suggested by the link to the DOC) "Authentication: Open System Authentication"  (instead of "Shared KeyAuthentication) [image: WPA2_AES_OK.png] [image: WPA2_AES_OK.png_thumb]

For ease of keeping it simple you could of accomplish the same network for your wireless and wired by just using your old wifi route as AP and connecting it to your wired network. You turn of the soho routers dhcp server, you give it a IP on your network for its lan.  And then connect it to your network via a lan port on it vs its wan.  There you go 30 second AP..  That sure and the hell is much easier than creating a bridge.. There are no routing rules if you just put the pfsense wifi on its own segment - firewall rules yes..  But if you make the them any any you pretty much have 1 network with just broadcasts not passing between them. As to getting a home budget AP, I would look towards the unifi stuff.. https://www.ubnt.com/unifi/unifi-ap-ac-lite/ You can have as many WAN connections you want, that has nothing to do with number of local network segments you run or don't run.

I'm running the RT-N66U router in router mode.

I was able to find the problem, hopefully this helps someone else. First, I had the Client IP set to the AP IP and it should have been the controller IP.  I found this issue by using packetcapture on the pfsense. Second, I needed a firewall rule on the wifi intferface to allow the controller to reach the firewall on port 1812.  And lastly, I had a fat finger mistake on typing in the CA cert info on the pfsense EAP tab.

Using an Cisco SG200-8P with Unifi UAP-AC-Pro working Perfect =)

Welp, you're right. Just switched it to the LAN and now everything works. Last piece of the puzzle. Thanks

using ath0 as wan had similar problem which the above solved it had another flaw though on boot as the dhclient quit because cat /tmp/ath0_wlan0_output ath0_wlan0: no link …........... giving up the interface_bring_up returns before the ath0_wlan0 link was present /*fire up dhclient */         if ($wanif) {                 // link not up as fast as interfaces_bring_up                 log_error("/etc/inc/interfaces.inc sleeping");                 sleep(10);         } mwexec("/sbin/dhcclient......

EA6900's are a bit more than $100, I show them on amazon for $171..  So you have 2 of these and more than 1 managed switch.. And your trying to skimp out on a few bucks vs getting another AP? "Am I trying to do the wrong thing?" I would have to say yeah your going about it wrong ;) Also your 2 EA6900's are AC.. Wouldn't you want your 3rd AP to also be AC..  Going to be a bit of an issue having same SSID on 2 of your AP doing AC, and then your third only doing N..  I can understand saving a few bucks..  But we are not talking getting a $1k AP..  You could get a unifi next gen AC-Lite model for under your $100 mark for sure.  Or you could go with any AC wifi router that can be had for half of that $100 mark and use it as AP..

Hi, Hope this might be helpful. https://forum.pfsense.org/index.php?topic=105444.0 Good Luck!!

Phishfry, thanks for the help  :) As per your instruction, I have successfully setup the WAN interface and now to receive wifi signals from the secured wireless network and access the internet through ethernet . It would have been impossible without your help. However, while connecting through the pfsense router. :-\ I'm getting error "scan_task: oops! scan cancelled during driver call(2)!" on my pfsense screen. Thanks in advance :)

Crossposting is not good idea.. I answered this question in your duplicate thread about this here https://forum.pfsense.org/index.php?topic=105751.0

@johnpoz: Its going to be crap, is what its going to be. Period… I don't believe it has any freebsd support.  https://www.freebsd.org/relnotes/CURRENT/hardware/support.html It barely usable for a device alone, sure not providing wifi to multiple devices.  1T1R means at best you could get is 150 PHY with short guard and 40mhz.. Not very viable..  More like 65PHY, might as well be using G at that point.. Post count, is that what your after with your cross posting, and hijacking of thread?? Didnt try to steal anything just wanted to post some info. well a friend of mine still has a Intel Centrino Advanced-N 6230 which is 2x2 i think and if i google real quick it seems to be supported by 10.1 so might give that a try. Before i spend 80 euro+ on some wifi thing. what i dont use a lot

Hi, Although I can't give you a proper solution to your problem, I recommend NOT using the WLE2000 card with pfsense and apu1d4. It gave me (on release 1.x and 2.0/2.1) nothing but trouble (endlessly rebooting and hangs) ending up with an broken WLE2000 adapter. After a long search trough forums and tech sites I decided to take a chance on a AR9280 based chipset mini pcie card which I bought cheap on ebay. http://www.ebay.com/sch/i.html?_odkw=ar9280&_osacat=0&_from=R40&_trksid=p2045573.m570.l1313.TR0.TRC0.A0.H0.TRS1&_nkw=ar9280&_sacat=0 ath0: <atheros 9280="">at device 0.0 on pci5 ath0: [HT] enabling HT modes ath0: [HT] 1 stream STBC receive enabled ath0: [HT] 1 stream STBC transmit enabled ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9280 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 The card works excelent on my pfsense 2.2.x Hope this helps</atheros>