dhcpcd-discuss

On 30/10/2017 20:38, Jakub Jankowski wrote:
> On 2017-10-25, Roy Marples wrote:
> > I'll guess that you started dhcpcd on a specific interface as it's 
> > bound to lladdr.
> > You can either start dhcpcd in master mode (ie don't specify an 
> > interface on the command line or pass it the -M flag or add master to 
> > dhcpcd.conf) or try the latest git head where I think I've fixed this 
> > here:
> > https://roy.marples.name/git/dhcpcd.git/commit/?id=ef53a17e01fc25aea22717373afcfcd9e35c85b5 
> >
> >
> > That should always let the kernel decide what address to send from, as 
> > long as it's on the interface.
> >
> > Let me know if that fixes it for you!
>
> Thanks! I've build dhcpcd from HEAD and indeed the subsequent Renew 
> packets now originate from my IA_NA address.
> I'm still puzzled by the fact I'm not getting any responses from my 
> ISP's DHCP server, but I think my side is now doing everything as expected.
> I'm having a case opened with my ISP, let's see if they can figure it out.

It might be that the unicast reply to you is now being received for an 
address on a different interface. I've been working on code to handle 
this for a few days now, but I've just lacked the time to progress it 
recently.

This is already done for IPv4 due to shared IP addressing, but it looks 
like it's more imperitive for IPv6 because we listen to the address 
instead of what's actually received on the interface (our IPv6 
implementation doesn't use BPF at all).

Hopefully I'll find the time to finish this soon.
In the meantime though, you could run a tcpdump on all interfaces to see 
if this indeed the case, or that your ISP is as you say, silent.
If it *is* silent, it might be because it didn't bind the sending of the 
address to the dhcpv6_client port (which it cannot do becasue it's not 
in master mode).

Roy