Ok, that is most likely my problem then. I used the IP address for Google as the monitoring IP for both. I'll change that when I get home from work and see how it goes. Thanks! -Alex

Solved using this procedure: 1-Leave DNS forwarder enabled. 2-Place DNS in  Services->DHCP server for OPT1. This allows correct host name resolving 3-NOT allow DHCP on wan to override DNS set in System General Setup. 4-Add a rule to allow acces from OPT1 to 15.0.0.1 (OPT1 interface webconfigurator) with Gateway set to default instead of Loadbalancer. Thanks

Haha, guess it was easier to handle than the cisco as you didn't even need a guide to set it up  ;D

You have to add a firewallrule with default gateway for all the vpn destination networks on dual WAN/loadbalanced pfSense or the loadbalancer/multiwan will send traffic directly to the WAN gateways bypassing the internal routingtable. I have the same setup at the office and it'S working fine when these rules are in place. You should move them to the top of your lan rules.

As I said, this is not yet implemented. Patches accepted.

This is a faq. Only connections running THROUGH the pfsense can be balanced. For everything running at the pfSense itself the default gateway is the WAN gateway. So squid can't make use of any gateway other than WAN unless your squid runs on another box inside your LAN.

That project is no longer active.  We took over SLBD code in our tree about a year ago. http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/tools/pfPorts/slbd/

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