dhcpcd-discuss

Re: Behavior when DHCP server pools changed and dhcpcd killed/restarted

Roy Marples

Thu Mar 15 17:12:49 2018

On 15/03/2018 02:32, jobhunts02@xxxxxxx wrote:
I have an interface enabled for both DHCPv4 & DHCPv6.  If I change the DHCPv6 pool on the server and then kill/restart dhcpcd, should I get an IPv6 address from the new pool like I do for IPv4 or should I keep my same IPv6 address?

For example, I initially have these addresses assigned by DHCP on my client:
192.168.2.180
2001:ed8:77b5:0:10:123:105:188/64
Both of these addresses are from the corresponding pool on the server.

I go to the server and change the IPv4 & IPv6 pools to:
192.168.2.130 to 192.168.2.139
2001:ed8:77b5:0:10:123:105:130 to 2001:ed8:77b5:0:10:123:105:139
The addresses on the client remain the same.

Then, I kill/restart dhcpcd on the client.  Now the respective addresses are:
192.168.2.130
2001:ed8:77b5:0:10:123:105:188/64

Should my IPv6 address have changed to something within 2001:ed8:77b5:0:10:123:105:130 to 2001:ed8:77b5:0:10:123:105:139?

You should have both 2001:ed8:77b5:0:10:123:105:188/64 and an address within 2001:ed8:77b5:0:10:123:105:130 to 2001:ed8:77b5:0:10:123:105:139. The first address is still valid and there is no real way of invalidating it from DHCP6 other than setting it's vltime and pltime to 0 at the server which is quite complicated.

The idea is that the address will expire by itself, unlike an IPv4 address.

Roy

References:
Behavior when DHCP server pools changed and dhcpcd killed/restartedjobhunts02
Archive administrator: postmaster@marples.name