Component: dhcpv6-client

7.22 Stable 2026-Mar-09 (1 month ago)

• allow unsetting "pool-prefix-length" parameter;
• improved log messages;

7.21 Stable 2026-Jan-12 (3 months ago)

• do not show I flag for disabled client;
• fixed misleading "couldn't acquire address, continue with prefix only" error when prefix is not even requested;

7.22beta1 Development 2026-Jan-02 (4 months ago)

• allow unsetting "pool-prefix-length" parameter;
• improved log messages;

7.21beta4 Testing 2025-Oct-28 (6 months ago)

• improved system stability when DHCPv6 client uses "rapid-commit=no", "accept-prefix-without-address=no" and receives only prefix from the server;

7.20.2 Stable 2025-Oct-21 (6 months ago)

• improved system stability when DHCPv6 client uses "rapid-commit=no", "accept-prefix-without-address=no" and receives only prefix from the server;

7.21beta2 Testing 2025-Oct-06 (6 months ago)

• do not show I flag for disabled client;
• fixed misleading "couldn't acquire address, continue with prefix only" error when prefix is not even requested;

7.20 Stable 2025-Sep-29 (7 months ago)

• added "accept-prefix-without-address" allowing client to accept prefix when address is not available although requested;
• update the routing table and address list on manual client configuration changes;

7.20beta2 Testing 2025-May-27 (11 months ago)

• added "accept-prefix-without-address" allowing client to accept prefix when address is not available although requested;
• update the routing table and address list on manual client configuration changes;

7.19 Stable 2025-May-22 (11 months ago)

• allow selecting to which routing tables add default route;

7.19beta2 Testing 2025-Feb-28 (1 year ago)

• allow selecting to which routing tables add default route;

7.18 Stable 2025-Feb-24 (1 year ago)

• added "validate-server-duid" option;
• allow specifying custom DUID;
• do not run script on prefix renewal;

7.18beta2 Testing 2025-Jan-21 (1 year ago)

• added "validate-server-duid" option;
• allow specifying custom DUID;
• do not run script on prefix renewal;

7.17 Stable 2025-Jan-16 (1 year ago)

• added prefix-address-list parameter;
• improved system stability when DHCPv6 client is enabled on non-existing interface;
• log message when response with invalid transaction-id received;

7.17beta5 Testing 2024-Nov-13 (1 year ago)

• improved system stability when DHCPv6 client is enabled on non-existing interface;
• log message when response with invalid transaction-id received;

7.17beta2 Testing 2024-Sep-27 (1 year ago)

• added prefix-address-list parameter;

7.16 Stable 2024-Sep-20 (1 year ago)

• do not add default gateway twice when both prefix and address is acquired;
• fixed T1, T2, valid-lifetime and preferred-lifetime compliance with RFC8415 by using value 0;
• pause client and remove dynamically installed objects while it becomes invalid;
• release client on failed renew attempt;
• update gateway address for default route on renew;

7.16beta3 Testing 2024-Jun-27 (1 year ago)

• release client on failed renew attempt (additional fixes);

7.16beta1 Testing 2024-Jun-05 (1 year ago)

• do not add default gateway twice when both prefix and address is acquired;
• fixed T1, T2, valid-lifetime and preferred-lifetime compliance with RFC8415 by using value 0;
• pause client and remove dynamically installed objects while it becomes invalid;
• release client on failed renew attempt;
• update gateway address for default route on renew;

7.14 Stable 2024-Feb-29 (2 years ago)

• install dynamic IPv6 blackhole routes in corresponding routing-table;
• updated error logging when multiple prefixes received on renew;

7.14beta10 Testing 2024-Feb-06 (2 years ago)

• updated error logging when multiple prefixes received on renew;

7.14beta6 Testing 2024-Jan-10 (2 years ago)

• install dynamic IPv6 blackhole routes in corresponding routing-table;

7.7 Stable 2023-Jan-12 (3 years ago)

• handle receiving of invalid T1 and T2 times;

7.7beta3 Testing 2022-Oct-26 (3 years ago)

• handle receiving of invalid T1 and T2 times;

7.6 Stable 2022-Oct-17 (3 years ago)

• fixed false error status reporting when server offers T1 or T2 value as 0;

7.6beta4 Testing 2022-Sep-01 (3 years ago)

• fixed false error status reporting when server offers T1 or T2 value as 0;