[systemd-devel] Systemd-networkd -- Cannot acquire DHCP lease on bridge interface

[Marcel Holtmann]

Hi Lennart,

>>>>>> Trying unicast, waiting some time and then trying broadcast, if a DHCP offer
>>>>>> is not sent within that time limit, seems like a fair thing to do. My 2
>>>>>> cents.
>>>>> 
>>>>> Yeah, it seems this is what we should do. I guess it makes sense to
>>>>> make RequestBroadcast=yes|no|automatic, and default to the latter.
>>>> 
>>>> Please name it "auto", not "automatic"...
>>>> 
>>>> Please make the time short enough though to still give a nice
>>>> feeling...
>>>> 
>>>> I figure the reverse of first trying broadcast, and then trying
>>>> unicast is unnecessary, right?
>>> 
>>> Yeah, I don't think it makes sense to expose this implementation
>>> detail. The preference should be for unicast if we don't know any
>>> better, as that causes slightly less network traffic, so I think we
>>> should do a couple of unicasts only before starting to do both, but
>>> that's not anything the user should care about.
>> 
>> if we have a test case that lets us test this easily, someone might
>> want to test the latest ConnMan and see if it does this
>> correctly. Since there we are doing the automatic fallback already.
> 
> What timeout did you pick?

we are using the DHCP retry timeout. So first one goes out unicast, second as broadcast, third as unicast and so on.

Not sure if this is a best strategy, but that is what we are trying out now. Unfortunately the person reporting it left the area with the funny behaving access point.

Regards

Marcel