dhcpcd-discuss

Indeed, and we find it useful to use it like that to control all dynamicaddress and route assignment.  And it makes this all the moreperplexing, because if dhcpcd can use the prefix length to assign astateless address, why not use the same prefix length for the DHCPv6address?  It wouldn't attempt to get the address at all if it hadn'treceived the correct advertisement.
hmm, could it be that we're sometimes talking about different advertisements? DHCPv6 versus Router Advertisements? I'm asking because I'm unsure whether this is the case or not, but I might be the one who mixes things up here...
Well, IPv6 addresses don't have prefix lengths outside the Linux kernel universe. Linux uses the prefix length attached to its addresses to autogenerate route table entries ... probably in an attempt to do IPv4 in IPv6. After all, IPv6 is just IPv4 with longer addresses ... what could probably go wrong ;) So with dhcpcd you should never see an address/128. Or am I mixing up the route table entries with the address table entries here, that is, you refer to the routing table entries?
From my experience with dhcpcd it correctly creates the required route table entries. And the IPv6 address table just contains /128 addresses, but not any prefix information. But I'm also dazzled why your setup doesn't work. Disclaimer: I use dhcpcd for PD and SLAAC only, never had a need to deploy IA-NAs.
Best regards,Harald

-------- Ursprüngliche Nachricht --------Von: Graham Breed <graham.breed@xxxxxxxxxxxxxx> Datum: 28.09.17  15:17  (GMT+01:00) An: Roy Marples <roy@xxxxxxxxxxxx>, dhcpcd-discuss@xxxxxxxxxxxx Betreff: Re: [dhcpcd-discuss] DHCPv6 addresses being assigned with /128
  prefixes 
On 28/09/17 13:43, Roy Marples wrote:

> ISC dhclient **only** does DHCPv6. It doesn't handle any RA recieved
> inforamtion such as prefixes, not will it generate any routes.
> AFAIK, no patches for it do either - instead a 3rd party will do this.
> NetworkManager, systemd, Linux kernel (if dhcpcd hasn't turned that off).
> 
> So what you say about dhclient not receiving SLAAC addressess makes
> perfect sense.

The interface is configured to receive the addresses, however Ubuntu
does that.  This is a separate test VM without dhcpcd.  And SLAAC works
with a "route" section in radvd.conf along with the "prefix" (or maybe
it just takes a while to apply).  But DHCPv6 is still giving /128
addresses in both cases.

So I'm still mystified in that both implementations think there's
something wrong, but I don't know what it is.

> dhcpcd is the only all-in-one solution :)

Indeed, and we find it useful to use it like that to control all dynamic
address and route assignment.  And it makes this all the more
perplexing, because if dhcpcd can use the prefix length to assign a
stateless address, why not use the same prefix length for the DHCPv6
address?  It wouldn't attempt to get the address at all if it hadn't
received the correct advertisement.


> dhcpcd is saying that a 3rd party deleted the address.

In that case, I know what the 3rd party is, so never mind this detail.


                   Graham

-- 
------------------------------

*Graham Breed*
Systems Developer, ApplianSys

ApplianSys House
Harry Weston Road
Coventry CV3 2UB

www.appliansys.com

*Our sales team sells by referral:*
Less time looking for customers, more time looking after them

ApplianSys Limited registered in England & Wales #: 07608382 at ApplianSys
House, Harry Weston Road, Coventry CV3 2UB