netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Singer <elf@buici.com>
To: John Heffner <jheffner@psc.edu>
Cc: netdev@vger.kernel.org, Jeroen Massar <jeroen@unfix.org>,
	Ben Greear <greearb@candelatech.com>, Al Boldi <a1426z@gawab.com>,
	linux-net@vger.kernel.org
Subject: Re: [RFC] ip / ifconfig redesign
Date: Mon, 5 Dec 2005 21:13:41 -0800	[thread overview]
Message-ID: <20051206051341.GB6820@buici.com> (raw)
In-Reply-To: <4394C726.80902@psc.edu>

On Mon, Dec 05, 2005 at 06:03:02PM -0500, John Heffner wrote:
> Rick Jones wrote:
> >John Heffner wrote:
> >>Yes, but if an interface will accept packets for a certain IP address, 
> >>and will send packets with that IP address, is there any reason it 
> >>can't ARP for that address?
> >
> >
> >If ARP RFC's say it shouldn't :) (I don't know that it does) ARP is ARP, 
> >accepting IPs is IP.  The maze of twisty passages may be similar, but 
> >they are distinct.
> 
> I actually think it would be out of scope for an ARP RFC to specify this 
> (and none I'm aware of do).  It really is an IP layer decision.  That 
> is, the decision naturally extends beyond the scope of ARP, applying 
> also to layer 2 devices which don't even do ARP.

Indeed.  We've been talking about ARP responses, not queries.

> >Is a MAC address a property of the host, or of the interface connected 
> >to the host?
> 
> Depends on whether you run your interfaces in promiscuous mode, and send 
> frames with different MAC addresses from one interface. ;-)

MAC addresses are owned by the link.  It is not meaningful for eth1 to
transmit the MAC for eth0.  Consider that both interfaces could be on
the same link.

Yes, we can do all manner of gymnastics, but this is something that
IEEE standardizes.


  reply	other threads:[~2005-12-06  5:13 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 [this message]
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
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=20051206051341.GB6820@buici.com \
    --to=elf@buici.com \
    --cc=a1426z@gawab.com \
    --cc=greearb@candelatech.com \
    --cc=jeroen@unfix.org \
    --cc=jheffner@psc.edu \
    --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).