dhcpcd-discuss

On Sat, 11 Nov 2017 12:14:10 +0000
Roy Marples <roy@xxxxxxxxxxxx> wrote:

> On 07/11/2017 20:06, Roy Marples wrote:
> > On 07/11/2017 18:44, Neal P. Murphy wrote:  
> >> I will try HEAD tonight and test more thoroughly. And send more 
> >> detailed logs.  
> > 
> > Please do, but I suspect you'll have the same issue.
> > Please build dhcpcd on 3.4.109 headers or older.
> > I don't understand why the /128 address was added fine though .....  
> 
> Any update here? I'd like to release a new dhcpcd soon and ideally 
> without any known issues :)

After some time figuring out how to deal with dnsmasq, I didn't see substantive differences betweeen RC3 and HEAD. Both handle addresses and delegations with aplomb.
  - Should dhcpcd remove the internet IF's IP6 address on '-k'? It does remove the internal
    IF's addresses. Or, more generally, should it remove all addresses it assigned when it exits?

General iaid questions:
  - What are the limitations on iaids? Short-ish numbers or strings? Long-ish strings?
  - Is every interface-address combination supposed to have a unique iaid? That is, if my
    eth0 had 5 addresses assigned, should it have 5 iaids? And if my eth3 has a /128 and
    a /64 assigned, should it have two iaids? Is there clear documentation for this anywhere
    (your docs, RFCs, ec.)?

Now that I'm correctly telling dnsmasq to add/remove IP6 DNS servers, bringing the links up and down is fairly reliable. Comcrash *still* like to give me a /64 instead of a /60 now and again. I guess they don't like something I save, recover and dynamically include in the dhcpcd.conf; removing those files and starting from scratch seems to get it working again. Query? Would it be reasonable to have dhcpcd reject the /64 offer when it explicitly requested a /60? (Instead of taking it, assigning it to the first interface--eth3 in my case--and then failing to assign anything to the other IFs?) Of course, I have to verify that that is really what happens.

Thanks!
Neal