Ping to distant servers does not resolve

hurrlipurr · 2019-09-28 13:22:40

Hi,

I just tried to install arch on my laptop for the first time following the steps on https://wiki.archlinux.de/title/Anleitu … Einsteiger

Everything worked fine, but somehow addresses won't get resolved, eg a ping to www.archlinux.org does not work while a ping to another machine in the local network works fine. I could manually fix this by
dhcpcd enp0s25
in the beginning, but after rebooting even this does not work any more, I just get back
dhcsp already running on pid 488
but ping still does not work.

I have another PC running Manjaro linux and I compared the /etc/resolv.conf. They look very similar on both systems.

I also read through some articles on network configuration and DHCP but nothing really helped.

I have no idea where I have to look. Any help would be very appreciated.

Thank you,
Oliver

Lone_Wolf · 2019-09-28 14:49:28

Please post the output of

$ ping 2a01:4f8:172:1d86::1
$ ping -4  138.201.81.199
$ ls -lR /etc/systemd/system

The first 2 commands ping www.archlinux.org directly by ipv6 & ipv4-address, the last one should show all user enabled systemd services*.

*
For listing services systemctl list-unit-files --state=enabled is often recommended.
On my system however that command doesn't list dhcpcd@enp4s0.service and syslog-ng@default.service which are enabled.
Makes me wonder whatother things systemctl misses.

hurrlipurr · 2019-09-28 17:05:45

Here we go...

[root@myhost oliver]# ping 2a01:4f8:172:1d86::1
PING 2a01:4f8:172:1d86::1(2a01:4f8:172:1d86::1) 56 data bytes
^C
--- 2a01:4f8:172:1d86::1 ping statistics ---
52 packets transmitted, 0 received, 100% packet loss, time 51683ms

[root@myhost oliver]# ping -4  138.201.81.199
PING 138.201.81.199 (138.201.81.199) 56(84) bytes of data.
64 bytes from 138.201.81.199: icmp_seq=1 ttl=54 time=20.6 ms
64 bytes from 138.201.81.199: icmp_seq=2 ttl=54 time=16.7 ms
64 bytes from 138.201.81.199: icmp_seq=3 ttl=54 time=16.8 ms
^C
--- 138.201.81.199 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 16.691/18.047/20.610/1.812 ms
[root@myhost oliver]# ls -lR /etc/systemd/system
/etc/systemd/system:
insgesamt 20
lrwxrwxrwx 1 root root   44 28. Sep 14:36 dbus-org.freedesktop.Avahi.service -> /usr/lib/systemd/system/avahi-daemon.service
lrwxrwxrwx 1 root root   49 28. Sep 14:37 dbus-org.freedesktop.timesync1.service -> /usr/lib/systemd/system/systemd-timesyncd.service
drwxr-xr-x 2 root root 4096 28. Sep 13:55 getty.target.wants
drwxr-xr-x 2 root root 4096 28. Sep 19:02 multi-user.target.wants
drwxr-xr-x 2 root root 4096 28. Sep 14:36 printer.target.wants
drwxr-xr-x 2 root root 4096 28. Sep 14:36 sockets.target.wants
drwxr-xr-x 2 root root 4096 28. Sep 14:37 sysinit.target.wants

/etc/systemd/system/getty.target.wants:
insgesamt 0
lrwxrwxrwx 1 root root 38 28. Sep 13:55 getty@tty1.service -> /usr/lib/systemd/system/getty@.service

/etc/systemd/system/multi-user.target.wants:
insgesamt 0
lrwxrwxrwx 1 root root 37 28. Sep 14:36 acpid.service -> /usr/lib/systemd/system/acpid.service
lrwxrwxrwx 1 root root 44 28. Sep 14:36 avahi-daemon.service -> /usr/lib/systemd/system/avahi-daemon.service
lrwxrwxrwx 1 root root 39 28. Sep 15:00 dhcpcd@enp0s25.service -> /usr/lib/systemd/system/dhcpcd@.service
lrwxrwxrwx 1 root root 38 28. Sep 15:51 dhcpcd.service -> /usr/lib/systemd/system/dhcpcd.service
lrwxrwxrwx 1 root root 43 28. Sep 14:36 org.cups.cupsd.path -> /usr/lib/systemd/system/org.cups.cupsd.path
lrwxrwxrwx 1 root root 40 28. Sep 13:55 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 36 28. Sep 19:02 sshd.service -> /usr/lib/systemd/system/sshd.service

/etc/systemd/system/printer.target.wants:
insgesamt 0
lrwxrwxrwx 1 root root 46 28. Sep 14:36 org.cups.cupsd.service -> /usr/lib/systemd/system/org.cups.cupsd.service

/etc/systemd/system/sockets.target.wants:
insgesamt 0
lrwxrwxrwx 1 root root 43 28. Sep 14:36 avahi-daemon.socket -> /usr/lib/systemd/system/avahi-daemon.socket
lrwxrwxrwx 1 root root 45 28. Sep 14:36 org.cups.cupsd.socket -> /usr/lib/systemd/system/org.cups.cupsd.socket

/etc/systemd/system/sysinit.target.wants:
insgesamt 0
lrwxrwxrwx 1 root root 49 28. Sep 14:37 systemd-timesyncd.service -> /usr/lib/systemd/system/systemd-timesyncd.service

Lone_Wolf · 2019-09-28 19:49:55

lrwxrwxrwx 1 root root 39 28. Sep 15:00 dhcpcd@enp0s25.service -> /usr/lib/systemd/system/dhcpcd@.service
lrwxrwxrwx 1 root root 38 28. Sep 15:51 dhcpcd.service -> /usr/lib/systemd/system/dhcpcd.service

Looks like you have 2x running network services. Disable dhcpcd.service and reboot .

then run

$ ping -4 www.archlinux.org
$ ping www.archlinux.org

hurrlipurr · 2019-09-28 22:43:32

After reboot I get:

[oliver@myhost ~]$ ls -lR /etc/systemd/system | grep dhcpcd
lrwxrwxrwx 1 root root 39 28. Sep 15:00 dhcpcd@enp0s25.service -> /usr/lib/systemd/system/dhcpcd@.service

...but still...

[oliver@myhost ~]$ ping www.archlinux.org
PING www.archlinux.org(apollo.archlinux.org (2a01:4f8:172:1d86::1)) 56 data bytes
^C
--- www.archlinux.org ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms

[oliver@myhost ~]$ ping -4 www.archlinux.org
PING apollo.archlinux.org (138.201.81.199) 56(84) bytes of data.
64 bytes from apollo.archlinux.org (138.201.81.199): icmp_seq=1 ttl=54 time=20.4 ms
64 bytes from apollo.archlinux.org (138.201.81.199): icmp_seq=2 ttl=54 time=16.0 ms
64 bytes from apollo.archlinux.org (138.201.81.199): icmp_seq=3 ttl=54 time=13.7 ms
^C
--- apollo.archlinux.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 13.652/16.671/20.371/2.784 ms

Lone_Wolf · 2019-09-29 10:16:50

[oliver@myhost ~]$ ping www.archlinux.org
PING www.archlinux.org(apollo.archlinux.org (2a01:4f8:172:1d86::1)) 56 data bytes
^C
--- www.archlinux.org ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms

[oliver@myhost ~]$

That shows us ipv6 name resolving is working, but something is blocking the response to ipv6 ping.
Firewalls/proxies do this, but your service list doesn't include those.

install traceroute from core repo.

post

$ traceroute www.archlinux.org

WorMzy · 2019-09-29 11:36:06

Mod note: Not an installation issue, moving to Networking.

hurrlipurr · 2019-09-29 16:18:03

[oliver@myhost ~]$ traceroute www.archlinux.org
traceroute to www.archlinux.org (138.201.81.199), 30 hops max, 60 byte packets
 1  _gateway (192.168.178.1)  0.587 ms  0.561 ms  0.532 ms
 2  * * *
 3  81.210.134.80 (81.210.134.80)  18.063 ms  17.981 ms  17.991 ms
 4  de-fra04d-rc1-ae20-0.aorta.net (84.116.196.226)  20.275 ms  21.190 ms  20.155 ms
 5  de-fra03b-ri1-ae5-0.aorta.net (84.116.133.118)  17.861 ms  18.775 ms  17.786 ms
 6  ix-ae-27-0.tcore1.fr0-frankfurt.as6453.net (195.219.50.106)  17.758 ms  18.191 ms  18.145 ms
 7  195.219.219.10 (195.219.219.10)  19.421 ms  19.034 ms  18.905 ms
 8  core24.fsn1.hetzner.com (213.239.203.150)  24.702 ms core23.fsn1.hetzner.com (213.239.229.74)  24.696 ms core24.fsn1.hetzner.com (213.239.203.150)  24.531 ms
 9  ex9k2.dc8.fsn1.hetzner.com (213.239.229.22)  25.572 ms ex9k2.dc8.fsn1.hetzner.com (213.239.229.18)  24.867 ms ex9k2.dc8.fsn1.hetzner.com (213.239.229.22)  24.696 ms
10  apollo.archlinux.org (138.201.81.199)  23.619 ms !X  22.582 ms !X  22.530 ms !X

Lone_Wolf · 2019-09-30 08:41:54

ooops, forgot traceroute default is IPv4.

$ traceroute -6 www.archlinux.org

Once you have the ipv6 list, ping each listed hop to determine where the ipv6 ping responses stop coming.
I suggest to start at the top of the list.

hurrlipurr · 2019-09-30 18:46:57

[oliver@myhost ~]$ traceroute -6 www.archlinux.org
traceroute to www.archlinux.org (2a01:4f8:172:1d86::1), 30 hops max, 80 byte packets
 1  2002:b2c9:1594:8000:464e:6dff:fe2c:3766 (2002:b2c9:1594:8000:464e:6dff:fe2c:3766)  38.975 ms  39.103 ms  39.076 ms
 2  * * *
...
29  * * *
30  * * *
[oliver@myhost ~]$ ping 2002:b2c9:1594:8000:464e:6dff:fe2c:3766
PING 2002:b2c9:1594:8000:464e:6dff:fe2c:3766(2002:b2c9:1594:8000:464e:6dff:fe2c:3766) 56 data bytes
64 bytes from 2002:b2c9:1594:8000:464e:6dff:fe2c:3766: icmp_seq=1 ttl=64 time=4.05 ms
64 bytes from 2002:b2c9:1594:8000:464e:6dff:fe2c:3766: icmp_seq=2 ttl=64 time=0.387 ms
64 bytes from 2002:b2c9:1594:8000:464e:6dff:fe2c:3766: icmp_seq=3 ttl=64 time=0.397 ms
64 bytes from 2002:b2c9:1594:8000:464e:6dff:fe2c:3766: icmp_seq=4 ttl=64 time=0.382 ms
64 bytes from 2002:b2c9:1594:8000:464e:6dff:fe2c:3766: icmp_seq=5 ttl=64 time=0.326 ms
^C
--- 2002:b2c9:1594:8000:464e:6dff:fe2c:3766 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4055ms
rtt min/avg/max/mdev = 0.326/1.107/4.045/1.469 ms

Lone_Wolf · 2019-10-01 11:48:22

Here's my traceroute -6 for comparison

$ traceroute -6 www.archlinux.org
traceroute to www.archlinux.org (2a01:4f8:172:1d86::1), 30 hops max, 80 byte packets
 1  fritz.box (2001:980:d230:1:eadf:70ff:fea5:680e)  1.217 ms  1.710 ms  2.271 ms
 2  lo0.dr14.d12.xs4all.net (2001:888:1:1004::1)  23.919 ms  23.928 ms  24.078 ms
 3  0.ae24.xr4.1d12.xs4all.net (2001:888:1:4047::1)  14.948 ms  21.196 ms 0.ae24.xr3.3d12.xs4all.net (2001:888:1:4046::1)  17.068 ms
 4  et-7-1-0.xr1.tc2.xs4all.net (2001:888:1:4000::1)  16.883 ms 0.so-1-2-0.xr1.tc2.xs4all.net (2001:888:1:4001::1)  17.091 ms 0.ge-1-2-0.xr1.sara.xs4all.net (2001:888:1:4005::1)  26.076 ms
 5  ae4-0.ams10.core-backbone.com (2001:7f8:1::a503:3891:1)  18.344 ms  19.066 ms  19.065 ms
 6  ae16-2074.fra10.core-backbone.com (2a01:4a0:0:2074::3)  24.880 ms  16.932 ms  16.936 ms
 7  2a01:4a0:0:2021::4 (2a01:4a0:0:2021::4)  17.425 ms  16.932 ms  17.242 ms
 8  2a01:4a0:1338:3::2 (2a01:4a0:1338:3::2)  18.028 ms  18.444 ms  17.940 ms
 9  2a01:4f8:0:3::335 (2a01:4f8:0:3::335)  22.499 ms 2a01:4f8:0:3::339 (2a01:4f8:0:3::339)  21.458 ms  21.365 ms
10  ex9k2.dc8.fsn1.hetzner.com (2a01:4f8:0:3::186)  20.843 ms  21.585 ms ex9k2.dc8.fsn1.hetzner.com (2a01:4f8:0:3::182)  21.147 ms
11  apollo.archlinux.org (2a01:4f8:172:1d86::1)  22.000 ms !X  21.711 ms !X  21.809 ms !X
$

install whois from extra

$ whois 2001:980:d230:1:eadf:70ff:fea5:680e    # first hop in my traceroute
$ whois 2002:b2c9:1594:8000:464e:6dff:fe2c:3766 # first hop of hurrlipurr traceroute

compare the outputs.

To me this suggests your provider doesn't give you dual ipv4 / ipv6 stack support but some kind of 6to4 setup .

I suggest you run

$ ping -6 www.archlinux.org
$ traceroute -6 www.archlinux.org

on another linux system (like the manjaro pc you mentioned or some livecd from another distro) to verify this is not distro related.

hurrlipurr · 2019-10-01 18:37:47

Yes, you are right:

Querying for the IPv4 endpoint 178.201.21.148 of a 6to4 IPv6 address.

BTW it's the same behavior on both machines. Don't know how the IPv6 ping ever worked on my PC.

I will contact my provider and ask them to change that.

Thank you very much for your support!

Oliver

Lone_Wolf · 2019-10-06 12:10:35

HTH, keep us posted on the outcome.

Also please edit your first post in this thread and add [Solved] to the title.

Arch Linux

#1 2019-09-28 13:22:40

Ping to distant servers does not resolve

#2 2019-09-28 14:49:28

Re: Ping to distant servers does not resolve

#3 2019-09-28 17:05:45

Re: Ping to distant servers does not resolve

#4 2019-09-28 19:49:55

Re: Ping to distant servers does not resolve

#5 2019-09-28 22:43:32

Re: Ping to distant servers does not resolve

#6 2019-09-29 10:16:50

Re: Ping to distant servers does not resolve

#7 2019-09-29 11:36:06

Re: Ping to distant servers does not resolve

#8 2019-09-29 16:18:03

Re: Ping to distant servers does not resolve

#9 2019-09-30 08:41:54

Re: Ping to distant servers does not resolve

#10 2019-09-30 18:46:57

Re: Ping to distant servers does not resolve

#11 2019-10-01 11:48:22

Re: Ping to distant servers does not resolve

#12 2019-10-01 18:37:47

Re: Ping to distant servers does not resolve

#13 2019-10-06 12:10:35

Re: Ping to distant servers does not resolve

Board footer