My Thanks to you Fábio Brit and everyone that has helped me out. In the end it turn out that removing the following line from my script fixed the issue. Why I'm not really sure why this worked, however the changes are as follows for anyone that hits the same issue: ip route add 23.215.3.16/28 dev eth0 src 23.215.3.20 table T1 --->#ip route add default via 23.215.3.17 table T1 ip route add 23.215.4.0/26 dev eth2 src 23.215.4.61 table T2 ip route add default via 24.215.4.1 table T2 ip route add 23.215.16.0/21 dev eth1 src 23.215.17.54 table T3 ip route add default via 24.215.16.1 table T3 ip route add 23.215.4.0/26 dev eth3 src 23.215.4.60 table T4 ip route add default via 24.215.4.1 table T4 Which effectively removed the default gateway setting and made the connection rely on the balancing part of the script: ip route add default scope global nexthop via 23.215.3.17 dev eth0 weight 1 nexthop via 23.215.4.1 dev eth2 weight 1 nexthop via 23.215.16.1 dev eth1 weight 1 nexthop via 23.215.4.1 dev eth3 weight 1 Note: I did adjust the weight values to 1s all around. Initial Speed Tests (Not Maxed) (Connecting to one IP address) eth0 â?? 1177.6 kbit/sec Upstream eth1 â?? 455.0 kbit/sec Upstream eth2 â?? 656.5 kbit/sec Upstream eth3 â?? 1004.3 kbit/sec Upstream I'm going to be monitoring it for the next few days and see how it does. I'll keep everyone updated. _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
