tasklwIP - A Lightweight TCP/IP stack - Tasks: task #12406, Add stateful DHCPv6


You are not allowed to post comments on this tracker with your current authentication level.

task #12406: Add stateful DHCPv6

Submitted by:  Simon Goldschmidt <goldsimon>
Submitted on:  Fri 11 Jan 2013 09:22:20 PM UTC  
Category:  IPv6 Should Start On:  Fri 11 Jan 2013 12:00:00 AM UTC
Should be Finished on:  Fri 11 Jan 2013 12:00:00 AM UTC Priority:  5 - Normal
Status:  None Privacy:  Public
Percent Complete:  30% Assigned to:  None
Open/Closed:  Open Planned Release:  None
Effort:  0.00

Fri 23 Feb 2018 06:39:09 AM UTC, comment #5:

Stateless DHCPv6 has been added in commit 76a13054ee9d2314673f779ea3ddb37f51775b14.

Stateful DHCPv6 remains to be done.

-> changed summary and planned release

Simon Goldschmidt <goldsimon>
Project Administrator
Wed 22 Nov 2017 12:45:51 PM UTC, comment #4:

Stateless DHCPv6 should be added for 2.1.0

Simon Goldschmidt <goldsimon>
Project Administrator
Mon 18 Mar 2013 11:35:26 AM UTC, comment #3:

Stateless DHCPv6 (i.e. Information Request - RFC 3736) is often needed to retrieve DNS (and SIP) server address(es). This is especially valid in an IPv6-only network.

Stateless DHCPv6 runs fine as an addon to SLAAC: The network informs the clients the support for it through the M/O-bits in the RA message during SLAAC.

To make use of IPv6 DNS server address(es), I think the LwIP DNS client need to be enhanced with support for transmitting on IPv6?

Harald Johansen <hajohans>
Mon 14 Jan 2013 03:56:17 PM UTC, comment #2:

So far I haven't ran into a case where I need DHCPv6.

Stateless address auto-configuration as currently implemented has been enough for me.

I understand that DHCPv6 is useful for additional configuration options (DNS servers? local NS?), but nothing critical.

I think it is OK to release 1.5.0 without it.

Ivan Delamer <idelamer>
Project Member
Sat 12 Jan 2013 07:09:24 PM UTC, comment #1:

I think it's a nice-to-have. Both at home and at work, SLAAC always triggers first and I never hit the fallback-to-DHCPv6 case.

However, looking at network managers such as connman, it'd be feature-parity to include it.

Grant Erickson <marathon96>
Fri 11 Jan 2013 09:22:20 PM UTC, original submission:

I don't know exactly how optional this is, but I'd like it to be included with the first IPv6-supporting release...

Simon Goldschmidt <goldsimon>
Project Administrator


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by hajohans (Posted a comment)
  • -email is unavailable- added by idelamer (Posted a comment)
  • -email is unavailable- added by marathon96 (Posted a comment)
  • -email is unavailable- added by goldsimon (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follow 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    Fri 23 Feb 2018 06:39:09 AM UTC goldsimon Percent Complete0% => 30%
        Assigned togoldsimon => None
        Planned Release2.1.0 => None
        SummaryAdd DHCPv6 => Add stateful DHCPv6
    Wed 22 Nov 2017 12:45:51 PM UTC goldsimon Assigned toNone => goldsimon
        Planned ReleaseNone => 2.1.0
    Wed 19 Aug 2015 08:40:34 AM UTC goldsimon Planned Release1.5.0 => None
    Tue 15 Jan 2013 08:23:31 AM UTC goldsimon CategoryDHCP => IPv6

    Back to the top

    Powered by Savane 3.3