[PATCH 2/3] zcip: allow our own class B range to be used for ZeroConf

[Stam, Michel [FINT]]

Hello Ralf,

The idea was to use it when you know that 169.254 is already been used
for something else, or when you have a specific need for a certain IP
range.

This might be used, for instance, if no DHCP server is available, yet
you do know what address range you wish to use. I am along the lines of
management IP addresses. For instance Cisco does something similar if
you enable switch clustering (they use the 10.x range).

Our particular use case is a mesh network, in which the nodes partaking
were using an IP range specifically assigned for the meshing purpose. As
the LAN side of the mesh node could use 169.254, this default range was
not an option.

As you said, clients that want to use said range will need to configure
it. Any other ZeroConf enabled devices can still use the 169.254 range
without risk of any conflicts, even with the alternate IP range.

Kind regards,

Michel Stam
-----Original Message-----
From: Ralf Friedl [mailto:Ralf.Friedl at online.de] 
Sent: Wednesday, October 15, 2014 9:14 AM
To: Stam, Michel [FINT]; busybox at busybox.net
Subject: Re: [PATCH 2/3] zcip: allow our own class B range to be used
for ZeroConf

Michel Stam wrote:
> 169.254 may already be used by a local network. This patch allows 
> specifying your own IP range.
Why would you want to use a different range? You would have to specify
it to each client, which seems against the idea of ZeroConf.