@XanALaOM00: how about… turn off NAT on the consumer router, turn the consumer router into AP mode, use the WAN port as an "access port" to Pfsense and configure the AP with a static IP address on the same subnet as the Pfsense Opt1 range (make sure to not hand out the same IP address in the DHCP range). In theory that would work - but in practice it doesn't unless your network is very simple.  All the consumer wireless routers that I've tried that approach with over the years will allow wireless devices to access the local network and the internet WAN via pfSense - but devices on the local network LAN often have subtle problems talking to the wireless devices.

@Spyryt: I set up a new PFsense box yesterday (running 2.1.5-release) and am currently having a few problems with the WiFi.  I can access the internet fine on my LAN connection, but I can't get devices connected via WiFi to connect to the internet.  The devices are getting an IP from DHCP. Here's my firewall rule for the wireless interface: ID Proto Source Port Destination Port Gateway Queue Schedule Description add add icon   IPv4 * * * * * * none   WiFi data The WiFi was actually working yesterday until I swapped the WiFi card.  The WiFi interface is bridged with the LAN connection. off the top of my head, always go with packet flow logically. what does the firewall log show?  can you ping your OPT1 Default gateway? can you ping your LAN default gateway?  can you ping your WAN ip address?  etc… if you can ping all of the above I would check your source NAT rules and verify that pfsense has created a rule to NAT your OPT1 source traffic.  etc...

I just posted a description of the process to get an AP running in another thread - "How to use a consumer wireless router with pfSense" - if you follow that then you should be able to get it working.  All AP's are different but the basic script is the same - I have always found it best to start off with a factory reset first so that everything is in a known state.

@amunrara: welcome no, i am using this one: http://www.amazon.com/Atheros-AR5BXB112-450Mbps-Wireless-N-Dual-Band/dp/B00L27OW18/ref=sr_1_4?ie=UTF8&qid=1420282213&sr=8-4&keywords=AR9380 however, it looks similar :) i got both :) the one that you have didnt fit in my mini itx due to cpu fan :) so i used half size. Now im trying to figure out hot to make my wifi work

Thanks Jimp. I never realised that was possible in pfSense. I feel silly for asking but at least now I know. Thanks again  :)

check this for guide https://www.youtube.com/watch?v=SOioAR3X6Ec

AR9380 chipset works for me with pfSense 2.2

That's just it, it does not work completely. Devices connected to the E3000 at first could not get an IP until after I created a static dhcp entry in pfsense for the E3000 itself, giving it's mac id and ip of 192.168.0.254, with a static arp entry as well. That worked only far enough enough to allow devices connected to the E3000 to then get an ip from pfsense, but not reach the internet. Going back into pfsense after the device has been given an ip, and turning that dhcp entry into a static entry, with static arp entry as well, will then allow the device to reach the internet. I have 3 other routers attached to pfsense, and all devices attached to them work fine, when it comes to the E3000, everything, including wired connections have issues unless a static dhcp/arp entry is made for them. Since the linux install that pfsense replaced worked fine with this setup, I'm assuming I'm missing something in pfsense. If fact, pfsense is running on the same hardware, just a new drive since the old one died.

Here is a good resource for Sierra modem capabilities. This is where i found the tip that data port is usually next to last comm port. The correct PPP comm/usb port seems to be the biggest guessing game on getting cellular working for me. http://whirlpool.net.au/wiki/sierra_advanced

Hi, I want to buy a TP-LINK TL-WDN3200 with this Ralink RT5572 chipset for my pfSense box. Under version 2.1.5 can I use this with wireless b capability? And with version 2.2 can I use this card with full wireless-n capability? Thanks!

can you please explain your configuration?

Well… Has anyone TRIED one, or have the data?????????? ????????????? ???????? ????? ??? ?

Finally, after some months, I've found a solution: The tick 'Persist common settings' in the WLAN-settings should be checked… Haven't found any explanation what this setting really does, but it solved the problem. Since then, the Denon client runs flawlessly. I've observed with tcpdump (listening on ath0_wlan0 interface of the pfsense), that now the size of the IP packages is variable, before it was always 1460...

It looks like Aironet cards does not support hostap (https://docs.google.com/spreadsheet/ccc?key=0AojFUXcbH0ROdHgwYkFHbkRUdV9hVWljVWl5SXkxbFE&hl=en#gid=0)

Well when you say work at N speeds i guess that is subjective. I went from1.5MB/S on G mode Stable 2.1.5(R52-350) to 4.5MB/S with 802.11N on 2.2beta(R52Hn). Not very impressive for what i was expecting but still faster. I hate to say yes for sure because i am a rookie, but I am definitely seeing connection speed of 150M max in windows. Usually it shows 300M at startup but drops to 100-150M when in use. One client using Intel 6205-N on Acer netbook and another using Atheros half card in Dell Latitude10 tablet. Both similar results from 30-40ft range using iperf. My pfSense wireless status also shows N connections. I can also confirm that the R52hn works in a Routerboard230 which i have pfsense running as an MIFI with an 3g aircard. Still an experimental build as its so darn slow in the webGUI. If you don't need 2.4 ghz there are some nice Compex 5ghz high power cards for 28 bucks on ebay(WLM200N5-26-ESD 400mW a/n NEW ). The dual band R52hn is nice and there are also some good umbiquity SR71 modules..

First thing I notice is that your pfsense firewall is on a different subnet from your access point(s). Unless you have a route set up within your network to send traffic from 10.10.2.0/24 to 10.10.1.0/24 then your access points won't be able to see the pfsense but will see each other. Either change the pfsense internal NIC to 10.10.2.1/24, for instance, or change your subnet mask to allow both networks to see each other (eg: 10.10.0.0/16).