Thank you very much for that additional information.  My biggest problem is right now that even from Shell I can not force the rate down and am confused if this is a glitch in FreeBSD or an issue because the driver is using an NDIS wrapped driver so we can have CCX support in the drivers as there are no open sourced drivers with CCX support.  As mentioned the "ifconfig -m" shows it as an optional media and mode and if I set the AP down to that media/mode only then it connects like that but otherwise it will only try to connect at the max the AP is offering. Does anyone else have any suggestions on why I can't even force the media/mode down from Shell directly?  If I could get this to work I could write it into the .xml file and load it.

Not sure about this driver as the command that you reference only applies to atheros chipsets. Maybe someone else knows something about urals.

Feel free to add this if it's bsd licensed. the popup code is still existent i think. Just eneble it again and add the new keygen code if you like.

The atheros chipset has a max ack/cts timer setting that will allow about 230km. The setting util in pfsense will allow for about 40km max. But that calc is not accurate.

this is my states while pinging and trying to connect to google.com I guess this means it isnt a NAT issue ? Proto  Source -> Router -> Destination                                          State    icmp 64.233.187.99:58624 <- 192.168.0.20                                         0:0 icmp 192.168.0.20:58624 -> 72.186.197.246:43117 -> 64.233.187.99       0:0 tcp 209.85.165.104:80 <- 192.168.0.20:49248                       SYN_SENT:ESTABLISHED tcp 192.168.0.20:49248 -> 72.186.197.246:57479 -> 209.85.165.104:80                                                                                                       ESTABLISHED:SYN_SENT

There is no WDS support at the moment. and afaik, there is no way to add it either, the closest you will get is with OLSR.

I haven't change my snapshot after it worked fine and this is what I curently have: Uptime: 17 days, 02:05 Wooosh!!! Run, baby run! :))) GJ!

@mani99: Won't it be supported in FreeBSD 6.2 like jeroen234 said? According to http://www.freebsd.org/releases/6.2R/schedule.html the expected release date of 6.2 is in 5 days. When is the next release of pfs planned? /Máni Check the FreeBSD release engineering docs.  6.2 is not even out yet!!

Go to diagnostics>edit and open "/usr/local/www/interfaces_wlan.inc" Then search for  "Allow  intra-BSS  communication" and remove the "" around that codeblock and save. This will bring back the option in the webgui.

another problem might be: Interfaces –> WAN --> Block private networks When set, this option blocks traffic from IP addresses that are reserved for private networks as per RFC 1918 (10/8, 172.16/12, 192.168/16) as well as loopback addresses (127/8). You should generally leave this option turned on, unless your WAN network lies in such a private address space, too. since your WAN lies in such a private address range you have to uncheck this checkbox

Try http://pfsense.com/~sullrich/1.0.1-SNAPSHOT-12-14-2006/ . These images are based on a newer freebsd version.

Pigtails, connectors and such are not necessarily working on 5.X even if they work great on 2.4. A lot of connectors have different specs. Be sure to get wires/connectors/pigtails that are made for operation up to 6ghz, or you might find yourself in all sorts of weird trouble. And if you keep testing with 2.4 antennas on the same cables you might find yourself even more lost  ???, since everything seems to perform nicely on 2.4  :-\

Our installers are still very new to wireless, especially regarding precision directional placements; perhaps more training and practice are in order.  Thanks for sharing some experiences aldo!  -pc

I'm not really in a position to test this, i'm located in .no and does not have the service available to develop and test. The previous work was done by having RDP access to a winXP PC and a FreeBSD unit with EVDO card. I think this work is better suited for someone that can have hands on access to a test system. It's very timeconsuming to work with someone else in a completely different timezone, and depend on that person to be able to fix stuff when I break stuff during testing (like the FreeBSD/pfsense setup not booting after new kernel compiles). If someone could provide a test setup where I can have access to a IP-reach KVM system, then maybe it can be done easier. But it's still not ideal. $$ allways makes it more interesting, but i still think this task is better suited for someone else. You can start a bounty thread and see what kind of $$ you can raise, if it's enough then someone (me perhaps) will most likely make it happen.

@sullrich: Try the latest snapshot from http://www.pfsense.com/~sullrich/ If this still has issues then post a message to the FreeBSD-mobile list. have been attempting to clarify the issue well enough to be able to post on freebsd-modile list. have tryed the 6.2 snapshots with no change. am presently trying to work out how to add the newest ath_hal into a build. but this is definately proving to be a difficult learning curve will post outcomes when i have any more information

The ATH cards has AES built in, WPA itself is provided by hostapd/wpa_supplicant. So setting up WPA with AES only should not steal much, but if you are running close to the HW limits, then hostapd/wpa_supplicant might become a problem.

i have same problem for 3 months now, but my link is stable and works fine. (cant ping computers on lan, and wifi clients cant ping aeach other, while lan computers can ping wifi clients) it seems that problem is in freeBSD bridge driver, something is wrong… i thingk guys will fix that...  ;)

Wireless users have to use the OPT1-IP as gateway. Simply set up a DHCP Server for the OPT1 at services>DHCP server, OPT1 tab. Then create a rule at firewall>rules, opt1 similiar to the default pass rule that is already present at firewall>rules, lan.

I've checked the instructions for the WAP, it looks like it will only work as a bridged unit with one particular router (!?). Looks like it's nothing to do with pfSense and therefore (unless anyone knows a way round this problem) this thread can be ignored

Also asked and answered before. Search the forum.