| commit | dc6c70fd5f505cdd9edad00eedccdd2fb1f9380c | [log] [tgz] |
|---|---|---|
| author | Patrick Rohr <prohr@google.com> | Tue Oct 24 09:45:26 2023 -0700 |
| committer | Patrick Rohr <prohr@google.com> | Tue Oct 24 11:44:46 2023 -0700 |
| tree | b017f2b7aa76b480ace539200f434194468c8bf7 | |
| parent | b8af9d5c19f954623b132c49b15609810681f00d [diff] |
Remove check that preferred lifetime >= t2 For a single address, DHCPv6 won't work well (i.e. potentially lose provisioning) if the preferred lifetime is lower than t2. However, this might be a valid scenario in a renumbering event in the presence of multiple prefixes. Additionally, in DHCPv6 it is up to the server to configure the client correctly. Test: TH Change-Id: I37b2a0b89deda85b3f7be29c8f02f685aa6e65f8