@GruensFroeschli: @nixgeek: I didn't want the DSL to be the primary WAN by default. Only to be used for failover, or for specific traffic. Guess I will have to wait. You dont need to have WAN as default. Default is what you define as default in the firewall rules on LAN-tab. Just set your OPT1 as default… Exactly, the WAN is only the default and not easily changed for traffic originating from the firewall itself (which in a normal policy routing configuration isn't much - DNS forwarder if you use it, and NTP if you use servers on the Internet).

http://doc.pfsense.org/index.php/MultiWanVersion1.2 Please search before asking…..

Thanks Pootie, Can't tell you what happened but it suddenly started working…. But it is and looking good so far. I don't have that under advanced tab at all... I did upgrade to latest release recently. I know it was there ounce upon a time. Also RRD graphs seem to of stopped since upgrade. Think I should "re-upgrade"? Support and help here is great! Next step to do though is to get WAN 1 as my prefered connection and try get more traffic down there. Any suggestions? I did use the guide originally. Helped a lot. Thanks

If you have checked previous reply and still have a problem: When an interface goes down, what does load balancing - status report? If it reports both down then you prob ably have your monitor IPs the wrong way round.

great it work now!! i put the correct Firewall Rules    and i works! loadbalancing and failover

i did read your whole post. you want DNS-failover. you might want to take a look at the DNS-server-package / DNS-Server-testing area. http://forum.pfsense.org/index.php/board,41.0.html

I have delt with this to a great degree. With FTP it is best to force FTP through 1 pipe or the other.  I found that with "passive' FTP connections the load balancer pushes port 21 out 1 pipe and then the other ports try to connect on the other pipe.  The remote server doesnt like this obviously. Some services do this.  I have no idea if there is a fix or not.

I see… but I'm not in a hurry with that balancing, so If there a chance that I can do it through the GUI in the next version, then I will wait. I just don't have such an easy access to that PC running PFSense, so I prefer the method with not having to take the flash card out of that PC. I would also prefer having my settings left intact after upgrade. Nevertheless thank you very much.

What do you have on the Status>Load Balancer page?  Does that show the WAN2 connection to be up? If that is shown to be down (even though you can send traffic through it) then it means that the monitoring is done wrong.

Thank you.  It turns out that the problem was with my ISP's server configuration.  All works now.

@Pootle: What is the IP configuration of your media centre PC? (IP address, net mask, gateway address, DNS address(es) What is the IP configuration of a wireless device? I assume your WRT54GX is not connected to the internet.  Is this correct? (as it is connected to the LAN side of your pdSense box). Regards Pootle in conf 1: My mediacenter Pc is configured with dhcp (static IP defined in dhcp server of pfsense). My wifi laptop get its dhcp lease thru the pfsense dhcp (static IP defined in dhcp server of pfsense) Wan port of wrt54SX is not connected to anything. in conf 2: My mediacenter Pc is configured with dhcp (static IP defined in dhcp server of pfsense). My WRT54GX is connected to my pfsense lan thru its wan interface and get a static IP defined in dhcp server of pfsense My laptop gets its IP from the WRT54GX. Both configurations give me the same results. I prefer conf 1 as I have one less routing so one less latency impact. The fact is that packets coming from Wifi laptopto the lan NIC of pfsense are not sent to my numericable WAN equally as is sent a packet coming from my PC mediacenter (or coming from the same laptop wire connected to any of the three switches in 100Mb). 'Free ISP' take care of both kind of packets whereas numericable does not.

oops, sorry for the last post. didn't bother to check the actual mask.  :-[ I did put in ip 192.168.79.187/22 and gw 192.168.76.1 for my OPT2 (OPT 1 is being used) and it is accepted fine on my machine. Maybe you have typo somewhere? If you have a space in the ip address field, that will also get the address rejected. I am using pfSense 1.2RC2

This will not work in pfSense.

You should be using http://doc.pfsense.org/index.php/MultiWanVersion1.2 if your pfsense verision is 1.2

Problem solved, I think.  It looks like the problem was with DNS.  I disabled the "Allow DNS server list to be overridden by DHCP/PPP on WAN" check box.  I'm not sure why I had to do that, but once I did and rebooted the machine, things started working.

Unless someone has done some serious work, squid cannot be used with load balancing…

erk, thats a bit wierd, which build are you using? (I'm currently on 1.2-RC2 built on Thu Aug 16 06:18:09 EDT 2007) Also the guide you need to use is http://doc.pfsense.org/index.php/MultiWanVersion1.2 for pfsense 1.2

wjs, yes if you put 1 modem behind a nat'ing router so they are (as far as pfsense is concerned) on different subnets, then load balancing should work quite happily, but you will need to find different monitor IP addresses for the 2 connections.