Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54993 - [dhcpcd] loses IPv6 address

Attached to Project: Arch Linux
Opened by Nico Schottelius (telmich) - Monday, 31 July 2017, 17:37 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 05 August 2017, 15:33 GMT
Task Type Bug Report
Category Upstream Bugs
Status Assigned
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:

In IPv6 only networks, dhcpcd loses the IPv6 address that it acquires using RADVD after some time.

Reconnecting by reassociating the wireless, makes dhcpcd reacquire an IP, until it it loses it again.

dhcpcd correctly logs this behaviour, but behaves not as expected (i.e. re-acquiring an address):

Jul 31 18:44:24 manager wpa_supplicant[324]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to d4:ca:6d:e5:d3:0b completed [id=4 id_str=Digital Glarus IPv6]
Jul 31 18:44:24 manager dhcpcd[397]: wlp2s0: carrier acquired
Jul 31 18:44:24 manager dhcpcd[397]: wlp2s0: IAID 71:b0:31:78
Jul 31 18:44:24 manager dhcpcd[397]: wlp2s0: adding address fe80::2de:b169:47f0:50ff
Jul 31 18:44:24 manager dhcpcd[397]: wlp2s0: soliciting an IPv6 router
Jul 31 18:44:24 manager dhcpcd[397]: wlp2s0: soliciting a DHCP lease
Jul 31 18:44:25 manager dhcpcd[397]: wlp2s0: Router Advertisement from fe80::21b:21ff:febb:6934
Jul 31 18:44:25 manager dhcpcd[397]: wlp2s0: adding address 2a0a:e5c0:0:4:d910:cdfa:43fa:57d3/64
Jul 31 18:44:25 manager dhcpcd[397]: wlp2s0: adding route to 2a0a:e5c0:0:4::/64
Jul 31 18:44:25 manager dhcpcd[397]: wlp2s0: adding default route via fe80::21b:21ff:febb:6934

[...]

Jul 31 19:12:43 manager wpa_supplicant[324]: wlp2s0: WPA: Group rekeying completed with d4:ca:6d:e5:d3:0b [GTK=CCMP]
Jul 31 19:17:43 manager wpa_supplicant[324]: wlp2s0: WPA: Group rekeying completed with d4:ca:6d:e5:d3:0b [GTK=CCMP]
Jul 31 19:22:43 manager wpa_supplicant[324]: wlp2s0: WPA: Group rekeying completed with d4:ca:6d:e5:d3:0b [GTK=CCMP]
Jul 31 19:27:43 manager wpa_supplicant[324]: wlp2s0: WPA: Group rekeying completed with d4:ca:6d:e5:d3:0b [GTK=CCMP]
Jul 31 19:31:16 manager dhcpcd[397]: wlp2s0: fe80::21b:21ff:febb:6934: router expired
Jul 31 19:31:16 manager dhcpcd[397]: wlp2s0: deleting default route via fe80::21b:21ff:febb:6934



Additional info:
* package version(s)
* config and/or log files etc.

[19:32] manager:annex% pacman -Q | grep dhcp
dhcpcd 6.11.5-1


Steps to reproduce:

Connect to IPv6 only network, wait some time, IPv6 address is deleted and not reacquired.
This task depends upon

Comment by Nico Schottelius (telmich) - Saturday, 05 August 2017, 21:09 GMT
Can I help somehow by providing more information / logs or similar?
Comment by Roy Marples (rsmarples) - Sunday, 06 August 2017, 16:20 GMT
You can attach a wireshark trace of the interface - just icmp6 is required.
But from the log snippet it looks like the router is only responding to solicitations, and isn't broadcasting periodically as it should.
Comment by Nico Schottelius (telmich) - Sunday, 06 August 2017, 17:53 GMT
Sure, I will as soon as I am in that network again.

Just for reference, I attached the radvd configuration from the routers:

# Coworking
interface bond0.7
{
AdvSendAdvert on;

prefix 2a0a:e5c0:0:4::/64 {
};

RDNSS 2a0a:e5c0::3 2a0a:e5c0::4 { AdvRDNSSLifetime 6000; };
DNSSL place5.ungleich.ch { AdvDNSSLLifetime 6000; } ;
};

It also makes me wonder that other machines running Devuan don't lose their ip address, but I will further check that as well.
Comment by Roy Marples (rsmarples) - Sunday, 06 August 2017, 19:36 GMT
> It also makes me wonder that other machines running Devuan don't lose their ip address, but I will further check that as well.

Maybe I can re-word it better :)
Your logs show that dhcpcd didn't receive an unsolicited Router Advertisement.
If it did, then it would at least have logged *something* if you enable `debug` in dhcpcd.conf
Comment by Nico Schottelius (telmich) - Friday, 01 September 2017, 08:47 GMT
Hey!

It seems like the last message exchange before losing the IP is after sending the advertisement. PCAP is attached.

Capturing on 'wlp4s0'
1 0.000000000 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
2 0.000048257 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
3 138.642000141 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
4 138.642029756 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
5 278.326204675 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
6 278.326265210 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
7 312.845732385 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
8 312.845791271 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
9 372.955001302 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
10 372.955058571 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
11 401.618089485 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
12 401.618132192 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
13 443.187113710 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
14 443.187165521 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
15 470.838696548 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
16 470.838739425 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
17 496.959971566 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
18 496.960017049 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
19 543.033043441 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
20 543.033094414 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
21 616.965029443 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
22 616.965088532 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
23 809.989269772 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
24 809.989325868 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
25 814.997320909 fe80::8499:7937:82fe:4fa5 → fe80::21b:21ff:febb:6934 ICMPv6 86 Neighbor Solicitation for fe80::21b:21ff:febb:6934 from e4:a7:a0:0a:a6:9f
26 815.095840932 fe80::21b:21ff:febb:6934 → fe80::8499:7937:82fe:4fa5 ICMPv6 78 Neighbor Advertisement fe80::21b:21ff:febb:6934 (rtr, sol)
27 820.244427494 fe80::21b:21ff:febb:6934 → fe80::8499:7937:82fe:4fa5 ICMPv6 86 Neighbor Solicitation for fe80::8499:7937:82fe:4fa5 from 00:1b:21:bb:69:34
28 820.244484786 fe80::8499:7937:82fe:4fa5 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement fe80::8499:7937:82fe:4fa5 (sol)
29 881.162902084 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
30 881.162949786 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
31 886.250650379 fe80::8499:7937:82fe:4fa5 → fe80::21b:21ff:febb:6934 ICMPv6 86 Neighbor Solicitation for fe80::21b:21ff:febb:6934 from e4:a7:a0:0a:a6:9f
32 886.258259440 fe80::21b:21ff:febb:6934 → fe80::8499:7937:82fe:4fa5 ICMPv6 78 Neighbor Advertisement fe80::21b:21ff:febb:6934 (rtr, sol)
33 891.413815808 fe80::21b:21ff:febb:6934 → fe80::8499:7937:82fe:4fa5 ICMPv6 86 Neighbor Solicitation for fe80::8499:7937:82fe:4fa5 from 00:1b:21:bb:69:34
34 891.413868964 fe80::8499:7937:82fe:4fa5 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement fe80::8499:7937:82fe:4fa5 (sol)
35 956.953663274 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
36 956.953717387 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)
37 961.983405104 fe80::8499:7937:82fe:4fa5 → fe80::21b:21ff:febb:6934 ICMPv6 86 Neighbor Solicitation for fe80::21b:21ff:febb:6934 from e4:a7:a0:0a:a6:9f
38 962.055981466 fe80::21b:21ff:febb:6934 → fe80::8499:7937:82fe:4fa5 ICMPv6 78 Neighbor Advertisement fe80::21b:21ff:febb:6934 (rtr, sol)
39 967.174980643 fe80::21b:21ff:febb:6934 → fe80::8499:7937:82fe:4fa5 ICMPv6 86 Neighbor Solicitation for fe80::8499:7937:82fe:4fa5 from 00:1b:21:bb:69:34
40 967.175019529 fe80::8499:7937:82fe:4fa5 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement fe80::8499:7937:82fe:4fa5 (sol)
41 989.395779674 fe80::21b:21ff:febb:6934 → 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 ICMPv6 86 Neighbor Solicitation for 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 from 00:1b:21:bb:69:34
42 989.395835201 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 → fe80::21b:21ff:febb:6934 ICMPv6 78 Neighbor Advertisement 2a0a:e5c0:0:4:6de6:d72f:b086:9cd2 (sol)

Comment by Nico Schottelius (telmich) - Thursday, 14 September 2017, 13:46 GMT
ping
Comment by Roy Marples (rsmarples) - Thursday, 14 September 2017, 13:52 GMT
I don't see a dhcpcd log here.
But from your log above, there is no Router Advertisement.
So the IPv6 address could easily be lost if it's not refreshed.

I don't see this as dhcpcd issue.
Comment by Nico Schottelius (telmich) - Friday, 29 September 2017, 10:57 GMT
Fun fact: if I keep a ping running, dhcpcd does *not* lose the ipv6 address.
Comment by Nico Schottelius (telmich) - Saturday, 16 November 2019, 12:11 GMT
This is fixed in the upstream package 8.1.2

Loading...