linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Savola <pekkas@netcore.fi>
To: "David S. Miller" <davem@redhat.com>
Cc: Daniel Gryniewicz <dang@fprintf.net>, <alan@lxorguk.ukuu.org.uk>,
	<richard@aspectgroup.co.uk>, <skraw@ithnet.com>,
	<willy@w.ods.org>, <carlosev@newipnet.com>,
	<lamont@scriptkiddie.org>, <davidsen@tmr.com>,
	<bloemsaa@xs4all.nl>, <marcelo@conectiva.com.br>,
	<netdev@oss.sgi.com>, <linux-net@vger.kernel.org>,
	<layes@loran.com>, <torvalds@osdl.org>,
	<linux-kernel@vger.kernel.org>
Subject: ARP and knowledge of IP addresses [Re: [2.4 PATCH] bugfix: ARP respond on all devices]
Date: Wed, 20 Aug 2003 08:31:31 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0308200828010.32417-100000@netcore.fi> (raw)
In-Reply-To: <20030819112912.359eaea6.davem@redhat.com>

On Tue, 19 Aug 2003, David S. Miller wrote:
[...]
> Consider the situation logically.  When you're replying to an
> ARP, _HOW_ do you know what IP addresses are assigned to _MY_
> outgoing interfaces and _HOW_ do you know what subnets _EXIST_
> on the LAN?
> 
> The answer to both is, you'd don't know these things _EVEN_ if
> you are a router/gateway.

Maybe I'm missing something but -- isn't it perfectly valid to assume the
node *ITSELF* knows about its interfaces, IP addresses, and its routes?
(Certainly, it can't know of what subnets exist on the LAN if those
haven't been configured on the node, e.g. in the form of an "interface
routes".)

ARP could look it up.

Sure, it would seem a bit like an OSI layering violation, but that's no 
news as OSI layering isn't strict anyway and has been shredded to pieces 
already in many other places.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


  parent reply	other threads:[~2003-08-20  5:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 12:02 [2.4 PATCH] bugfix: ARP respond on all devices Richard Underwood
2003-08-19 12:35 ` Alan Cox
2003-08-19 18:30   ` Daniel Gryniewicz
2003-08-19 18:29     ` David S. Miller
2003-08-19 19:12       ` Daniel Gryniewicz
2003-08-19 19:10         ` David S. Miller
2003-08-20 16:49         ` Bill Davidsen
2003-08-20 17:00           ` David S. Miller
2003-08-20 17:44             ` Ben Greear
2003-08-20 17:48               ` David S. Miller
2003-08-20 21:34                 ` [RFC][2.4 PATCH] source address selection for ARP requests Willy Tarreau
2003-08-20 21:47                   ` David S. Miller
2003-08-20 22:27                     ` Willy Tarreau
2003-08-20 22:35                       ` David S. Miller
2003-08-20 22:59                         ` Willy Tarreau
2003-08-20 23:18                 ` [2.4 PATCH] bugfix: ARP respond on all devices Julian Anastasov
2003-08-23 20:50                 ` Bill Davidsen
2003-08-20 19:08             ` Bill Davidsen
2003-08-20 20:07               ` Bas Bloemsaat
2003-08-19 19:17       ` Discussion fucking closed WAS(Re: " jamal
2003-08-19 19:42       ` bill davidsen
2003-08-20  5:31       ` Pekka Savola [this message]
2003-08-19 13:11 ` Bas Bloemsaat
2003-08-19 15:34   ` David S. Miller
2003-08-19 17:39     ` Lars Marowsky-Bree
2003-08-19 17:36       ` David S. Miller
2003-08-19 21:01         ` Harley Stenzel
2003-08-19 16:19   ` Stephan von Krawczynski
2003-08-19 16:54   ` David S. Miller
2003-08-19 17:15     ` Stephan von Krawczynski
2003-08-19 16:56 ` David S. Miller
2003-08-20  5:18   ` host vs interface address ownership [Re: [2.4 PATCH] bugfix: ARP respond on all devices] Pekka Savola
2003-08-20  5:38     ` Valdis.Kletnieks

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=Pine.LNX.4.44.0308200828010.32417-100000@netcore.fi \
    --to=pekkas@netcore.fi \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bloemsaa@xs4all.nl \
    --cc=carlosev@newipnet.com \
    --cc=dang@fprintf.net \
    --cc=davem@redhat.com \
    --cc=davidsen@tmr.com \
    --cc=lamont@scriptkiddie.org \
    --cc=layes@loran.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=netdev@oss.sgi.com \
    --cc=richard@aspectgroup.co.uk \
    --cc=skraw@ithnet.com \
    --cc=torvalds@osdl.org \
    --cc=willy@w.ods.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).