This may be a deficiency of my understanding but I've just noticed that in our test network using dhclient the addresses received from dhcpy6d are /128 not /64: fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4/128.
dhcpy6d is handing out /64 prefixes and dhclient is setting a /64 prefix length so I'm currently confused as to where the responsibility lies. Didn't notice this earlier since we also have RAs announcing the same prefixes with SLAAC EUI64 and that generated the expected /64 route table entries.
This may be a deficiency of my understanding but I've just noticed that in our test network using dhclient the addresses received from dhcpy6d are /128 not /64:
fddc:7e00:e001:ee00:fffe:f875:a4f3:42b4/128
.dhcpy6d is handing out /64 prefixes and dhclient is setting a /64 prefix length so I'm currently confused as to where the responsibility lies. Didn't notice this earlier since we also have RAs announcing the same prefixes with SLAAC EUI64 and that generated the expected /64 route table entries.