netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: netdev@vger.kernel.org
Subject: Re: Weak host model vs .interface down
Date: Fri, 11 Jun 2010 09:32:20 -0700	[thread overview]
Message-ID: <4C126514.30905@hp.com> (raw)
In-Reply-To: <OF1D06F11A.44DE8C5A-ONC125773F.00437856-C125773F.004425B9@transmode.se>

Joakim Tjernlund wrote:
> Linux uses the weak host model which makes the IP addresses part of the system
> rather than the interface. However consider this:
> 
> System A, eth0 connected to the network
> # > ifconfig eth0 192.168.1.16
> # > ifconfig eth1 192.168.1.17 down
> 
> System B
> # > ping 192.168.1.17
> PING 192.168.1.17 (192.168.1.17) 56(84) bytes of data.
> 64 bytes from 192.168.1.17: icmp_seq=1 ttl=64 time=0.618 ms
> 
> Isn't it a bit much to respond on 192.168.1.17 when its interface is down?

As you said at the beginning, the weak end system model presumes the IP address 
is part of the system.  Seems to me that means unless one removes the IP address 
from the system it is reasonable for the system to continue to respond to that 
IP address.  Regardless of what happens to any individual interface.

Now, I wouldn't expect it to continue to respond to 192.168.1.17 through eth1, 
but if eth0 is indeed connected to the same broadcast domain, given the 
following of the weak end-system model, continuing to respond seems consistent 
with enthusiasticaly following the weak end-system model.

rick jones

  parent reply	other threads:[~2010-06-11 16:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 12:24 Weak host model vs .interface down Joakim Tjernlund
2010-06-11 15:48 ` [PATCH net-next-2.6] ipv4: sysctl to block responding on down interface Stephen Hemminger
2010-06-22 17:15   ` David Miller
2010-06-30 20:55     ` Stephen Hemminger
2010-06-30 20:58       ` David Miller
2010-06-28 19:03   ` Joakim Tjernlund
2010-06-28 19:42     ` Eric Dumazet
2010-06-28 21:09       ` Joakim Tjernlund
2010-06-28 21:28         ` Mitchell Erblich
2010-06-28 21:58           ` Joakim Tjernlund
2010-06-28 21:57         ` David Miller
2010-06-28 23:30           ` Joakim Tjernlund
2010-06-29  3:01             ` David Miller
2010-07-01 11:23     ` Andi Kleen
2010-07-01 11:48       ` Joakim Tjernlund
2010-06-11 16:32 ` Rick Jones [this message]
2010-06-11 17:06   ` Weak host model vs .interface down Joakim Tjernlund
2010-06-11 17:13     ` Rick Jones
2010-06-11 19:41       ` Joakim Tjernlund
2010-06-11 23:57         ` Mark Smith
2010-06-12  9:34           ` Joakim Tjernlund
2010-06-11 19:50     ` Mitchell Erblich
2010-06-11 20:46       ` Joakim Tjernlund

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=4C126514.30905@hp.com \
    --to=rick.jones2@hp.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).