Re: [RFC] ip / ifconfig redesign

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Dec 02, 2005 at 11:49:28PM +0100, Jesper Juhl wrote:
> > A link needs to exist for it to have an address.
> >
> 
> I'm only guessing since I'm not entirely sure what Mr. Boldi means,
> but my guess is that he's proposing that an app can bind to an IP
> address without that address being assigned to any currently available
> interface and then later if that IP does get assigned to an interface
> the app will start recieving traffic then. Also possibly allowing the
> address to be removed from one interface and then later assigned to
> another one without apps noticing.
> I don't know /if/ that is what was meant, but that's how I read it.
> 
> 

I don't think that addresses really need to be bound to link, but
networks and routes do.

  # ip addr add 1.2.3.4/24 dev eth0

has the dual purpose of adding an address to the interface *and*
adding a route to the network. 

It might make sense to allow the address to exist without a link in
order to allow a local port listener to continue to accept connections
even though the network moved to another link, e.g. wireless to
wired.  Then again, perhaps, this shouldn't matter.

What does Mr. Boldi propose?
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux