Thank you for the links.

I think that we only need 3 if I understand everything correctly.  2 inbound from ISPs and 1 outbound to the network?  Maybe 2 outbound not entirely sure yet, I have not gotten far enough in my reading.

Sullrich you the man

Thank You Muchly

Regards

MD

Thnx
I'll update the firewall.

Actually it's not that complicated. Add the 2 interfaces and configure them (either DHCP or static assignments with gateways). Then just add these to the pool that you already have. That's it (unless you want to work with more than one pool or want to use failoverpools now or whatever).

Please you help will be highly appreciated.
Thanks

Turns out the cause of this was the bridging was not working as anticipated; I was under the impression that bridging an interface with another effectively gave you a layer 2 connection between the two ports. Moving the computer from the bridged port into the port the bridged port was bridged with resolved this.

Excellent Thank You Very Much for the Reply

Best Regards

MD

The default gateway will always be and stay at WAN. There is no option in the gui to change this. This has nothing to do with loadblaancing or policybased routing btw. These features are handled by pf.

Many thanks for your soon answer, I'll try to setup this.

PPPoE will work with loadbalancing when configured in 1.0.1 release. The lates snapshot can't use PPPoE currently as poolmember as we changed the logic of the poolgeneration. This needs fixing atm.

m0n0 can do mulit interface shaping. We tried to integrate the m0n0 shaper to have an alternative but atm it looks like dummynet and pf have issues in freebsd. However, there is also a bounty to make the pfsense shapewr multi-interface-capable (see http://forum.pfsense.org/index.php/topic,2718.0.html ).

Turn on the static route filtering option at system>advanced.

If you don't have WINS, Netbios names resolve via broadcast, which will not cross a router from one subnet to another. Either setup WINS on a server on each subnet and point them to each other as push-pull partners, or just use DNS names as others have suggested. I suppose you could populate the LMHOSTS file and distribute it, but that is an ugly hack that would not scale well.

Yes you can do this with pfsense, you need to update build 1.0.1 though to get balance with failover working.  I am assuming you only want to use 1 IP address on the cisco box  :)

I am currently running 1.0.1-SNAPSHOT-02-14-2007
built on Sat Feb 17 07:44:14 EST 2007

The wiki at http://doc.pfsense.org/index.php/Multi-Wan/Load-Balancing tells you how to do it.

local log will not survive a reboot

can you verify this by looking at /tmp/rules.debug ?

xl1 - WAN 212.1.2.41 gw fixed with 213.1.2.146
xl2 - OPT1 213.1.2.146 gw fixed with 213.1.2.145

you have a loop between xl1 and xl2
the gateway for xl1 is wrong
you enter a ip of xl2 but the xl2 ip is not on the xl1 site

Try upgrading and redo the load balancing pools.

If I understand you right xplozia, then you can do this with pfSense - see here http://doc.pfsense.org/index.php/Multi-Wan/Load-Balancing for load balancing, with this set up you can also make particular traffic (to an internet server, or from a local server) favour a particular connection.

Note that to get this you need the 1.0.1 iso disc, and then update to mid jan or later snapshot - I'm currently running on 9th Feb snapshot which works mostly OK for me.