It's working fine for us.  We have dual radio nodes…11a for backhaul and 11g for distribution.

…"how should I design this szenario. Should I use the AP ? Where should I put it to?"...

Do you want the linksys and the pfSense system to both be wirelessly directly connected to your mesh?  And, they will be in separate locations?  Otherwise, if they are near each other, only one needs to be on the wireless mesh and functioning as a wireless "AP"; thus, the second unit would be connected to the first via ethernet/wired.  So, configure routing as normal, and add an HNA route announcement in OLSR for the second unit's IP & netmask.

Freifunk/olsr for Linksys WRT54GL...
http://212.222.128.68/sven-ola/ipkg/g+gl/
To also use it as an "access point", update it with this package: "freifunk-dnsmasq..*_mipsel.ipk" from...
http://212.222.128.68/sven-ola/ipkg/packages/

If you want wireless dhcp to Not use NAT and serve "real routed" IPs to local wireless clients then ssh (or PuTTY) into your linksys, you'll need to backup copy and delete /etc/dnsmasq.conf then recreate it because it's just a reference to a rom file, edit /etc/dnsmasq.conf with "vi" editor and add an extra "dhcp-range" line for device "wlnat" and configure the desired dhcp IP range and netmask (restrict range to your node's IPs) for wireless clients, also comment out lines begining with "address=", and if you set up "olsr nat" in the gui then erase it.  [update] Newer versions may require DNS server IPs to be specified in dnsmasq.conf.
If you need more help check the Freifunk mailing list…
http://freifunk.net/pipermail/wlanware/
Translations...
http://translate.google.com/translate_t
http://wiki.freifunk.net/Freifunk_Firmware_%28English%29
http://freifunk.net/wiki/FreifunkFirmwareEnglish

As for OLSR on pfSense:
sample olsr & dnsmasq configs...
http://forum.pfsense.org/index.php/topic,677.msg8294.html#msg8294
plus add startup shell scripts such as these for olsrd & dnsmasq ...
http://forum.pfsense.org/index.php/topic,677.msg8180.html#msg8180

thanks for the reply hoba!

If it's prism 2 based and you find the correct firmware to make it operate in AP mode, then it should be found by freebsd. If it's PrismGT or somthing along those lines then it will not work. In general old prism cards/prism cards in general are not recommended. Try to get your hands on something Atheros based.

In my case nothing is working. I tried ping, windows remote desktop, file sharing (but I can see the computer in the workgroup)….
After I reset the settings to default it is working!!!!

If I upload the Traffic Shaping settings than the WLAN clients won't see each other. I uploaded the other setting and it working good. (I have to reconfig the Traffic Shaper, arh!)
I have the problem. I made a WLAN Traffic Shaping rule (WLAN<->WAN High priority). If I delete this rule than the client can communicate each other!!!!!!!!!!!! (Moreover this rule do not work)

And I found another bug in RC3: If I delete a rule in the Traffic Shaper than the Apply Changes button won't appear.

Make sure you are using the correct mode (most likely infrastructure) with the wificard. Also note that 48 MB RAM is not enough RAM. We only support systems with at least 128 MB. Below that amount of rum you can encounter unpredictable problems due to processes not starting or randomly killing services.

ok so theres no chance to get in running? :(

hi,
canyon wf 511 on rt 2561 is not detected on pfs RC2, how this can be fixed? or can it be fixed at all?
i see there are drivers but i cant found any tutorials
thnx

machine is
intel p4 1.7
intel mainboard
256 ddr

::) 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.