Oh I forgot to post back in here….
Well,  jrmann1999 , what I did was that I set LAN interface (OPT1) to work as LAN(sory for redunducy) and I set ATH0 to work as WAN
Then I wen and diasabled routing and NAT and configured WAN wireless setings. All works fine... oh yea i think u have to config firewall too... dont remember that was half or more yeras ago....

Try authmode open.

Thanks Scott, thanks Hoba

My WIFI PCI Card: Netgear WG311T (Atheros)

What i did the last hour: first i upgraded from BETA4 again to RC2 by executing 'cvs_sync.sh releng_1 && shutdown -r now' via Putty…

Then i followed the advise of Hoba to set the WEP Key to 'open' from shared - that did the trick! WIFI worked on the RC2! But much more Headache i earned as the internet was not accessible at all anymore - reloaded the pfsense, reloaded the Laptop - no chance, even via Ethernet i did not succeed anymore to access the www!

Made a trace, stuck on the pfsense... strange that DNS resolving worked (checked interface status of WAN - released and renewed the IP of my Provider - no effect - no access; however... got rid again of the RC2 and changed to the 'RELENG_1_SNAPSHOT-07-23-2006' - the Trick with the 'open' WEP Key still worked and now the www was accessible again (settings never changed, they were always inherited obviously as i did firmware upgrades via GUI)

So finally i'm glad that everything runs now, am wondering if the GUI shows me the next days again the CPU Load Bar fully up at 100% - even as 'top' says 5% ;-) - if so, i could live with that!

Thanks Guys, i'm going now around to change the hosts config from 'shared' to 'open'  ;D

If you have the ability to test, then this might be of interest: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bluetooth.html

If this can be tested and config files and command strings needed can be provided to me, I'll try to add this to the 1.1 wireless stuff.

It's true that cards/radios that can see eachother will "take turns" but lots of the clients will most likely not see all of them, so your clients will most likely generate "noise" to the other panels/sectors. I'd go with multiple channels or antenna splitters, and for backhaul I'd use 5.X GHz.

Problem was solved.

Solution: donnot use a client program from Planet, I uninstalled this Planet aplication then try connect with WPA-PSK with orignal widnows XP program and it WORKS !

Thanks for the info. I'll just move to a captive portal and mac filtering for the residential. I was planning on having business connections rent our bridges, so it won't matter to use the same encryption key since they won't know the key.

Great!!

Route?  You mean path?  Unix uses /path/to/file.

olsr is a protocol for sharing dynamic routing info
all wirelles cards you have to put in ad hoc mode and use the same sidd and channel
so that there a backbone is forming

olsr will send out info frames so now and then
by with the ather nodes will find there neabors and the how good that rout is and to with nodes that node has access

routes you can enter in the hma of olsr and will then be shaerd on the olsrd mesh
with his you enter only the local routes of a olsr node on iets node
this info will be send out bij the olsr protocol every so manny seconds
olso route info fron other nodes that it haerd will be send so that there can form a route

if a route or node disapeers that on the holle olsrd mesh it will be gone in a few seconds
and a new route will be found if posebole

I have tested the old version of the card and it works fine so you will have to tell me if you have the new version of the card or old.  I have only compiled the europen drivers.

Antennaplacement and cables are important in this scenario. Actually I know there are people using pfSense as wireless relaystations with 2 wireless nics (kind of repeater but with 2 seperate cards and routed). Check your hardwaresetup.

pfSense uses the same HAL as madwifi, but pfSense is FreeBSD not linux, so the driver is not the same. The HAL does support 1 STA + multiple AP (multiple SSIDs) but the driver code for FreeBSD does not. If/when this is added it will most likely be supported in later pfSense versions, but for now this is not possible.

The CM9 does have issues with some pure B clients of older types, this is normally a issue with long/short preamble. And should be solved by getting a updated firmware for the 802.11b card. I do know that some cards have proven dificult in the past, but I don't use any pure B cards regularly anymore. I do have a notebook with a proxim goldcard, but I haven't used it for more then a year now, I might try it with pfsense if I have some spare time in the future. Your best bet would be other cards or updated firmwares.

I just bought a used Linksys WRT54G for $15, reflashed it with DD-WRT firmware and use it as my wireless bridge.  If you're considering this just make sure it's a version 1-4 model, v5 won't work.

It works well enough to stream pretty much any media off my server.

Great, I'll make the order :).

Unless you have reason to believe this is really a DNS tunnel, my bet is that they've just configured OpenVPN to use port 53.  Blocking DNS to servers not under your control should fix the problem.

–Bill

ok, i will try it.

thank you very much !!!! or like one says in my country : Merci énormement ! ;)

The "magic" happens in the /sbin/athctrl.sh script.