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

Marc Singer wrote:
> On Mon, Dec 05, 2005 at 09:01:00AM -0500, John W. Linville wrote:
> 
>>On Sat, Dec 03, 2005 at 10:33:32AM -0800, Ben Greear wrote:
>>
>>>Al Boldi wrote:
>>>
>>>
>>>>Here specifically, ip/ifconfig is implemented upside-down requiring a 
>>>>link/dev to exist for an address to be defined, in effect containing layer 
>>>>3 inside layer 2, when an address should be allowed to be defined w/o a 
>>>>link/dev much like an app is allowed to be defined w/o an address.
>>>
>>>[Removed lkml from CC list]
>>>
>>>You can add multiple virtual IP addresses to physical interfaces.  It
>>>makes no sense to have an IP without any association to an interface
>>>in my opinion.  Often, when you have multiple interfaces, you most 
>>>definately
>>>want different IPs associated specifically with particular interfaces.
>>>Think about redundant paths, routers, firewalls, and such.
>>
>>The association between IP addresses and links is already a bit murky.
>>Reference the arp_announce sysctl for what I mean.  I recall Dave M.
>>emphasizing on at least one occassion that IP addresses belong to
>>the _box_, not to the link.
>>
>>I think Al B.'s idea merits some consideration.  I definitely think
>>we blur the distinctions between L2 and L3 a bit too much in places.
>>
>>Of course, patches would be helpful...
> 
> 
> 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.  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.

> As for changing the behavior, I haven't seen a compelling reason to
> change it.  IMHO, without a motivating case, we would be mucking about
> without a clear goal.

Agreed.

Thanks,
Ben


> -
> 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


  parent reply	other threads:[~2005-12-05 18:00 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 [this message]
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=43948049.3040508@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=a1426z@gawab.com \
    --cc=elf@buici.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).