From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] ipv4: add link_filter sysctl
Date: Wed, 18 Mar 2009 18:21:15 -0700 (PDT) [thread overview]
Message-ID: <20090318.182115.43965264.davem@davemloft.net> (raw)
In-Reply-To: <20090313161253.0f02da26@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Fri, 13 Mar 2009 16:12:53 -0700
> Add a new parameter that controls how kernel responds to packets
> when interface is down. This is done to solve the problem of:
>
> Assume topology of:
> A <-----------> Router X--- down link
> 10.1.1.2/24 10.1.1.1/24 10.2.1.1/24
> eth0 eth1
>
> If A pings 10.2.1.1 then with normal Linux semantics Router would
> respond even if eth1 link on 10.2.1.1 was down. This causes some network
> management tools (that work with other router OS's) to falsely
> report that link is okay.
>
> The problem is that a Linux router does not respond the way
> other systems do. This is the router equivalent of "Strong ES"
> model, it is not the same as "Strong ES" as defined in Host
> Requirements.
>
> The new parameter adds an additional check on slow input packet
> path, and causes route cache flush if enabled and carrier is
> lost.
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
There is nothing "router" about this situation.
When 10.2.1.1 is being pinged, it is in the role of an end-system in
that transaction.
The "router" is reachable by "A", and as a consequence so is that IP
address 10.2.1.1, and therefore the ping should succeed.
next prev parent reply other threads:[~2009-03-19 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 23:12 [RFC] ipv4: add link_filter sysctl Stephen Hemminger
2009-03-19 1:21 ` David Miller [this message]
2009-03-19 2:42 ` Stephen Hemminger
2009-03-19 5:34 ` David Miller
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=20090318.182115.43965264.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).