Re: [LARTC] Multipath, 2.4.16 + Julian's patches.

From: Adrian Chung <adrian@enfusion-group.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath, 2.4.16 + Julian's patches.
Date: Fri, 14 Dec 2001 15:00:34 +0000	[thread overview]
Message-ID: <marc-lartc-100834209714723@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100831072321841@msgid-missing>

On Fri, Dec 14, 2001 at 01:45:43PM +0200, Julian Anastasov wrote:
> > 50:     from all lookup 50
> 
> 	Adrian, check ip rule 50, the target should be main. Try
> all paths with ip route get ...

Okay, my mistake...  I modified rule 50 so that the target is now the
'main' table which the kernel seems to populate.

My rules look like this:

[root@wolverine /]# ip rule ls
0:      from all lookup local
50:     from all lookup main
201:    from 216.187.106.224 lookup 201
202:    from 24.112.58.139 lookup 202
222:    from all lookup 222
32766:  from all lookup main
32767:  from all lookup default

And main is:

[root@wolverine /]# ip route show table main
192.62.100.1 dev eth0  scope link
24.112.58.139 dev eth1  scope link
216.187.106.224 dev eth2  scope link
216.187.106.128/25 dev eth2  proto kernel  scope link  src 216.187.106.224
192.62.100.0/24 dev eth0  proto kernel  scope link  src 192.62.100.1
24.112.58.0/23 dev eth1  proto kernel  scope link  src 24.112.58.139
127.0.0.0/8 dev lo  scope link

The other rules are unchanged from my previous mail.

The weird thing is, even with this rule:

[root@wolverine /]# ip route show table 222
24.0.0.0/8  proto static
        nexthop via 24.112.58.1  dev eth1 weight 2
        nexthop via 216.187.106.252  dev eth2 weight 1
default  proto static
        nexthop via 216.187.106.252  dev eth2 weight 2
        nexthop via 24.112.58.1  dev eth1 weight 1

I still get the following output:

[root@wolverine /]# ip route get from 192.62.100.1 to 24.2.9.58
24.2.9.58 from 192.62.100.1 via 24.112.58.1 dev eth1
    cache  mtu 1500 advmss 1460
[root@wolverine /]# ip route get from 192.62.100.1 to 24.2.9.59
24.2.9.59 from 192.62.100.1 via 24.112.58.1 dev eth1
    cache  mtu 1500 advmss 1460
[root@wolverine /]# ip route get from 192.62.100.1 to 24.2.9.60
24.2.9.60 from 192.62.100.1 via 24.112.58.1 dev eth1
    cache  mtu 1500 advmss 1460
[root@wolverine /]# ip route get from 192.62.100.1 to 24.1.2.3
24.1.2.3 from 192.62.100.1 via 24.112.58.1 dev eth1
    cache  mtu 1500 advmss 1460
[root@wolverine /]# ip route get from 192.62.100.1 to 24.112.58.7
24.112.58.7 from 192.62.100.1 dev eth1
    cache  mtu 1500 advmss 1460
[root@wolverine /]# ip route get from 192.62.100.1 to 24.100.155.45
24.100.155.45 from 192.62.100.1 via 216.187.106.252 dev eth2
    cache  mtu 1500 advmss 1460

The last one is going out via eth2, instead of eth1, even though eth1
is still up?

My IPtables rules are set up as:

        /sbin/iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
        /sbin/iptables -t nat -A POSTROUTING -o eth2 -j MASQUERADE

If that makes any difference?

--
Adrian Chung (adrian at enfusion-group dot com)
http://www.enfusion-group.com/~adrian
GPG Fingerprint: C620 C8EA 86BA 79CC 384C E7BE A10C 353B 919D 1A17
[rogue.enfusion-group.com] 9:57am up 134 days, 1:56, 2 users

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/