3:40 p.m.
Hi,
After a successful connection to a service, ConnMan starts DHCP
procedure to get an IPv4. However, if such procedure fails then
ConnMan will assign a Link-local address to that given interface. At
the end of this process, ConnMan will notify the assigned IPv4 address
with "dhcp" as method. We consider it should be "auto" in order to
let
know that the DHCP process failed and that address is a Link-local
address. What do people think?
Regards,
Jose Blanquicet
8:21 a.m.
Hi Jose,
On 05/08/2017 04:40 PM, Jose Blanquicet wrote:
Hi,
After a successful connection to a service, ConnMan starts DHCP
procedure to get an IPv4. However, if such procedure fails then
ConnMan will assign a Link-local address to that given interface. At
the end of this process, ConnMan will notify the assigned IPv4 address
with "dhcp" as method.
Yep, that is indeed misleading.
We consider it should be "auto" in order to let
know that the DHCP process failed and that address is a Link-local
address. What do people think?
According the docs we report for IPv4 dhcp, manual and off. For IPv6 is
auto, manual, 6to4 and off. If I got that correct[1] then is IPv6's auto
the LL for IPv4. So yes, that sounds the right thing to do.
Thanks,
Daniel
[1] https://en.wikipedia.org/wiki/Link-local_address
8:38 a.m.
Hi Daniel,
According the docs we report for IPv4 dhcp, manual and off. For IPv6
is
auto, manual, 6to4 and off. If I got that correct[1] then is IPv6's auto the
LL for IPv4. So yes, that sounds the right thing to do.
That was also what I understood from [1] and [2]. We will start
working on a patch to set "auto" for IPv4 when the address is got
through LL and update the docs according to that. Any
comment/suggestion?
[1] https://tools.ietf.org/html/rfc3927
[2] https://tools.ietf.org/html/rfc2462
Regards,
Jose Blanquicet
1869
days inactive
1876
days old
2 comments
2 participants
participants (2)
-
Daniel Wagner -
Jose Blanquicet