On Nov 22, 2007 3:34 PM, Raja Subramanian <[EMAIL PROTECTED]> wrote: > On 11/22/07, Siju George <[EMAIL PROTECTED]> wrote: > > On Nov 22, 2007 12:48 PM, Rajkumar S <[EMAIL PROTECTED]> wrote: > > > On Nov 22, 2007 11:55 AM, Siju George <[EMAIL PROTECTED]> wrote: > > > I am afraid this will not be of any help. By default all packets > > > originating from the box goes via default gateway. Even if the source > > > ip is changed, it will get nated via the default gateway itself. > > > > > With some clever pf settings, you can work around this problem and get > your local daemons go through non-default gateways. This is also done > without using ECMP. > > I've got pftpx working this way and load balancing ftp across multiple WAN > connections on FreeBSD 6.1. Note that pftpx needed some patching to > ensure that the pf rules it generated include "route-to" for the data path. > Since squid does not insert pf rules, squid modifications are not necessary. > > Here is the overview: > > Step 1: run multiple instances of squid, one per WAN interface > > > Step 2: configure squid so that each instance is uses a WAN IP as source > for external connections. By default squid will bind to 0.0.0.0:0 when it > makes an outgoing connection, and the kernel decides to choose the interface > with the default gateway and so the problem. Override this functionality by > explicitly getting squid to use a specific WAN address. > > Eg. Squid 1 will use $EXT_IF1_IP as source address. > Squid 2 will use $EXT_IF2_IP and so on. >
Thanks a million Raja for your reply. You have been a source of immense help to me :-) How do I achieve the above functionality? Are you talking about the "tcp_outgoing_address" option in Squid? Thank you so much once again :-))) Kind Regards Siju _______________________________________________ bsd-india mailing list [email protected] http://www.bsd-india.org/mailman/listinfo/bsd-india
