From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Furniss Date: Wed, 12 Jan 2005 11:10:49 +0000 Subject: Re: [LARTC] How to balance OUTBOUND traffic by packet if.. Message-Id: <41E505B9.9060700@dsl.pipex.com> List-Id: References: <1383.192.168.1.2.1105108845@maild.mine.nu> In-Reply-To: <1383.192.168.1.2.1105108845@maild.mine.nu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org junk@maild.mine.nu wrote: > I am still looking for a solution to this problem....... > >>junk@maild.mine.nu wrote: >> >>>Hi, >>>Yes i did give this a try a couple of times before with no success >>> >>> /sbin/iptables -I OUTPUT -m nth --every 2 --packet 1 -t mangle -j MARK >>>--set-mark 0x2 >>> /sbin/iptables -I OUTPUT -m nth --every 2 --packet 0 -t mangle -j MARK >>>--set-mark 0x1 >>> >>> ip rule : >>>0: from all lookup local >>>201: from all fwmark 0x2 lookup 202 >>>201: from all fwmark 0x1 lookup 201 >>>32766: from all lookup main >>>ip route show table 202 >>>default via 212.199.28.244 dev ppp1 proto static src 80.178.89.120 >>>ip route show table 201 >>>default via 212.199.26.111 dev ppp0 proto static src 84.94.148.214 >>>ip route show table main >>>212.199.26.111 dev ppp0 proto kernel scope link src 84.94.148.214 >>>212.199.28.244 dev ppp1 proto kernel scope link src 80.178.89.120 >>>default proto static equalize >>> nexthop via 212.199.26.111 dev ppp0 weight 1 >>> nexthop via 212.199.28.244 dev ppp1 weight 1 >> >> >> >>I must admit I am more into tc than ip so I've never tried it. >> >>My guess is that you need to get rid of equalize/weights as these load >>balance per connection and the routes get cached. >> >>Andy. More things I would try - mark in postrouting, snat to the adress of downlink you want return to use. Get rid of the src adresses in in tables. Andy. _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/