DHCPREQUEST unicast conflicts with RFC 1122 (when USE_LPF)

[Kim F. Storm]

"David W. Hankins" <David_Hankins at isc.org> writes:

> On Fri, Jun 09, 2006 at 02:47:57PM +0200, Kim F. Storm wrote:
>> I see the problem with the ISC DHCP clients that I've configured on
>> our GNU/Linux clients using LPF to send requests.
>
> What version?
>
> In the sources I'm looking at, LPF uses the fallback interface
> for unicasts.
>
> This 'fallback interface' is a standard berkeley UDP socket, so
> the destination mac address should be determined by the operating
> system.
>
> If you're running 3.0.1 or later, I'd like to see the initial
> messages logged (or printed to stdout) by dhclient when it starts
> up.  In particular if a Socket/fallback is present on its interfaces
> list.

Thanks for the pointer -- this solved the problem for me.

Digging through the code we use, I found that a collegue of mine had
patched the code to disable the fallback interface, so it used LPF for
the unicasts.

It seems that he was confused by the name "fallback interface".  Why
not call it "unicast interface" in accordance with its purpose.

Many thanks for the quick response and sorry for the noise.

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