netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Singer <elf@buici.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Al Boldi <a1426z@gawab.com>,
	netdev@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [RFC] ip / ifconfig redesign
Date: Mon, 5 Dec 2005 13:03:29 -0800	[thread overview]
Message-ID: <20051205210329.GC20824@buici.com> (raw)
In-Reply-To: <43948049.3040508@candelatech.com>

On Mon, Dec 05, 2005 at 10:00:41AM -0800, Ben Greear wrote:
> >Precisely the case.  It should be the case that a box response to an
> >arp on *any* interface for *any* IP address known to the box.
> 
> I certainly don't mind if this is a configurable, or even default
> behaviour, but we also need the ability to only respond to particular
> arps on particular interfaces, based on the IP addresses assigned
> to those interfaces.

Why?  The routing determines connectivity, not ARP.  AFAIK, ARP
requests are not made on interfaces that lack that the network being
queried.

If I put a host with an address on network 12 onto an ethernet segment
for network 10 and then ARP for addresses on network 10, I ought to be
able to send packets to those hosts (baring a firewal).  However, I
won't be able to get anything back because those hosts don't know how
to send to network 12.  Misconfiguration?  Yes.  Non-compliant?  No.

> I am able to get this particular arp binding working today, so I'm
> not suggesting changes, just mentioning that there are other
> configurations than what you mention that are useful to people.

Anyway, I haven't seen a good reason to change the current behavior.
While the above described functionality is missing, no one has made a
case to support it.

  parent reply	other threads:[~2005-12-05 21:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 19:53 [RFC] ip / ifconfig redesign Al Boldi
2005-12-02 19:59 ` Pekka Savola
2005-12-02 20:08 ` Ben Greear
2005-12-02 20:38 ` linux-os (Dick Johnson)
2005-12-02 22:49   ` Jesper Juhl
2005-12-10 18:51   ` Stefan Smietanowski
2005-12-02 22:40 ` Jeff V. Merkey
2005-12-03 13:46 ` Al Boldi
2005-12-03 18:33   ` Ben Greear
2005-12-03 20:25     ` Al Boldi
2005-12-05 14:01     ` John W. Linville
2005-12-05 14:20       ` Jeroen Massar
2005-12-05 17:40       ` Marc Singer
2005-12-05 17:59         ` Jeroen Massar
2005-12-05 20:56           ` Marc Singer
2005-12-05 22:19           ` John Heffner
2005-12-05 22:28             ` Rick Jones
2005-12-05 22:30               ` John Heffner
2005-12-05 22:43                 ` Rick Jones
2005-12-05 23:03                   ` John Heffner
2005-12-06  5:13                     ` Marc Singer
2005-12-05 22:48             ` Jeroen Massar
2005-12-05 22:56               ` John Heffner
2005-12-05 23:10                 ` Jeroen Massar
2005-12-06  5:18               ` Marc Singer
2005-12-05 18:00         ` Ben Greear
2005-12-05 20:10           ` John W. Linville
2005-12-05 21:03           ` Marc Singer [this message]
2005-12-05 20:48       ` Al Boldi
2005-12-14 14:19 ` Al Boldi

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=20051205210329.GC20824@buici.com \
    --to=elf@buici.com \
    --cc=a1426z@gawab.com \
    --cc=greearb@candelatech.com \
    --cc=linux-net@vger.kernel.org \
    --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).