Working on howl port

[Andrea Campi]

On Sat, Dec 11, 2004 at 01:47:19PM -0500, Chuck Swiger wrote:
> If your first implementation happens to leave the interface with a 169.254 
> IP address, it's doing something it shouldn't, however that is likely to be 
> mostly harmless until you or someone has a chance to improve the 
> implementation.

Agreed. ;-)

> autoipd and DHCP/dhclient should never get into a fight, nor should autoipd 
> conflict with a manually-assigned network config: autoipd should only try 
> to configure a link-local address during the interval when nothing else has 
> done so, or if autoipd has reason to believe that the existing 
> configuration is invalid (ie, after the carrier drops).  Any time dhclient 
> gets a lease and assigns an IP address to an interface, autoipd needs to 
> back out of the way.

Uhm. Yes, link state changes and possibly other events can
reasonably be used for this. I guess I can use route change
notifications from dhclient to notice something's up.
Actually, all this is nifd's business, not autoipd proper; the
two work in concert.

Just to check my assumptions: is it reasonable to assume autoipd
has total control over the 169.254 block? I don't want to have to
bother about preserving any existing address in that range etc.

OK, I'll do the straighforward implementation first but I'll keep
an eye to DTRT.

Thanks for beating me with clues!

Bye,
	Andrea

-- 
            Give a man a fish and you feed him for a day;
     teach him to use the Net and he won't bother you for weeks.