From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] failover problems
Date: Wed, 24 Jul 2002 18:47:07 +0000 [thread overview]
Message-ID: <marc-lartc-102753634710854@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102745669304746@msgid-missing>
Hello,
On Wed, 24 Jul 2002, Tobias Geiger wrote:
> Yes. i used 2.4.19pre-10 kernel.
> This behaviour affects only ppp-devices (never tried ippp but i guess it's
> the same)
>
> i also wondered, why failover doesn't work when using different
> route-entries for each nexthop...
Hm, the kernel can not perform failover for NOARP devices
that are always in UP state. It is possible only for ARP devices
and for default routes with same metric. But if the first route
is automatically deleted from kernel the 2nd one will be used. No?
> another confusing thing: using "nexthop via dev ppp0" in a table made me
> think that i don't need a gateway address at all... but unfortunatly
> that's no the case :(seems that ip searches the gateway address itself so
> that after appp-reconnect (where i get another gateway address) the table-entries
> aren't valid anymore.
The "via GW" syntax is not mandatory for ppp devices, you
can use only "nexthop dev ppp0", just remove this "via", you have
syntax error. As for ppp devices, it is recommended your scripts
to recreate the multipath routes to contain nexthops only for
valid ppp devices (for which you have established link). As you see,
the new kernels delete the multipath route for you, so you can't
rely on permanent multipath route (I assume the ppp devices really
pass unregistration). Even in the old kernels you have to recreate
the route because when one ppp devices is registered again its
nexthop status does not change, it remains dead.
> Thanks
>
> Tobias
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-07-24 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 20:35 [LARTC] failover problems Tobias Geiger
2002-07-23 20:55 ` Tobias Geiger
2002-07-23 21:14 ` Julian Anastasov
2002-07-24 16:46 ` Tobias Geiger
2002-07-24 18:47 ` Julian Anastasov [this message]
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-102753634710854@msgid-missing \
--to=ja@ssi.bg \
--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.