diff options
author | Thomas Markwalder <tmark@isc.org> | 2017-12-07 07:02:06 -0500 |
---|---|---|
committer | Thomas Markwalder <tmark@isc.org> | 2017-12-07 07:02:06 -0500 |
commit | 59336f8007988c2e77999da06de5dfd922dcec97 (patch) | |
tree | 53fe122a8743b7718a5c1d7efa97857929769eb7 /RELNOTES | |
parent | b4e157d82c161a3697011d64e840d4d5aeb3183d (diff) | |
download | isc-dhcp-59336f8007988c2e77999da06de5dfd922dcec97.tar.gz |
[master] Server(v6) releases pre-existing leases when client roams to new network
Merges in rt44576.
Diffstat (limited to 'RELNOTES')
-rw-r--r-- | RELNOTES | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -237,6 +237,20 @@ dhcp-users@lists.isc.org. doing load balancing within failover. [ISC-Bugs #45364] +- If the server detects that a DHCPv6 client (IAID+DUID) has roamed to a new + network, it will now automatically release pre-existing leases on the old + network. When this occurs the server will emit a log statement: + + "Client: <id> roamed to new network, releasing lease: <address>" + + The server will carry out all of the same steps that would normally occur + when a client explicitly releases a lease. Prior to this the server simply + dropped the pre-existing leases on the floor without doing the appropriate + clean-up. Clients that need leases in multiple networks must supply a + unique IAID in each IA. Thanks to Fernando Soto from BlueCat Networks for + reporting the issue. + [ISC-Bugs #44576] + Changes since 4.3.0 (bug fixes) - Tidy up several small tickets. |