Re: [RFC] handle return codes of inetaddr_notifiers

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

 



On Wed, 3 Nov 2004 08:46:16 +0100
Thomas Spatzier <tspat@de.ibm.com> wrote:

> On Wednesday 03 November 2004 08:36, David S. Miller wrote:
> > 
> > Why don't you add a special list to the inetdev structure,
> > making it a list of ipv4 addresses which may not be added to
> > the system?  Add generic interfaces exported by net/ipv4/inetdev.c
> > which add/delete such addresses, and make the normal userspace
> > invoked routines which add addresses check this exclusion list.
> 
> Do you mean a list of IP addresses that are already in use by other
> OS images, and, hence, cannot be used by our Linux image?
> This won't work. There are up 160 (and in the future even more)
> OS images on one card. And these images don't have knowledge about
> each other. So we cannot create this IP address list.

If they don't have knowledge about each other, how can registry
of an IP address fail in the first place then?  Something has
to reject it.
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
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