If your clients do not find the wireless network then the problem seems to be related to your Netgear WAP.
But since you don't post more helpful informations this is an all chris-tal ball © solution.

7447 tx failed 'cuz FIFO underrun

I found when this happens, my wireless connection drops and reconnects kinda transparently. The result was that traffic goes very high, then dips very very lo and high again. Many spikes while using high bandwidth applications like newsgroups and torrents.

Is this what you ar experiencing?

Thanks I will check it out.

Since this has gone to the topic of DNS, Wireless, and Active directory do you want me to start a new thread involving that somewhere else on the forum.

Thanks
Eckman

@http://forum.pfsense.org/index.php/topic:

If you want to force your clients to send their traffic over the VPN you need to set some custom options:
Please read the following thread for more infos:
http://forum.pfsense.org/index.php/topic,6056.0.html

read the man pages.
i think i remember reading somewhere you have to leave the dev1 out if the server is in the same subnet

In my case WIFI and LAN are different subnets so I think it should be OK (ie routed not bridged).

Thanks for the link to the other topic, some useful tips in there

Dean

Try to create a rule and it should work :)

(keyword: filtering bridge)

You can find the kernel configs here: http://pfsense.com/cgi-bin/cvsweb.cgi/tools/builder_scripts/conf/ you might see what is missing for you to get the card running.

I think you might have missunderstood something, TKIP = Temporal Key Integrity Protocol = an encryption protocol and is supported.
But only with PSK (Pre-Shared Key) what you are looking for is probably EAP-TLS, EAP-TTLS or EAP-PEAP. This has yet to be implemented due to the fact that I don't have much time to finnish it, and haven't had so for a year now. The wireless needs a update and rewrite but someone that has enough time has to do it.

can you do a ifconfig wi0 list caps from the shell and show me the output ?

Try with a switch between.

opt1 –-- switch ---- laptop

also remember a default rule on opt1

You could use the search function of this forum and find this post:

http://forum.pfsense.org/index.php/topic,2237.msg15141.html#msg15141

@sabo:

Here is a link to a post with some basic configuration information.

Remember when setting up WDS  each additional Access Point the bandwidth will drop significantly.

http://forum.pfsense.org/index.php/topic,7341.0.html

Sabo,

Mesh is NOT WDS (although) some think it works the same (grin).

I have not tried configuring a WRT-54 (Linksys) with OpenWRT to run in Mesh mode yet but have done so with PFSense running on three Alix boards - given the Mesh software is basically the same on the OpenWRT implementation and the PFSense implementation it should work fine.

Just a note: WDS (Wireless Distribution System) and OLSR (optimised Link-State Routing) are two completely different animals - WDS is setup as a static-linked repeater system with fixed-path routing where as OLSR (mesh) is a true self-learning dynamic routing-relay system.  The OLSR system is self-healing in terms of repeater hops and optimises itself as to the changing conditions of the radio links (quality).

At some point in the near future I plan on working with the OLSR package on PFSense and the WRT-54 routers to see how robust the system actually is - I can see where such a system would be advantagous in some applications (especially mobile-based systems).

Just some thoughts…

gm...

To setup an Opt1 go to the web GUI and Interfaces->(Assign). If Opt1 doesn't show up from the Assign page then your system is not recognizing your device. If you do see then assign the interface and refresh your page. Then look at the menu and you should now see Interfaces->Opt1 you can configure the interface from there.

THX, it WORKS!!!

And now LAN is also protected from WLAN.

Going to wiki … 8)

Happy Holydays!

It looks like, due to bridging, the arp table isn't populated correctly.
try tcpdump -i bridge0 (or whatever bridgeN corresponds this interfaces pair) and see what's going on when you try to access the web page and are getting a timeout.

watch for messages like "who has arp blablabla" and replies

ifconfig ath0 ?
cat /tmp/ath0_setup.sh ?