you need 2x 750 mha for the cards that is 1,5 ah
and 1,5 ah for the wrap
so you need a adapter with at least 3 ah

In what mode does that nic run? In accesspoint mode it should show always link up. In case it's one of the client modes like infrastructure or adhoc it means the accesspoint it was connected went down.

What are the next best few non-atheros mini-pci wireless cards?

Check status>systemlogs for obvious messages. If you can't access your system anymore after this bug occurs setup a remote syslog server to send the messages to another system to investigate later.

If this is a wrap or a soekris make sure your PSU is strong enough to handle the 2 wireless cards. If it is a wrap make sure you have the latest bios. There were some fixes that affect atheros problems.

@hoba:

If you want to unhide it from the gui just remove the two highlighted green lines from the file ( http://cvstrac.pfsense.com/chngview?cn=14890 ) by using diagnostics>edit but it won't work. That's why it was hidden. It's not a pfSense bug but a driver bug in freebsd.

Thanks a lot !! I unhided the setting and enabled it and as far as i can tell it works for me.

The fix already is in the codetree, no need for further information on the situation. This bug does not always appear, so you only need to reboot if the rules are not applied.

Never heard of issues like that yet. Maybe your ISP is a bit "special".

I'm not surprised as my only problems thus far have been with a USB keyboard :) Unfortunately I can only use half height cards in this case, and I haven't found any dual ports that would fit. If that kind of error simply kills the wireless, I can live with it being a little flakey since it's just for Internet connectivity in conference rooms. As long as it doesn't kill the firewall completely.

Which CPEs do you recommend for this? I know Tranzeo is one but are their any others just as good and cheaper?

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

Pete ipro.net, inc. pc@ipro.net

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