netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hasso Tepper <hasso@estpak.ee>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev@oss.sgi.com
Subject: Re: Link detection
Date: Mon, 14 Mar 2005 20:41:21 +0200	[thread overview]
Message-ID: <200503142041.21451.hasso@estpak.ee> (raw)
In-Reply-To: <20050314145710.GO31837@postel.suug.ch>

Thomas Graf wrote:
> * Hasso Tepper <200503141605.02959.hasso@estpak.ee> 2005-03-14 16:05
> > I think that you misunderstood. I don't talk about any routes created
> > by any user space applications or by user. These _must_ be untouched of
> > course. I'm talking about routes _kernel_ creates if address is added
> > to the interface. All other routes are not problem anyway. Even if
> > their next hop points to network behind down interface, their next hop
> > is unreachable and route shouldn't be used, no?
>
> Makes a lot more sense now. Yes, the nexthops should be marked
> unreachable since the routing cache flushed upon a NETDEV_CHANGE.
>
> What about setting RFT_REJECT/RTN_UNREACHABLE on those routes for the
> time the carrier is gone?

>From users' point of view I think that any solution is acceptable which 
prevents kernel to actually use these routers if carrier is down. And 
setting flags might be less expensive of course.


with my best wishes,

-- 
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator

  reply	other threads:[~2005-03-14 18:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 12:35 Link detection Hasso Tepper
2005-03-14 13:32 ` Thomas Graf
2005-03-14 14:05   ` Hasso Tepper
2005-03-14 14:57     ` Thomas Graf
2005-03-14 18:41       ` Hasso Tepper [this message]
2005-03-14 14:41   ` Hasso Tepper
2005-03-14 15:03     ` Thomas Graf
2005-03-14 16:54     ` Thomas Graf
2005-03-14 16:16 ` [PATCH] ip link should print NO-CARRIER for !IFF_RUNNING && IFF_UP Thomas Graf

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=200503142041.21451.hasso@estpak.ee \
    --to=hasso@estpak.ee \
    --cc=netdev@oss.sgi.com \
    --cc=tgraf@suug.ch \
    /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;
as well as URLs for NNTP newsgroup(s).