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.

Thank you very much, it's ok now !

PcEngines is shipping cases with pre-drilled holes (2port has 2 and 3port has 1) since the end of 2005.

I see.  When a laptop that is only capable of 11b in ad-hoc connects, does it also cause all other ad-hoc 11g 54mbps connections to be throttled down to 11b?  Even with odfm=cts/rts?  I have the 11g only checkbox enabled in the pfSense GUI but it still let the laptop connect, presumably because it is technically capable of 11g in AP Client mode.

Thanks very much guys.. I already ordered one.

Some of these vendors sell wireless stuff and all have donated something to pfSense http://www.pfsense.org/index.php?id=40 –Bill

This is not implemented in GUI, but you could use this parameter on command line, and possibly also hardcode it into /etc/inc/interfaces.inc bssid address     Specify the MAC address of the access point to use when operating     as a station in a BSS network.  This overrides any automatic     selection done by the system.  To disable a previously selected     access point, supply any, none, or - for the address.  This     option is useful when more than one access points have the same     SSID.  Another name for the bssid parameter is ap. This will tell the client to only associate to the AP with whatever mac address you specified.

Any chance you use the wrong antenna port ? Also, you might want to try to lower the output power. If the card has a poor rf output it might be generating too much noise. I have not encountered any behaviour like this with pfsense/freebsd, so this is just a guess. You can also try to play with the following sysctls from a shell. dev.ath.0.txantenna: 0,1,2 (antenna port 0 or 1, both=2) dev.ath.0.rxantenna: 0,1,2 (antenna port 0 or 1, both=2) dev.ath.0.diversity: 0,1 (0=disable 1=enable) dev.ath.0.tpscale: 0,1,2,3,4 (size of increment that TPC will use to up/down the power, normally 1 is the best choice, atleast that is my experience) dev.ath.0.tpc: 0,1 (0=disable 1=enable) dev.ath.0.tpack: 63 (ack power) dev.ath.0.tpcts: 63 (cts power) A little more description: dev.ath.0.txantenna: The antenna used to transmit (normally the same as RX antenna) dev.ath.0.rxantenna: The antenna used to receive (normally the same as TX antenna) (A different RX antenna can be used if your regulatory restrictions makes you want to use a higher RX gain antenna to overcome the output limits of your regdomain. An example would be; you can only output 20db E.I.R.P on a long distance link, and to overcome the signal loss you use a higher gain antenna for RX gain, since you are not transmitting at more then 20dbi you can still receive with 36dbi or more if you like too, as the regdomain restriction is normally only applied to transmitting power and not receive gain. This is perfectly leagal in all of the regdomains as far as I know) dev.ath.0.diversity: Switch off and on the use of antenna diversity (normally only used if you have two antennas connected) dev.ath.0.tpc: Switch on or off Transmission Power Control (can be tricky in point to multipoint applications) dev.ath.0.tpscale: Size of the increment that TPC will use to up/down the power, normally 1 is the best choice, atleast that is my experience. A higher scale value will most likely make the link drop if the signal is close to what it needs to be and the TPC is trottled down.) dev.ath.0.tpack: controll the ack power seperatly (normally the same as tpcts) dev.ath.0.tpcts: controll the cts power seperatly (normally the same as tpack) All this will be controlable from GUI in 1.1 (1.0 is frozen so no new features there) EDIT: this info is added to the wiki http://wiki.pfsense.com/wikka.php?wakka=Wireless EDIT2: this info is also added to the doc site: http://doc.pfsense.org/index.php/Wireless_networking_with_pfSense