@sganarelle:

will i have to change that to 192.168.2.x?

Yep.

really interesting discussion and hoba's answers. thank you all. (while creating loadbalansing pool and using instructions i also thinked that it would be great to improve documentation and to add some texts in the user interface of pfsense)

OLSR is already discussed at http://forum.pfsense.org/index.php?topic=677.75 . Also make sure you are on the latest snapshot when you test this ( it's http://pfsense.com/~sullrich/RELENG_1_SNAPSHOT-07-12-2006/ atm).

You don't need routes for directly connected subnets of the pfSense. Just create a pass firewallrule for traffic with destination this subnet with the gateway set to this WAN.

thanks.

YES that  was it….problem solved.
But for the information i didnt change anything on wrap1, i only changed wrap2 settings and that did the job.

thank you

YEAAAAAAAAAAAAAAAAAAAAA!!!!!!!!!!!!!!!!!!!!!!

thanks to all, specially to hoba.
I solve my DNS PROBLEM, I don't set option Services-> DNS Forwarder -> Enable DNS forwarder

all run ok now

:)

I have the ultimate live-cd version (1.0-RC1) but in this version don't are the new option "USE INTERFACE AS GATEWAY".
I Don't HD and need this option for solve DNS PROBLEM and other bug fixed.

That I can do?

Can't compile new live-cd without this bug?

Tks friends

Loadbalancing requires routing. It doesn't work for transparent setups as it utilizes a gatewaypool.

@hoba:

Actually you CAN do some kind of weighting. Let's say one of your lines is twice as fast as the other you can do that by adding 2 times gateway IP of fast line and 1 times gateway IP of slow line to the pool (you also could do that 5:3 or whatever you like). Haven't tried that myself but heared it was working for someone I asked to try that. Give it a go and report back  ;)

This unfortunately doesn't work due to pf handling route-to's.

"Other" simply accepts the traffic for these IPs where "proxyARP" generates layer2 messages for the virtual IP.

the gateway ip is static.
and pfsense always got the same ip from modem router.

even i try manually set a static ip, the problem persist.

rgds,
rex

Adding this to hostapd.conf should give you what you are looking for. This should work in hostapd 0.4.8 and newer.

rsn_preauth=1
rsn_preauth_interfaces=em0 (layer2 connected interface to talk to other AP's)
The rsn_preauth lines are only for preauthentication of WPA key etc. This provides the client to preauth to the new AP prior to actually associating(romaing to) with the new AP.

iapp_interface=em0 (layer2 connected interface to talk to other AP's)

@hoba:

Not with pfSense 1.0 but a feature like this will be in the next version (not yet implemented).

failover wan won't work unless you have load balanced wan right now.  I might talk hoba into setting this up during our hackathon so we can get this working.

–Bill

@ribes:

@sullrich:

This feature was recently MFC'd and had been forgotten.

If this is a full installtion then issues these commands from a shell to update:

cvs_sync.sh releng_1

Is there a way to try this on an embedded platform?

No, you only could use diagnostics> edit file from the webgui to replace the file the changes were made:
http://cvstrac.pfsense.com/chngview?cn=12705

Yes.  Be sure to visit the faq and query about ftp and such.  There are a few limitations for multi-wan but it should mostly just work.    Sounds like your 3 wan is really just a LAN, btw..  So you may be only needing 2 WAN's.

We do not route either of them from what I know.  At this point you will need to dive into the code and prove me otherwise.  It doesn't work, period.

From the frontend yes and it also is presented this way in the created ruleset, however the roundrobin still is used without weighting. We did some tests with that and billm did some debugging and knows why it is not working. This behavior can't be changed atm.

If you want HTTPS and SMTP on one WAN only make sure it is one of the reliable ones. We don't have interface failover (if WAN dies use WAN2 for example) in pfSense 1.0. This is something that already is worked on in HEAD. The poolfailover however will work.

There are also some (poorly written) webservices that won't work with plain HTTP or other protocols and multiwan. You should add an hosts alias for these destinations to add IPs to when you encounter problems and send these out one of the WANs only by creating a rule for this alias destination.

I don't clame to be the smartest person about OLSR but it sounds like that is a bug….  It shouldn't be adding "distant" routes to your node?