Bug 12206 - DHCPv6 client is not compliant with RFC3315
Summary: DHCPv6 client is not compliant with RFC3315
Status: NEW
Alias: None
Product: Busybox
Classification: Unclassified
Component: Networking (show other bugs)
Version: 1.31.x
Hardware: All Linux
: P5 critical
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-09 11:36 UTC by Markus Gothe
Modified: 2019-09-13 16:37 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Gothe 2019-09-09 11:36:12 UTC 
From the RFC: "A client MUST include an Elapsed Time option in messages to indicate how long the client has been trying to complete a DHCP message exchange."

and it seems to be unable to get a correct lease from certain embedded DHCPv6 servers, whereas the WIDE DHCPv6 does comply and gets a lease.
Comment 1 Denys Vlasenko 2019-09-12 10:53:38 UTC 
What are those "certain embedded DHCPv6 servers"? Name, version?
Comment 2 Markus Gothe 2019-09-12 10:59:04 UTC 
It's embedded in the Sierra Aircard modems, however it did seem the issue was with DUID type 1 (it wanted DUID type 3). But I also observed this behavior.
Comment 3 Denys Vlasenko 2019-09-13 16:37:31 UTC 
(In reply to Markus Gothe from comment #2)
> however it did seem the issue was with DUID type 1 (it wanted DUID type 3).

!?