DHCPREQUEST unicast conflicts with RFC 1122 (when USE_LPF)

[Kim F. Storm]

Ted Lemon <mellon at fugue.com> writes:

> Kim F. Storm wrote:
>>
>> It seems that he was confused by the name "fallback interface".  Why
>> not call it "unicast interface" in accordance with its purpose.
>>   
> 'cuz I was annoyed that I had to put in that code?   :'}
>
> The good news is that the new version of the client won't require this 
> code anymore.   :')

Sounds good.

I talked to the collegue who had disabled the fallback interface in
the first place, and his argument was that on Linux, if you send on a
normal socket, the kernel will select any available local IP address
as source in case you transmit on an interface which doesn't have its
own address.  So a DISCOVERY request may get a bogus source IP address.

That caused troubles on a system with multiple interfaces, most of which
have pre-configured static addresses.

I haven't verified whether that is really true, but I've undone his
hacks, so I'm now using the fallback interface -- seeming without
problems...

-- 
Kim F. Storm <storm at cua.dk> http://www.cua.dk