In the IPv6 environment, dhclient receives the Advertise message but does not send the Request message.
I'm preparing for the migration from ISC DHCP to Kea. After testing the IPv4 environment, I set up an IPv6 server. However, I find that the dhclient continues to send Solicit packets after receiving the Advertise packet from the server.
Packet information
2023-01-29T07:07:41.700741+08:00 linux_supse12sp4_workstation dhclient: XMT: Solicit on eth2, interval 1070ms.
2023-01-29T07:07:41.701790+08:00 linux_supse12sp4_workstation dhclient: RCV: Advertise message on eth2 from fe80::2a6e:ddff:fe88:c857.
2023-01-29T07:07:42.770686+08:00 linux_supse12sp4_workstation dhclient: XMT: Solicit on eth2, interval 2240ms.
2023-01-29T07:07:42.771269+08:00 linux_supse12sp4_workstation dhclient: RCV: Advertise message on eth2 from fe80::2a6e:ddff:fe88:c857.
2023-01-29T07:07:45.023356+08:00 linux_supse12sp4_workstation dhclient: XMT: Solicit on eth2, interval 4580ms.
2023-01-29T07:07:45.036353+08:00 linux_supse12sp4_workstation dhclient: RCV: Advertise message on eth2 from fe80::2a6e:ddff:fe88:c857.
2023-01-29T07:07:49.608250+08:00 linux_supse12sp4_workstation dhclient: XMT: Solicit on eth2, interval 9490ms.
2023-01-29T07:07:49.631751+08:00 linux_supse12sp4_workstation dhclient: RCV: Advertise message on eth2 from fe80::2a6e:ddff:fe88:c857.
2023-01-29T07:07:59.125548+08:00 linux_supse12sp4_workstation dhclient: XMT: Solicit on eth2, interval 19860ms.
2023-01-29T07:07:59.126206+08:00 linux_supse12sp4_workstation dhclient: RCV: Advertise message on eth2 from fe80::2a6e:ddff:fe88:c857.
However, when using ISC DHCP, it is completely normal, and the network adapter configuration on the server and client is identical.
Here are the contents of the server configuration file:
{
"Dhcp6": {
"valid-lifetime": 120,
"renew-timer":100: 60,
"rebind-timer": 60,
"preferred-lifetime": 120,
"interfaces-config": {
"interfaces": [ "eth2" ]
},
"lease-database": {
"type": "memfile",
"persist": true,
"name": "/var/lib/kea/dhcp6.leases"
},
"subnet6": [
{
"subnet": "2000:192:168::/64",
"pools": [
{
"pool": "2000:192:168::64:1028-2000:192:168::64:8484"
}
]
}
]
}
}