dhcpcd-discuss

Re: prefix delegation on multiple devices; only one delegates prefix gets renewed

David Flatz

Tue May 23 11:33:51 2017

Hey Roy

Roy Marples (2017-05-23 09:35+0100):
On 22/05/2017 19:11, David Flatz wrote:
I'm running dhcpcd 6.11.5 on x86_64 void linux with musl.  I've
configured it to obtain a prefix from my ISP and delegate it to two
interfaces.  At the initial launch both interfaces get a working address
and routes but when dhcpcd tries to renew only one of those interfaces
keeps its address and the other one stops working.

...

I have no idea whether this is a problem with my configuration, with my
ISP or with dhcpcd.

It's a problem with dhcpcd, probably fixed here:
https://dev.marples.name/D112

It might apply cleanly to dhcpcd-6, let me know how it works for you!

Thanks for the reply.

The patch didn't apply cleanly on dhcpcd-6 and modifying it by hand only resulted in segfaults. So I switched to 7.0.0-rc1 with the patch applied. Unfortunately the behaviour is still the same:

#v+
info: May 23 10:23:30 [20399]: dev: loaded udev
info: May 23 10:23:30 [20399]: DUID 00:01:00:01:20:b1:c0:37:00:0d:b9:40:82:48
info: May 23 10:23:30 [20399]: enp1s0: IAID b9:40:82:48
info: May 23 10:23:30 [20399]: enp1s0: IAID 00:00:00:00
info: May 23 10:23:30 [20399]: enp1s0: soliciting a DHCPv6 lease
info: May 23 10:23:30 [20399]: enp2s0: IAID b9:40:82:49
info: May 23 10:23:30 [20399]: enp2s0: using static address 192.168.13.1/24
info: May 23 10:23:30 [20399]: enp2s0: adding route to 192.168.13.0/24
info: May 23 10:23:30 [20399]: enp3s0: IAID b9:40:82:4a
info: May 23 10:23:30 [20399]: enp3s0: using static address 192.168.5.1/24
info: May 23 10:23:30 [20399]: enp3s0: adding route to 192.168.5.0/24
info: May 23 10:23:30 [20399]: enp1s0: soliciting an IPv6 router
info: May 23 10:23:30 [20399]: enp1s0: Router Advertisement from fe80::1edf:fff:feb6:967f
info: May 23 10:23:30 [20399]: enp1s0: adding address 2a02:168:2000:e:1bb7:71cc:3092:230d/64
info: May 23 10:23:30 [20399]: enp1s0: adding route to 2a02:168:2000:e::/64
info: May 23 10:23:30 [20399]: enp1s0: adding default route via fe80::1edf:fff:feb6:967f
info: May 23 10:23:31 [20399]: enp1s0: soliciting a DHCP lease
info: May 23 10:23:31 [20399]: enp1s0: ADV 2a02:168:5cf3::/48 from fe80::1edf:fff:feb6:967f
info: May 23 10:23:31 [20399]: enp1s0: accepted reconfigure key
info: May 23 10:23:31 [20399]: enp1s0: REPLY6 received from fe80::1edf:fff:feb6:967f
info: May 23 10:23:31 [20399]: enp1s0: renew in 1200, rebind in 1800, expire in 86400 seconds
info: May 23 10:23:31 [20399]: lo: adding reject route to 2a02:168:5cf3::/48
info: May 23 10:23:31 [20399]: enp1s0: delegated prefix 2a02:168:5cf3::/48
info: May 23 10:23:31 [20399]: enp2s0: adding address 2a02:168:5cf3:d::1/64
info: May 23 10:23:31 [20399]: enp2s0: adding route to 2a02:168:5cf3:d::/64
info: May 23 10:23:31 [20399]: enp3s0: adding address 2a02:168:5cf3:5::1/64
info: May 23 10:23:31 [20399]: enp3s0: adding route to 2a02:168:5cf3:5::/64
info: May 23 10:43:35 [20399]: lo: deleting reject route to 2a02:168:5cf3::/48
info: May 23 10:45:53 [20399]: enp1s0: offered 212.51.143.146 from 77.109.140.123 `ligustica.init7.net'
info: May 23 10:45:53 [20399]: enp1s0: probing address 212.51.143.146/24
info: May 23 10:45:59 [20399]: enp1s0: leased 212.51.143.146 for 1800 seconds
info: May 23 10:45:59 [20399]: enp1s0: adding route to 212.51.143.0/24
info: May 23 10:45:59 [20399]: enp1s0: adding default route via 212.51.143.1
warn: May 23 10:53:31 [20399]: enp1s0: failed to renew DHCPv6, rebinding
warn: May 23 10:53:32 [20399]: enp1s0: fe80::1edf:fff:feb6:967f: DHCPv6 REPLY missing Prefix
err: May 23 10:53:32 [20399]: enp1s0: no useable IA found in lease
info: May 23 10:53:32 [20399]: enp2s0: deleting address 2a02:168:5cf3:d::1/64
info: May 23 10:53:32 [20399]: enp2s0: deleting route to 2a02:168:5cf3:d::/64
info: May 23 10:53:32 [20399]: enp3s0: deleting address 2a02:168:5cf3:5::1/64
info: May 23 10:53:32 [20399]: enp3s0: deleting route to 2a02:168:5cf3:5::/64
info: May 23 10:53:32 [20399]: enp1s0: soliciting a DHCPv6 lease
info: May 23 10:53:32 [20399]: enp1s0: ADV 2a02:168:5cf3::/48 from fe80::1edf:fff:feb6:967f
info: May 23 10:53:33 [20399]: enp1s0: accepted reconfigure key
info: May 23 10:53:33 [20399]: enp1s0: REPLY6 received from fe80::1edf:fff:feb6:967f
info: May 23 10:53:33 [20399]: enp1s0: renew in 1200, rebind in 1800, expire in 86400 seconds
info: May 23 10:53:33 [20399]: lo: adding reject route to 2a02:168:5cf3::/48
info: May 23 10:53:33 [20399]: enp1s0: delegated prefix 2a02:168:5cf3::/48
info: May 23 10:53:33 [20399]: enp2s0: adding address 2a02:168:5cf3:d::1/64
info: May 23 10:53:33 [20399]: enp2s0: adding route to 2a02:168:5cf3:d::/64
info: May 23 11:13:36 [20399]: lo: deleting reject route to 2a02:168:5cf3::/48
#v-

I didn't reboot, so there might still be old addresses and routes around, I don't know if that's a problem and if I should try again with a clean reboot.

I noticed that on the initial request the "no useable IA found in lease" and "REPLY missing Prefix" messages didn't show up anymore but on renew they are there again.

Config stayed the same.

Just tell me if I can supply you with more info.

David

Follow-Ups:
Re: prefix delegation on multiple devices; only one delegates prefix gets renewedRoy Marples
References:
prefix delegation on multiple devices; only one delegates prefix gets renewedDavid Flatz
Re: prefix delegation on multiple devices; only one delegates prefix gets renewedRoy Marples
Archive administrator: postmaster@marples.name