dhcpcd-discuss

It appears that dhcpcd-9999 fully passed my test.  Initial startup looked
fully correct.  I power cycled the modem and it was able to re-acquire both
an ivp4 and ipv6 address, and the default ipv6 route looks correct.  I
never saw the ipv6 route get removed on 'watch -n 1 route -6n', so I'm not
sure if that's correct, but it appears to be functioning.  I do see the
'adding route to <ipv6prefix>' in the log during re-bind though, which I
didn't under 6.11.3.  7.0.0-rc1 had something weird going on that tried to
renew on all my interfaces, and I think that was actually causing the v6
problem on rebind.  9999 didn't do the same.

As a final test, I manually deleted the v6 default route while my modem was
off.  when it turned back on, dhcpcd-9999 got both v4 and v6 leases
correctly, and set up the default routes correctly.

Thank you for the help,
I'll watch for the next 7.0.0 release and re-test on that.  Enjoy Spain.

Nathan


On Sat, May 27, 2017 at 9:39 AM Roy Marples <roy@xxxxxxxxxxxx> wrote:

> On 27/05/2017 14:36, Nathan O'Meara wrote:
> > I just tried 7.0.0-rc1, and while it works similarly on first bind, I
> > did notice that it seems to be trying to get DHCP leases on all
> > adapters, not only the one listed in the config.  It also seemed to fail
> > to rebind the ipv6 address at all after I power cycled the modem.. about
> > to try 9999.
>
> I don't expect any to pass the renew or rebind, that seems an issue with
> your upstream.
> We can analyse tcpdumps to work out more.
>
> We are only concerned about the correctness of the routes being applied
> after getting a new lease.
>
> Roy
>