Re: [LARTC] Multiple uplinks, ssh connections hang

["Denny Zulfikar" <dennyzulfikar@gmail.com>]

Hello korey,

I don't think your configuration will work well, because there're
balancing using "weight" connection. So, if you have
connection-oriented-application that must sure passing their traffic
only from one connection (such as ssh and https-please try to test
open and login to hotmail.com), it will fail when the default routing
switch from one gateway to another (round robin).

Dont use this config for connection-oriented application. it's round
robin rule, that will switch  from one gateway to another without
notice/know about traffic type.
"ip route add default scope global nexthop via 192.168.200.1 dev eth2
weight 1 nexthop via x.175.244.1 dev eth1 weight 1"

please refer to this documentation howto develop multpile internet
connection gateway.
http://linux-ip.net/html/adv-multi-internet.html

Best Regards,
Denny Z


On 2/27/07, Korey O'Dell <korey@zaneray.com> wrote:
> Folks,
> Ive got two ISP connections that I am using with:
> ---
> ip route add 192.168.200.0/24 dev eth2 src 192.168.200.11 table connection1
> ip route add default via 192.168.200.1 table connection1
>
> ip route add x.175.244.0/24 dev eth1 src x.175.244.2 table connection2
> ip route add default via x.175.244.1 table connection2
>
> ip rule add from 192.168.200.11 table connection1
> ip rule add from x.175.244.2 table connection2
>
> echo "Enabling load balancing between ISP connections..."
> ip route add default scope global nexthop via 192.168.200.1 dev eth2
> weight 1 nexthop via x.175.244.1 dev eth1 weight 1
>
> iptables -t nat -A POSTROUTING -o eth1 -j SNAT --to x.175.244.2
> iptables -t nat -A POSTROUTING -o eth2 -j SNAT --to 192.168.200.11
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc