[systemd-devel] [PATCH] sd-dhcp-client: Sets broadcast flag to 1

[Tom Gundersen]

On Fri, May 30, 2014 at 3:24 AM, Camilo Aguilar
<camilo.aguilar at gmail.com> wrote:
> Hi Tom, the patch did not work because there is no layer2 file. Would it be
> safe to assume that no file is the same as the file having 0? This is out of
> my reach unfortunately, but I will be happy to read whatever link you throw
> at me.

I don't think that would work, as only the qeth driver actually
exposes the layer2 file (and to the best of my knowledge the other
upstream drivers support unicast). If other drivers also can't do
unicast, then they need to expose this information to us somehow, I'm
afraid that I don't know anything about the VMWare driver, but
hopefully we can find a way to get this info out of that driver too
(would of course be nice if everyone used the same interface...).

> Also, to better clarify how ISC dhcp-4.3.0 works. It seems it uses raw
> sockets as a first attempt (layer2 unicast) and falls back to normal BSD
> sockets which will always set the broadcast flag on:
> https://cloudup.com/cAneyImU2H2 and
> https://gist.github.com/c4milo/017a50a6f5d329887707

I'd really hope we could avoid setting broadcast everywhere, as that
seems very wasteful...

Cheers,

Tom