Thanks i will try that

For 2009 i will be a better man and give more info on my post ;D

I tried the TL-WN651G in the spare slot of my P2B. The BIOS doesn't even report it. pfSense doesn't see it it any fashion - it was just as if nothing was plugged into that slot.

I also have a Gigabyte GN-WPKG PCI card which has a Ralink 802.11G chipset. i plugged the Gigabyte card into the same slot I used for the TP-LINK card. The Gigabyte card was reported by the BIOS and the ral driver in pfSense 1.2.1-RC1. I didn't attempt to configure the Gigabyte card or use it. But there was something curious about this card as well. The system has a USB PCI card using a NEC USB 2.0 chipset. With this USB card in the system the startup would hang soon after reporting the NEC USB devices. When I removed the card with the NEC USB chipset the system started up and entered the usual configuration dialogue when booting from pfSense CD.

I suspect you may need to choose carefully when it comes to getting a wireless PCI card for the P2B. I suspect the Gigabyte GN-WPKG card has been superseded. Based on this experience I would be cautious about assuming a card with a recent chipset will work on the P2B motherboard.

I've got one of these http://www.netgate.com/product_info.php?cPath=26_34&products_id=474 running in a pfSense system. The Valemount looks to be a 6th gen Atheros chipset also, so it SHOULD work.

If you mean the FreeBSD list of supported hardware, NO, you need to look at each of the supported wireless lan chipsets to see if access mode is supported. The web page has links to the man pages for the indicidual drivers and the man pages indicate what modes are supported by the driver.

If you mean the madwifi list of cards with the Atheros chipset, then I think the answer is YES because the FreeBSD ath driver supports access mode on the Atheros chipsets it supports. However you need to exercise some caution because some suppliers (among them Belkin, D-Link, Linksys, Netgear) will use the same model name for cards with different chipsets.

If you are looking for a PCI card based on the Atheros chipset I have had good experience with TP-Link TL-WN651G. It works well with 3 to 4 PCs in a home network. TP-Link seem to change model name when they change chipsets.

I will analize the link u give to me and try to test.

Thanks!!!

http://forum.pfsense.org/index.php?action=search
keywords: wireless MAC filter

I've been attempting to resolve my absurd in/out error issues for some time now, but with no real luck.  My environment is powered by an Atheros AR5212 (I believe…will edit and correct when I have the time) that has managed to be a genuine pleasure to configure, but a nightmare to operate.  In-out errors are through the roof even with the special build of 1.2-release.

@covex:

If I setup the antenna-settings correctly…

what do you mean by that? could you please post your settings here…

I would like to learn a bit more about this, too.  PFSense has pretty much been a case of solid on-the-fly learning in an attempt to provide a more flexible network environment.  I'm vaguely aware of what benefits specialized configurations bring to the table, but not necessarily how to do them.

My current physical setup has two antennas, with one just barely able to reach (but still connected).  If I were to attempt single-antenna operation, what settings would I need to apply in the console/bootloader to force it to a single antenna, and is there any genuine reason I should strive for two?

How that flew past my head I don't know…..

GruensFroeschli I am now up and running.

THANK you sir!

The ralink card shows up as ral0 it's a PCI card.
Anyway anything I try works only if I disable any kind of protection. With it no go.
Nothing is outputted on the console as for syslog I'm not actually sure what I should be looking for.
But clients show in the dhcp lease log even if the encryption is enabled.

Thanks.
Bye

For now do not hope on drivers unless you want to go the ndisgen part.
That's what i use for my own 802.11n card that is a broadcom 43xx something.

I maybe will find someday the time to make it work with freebsd drivers since the basics of the driver are in some drivers added to head of freebsd.

pfSense requires at least two interfaces: LAN and WAN. In your case, if sis0 (the onboard Ethernet) is your "LAN" then ath0 (your Atheros mini-PCI card) is your "WAN".

easy way of checking for atheros chipset…...anything thats 108mb is a atheros chipset they own 108mb

Thanks, that worked.