From: Paul Evans <pevans@catholic.org>
To: lartc@vger.kernel.org
Subject: [LARTC] equal cost multipath
Date: Wed, 19 Feb 2003 11:15:24 +0000 [thread overview]
Message-ID: <marc-lartc-104565353710118@msgid-missing> (raw)
Hi again :-)
Ok, I have now learned how to make that work. Learning this via ssh on a dial
up connection has been a bit of a trial to say the least. I only managed to
make 5 experiments in that time, because, of course, whenever I was wrong,
I'd lock myself out...
Simply, I have 3 dsl lines, and I wanted to multipath two of them. One 2MB
xdsl line was all mine (ppp0) and, for trial purposes, the other came off of
a switch from an existing NT router. For a week and a half I couldn't tell
any diff between my set up and known setups from this list (thanks William et
al.).
In the end, I had to be *told* the ip of the NT router and then it worked no
problem: I had been using the wrong ip :-(
I will hard code it for now, because ultimately I will just be grepping for
pppx's (when the NT router is replaced by this), but I really wonder how I
could have discovered it.
I saw these:
Destination Gateway Genmask Flags Metric Ref Use Iface
148.235.145.81 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
66.181.42.64 0.0.0.0 255.255.255.224 U 0 0 0 eth1
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
172.36.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 148.235.145.81 0.0.0.0 UG 0 0 0 ppp0
148.235.145.81 dev ppp0 proto kernel scope link src 200.67.64.110
66.181.42.64/27 dev eth1 scope link
10.0.0.0/24 dev eth0 scope link
172.36.0.0/16 dev eth2 scope link
127.0.0.0/8 dev lo scope link
default via 148.235.145.81 dev ppp0
The ip I needed was 66.181.42.68 to get out on eth1. How can I discover that
without being told?
I've typed ip xxx so often that I now understand the wisdom behind allowing
all those short forms, I've read the cref.ps, lartc and stef's site etc., but
I must be missing some ls command somewhere...
--
Regards, Paul Evans
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-02-19 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 11:15 Paul Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-23 11:13 [LARTC] equal cost multipath Alexander Trotsai
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=marc-lartc-104565353710118@msgid-missing \
--to=pevans@catholic.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox