@rocketdog: Is there any easy way to update pfSense to 2.1, That won't help. You need to load the firmware at boot time: add the following line to pfSense file /boot/loader.conf.local (create the file if it doesn't already exist):``` runfw_load="YES"

I finally got wifi to work. Had to really read it over and over. It was the protocol that was goofing me up. LOL Thank you for all the help! I will get working on a video tutorial very soon

I guess I just had bad luck. I'll stick with the external AP for now and maybe when pfSense moves to 9.x I'll try again :)

It certainly is… I've just thrown up the same scenario on my spare Thinkpad to test (see attached)... Caveats are: You'll need a good signal! The Wifi will probably be NAT'd - decrease the MTU on the WAN to 1492 & LAN to 1484 to avoid fragmentation (double-NAT!) I'm assuming the 'source' of the wifi is friendly (neighbour, commercial service, café etc.) not just some random, open network you can 'see' from your new place! NB.  The screenshot is showing 'update available' for 2.0.2 - this is because the wifi I'm testing with is the captive portal on a 'live' pfsense box, the challenge page is making it thinks there's an update?!? [image: Wifi_WAN.PNG] [image: Wifi_WAN.PNG_thumb]

I've been messing with that for days now.  There are no open areas, switching to a less used channel helps temporarily but they're all fighting for limited space. I've got a few things that can't support 5ghz so I "fixed it" with a wired AP in the other room.  When I plugged in the second AP in the office with the pfSense box, it had the same problem.  When I plug it into a drop in the same room as the Roku, 15-20 feet away, it works perfectly. I don't do wireless professionally but am a network engineer.  Constant retransmissions and timeouts on one frequency, plus a huge number of competing APs and who knows what else, but not another makes me pretty sure this is an interference issue.

It is a DDWRT Bug..!! I discovered that the encryption agent is using the wrong bridge interface. Thank You very much  :D Now I'll go into DDWRT forum to get help for this Bug  ;)

Despite the heroic efforts by Adrian Chadd, FreeBSD 8.x (the operating system pfSense in based on) Wifi support isn't very good. So unless you are very knowledgeable and/or have a lot of free time to experiment and learn, my suggestion would be to just get a stand-alone wireless AP or a consumer Wifi-router and load it with *WRT (DDwrt, Tomato, OpenWRT etc) firmware. Finally, "hidden" BSSID doesn't offer any security, so make sure you use WPA2 over your Wifi network.

It seem as though someone has worked on the F.20 bios Last post by sovem http://www.bios-mods.com/forum/Thread-REQUEST-HP-Elitebook-8530p-whitelist-removal-F-20-sp55640?page=2 A bit paranoid about flashing a anonymous source file…..What do you guys think guys? I've searched around and it seem as though sovem shoots the OEM's between the Eyes!

Thanks for everyone's help, but I'm just going to get a different computer.  :)

@joebobfrank: When I ping the wlan0 interface from my wired machine on the LAN the average time is 0.152 ms. That is a big difference. You are not comparing like with like. A full duplex wired interface can talk whenever it wants. A WiFi device generally has to wait its turn because it has to share the communications channel.

@joebobfrank: It is very slow. Something is wrong with the set up. Please provide more detail than "very slow". What activity is "slow"? How slow? What device(s) are the WiFi clients? What signal strength do they report? Ae you sharing a wireless channel with other devices? etc …

Ok, so I needed to add two new rules for this in the NAT outbound section: WAN2 192.168.5.0/24 * * 500 * * YES Rule for ISAKMP WIFI to WAN2 WAN2 192.168.5.0/24 * * * * * NO Rule for WIFI to WAN2 It all works fine now. NOTE: anyone else with a multi WAN system will need to add the same rules for WAN1. I'm not adding these rules as I don't want WIFI to work if WAN1 is active, its just not fast enough. Do I need both of these rules? The second rule seems fairly obvious but the first one?

As you may know wireless devices uses air as their media and it's by design shared media. –> less clients -> less "noise" -> better throughput so, this kind of bonding multiple nics, ain't gonna do any good if you don't have multiple accesspoints and spreaded channels, so no accesspoint is going to use same channel than it's friend. Plus with cable you can have better speeds

I agree with the coments about enterprise gear…  In my organization, we use Cisco 1121g APs.  As they are way past end of life, and are very inexpensive, I have used them at home and on other jobs I have done alone the way...  They are pretty much bullet proof and when it comes to power and sensitivity, they run circles around the soho gear on the market.  Interstingly, I have had several of them apart and have modified them for external antenae which is just another cool way of extending range. Getting experience with the cisco gear is a great idea because of Cisco's own unique nuance and the marketability of putting "Cisco" on your resume. All of our switches are Cisco 3750 series and we try to maintain a balance between high dollar gear and "getting by" in other areas, but converse to sticking with name-brand gear, we recently abandoned all of our Sonicwall shizzel in favor of pfSense. The transition to pfSense has been one of the best things I've done in a while.  Being new to pfSense however, means that I am still learning my way around... Now that I have gotten completely off subject, let me get back on - When the entprise gear is affordable and accessible, it's good to get your feet wet...

@thekeymaker: Card works but it look like to only supports infrastructure mode. Check the man page. It doesn't say AP mode is supported. I don't know what is involved in supporting AP mode on the card. http://forum.pfsense.org/index.php/topic,57771.msg309272.html contains a link to a mini PCI-Express card available from Amazon that is reported to work. @thekeymaker: ~ we should be coming during the Winter season so hopefully it might be slightly colder… I live on the Gold Coast, about 900km North of Sydney. Temperatures have been much more reasonable here recently. Winter is beautiful, too warm for snow. The tourism people say "beautiful one day, perfect the next"

@Jappmannen: I guess all the G-cards out there are supported in pfSense 2.0.2 then? Or is there any card that I should watch out for? Many WiFi chipsets seem to have a short life. Some card suppliers change the chipsets without changing the model number. Not all WiFi chipsets are supported by FreeBSD. That said, people generally seem to have success with cards with Atheros chipsets and they generally have the widest variety of configuration options. The best place to get a PCI card with Atheros chipset is probably eBay because a lot of the sellers are prepared to disclose the chipset of the card they are selling. The FreeBSD man page for the ath driver (see http://www.freebsd.org/cgi/man.cgi?query=ath&apropos=0&sektion=0&manpath=FreeBSD+8.1-RELEASE&arch=default&format=html) mentions the AR5005VL chipset is not supported. From time to time the pfSense wireless forum contains reports of successful use of a particular brand and model of card but these aren't always helpful because cards with the same model number can contain completely different chipsets.

@foxround: but now i create the Client mode and i wasnt sucessfull! Do you recall what you did at that step? Please post the output of pfSense shell commands``` ifconfig /etc/rc.banner

I bought the Rosewill RNX-N600UBE and have set it up as an AP. Had to add the following lines to /boot/loader.conf``` if_run_load="YES" runfw_load="YES" I've run into an issue were my iPhone 4S cannot connect to the AP, I tried connecting with security enabled and also without any security. Connecting with any laptop works fine.

I think I figured out the cause for this. When the last time this problem occured I checked via serial console the system.log and found the following message multiple times: ath0: ath_rx_proc: no mbuf! After a bit googling I found a some mailist entrys like this one http://marc.info/?l=pfsense-support&m=129098214008714. Disabling the traffic sharpner seems to do the trick, it runs now way longer without trouble and still uses about the same MBUF amount constant.