I meant you should connect a directional antenna to the computer (the pfSense) connecting to the accesspoint.
A directional antenna has benefits for both sides.

The CP can currently only one one interface be enabled.

@chrisssooo:

Hi,
i have do it on a embedded system.

You must do it over the WebGUI becourse the write permissions is only over it.
Use pfsense 1.2.1 RC2 becourse FreeBSD 7.0

Step 1:
Download the 4 Kernel modules: http://deponie.yamagi.org/freebsd/iwi/
Go in the WebGUI in "Diagnostics->Command Prompt".
Upload all 4 Kernel Modules over the "Upload" function.
The Files will be upload to /tmp/
After Upload use also in "Diagnostics->Command Prompt" the "Execute Shell command" function to move the files to the right location.
1. Type in Command: "mv /tmp/if_iwi.ko /boot/kernel/" and click on "Execute"
2. Type in Command: "mv /tmp/iwi_* /boot/kernel/" and click on "Execute"
Now the Kernel Modules are on the right location.

Step 2:
Now edit the /boot/loader.conf File.
Go on WebGUI in "Diagnostics->Edit file".
Type in the field "Save/Load from path"  this Text: "/boot/loader.conf" and click on "Load".
Add this 7 Lines at the end:

if_iwi_load="YES" wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" legal.intel_iwi.license_ack=1

and click on "Save"
Reboot pfSense.

Step 3:
Now you can Assign you card in the WebGui over "Interfaces->assign" whit the "Plus" and configure it.
But when you read this Thread you must know:
ITS ONLY POSSIBLE TO SET THIS CARD TO "Infrastructure" AND "Ad-hoc" … "Access point" DONT WORK!!!

I hope its work for you :)

Thanks a milion this worked like a charm. This should be stickied somewhere as its a sure fire and quick way to get those cards working.

Well, I spent this weekend trying to figure out what was causing this.  The card's rated at a maximum of 18 dBm at 6 megabits according to the datasheet (so, about 63 mW, according to this calculator).  Unfortunately, it doesn't list what power output it has on lower modes.  I tried turning down the power anyway (to about 60%), but unfortunately it didn't seem to help.

I did some more searching and found a Google cache of this post from the now-closed 1.2.1 RC forum of somebody having a similar issue and it seems like it could be a FreeBSD 7 issue.  I tried reverting to 1.2, but it didn't help much.  I could load YouTube, which gave me a connection error before, but I couldn't actually play more than a few seconds of any video.  So, if it is a FreeBSD issue, it's one that was somehow missed in 6.2 and 7.0.

Just to make sure it wasn't the iPod itself, I pulled out my old WRT54G and turned it into an access point.  It works just fine.  So, I've got a solution for now, but I'm going to continue to try to find out more information about what might be happening, as I'd really like to use my pfSense unit as the AP instead of having a separate one.

I'll look into whether it might be the power supply.  I didn't think of that possibility.  It'd be nice if I could just replace that, as it can't be very expensive.

excellent. thank you for your help.

thank you! works perfect now (again) :)

Hi,

I use a mini ITX motherboard. A VIA PD series motherboard.
I just installed 1.2.1 final release and my wireless NIC started working.  Although I seem to be losing connection every 10 minutes or so…

ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: <atheros 5212="">mem 0xea000000-0xea00ffff irq 11 at device 20.0 on pci0
ath0: [ITHREAD]
ath0: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:19:5b:89:e7:d2
ath0: mac 10.5 phy 6.1 radio 6.3

So far wireless is not what I would call very stable for me unfortunately.  :-</atheros>

That such a friend!
At the moment it achieves placing client mode but without result of entry into the Internet but no longer do that ay that I lack any information please?

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!