All of lore.kernel.org
 help / color / mirror / Atom feed
From: " Tobias Geiger" <tobias.geiger@web.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] failover problems
Date: Wed, 24 Jul 2002 16:46:37 +0000	[thread overview]
Message-ID: <marc-lartc-102753168801469@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102745669304746@msgid-missing>

>
>         Hello,
>
> On Tue, 23 Jul 2002,  Tobias Geiger wrote:
>
>> to be precisly: the problem is i have several nexthops (e.g. ppp0
>> +eth1 +eth2) for the same route and this WHOLE Route is deleted,
>> although only the ppp0-device dissapears...
>> and i cannot add several entries in different tables, cause this seems
>> not to do failover
>
>         Yes, similar behavior appeared in latest 2.4.19pre kernels,
> it looks like a recommendation the users to recreate their routes
> because a device in nexthop was unregistsred. Is this true for
> your setup?
>

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...

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.

Thanks

Tobias



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-07-24 16:46 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 [this message]
2002-07-24 18:47 ` Julian Anastasov

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-102753168801469@msgid-missing \
    --to=tobias.geiger@web.de \
    --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.