dhcpcd-discuss

On 02/02/2016 15:58, Nicholas Williams wrote:
> Okay, so here's where I'm not following. As shown below, I can configure
> the interface with dhcpcd, get an IPv6 address, and use it, but my
> DHCPv6 lease info is empty:
> 
> $ ifconfig eth2
> eth2      Link encap:Ethernet  HWaddr 08:00:27:21:d4:16  
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:12 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:2351 (2.3 KB)  TX bytes:4360 (4.3 KB)
> 
> $ sudo dhcpcd eth2
> eth2: adding address fe80::a00:27ff:fe21:d416
> eth2: waiting for carrier
> eth2: carrier acquired
> DUID 00:01:00:01:1e:43:88:3a:08:00:27:21:d4:16
> eth2: IAID 27:21:d4:16
> eth2: soliciting an IPv6 router
> eth2: rebinding lease of 172.20.10.6
> eth2: probing address 172.20.10.6/28 <http://172.20.10.6/28>
> eth2: Router Advertisement from fe80::87:17f5:6412:6666
> eth2: adding address 2600:1004:b140:f81a:a00:27ff:fe21:d416/64
> eth2: requesting DHCPv6 information
> forked to background, child pid 3295
> 
> $ ifconfig eth2
> eth2      Link encap:Ethernet  HWaddr 08:00:27:21:d4:16  
>           inet addr:172.20.10.6  Bcast:172.20.10.15  Mask:255.255.255.240
>           inet6 addr: 2600:1004:b140:f81a:ac07:d36c:5c5a:4d56/64
> Scope:Global
>           inet6 addr: fe80::a00:27ff:fe21:d416/64 Scope:Link
>           inet6 addr: 2600:1004:b140:f81a:a00:27ff:fe21:d416/64 Scope:Global
> 
> $ ping6 2a03:b0c0:1:d0::2da:c001
> PING 2a03:b0c0:1:d0::2da:c001(2a03:b0c0:1:d0::2da:c001) 56 data bytes
> 64 bytes from 2a03:b0c0:1:d0::2da:c001: icmp_seq=1 ttl=52 time=153 ms
> 
> $ sudo dhcpcd -U6 eth2
> dhcp6_client_id='000100011e43883a08002721d416'
> dhcp6_name_servers='fe80::87:17f5:6412:6666%eth2'
> dhcp6_reconfigure_accept='1'
> dhcp6_server_id='000100011e438ac66e72e753d864'
> 
> That's it. There's no more information in my lease. I don't
> have dhcp6_ia_na1_ia_addr1, name_servers, domain_search, or any other of
> the information you have in your lease in my lease. What am I missing /
> misunderstanding?

That address looks like it was configured from the result of a RS/RA
transaction, not DHCPv6.

You don't *need* DHCPv6 at all for auto configured IPv6 to work - you
can even transmit DNS information in the RA these days.

Again, you're posting dhcpcd output but stopping when it forks.
We need to see the logs after it forks.
In in doubt, use the --logfile /tmp/dhcpcd.log option when starting it
and attach that file next time.

Roy