From: Joshua Szmajda <josh@loki.ws>
To: lartc@vger.kernel.org
Subject: [LARTC] multipath routing question
Date: Tue, 04 May 2004 16:21:29 +0000 [thread overview]
Message-ID: <4097C309.1000200@loki.ws> (raw)
Hi All,
I have a linux router, configured with two internet connections and two
lan segments. I've setup multipath routing as described in
http://lartc.org/howto/lartc.rpdb.multiple-links.html
My problem (I think) is that somehow the router will randomly choose
incorrect routing paths for different hosts, for example:
on my workstation (192.168.1.20), I ssh to a server I have on an
external network (157.238.135.60), and my connection locally hangs. On
the router, I search the routing cache:
# ip route show cache | grep 157.238.135.60
157.238.135.60 via 207.180.31.137 dev eth0 src 207.180.31.140
157.238.135.60 from 192.168.1.20 tos 0x10 via 10.14.1.1 dev ppp0 src
192.168.1.1
157.238.135.60 from 192.168.1.20 via 207.180.31.137 dev eth0 src
192.168.1.1
192.168.1.20 from 157.238.135.60 dev eth3 src 207.180.31.140
Compare this to cache entries for a host that does work (157.238.135.90):
# ip route show cache | grep 157.238.135.90
192.168.1.20 from 157.238.135.90 tos 0x10 dev eth3 src 207.180.31.140
157.238.135.90 via 10.14.1.1 dev ppp0 src 151.203.160.233
192.168.1.20 from 157.238.135.90 dev eth3 src 207.180.31.140
157.238.135.90 from 192.168.1.20 via 10.14.1.1 dev ppp0 src 192.168.1.1
157.238.135.90 from 192.168.1.20 tos 0x10 via 10.14.1.1 dev ppp0 src
192.168.1.1
My question is: why does this happen? what can I do to fix it?
Thanks in advance!
Here's some information from my router:
# ip route
10.14.1.1 dev ppp0 scope link src 151.203.160.233
207.180.31.136/29 dev eth0 scope link src 207.180.31.140
192.168.1.0/24 dev eth3 scope link src 192.168.1.1
10.0.0.0/16 dev eth2 scope link src 10.0.0.1
127.0.0.0/8 dev lo scope link
default
nexthop via 207.180.31.137 dev eth0 weight 2
nexthop via 10.14.1.1 dev ppp0 weight 1
# ip rule show
0: from all lookup local
32764: from 151.203.160.233 lookup T2
32765: from 207.180.31.140 lookup T1
32766: from all lookup main
32767: from all lookup 253
# ip route show table T1
207.180.31.136/29 dev eth0 scope link src 207.180.31.140
192.168.1.0/24 dev eth3 scope link src 192.168.1.1
10.0.0.0/16 dev eth2 scope link src 10.0.0.1
127.0.0.0/8 dev lo scope link
default via 207.180.31.137 dev eth0 src 207.180.31.140
# ip route show table T2
10.14.1.1 dev ppp0 scope link src 151.203.160.233
192.168.1.0/24 dev eth3 scope link src 192.168.1.1
10.0.0.0/16 dev eth2 scope link src 10.0.0.1
127.0.0.0/8 dev lo scope link
default via 10.14.1.1 dev ppp0 src 151.203.160.233
Thanks Again,
-Josh
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-05-04 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 16:21 Joshua Szmajda [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-04 2:27 [LARTC] multipath routing question Thiago Vinhas
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=4097C309.1000200@loki.ws \
--to=josh@loki.ws \
--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.