From: Pierrick Hascoet <pierrick.hascoet@hydromel.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath routing problem.
Date: Tue, 16 Oct 2001 06:50:55 +0000 [thread overview]
Message-ID: <marc-lartc-100321503606398@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100316591327333@msgid-missing>
On Mon, 15 Oct 2001, Julian Anastasov wrote:
> > ip route add default nexthop via <gw0> dev eth0 nexthop via <gw1> dev eth1
> >
> > default
> > nexthop via AAA.AAA.AAA.AAA dev eth0 weight 1 dead
> > nexthop via BBB.BBB.BBB.BBB dev eth1 weight 1
>
> Is the eth0 interface down?
No, the eth0 interface is up and working correctly, i can ping the router
which is directly connected to eth0.
Best regards,
Pierrick.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-10-16 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 17:11 [LARTC] Multipath routing problem Pierrick Hascoet
2001-10-15 18:41 ` Julian Anastasov
2001-10-16 6:50 ` Pierrick Hascoet [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-16 10:34 [LARTC] multipath " Logu
2006-02-07 1:23 [LARTC] Multipath Routing Problem Charlie Meyer
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-100321503606398@msgid-missing \
--to=pierrick.hascoet@hydromel.net \
--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