From: Alexander Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Multi-path routing only using last nexthop in default
Date: Tue, 17 Jan 2006 04:16:22 +0000 [thread overview]
Message-ID: <20060117041622.GD10902@samad.com.au> (raw)
In-Reply-To: <2af436490601161759l3a452733s7bc93c14fde96b09@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2509 bytes --]
On Mon, Jan 16, 2006 at 08:59:32PM -0500, Jody Shumaker wrote:
> I found that for ppp devices, i should ony define the next hop with the
> dev, not a via. However this still didn't fix my problem, but I've narrowed
> down my problem a little further.
>
> # ip route get 66.189.123.136
> 66.189.123.136 dev ppp0 src 71.248.183.244
> cache mtu 1492 advmss 1452 metric10 64
> # ip route get 66.189.123.137
> 66.189.123.137 dev ppp0 src 66.189.76.198
> cache mtu 1492 advmss 1452 metric10 64
doesnt the second ip r g just show you what you have in the route cache,
when I try it on my multi home machine
default metric 5
nexthop via 141.168.16.1 dev eth0 weight 3
nexthop via 220.233.1.45 dev ppp0 weight 4
but this might be because I don't have the round-robin patch applied to
the kernel.
>
> It does properly do a 5:1 round robin choice , but only the src changes, not
> the dev. The above I believe should really have outputted for the second
> route:
> 66.189.123.137 dev eth1 src 66.189.76.198
> cache mtu 1492 advmss 1452 metric10 64
>
> I'm not sure what is wrong with my config, as I've gone over and over it. My
> best guess is that something is wrong in the kernel I compiled with the
> patches.
>
> # ip rule show
> 0: from all lookup local
> 50: from all lookup main
> 201: from 71.248.183.244 lookup 201
> 202: from 66.189.76.198/22 lookup 202
> 221: from all lookup 221
> 32766: from all lookup main
> 32767: from all lookup default
>
> # ip route show table main
> 10.9.44.15 dev ppp0 proto kernel scope link src 71.248.183.244
> 192.168.100.0/24 dev eth1 proto kernel scope link src 192.168.100.2
> 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1
> 66.189.76.0/22 dev eth1 proto kernel scope link src 66.189.76.198
> 127.0.0.0/8 dev lo scope link
>
> # ip route show table 201
> default via 10.9.44.15 dev ppp0 proto static src 71.248.183.244
> prohibit default proto static metric 1
>
> # ip route show table 202
> default via 66.189.76.1 dev eth1 proto static src 66.189.76.198
> prohibit default proto static metric 1
>
> # ip route show table 221
> default proto static
> nexthop via 66.189.76.1 dev eth1 weight 1
> nexthop dev ppp0 weight 5
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-01-17 4:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 1:59 [LARTC] Re: Multi-path routing only using last nexthop in default Jody Shumaker
2006-01-17 4:16 ` Alexander Samad [this message]
2006-01-17 5:37 ` Jody Shumaker
2006-01-17 19:23 ` Alexander Samad
2006-01-17 21:53 ` Jody Shumaker
2006-01-18 2:13 ` Alexander Samad
2006-01-18 2:22 ` Ciprian Constantinescu
2006-01-18 4:59 ` Jody Shumaker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060117041622.GD10902@samad.com.au \
--to=alex@samad.com.au \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.