dhcpcd-discuss

Puzzled by DHCPv6 in many ways

Tobias Klausmann

Fri Jun 09 18:29:40 2017

Hey,

$ dhcpcd --version
dhcpcd 7.0.0-rc1
Copyright (c) 2006-2017 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH
$ 

So I have been using dhcpcd for a few days to get v4 and v6
addresses plus a prefix delegation from my ISP (init7).

Interestingly, if you use PD, dhcpcd goes on to solicit addresses
on all interfaces mentioned, including the ones that prefixes are
delegated to, for some reason. But that is a problem I'll deal
with once I have figured out the one below.

IPv4 works okay:

DUID 00:01:00:01:20:cd:93:8a:00:0e:0c:72:4d:35
wan1: IAID 0c:72:4d:35
wan1: soliciting a DHCP lease
wan1: offered 185.72.66.139 from 77.109.140.123 `ligustica.init7.net'
wan1: ignoring offer of 185.72.66.212 from 213.144.129.5 `carnica.init7.net'
wan1: probing address 185.72.66.139/25
wan1: leased 185.72.66.139 for 1800 seconds
wan1: adding route to 185.72.66.128/25
wan1: adding default route via 185.72.66.129
forked to background, child pid 13757                                             

But note how it never even tries to solicit a v6 address. I have
searched high and low for a way to get dhcpcd to tell me *why* it
doesn't even try, to no avail. Note that that it *used* to do so,
but at some point it stopped. Deleting the fe80 address from the
i/f, nuking the lease files and even the DUID file and secret did
not help. 

What am I doing wrong?

Config:

$ grep -Ev '^(\ *#|$)' /etc/dhcpcd.conf                                  
duid                                                                             
persistent
option rapid_commit
option classless_static_routes
option interface_mtu
nooption domain_name_servers, domain_name, domain_search, host_name
require dhcp_server_identifier
allowinterfaces wan1
persistent
nohook lookup-hostname, resolv.conf, hostname, ntp, timezone
noipv4ll
noipv6rs
timeout 0
$

Below is with v4 already configured and that dhcpcd still running,
dunno if that is supported. Without wan1 being configured, the
same happens.

# dhcpcd -C resolv.conf -C ntp.conf -C yp.conf -h '' --ipv6only -d  -m 4 wan1
dhcpcd-7.0.0-rc1 starting                
wan1: executing `/lib/dhcpcd/dhcpcd-run-hooks' PREINIT                            
wan1: executing `/lib/dhcpcd/dhcpcd-run-hooks' CARRIER                            
DUID 00:01:00:01:20:cd:93:8a:00:0e:0c:72:4d:35                                    
wan1: IAID 0c:72:4d:35                   
[hangs here forever, no DHCPv6 solicitations visible in tcpdump]

Regards,
Tobias

-- 
Sent from aboard the Culture ship
	But Who's Counting?

Follow-Ups:
Re: Puzzled by DHCPv6 in many waysTobias Klausmann
Archive administrator: postmaster@marples.name