@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 ?

MAC-Filtering does not work with my atheros-card…

or it's because i noted the MAC like xx:xx:xx:... in the files, but it should be correct, or not ?

Glad I came across this thread before I posted my problem!!  ;)

I was having similar problems like "namviet": On my laptop (WinXP) I was able to surf using LAN, but no luck using WLAN!!  >:(  In addition, through WLAN I was not able to ping my gateway (192.168.1.1)  and yet I was able to access the web interface and make any changes that I needed to make without any problems.  ???  I even had my NIC "disabled" when I'd have the wireless NIC "enabled", and vice-versa (to avoid any possible conflict).

I know it's weird and doesn't make sense.  And yes, I did have the firewall rule setup for the WLAN.

Thanks to "Perry" and the pic he included, I realized where my mistake was…..in the firewall rule for WLAN I had the source as "LAN Subnet" (fyi, I had also tried "any", which obviously didn't work) and not "WLAN Subnet".  This was the difference maker for me.  Such a mistake had me going in circles.

Thanks again and hope this helps whoever is running into the same problem.

yep, now I'm feeling silly, forgot about one interface, the on board one, so, yes, the wifi card isn't even recognized.

I guess I should pick up one of these atheros cards I've seen mentioned around here.

Hi,
  Just to clear all doubts I have tryed with all channels. No luck.
Auto 1,2,3,4,5,6,7,8,9,10,11,12,13

Khufu

Thanks for the reply.
I hope it is done.
Interface bonding and n class interface cards make for exiting days ahead.
The wimax forum has caged us up from the speeds and distances they can run in the licenced bands by not ratifying N or releasing good candidates into the unlicensed markets.
Compared to b/g/a this is a slow train coming.
Pfsense is a excellent platform for this kind of development
An entire branch of revenue generation would be opened up for a WISP product that could smoke a LOK box.

Regards

Well… Possible reason for your problems is your router from Ebay.... Here what you can try to check it:

1.Try changing working frequency on router
2. Try to access router from different computer, and work through it for several hours, if it drops frequently, then most likely it is your router.