From: Ben Greear <greearb@candelatech.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, netdev <netdev@vger.kernel.org>
Subject: Re: IP address: property of host or interface?
Date: Mon, 26 Jan 2009 10:06:58 -0800 [thread overview]
Message-ID: <497DFBC2.4030903@candelatech.com> (raw)
In-Reply-To: <497DF629.70602@hp.com>
Rick Jones wrote:
>> So.. am I right that an IP address is a HOST property, not an INTERFACE
>> property, and that the traditional way is just more convenient to set
>> up? And
>> that all the tools that complains that "there's no IP address
>> assigned to this
>> interface" (tcpdump) are wrong? :)
>
> There are two "schools" of thought - the Linux stack follows the "weak
> end system" model in which IP addresses are treated as a host
> property. There is another school of thought called the "strong end
> system" model where IP addresses are an interface property. There are
> some "other" stacks out there which can be configured to behave in a
> "strong end system" way but they tend to default to more of something
> in between the two.
>
> Tcpdump may simply be caught in the middle :)
With a bit of configuring (away from system defaults), Linux can behave
as a 'strong end system', and even
in default behaviour, I don't believe it will process IP packets from an
interface that has NO IP address assigned
to it.
Thanks,
Ben
>
> rick jones
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2009-01-26 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 13:57 IP address: property of host or interface? Michael Tokarev
2009-01-26 17:43 ` Rick Jones
2009-01-26 18:06 ` Ben Greear [this message]
2009-01-26 18:20 ` Michael Tokarev
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=497DFBC2.4030903@candelatech.com \
--to=greearb@candelatech.com \
--cc=mjt@tls.msk.ru \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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 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.