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

[Camilo Aguilar]

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.

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

Best,
Camilo


On Thu, May 29, 2014 at 1:41 PM, Camilo Aguilar <camilo.aguilar at gmail.com>
wrote:

> Hi Tom, thanks for the updated patch. I'm going to test it and let you
> know the results.
>
> As for the drivers involved here: e1000 and vmxnet3 (VMware)
>
> Best,
> Camilo
>
>
> On Thu, May 29, 2014 at 1:18 PM, Tom Gundersen <teg at jklm.no> wrote:
>
>> On Thu, May 29, 2014 at 6:05 PM, Camilo Aguilar
>> <camilo.aguilar at gmail.com> wrote:
>> > No, I don't see it in any of the machines that are failing.
>>
>> What driver is used on the interface that fails? The qeth driver
>> should always expose the layer2 value in sysfs as far as I can tell.
>> The attached (entirely untested) update of your patch should fix the
>> issue when the layer2 value is available.
>>
>> Cheers,
>>
>> Tom
>>
>
>
>
> --
> *Camilo Aguilar*
> Software Engineer
> http://github.com/c4milo
>
>
>


-- 
*Camilo Aguilar*
Software Engineer
http://github.com/c4milo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140529/5dc1507f/attachment.html>