::) Yup, I'l try and try to see what I did wrong.

I was investigating the same thing a couple of months ago. I read alot of discissions on  mailinglists and got the impression that the guy that's responsible for the drivers Sam? doesn't think that turbo mode is a good thing on 2.4Ghz.
It works just fine in linux, and the HAL is the same for linux and BSD if I'm not misstaken, so I would assume that it's not implemented in the drivers.

The only thing that is not doable is to have trafficshaping at more than 2 interfaces, so you can't limit the neighbours to only use 512kbps. For the rest create a block rule at the wireless interface to not allow access to the other suibnets but to wan. Enable the pptp server or enable mobile ipsec clients (depending on what you prefer, pptp is probably easier to set up and most os's support it out of the box whereas you most likely need an additional ipsec client when using ipsec). Then you can tunnel in to your other networks with your own wireless client whereas the others can't access your private subnets and also only see encrypted traffic from your notebook to these subnets.

Not sure how this could be possible with a single radio, when I have seen something similar done you were always required to have dual-radio's in the device as each radio is only capable of broadcasting out one signal.

What you could do is use is a static dhcp address for the wpa2 area and leave it open on the rest. Then have a rule on the wireless card's rulset to say if you are in this ip range(those that need access to the lan) make an allow rule based on IP and then direct traffic that way. For the bandwidth shaping you could set some priority based on the IP range, this portition of it is a bit limited though.

nevermind about the P-IRQ, your using a WRAP setup…....P-IRQ is the prioity IRQ assignments....can get this problem with atx PIII/Socket A motherboards which use PC133 memory. Only found this problem in a 5 PCI slot asus board with using 3 pci cards + agp card....needed to shuffle the cards around as they had a P-IRQ conflict causing the above problem.

well, I added the interface and everything, booted up.  I changed the wireless setting to Ad-Hoc, then like my system rebooted and I cant boot back into it (I get mounting errors at bootup).  Any suggestions on how to boot back into my pfsense hard drive so I dont have to do the whole installation again, took a while to do that build thing above.  I am booted in the system right now using live cd, but I wont be able to access my partitions without mounting them.

thanks,
Zack

I have 2 pfSense boxes separated by 700mt with a 5,8Ghz turbo link using CM9 cards. FTP transfer at around 5,5Mbytes/sec.

Even today, when AR5004x begins to be EOL, I still think cards like CM9 are the way to go. It's a shame that Atheros stop production of this wonderfull chipsets in flavour of the cheap AR5006x. I know i'll miss CM9 a lot…

Macfiltering is not supported in the current wireless frontend. This will make it most probably in a version after 1.0 was released.

guess the next step is going to be some mechanism that would allow me to force wireless connections to have to connect to a vpn in order to send any traffic … then WEP wouldn't matter at all.. (any hints on the best mechanism to do this would be appreciated Cheesy )

setup ptpp server on pfsense
block all trafic on wireless interface
open all trafic on ptpp clients interface

now you can only internet true vpn

You can't block traffic with source=destination subnet. This traffic doesn't pass the pfSense. In fact you have to allow traffic between the wireless clients with that option but beyond that it's not a pfSense issue.

You first have to assign the wireless interfaces. You can do that from the shell menu or from the webgui at interfaces>assign. You should have ath0 and ath1 assigned to an OPTx interface each. Then simply go to interfaces>OPTx and configure your wireless settings there. You will have advanced settings if the interface is wireless (like ssid, wep, wpa, mode,…).

Try to get an atheros based card: http://madwifi.org/wiki/Compatibility

Going to reuse this old post. I didn't use my Wlan that much when i started this post so i let it be nonworking, but now i want to get it to work again ;)

This is the issue:

When i use the webGUI i do: Interface -> Assign -> (+) -> Then i get a "OPT1" and can chose from sis0, sis1, sis2, ral0 the lates one (ral0) is my wlancard so the machine have found it, but when i got the Wlan tab i cant chose that card there only sis, sis1, sis2…. =/

Why is this? Is my wlan card not supported?

edit btw i upgraded to latest version of pfsense now, RC2

Appart from all the right directions contained in lsf's post I would add that you should house all of your wifi equipment in a meticulously shielded, preferably aluminum, box.

Interference first becomes evident by blocking your front-end via the antenna input path.
When you are done with this, a RF band pass filter is not a luxury in your case in my opinion, it will still reach and de-sensitize your wifi receiver through other paths.

One last advise, if you are deploying point-to-point links use the most directional antennas you can afford with the best front to back ratio you can buy.

If you look at your card spec. you will see why it is like this:

Example spec.

@54mbit A output = 13dbm
@6mbit A output = 18dbm
etc. etc.

Then dbi to mw:
13dbm = 20mw
18dbm = 63mw

so txpower = max power the card can handle.
txpowmax = max output in current mode.

If you need 24 db EIRP then you need to calculate your output, meaning radio output in mw - convert mw to db, subtract any insertion loss / connector loss / filter loss /spiltter loss /cable&pigtail loss etc. then add antenna gain.
For the 400mw cards this will not be correct. they do not show output power in mw, but rather output power in mw +10dbi (astleast some do this). so mw to dbi +10dbi -"whateverloss" +antenna gain = dbi
then you can do dbi to EIRP ( www.e-zy.net is a nice place for wireless calculators )

@lsf:

None of those cards are supported by freebsd.

Ok…  :'(
Thanks for the reply

I think one of the devs has a RAL somewhere that worked. I'm not sure if all modes (like hostap) are supported though. We provide all nicdrivers that are officially supported by freebsd but recommend using atheros chips in general as they support the full set of features (WPA, AES in hardware, hostap, …) and are used by the devs.

Thanks hoba for your quick reply. I have gotten it to work and it works very well. I am seriously impressed with pfsense. I believe that my WEP problem is related to the webgui problem discussed here…http://forum.pfsense.org/index.php/topic,770.msg8676.html#msg8676 . What I ended up doing was switching authentication from the default 'open' to 'shared' at which point I saved the setting and then changed it back to 'open' and resaved the setting. After I renewed the ath0 everything worked fine. I am not sure if this bug is being addressed but the behavior is consistently broken (I tested it three times with fresh installs each time.) It is however, a minor detail in an otherwise amazing product. Thanks to all for your hard work.