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.

I kept having intermittent problems so I changed my setup.  I think having OLSR and Captive Portal and Traffic Shaper, etc, running on one machine was too much for it.  So now the computer that was a pure MPR is now an OLSR "access point" of sorts.  I have OLSR bound to WAN, and LAN is bound to the wired LAN card with a cable running to my firewall/router which acts as captive portal, bandwidth manager, and other things.  I have OLSR turned off on the firewall/router computer.

I had gotten everything working good but when I turned on the Captive Portal I had a problem.  The https captive portal page would come up and when I typed in my name and password the browser would try to reach my homepage and then get redirected to the Captive Portal page again.  This happened every time I clicked on the Continue button on the captive portal page.

I finally got it to work by putting the MAC address of the "access points" LAN card in Pass-through MAC.  I also had to put a check next to Disable MAC Filtering under the Captive Portal tab.

Now when I start up my browser and the homepage tries to come up I get redirected properly to the captive portal and then get directed to my homepage after logging in.  Everything seems more stable with this setup.

I've sent you the ip/pwd.

Test's:

http://pr0n.se/wireless-pfsense/

Evidently very shaky when transferring from the soekris.

madwifi compat. list is probably the best source. This can give you some heads up info tho. http://customerproducts.atheros.com/customerproducts/default.asp

The systemspecs should be ok, however you are running an unsupported configuration atm.

You could switch LAN or OPT1 to be the wireless/olsr interface; or, enable the olsr dynamic gateway extension and it will overwrite your default route in the route table.

olsr + dhcp to non-olsr wireless clients (pseudo-AP), combined all on one wireless card…
http://forum.pfsense.org/index.php/topic,2353.0.html

@KiFFuSeR:

I have 3 pfsense machines working with that card as Wan interface doing wireless client type router in a community based setup.

¨
You are right… i tried other box and this card and everything works fine !
Thanks

Wait for 1.2 which will be based on FreeBSD 6.2.  No time table as we are not in control of releasing FreeBSD 6.2.

Got it to work at last…

Reasons for the trouble were two things.

1. The documentation says theres no filtering between bridged interfaces. But I have to set a rule on the OPT1 interface to allow all traffic to all nets like this to make it work (especially for DHCP request).

Proto Source Port    Destination    Port    Gateway    Description  *    *      *      *           *      *          OPT1 -> Any

So there IS filtering between bridged interfaces.

2. Flaky Wlan driver on the client side. Nasty Netgear WG511 PCMCIA Card. Forced it to eat a newer driver for an 3Com Office Connect Card and works now without problems and even has AES support now.

So for all people with the same problem:

If you want to create the following setup:
WAN -> Internet
LAN -> Local wired network
OPT1 -> AP Wireless LAN bridged to Local wired Network
just do the following

-Get your WAN and LAN running. Then go to the OPT1 settings page and set it to be bridged with LAN. Leave the IP configuration for the OPT1 interface to static.

-Setup the remaining wifi stuff (WPA,WEP,Keys etc) and save the settings.

-Next go to the Firewall Rules settings page and click on OPT1 interface. Add a new rule to allow traffic from any to any.

This did the trick for me.

Just in case anyone else is interested the Lucent Hermes chipset cards do not support AP mode in BSD.

http://www.freebsd.org/cgi/man.cgi?query=wi&sektion=4&manpath=FreeBSD+6.1-RELEASE

bummer as that is all I have for cards :)

Interestingly enough my Orinoco BG2000 AP uses this exact same card and works just fine as an AP.

Maybe your card doesn't support WPA2 under freebsd. We don't detect the capabilities of the card concerning wpa2 afaik. You'll find a config script (generated from your gui settings) for the wireless card in your /tmp folder. Try to ssh in to your system and run the script manually. Does it reject some of the options that the script tries to set?

@jeroen234:

if iam lucky i will have sunday 2 senao 11mb wireless cards that use wi0 driver
and 1 atheros card for my soekris box then i will do some tests
i will have then :
wan,lan,opt1,opt2,opt3

sounds great! please let me your test results known

best regards

stop using rc3 its stoneage pfsense
use 1.01 pfsense insted