Arch Linux

wangchong

Member

Registered: 2013-06-25

Posts: 76

cannot access ipv6 after updated networkmanager and dhcpcd

I updated networkmanager and dhcpcd yesterday and cannot reach ipv6 site now.

ipv6 website cannot be reached:

[wangc@wangc-work ~]$ ping ipv6.google.com
ping: unknown host ipv6.google.com

I can confirm ipv6 accessibility because another computer in the same office can reach ipv6 website.

Can anyone help me with the issue?

Last edited by wangchong (2015-05-09 02:40:57)

Foucault

Member

From: Athens, Greece

Registered: 2010-04-06

Posts: 214

Re: cannot access ipv6 after updated networkmanager and dhcpcd

You need ping6 for ipv6 ping. Also check your routes with route -6 (or ip -6 route show enp3s0) and check if you can reach your gateway. It will be a fe80:: address that is displayed in the "Next Hop" column of the route output. Check if this corresponds to the default route (::/0). For example

Kernel IPv6 routing table
Destination                    Next Hop                   Flag Met Ref Use If
[some output]
::/0                           fe80::whatever             UG   1024 8     0 enp3s0
[some output]

See if you can reach your gateway with ping6 fe80::whatever%enp3s0.

Last edited by Foucault (2015-05-07 09:30:13)

---

AUR packages – github

wangchong

Member

Registered: 2013-06-25

Posts: 76

Re: cannot access ipv6 after updated networkmanager and dhcpcd

Thanks foucault, I can reach ipv6 site now, though I don't know what happened.

EDIT:

actually, this problem has not been solved.
Sometimes when I cannot reach ipv6 site, I restart NetworkManager:

sudo systemctl restart NetworkManager

This sometimes works and when it works, the wired menu in NetworkManager becomes "enp3s0"(usually it's "wired connections")

This is some journal

[wangc@wangc-work ~]$ sudo journalctl -u NetworkManager.service -n 200|grep -i v6
May 09 10:12:33 wangc-work NetworkManager[3341]: <info>  Policy set 'enp3s0' (enp3s0) as default for IPv6 routing and DNS.
May 09 10:12:43 wangc-work NetworkManager[3341]: <info>  Policy set 'enp3s0' (enp3s0) as default for IPv6 routing and DNS.
May 09 10:14:22 wangc-work NetworkManager[3510]: <info>  (enp3s0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 09 10:14:22 wangc-work NetworkManager[3510]: <info>  (enp3s0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) started...
May 09 10:14:22 wangc-work NetworkManager[3510]: <info>  (enp3s0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) complete.

EDIT:

A correction, I do not have an ipv6 address with NetworkManager and I found that I can disable NetworkManager and use dhcpcd to work around this.

[wangc@wangc-work ~]$ sudo dhcpcd enp3s0
enp3s0: adding address fe80::30a2:e2b8:c54c:abd8
DUID 00:01:00:01:1c:dc:74:6c:60:a4:4c:a9:ac:2e
enp3s0: IAID 4c:a9:ac:2e
enp3s0: soliciting an IPv6 router
enp3s0: rebinding lease of 166.111.26.195
enp3s0: Router Advertisement from fe80::3e61:4ff:fe44:eff0
enp3s0: adding address 2402:f000:1:1a01:9552:77a2:b636:436c/64
enp3s0: adding route to 2402:f000:1:1a01::/64
enp3s0: adding default route via fe80::3e61:4ff:fe44:eff0
enp3s0: NAK: from 166.111.8.17
enp3s0: deleting route to 166.111.26.0/23
enp3s0: soliciting a DHCP lease
enp3s0: offered 166.111.26.211 from 166.111.8.17
enp3s0: leased 166.111.26.211 for 3600 seconds
enp3s0: adding route to 166.111.26.0/23
enp3s0: adding default route via 166.111.26.1
forked to background, child pid 4031

Last edited by wangchong (2015-05-09 02:41:33)