Using an AP is easier that using pfsense, i agree. But the need custome AP by using m0n0wall or pfsense letus try this fix. because it is only a missing module. if i got it right. think about having 6 APs on the same machine. thats a station! and much much cheaper and more relaiable i am sure it will be. FreeBSD 8 improved the wireless much, and so on FreeBSD will continue supporting allot of hardware in next releases. i will try to post this to bug tracker and see what happen.

after editing /boot/defaults/loader.conf  by replacing if_run_load="NO"      # Ralink USB 802.11 wireless adaptert with runfw_load="NO"                # Firmware Module for Ralink driver and reboot with connecting my USB wifi system logs shows Feb 10 13:55:32 kernel: Root mount waiting for: usbus0 Feb 10 13:55:32 kernel: uhub0: 2 ports with 2 removable, self powered Feb 10 13:55:32 kernel: Root mount waiting for: usbus0 Feb 10 13:55:32 kernel: ugen0.2: <ralink>at usbus0 Feb 10 13:55:32 kernel: run0: <1.0> on usbus0 Feb 10 13:55:32 kernel: Root mount waiting for: usbus0 Feb 10 13:55:32 kernel: run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address a0:f3:c1:0f:fb:f8 Feb 10 13:55:32 kernel: runfw: root not mounted yet, no way to load image Feb 10 13:55:32 kernel: run0: failed loadfirmware of file runfw Feb 10 13:55:32 kernel: run0: could not load 8051 microcode Feb 10 13:55:32 kernel: device_attach: run0 attach returned 6 so maybe kernel was not compiled with option "device runfw" regards</ralink>

@podilarius: 255.255.255.240 is not a valid private IP address. This will cause a lot of problems.  I would stick to 10.x.x.x/8 or 172.16.x.x/12, 192.168.x.x/24 addresses. ah, thank you - this solved my access problem! I have 192.168.255.1/24 now. Thanks

@johnpoz: And what rules did you create on the opt1 wifi firewall tab? Thanks, that was my mistake. I thought the firewall would allow anything with default settings. Now I have set the rules like described in the article and everything seems to work with the standalone configuration. Maybe I try the bridge configuration at the weekend.

ive answered my own question i have used access point and i have good reception on all my devices anywhere in my house

check your rules, your lan will have a 'default allow to any' rule, and your wifi will need the same. not sure about the wireless n issue, but i had the same issues with a ralink device.  i think it was that the driver just didn't support it, but i didn't need the speed, so i didnt pursue it.

I remember having a similar problem when I first setup my wireless, the internet wouldn't work on my kindle and a few other things but it did work on my laptop and iphone. I switched the wireless channel and everything worked.

no body know ,if intel 4965 can use on pfsense?Please help me ,please.

Well, I answered my own questions even though I went about it differently. Was having trouble with an error message with wireless nics, something about the beacon not responding properly.  After a search, I found that there's a fix but it was too much of a hassle for me.  So instead I added a TPLINK wireless router to the network that  I had lying about.  Smae results. Answers to my questions are 1.  Yes 2.  Yes, a new ip address from the appropriate dhcp scope is leased 3.  You only need ot enter the gateway address if it's different then the address of the pfsense machine

There are some reports in the forum reflecting that pfSense 2.1 has some problems with at least some WLAN cards. I've recently found out that an Atheros AR5413 WLAN card (Compex WLM54AG) on my Alix2D13 stopped working after upgrading from pfSense 2.0.3 to version 2.1: http://forum.pfsense.org/index.php/topic,68531.0.html. I am having an Atheros AR9280 based WLAN card (Ubiquiti SR71-E) that is currently working fine in my Soekris net6501 under pfSense 2.0.3 (nanoBSD i386 2G on a 4G compact flash card, no packages installed). Because of the problems I have when upgrading my Alix board I currently delayed the upgrade of my Soekris machine. Besides the annoying need to open the case for a reflash of the compact flash card I am afraid the AR9280 might stop working under pfSense 2.1 just the same way the AR5413 did. Regards, Peter

Hey, I didn't see your thread here until now. Just created a new thread about the same exact adapter: http://forum.pfsense.org/index.php/topic,70415.0.html Have you had any luck? What if you try the steps I said I tried? I'm curious if you'd get it to work with those three steps so I can determine if it's something with my setup.

Wow I read my original post and I cringe. I have been learning a lot thanks to this forum. Thank you for not lambasting me with sarcasm. So long story short I have a working scenario to begin the pfSense journey. AT&T RG DMZ+ > Netgate WAN Supporting: LAN (Default port. Left this one alone so I could mess with others and not get locked out) BRIDGE (LANx3, Separate ports for 2 different physical LAN's and Asus RT-N66U for WiFi) LAN (Opt6) is a separate WAP with Internet only access. Caveats discovered on this build: gettytab is busted. Fix seems to be remove al=root: and change speed from 115200 to 9600. minupnpd  seems to dislike BT traffic and starts spamming Routing log. Still researching this one. IPsec Mobile is functional but booting with errors. Still researching. Various Firewall and Snort alerts that need researching. I have a Firewall and functional WAP's, it's a start. Now back to reading forums.

As for setting up your old router as an AP most routers have a way to set that up in their web interface just google for your specific router and you'll be able to find something. As for using it with pfSense you can just plug the AP into your switch and it will work okay. I've been using that as a set up for about a month now. However I see slower speeds on the WiFi than I used. I believe if you cable the AP into opt1 NIC as long as you have pfSense set up to use that interface it should work better than just plugging the AP into the switch. I'm actually going to set this up later when I have time to take a spare NIC out of another computer I have.

So you want to use pfsense as the actual AP?  That does not seem like a good idea to me, pfsense wireless support is not the greatest and doesn't even support N wireless, etc. https://doc.pfsense.org/index.php/Is_802.11n_wireless_supported I would recommend pfsense as the firewall/gateway any day of the week.. But as AP in a OLSR network – for starters you want to run that in a building?  OLSR is an wireless adhoc network routing daemon.. In a nut shell tells you what hosts to talk to in the mesh to get you to specific host X the fastest.  Normally these would be used in a mobile network where hosts are moving. Why would this be a good idea to cover a building for wireless access?