I suggest you save yourself some trouble and buy a supported card that also supports access point mode. I'm pretty sure that in the last couple of months I have posted a list of cards supported in pfSense and supporting Access Point mode and available where I live for under US$30 (after conversion from local currency).

Its often necessary to do a pfSense firewall state reset after changing firewall rules. See Diagnostics -> States, click on Reset States tab.

I don't really know.  It might work well for some, but for me it doesn't because it ends up picking channel 1 for 802.11g, while the middle channels work best on the hardware I have.

there is an edit button so that one can edit their post.

I went into interfaces then opt1 and changed dhcp to static. After I saved it I could no longer connect to the wireless.

@BrainEater: I'm going to try setting the gateway to 192.168.1.1…...... That may not help. If the laptop is getting an IP address from pfSense it should also be getting the default gateway address from pfSense (and probably the IP address of the DNS server.) So, in your configuration, for a system connected to OPT1 the default gateway will be 192.168.3.1 (the pfSense OPT1 IP address). For broadcast media such as Ethernet and WiFi the default gateway needs to be on the same subnet as the interface in use unless you have a static route to the gateway through a system on the same subnet. If you change the firewall rules you generally need to reset states to have the rule change take effect. See Diagnostics -> States, click on the Reset States tab. Did you reset firewall states? For troubleshooting, from the pfSense console you could try pinging your laptop and pinging somewhere on the Internet. If both succeed then try pinging the same internet destination from the laptop. If the ping from the laptop doesn't succeed then look in the pfSense firewall log and system log to see if there are any "interesting" reports.

The interface does not require an IP address for it to show as enabled/working. What is the interface's status on Status: Interfaces?

there are pci based dsl modems that are still sold (unlike pci cable modems which are not sold anymore) the pci dsl modems are around $120 USD+, you would be best to bridge (disable the router portion of it) the dsl gateway and use it as a modem only.

Yes From your topic i have learned many more things. thanks

The router hardware is going to be determined by the bandwidth available and the packages you use.  Adding something like snort will dramatically increase the hardware requirements. As to the wireless, most vendors recommend no more than 25 clients per AP.  My personal recommendation would be something more along the lines of 15-20. I've had really good luck with Netgear's ProSafe APs & Wireless Controllers.  They're a high-quality but cheap alternative to something like Cisco hardware.  You can do multiple SSIDs and forcibly tag them with VLANs which can then be routed, filtered, etc. by your pfSense box.

@Citymesh: I found the issue. It seems that some Atheros chipsets are just not supported. I used other wifi cards and the work without any issue. That the ath driver apparently recognised the chipset on the card and claimed ownership suggests that the driver is erroneously recognising a chipset it doesn't really know about OR the card is broken. In the interests of better understanding the problem it would be helpful if you could put the card back in the system, reboot, collect the output of the two shell commands: # dmesg # pciconf -l and post it here. Its possible there is something about your card (a different chipset revision for example) that requires a driver tweak. @Citymesh: Any idea on the ATH9K kernel development? Will it be completed soon? That question would probably be better asked in an appropriate FreeBSD forum.

There is no support for "wireless N" cards in pfSense 1.2.3. There is some support for some "wireless N" cards in pfSense 2.0 which is still under development. In common with many open source projects, with pfSense it is better to check the support for a particular piece of hardware before buying it rather than buy the hardware and then look for support. http://doc.pfsense.org/index.php/Supported_Wireless_Cards describes some of the problems with recommending particular wireless cards. My usual source for finding the type of chipset in wireless cards (http://linux-wless.passys.nl/) doesn't appear to list your card. Unless you are prepared for the discomfort and discouragement of being a pioneer you would probably be better off using a TP-Link TL-WN651G (PCI card, uses Atheros chipset) or Tenda W54P. I've had satisfactory experience with the TP-Link TL-WN651G on pfSense 1.2.3 but others have been less impressed. I have no experience with the Tenda W54P but the chipset it apparently uses is supported in pfSense 1.2.3. In USB devices I've had good experience with light usage of TP-Link TL-WN321G and D-Link DWL-G122 rev C1 (both supported by rum driver) in pfSense 1.2.3 but the rum driver in snapshot builds of pfSense 2.0 is broken for hostap and ad-hoc modes.

@gilbertoyee: i need know how many users simultaneous support one PCI WIFI on Pfsense AP Mode. It depends on what you want them to be able to do. If you want the users to be able to simultaneously watch streamed high definition video the answer is probably one (maybe!). If you want them to be able to concurrently browse public web sites that are mainly text then I suspect the answer could be hundreds (provided your bandwidth to the internet is high enough). You can always add an additional card to get more bandwidth (but don't have them using overlapping radio frequencies). @gilbertoyee: what PCI card wifi is good? On pfSense 1.2.3 I've had good results with a Atheros based card, the TP-Link TL-WN651G, on my home network where I've probably had no more than six concurrent users. Others have been less happy with their Atheros based card. On pfSense 2.0 BETA I've been using a Ralink RT-2561 based card from Gigabyte which seems to be no longer available. The Tenda W54P and ASUS G31 seem to use a similar chipset. I haven't given the wireless interface on this setup  any serious work.

It should work. @cruzades: after I plugged-in the USB Adapter into the USB port of pfsense box luckily it was detected, But which driver recognised it? If ugen, then its not a supported adapter.

It took me a while to set it up and fine tuning it. Exactly what i needed ! I've just added a syslog-ng  to keep the logs. Thanks again leoalfa09

@wallabybob: OK, so your earlier report that you can't ping a computer on the LAN from a computer on the wireless is no longer current? sorry i miss read that from the wireless to lan computer i get no reply. from lan computer to wireless computer i get 100% reply. @danswartz: you're missing the key point though: if you have a default "allow any" rule, there IS no extra control, so you are complicating your setup for no real gain. i understand what you are saying and it does make since. if i put the wireless on the lan do i need to bridge it with anything or just plug it in and good to go? nvm  thats a dumb question once i think about it im going to hook the wireless into the Lan. if i ever need to add some restrictions to it i might move it back. and amazing enough it worked perfectly thanks a lot for all your help many next time i have to do this kind of stuff i will be more familiar with the firewall rules.

I found it easy enough to add a wireless interface to pfSense AFTER I had been using it with wired interfaces for some weeks. After installation of the hardware (assuming its supported by the underlying FreeBSD) there are just a couple of clicks in the web GUI to tell pfSense that the new interface is available for pfSense to use ad then filling in the configuration screen for the interface.