The DHCPv6 server also has the following problems:
- routes to delegated prefixes are added to routing table with the "Dynamic Static" flags - I'd prefer to have the "Dynamic Connected" flags set (and Static unset) as the entry is not static and can disappear when the client releases the prefix. This would help with redistribution via OSPFv3.
- when the DHCPv6 pool prefix and interface prefix overlap, the DHCPv6 server should NOT hand out the prefix assigned to any interface in the system. E.g.: I have 2a01:8c00:ff44
:/64 assigned to my testing bridge (and WAN iface of the client) and 2a01:8c00:ff44
:/56 prefix set for DHCPv6 pool (with the length of prefixes handed out set to 64). DHCPv6 server with no worries hands out the 2a01:8c00:ff44
:/64 prefix to my client, which does not work, as the client cannot have the same prefix on both WAN and LAN interfaces.
In case pool Prefix length is longer than /64 (/63, /62, ...), the client actually selects the next /64 prefix for LAN interface, which makes this configuration work - I'd prefer to have the overlapping /64 and "/PrefixLength" not handed out to clients.
And yes, RADIUS is a must