Thanks for the help.

thanks,
that helped.

@baronsamedi:

@cmb:

Do both of your connections use the same gateway IP?

y what if they did have the same gateway ip? im multiwanning and 2 of my wans have same gateway

Then it won't work for load balancing, it requires unique gateways to policy route. In that case you need an intermediate NAT machine so the gateways differ.

whene i put sticky connection the connexion became non stable
and may client have no connexion
so i don't use it
this  problem is the same for 1.2 or 1.2.1
thanks

I had this very same problem - It manifests in two ways,

You loose DNS when you pull the wan out as GruensFroeschli said, to get round this add an outside DNS server to your DHCP DNS list set your router as DNS 1 and say OPENDNS server as DNS 2. Obviously this only works if you are using DHCP to assign IP's to your LAN.

Second you have the same gateway outside between OPT1 and WAN - this was happening to me because I use the same ISP for both WAN interfaces. both interfaces worked but When I pulled WAN out it would kill OPT1 also. Also in my logs the WAN interface could hear the OPT1 interface broadcasting for an address.

To get round this I plugged my OPT1 modem in to a spare NIC this forced my ISP to give it a new IP and eventually I got one with a completely different gateway, and now loadbalance and failover is working perfectly.

I know this may not be directly the same as your problem but may give you some pointers.

Untitled-2.jpg
Untitled-2.jpg_thumb

Does anyone know how much money it would take to get multiple PPPoe done sooner or 1.3 out sooner, or is it a time and testing issue?

yea it works i was maxing out my upload bandwith and i checked the traffic report and and all of them was 2MB upload and when i got and check my ip website i see all 3.. would the same gateway slow down my torrent speed taht the only place i see it lagging some times?

@Coldfirex:

… For both LANs they my rules are directing to the gateway 'default'.  I have experimented with putting my loadbalance pools as the gateway but I have not been able to get it working.

This has to be the pool, otherwise it points the clients to one gateway only. And if that fails…

In your posted config I saw rules originating on OPT1 to access gateway "Wan2 Failvoer..." and "Wan1 Failvoer..."
I haven't seen those for LAN.

To get it working you should start with a card blanc rule  <allow* from*="" to*="" gateway:pool="">  on both your LAN IFs.

I haven't setup a dual WAN config myself yet. These assumptions are from my understanding of how it should work...</allow*>

Just a side note.  Removing Squid and using the box soley as a router fixes the problem.  Definately a Squid cache issue.  But I require filtering, so either I fix Squid or place a filter appliance between the network and the pfSense box.  Any ideas on the Squid issue not resolving names?

That might be broadcasting problems of NetBios. Can you try to access the shares with the ip directly instead of using computers name and see if the problem exists again?
If not there might be problems with path mtu discovery since file sharing might be sending packet with Dont fragmetn bit set and in pfSense you need to set some scrub rules to remove that flag, though not possible through the GUI afaik.

1: yes
2: yes, but the different WAN's have to be in separate subnets and cannot have the same gateway.
3: it works well for me for bittorrent traffic.

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

System:

Advanced:
If you want to be able to use NAT-mappings from withing your own LAN disable the checkbox "Disable NAT Reflection"

You might have to create a rule with as destination: "globalIPofServer" and gateway * above the rule that forces the traffic to a specific WAN.
But i'm not sure about that.