[Solved] Ipv4 not working while ipv6 works fine

Just1number · 2013-12-29 13:17:05

I was setting up an arch linux maschine and encountered the following problem:

$ ping6 -c2 google.com
PING google.com(2800:3f0:4004:801::1001) 56 data bytes
64 bytes from 2800:3f0:4004:801::1001: icmp_seq=1 ttl=45 time=237 ms
64 bytes from 2800:3f0:4004:801::1001: icmp_seq=2 ttl=45 time=242 ms

--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 237.331/239.835/242.339/2.504 ms

$ ping google.com
connect: Network is unreachable

same happens with local ips.
I was able to install the base system, because the pacman mirrors seem to work with ipv6,
but its not possible to install some stuff from the AUR without ipv4.

Here is some more information:

ip a says I have the right ipv4 (198.168.178.80):

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 90:2b:34:96:1e:4f brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.80/16 brd 169.254.255.255 scope global enp3s0
       valid_lft forever preferred_lft forever
    inet6 2a02:908:e270:453:922b:34ff:fe96:1e4f/64 scope global dynamic 
       valid_lft 7142sec preferred_lft 3542sec
    inet6 fe80::922b:34ff:fe96:1e4f/64 scope link 
       valid_lft forever preferred_lft forever

my dhcpcd seems fine:

$  systemctl status dhcpcd
dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled)
   Active: active (running) since So 2013-12-29 13:46:14 CET; 21min ago
  Process: 251 ExecStart=/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
 Main PID: 262 (dhcpcd)
   CGroup: /system.slice/dhcpcd.service
           └─262 /bin/dhcpcd -q -b

Dez 29 13:46:21 eins dhcpcd[262]: enp3s0: using IPv4LL address 169.254.17.44
Dez 29 13:46:21 eins dhcpcd[262]: enp3s0: adding host route to 169.254.17.44 via 127.0.0.1
Dez 29 13:46:21 eins dhcpcd[262]: enp3s0: adding route to 169.254.0.0/16
Dez 29 13:46:26 eins dhcpcd[262]: enp3s0: soliciting a DHCP lease
Dez 29 13:46:26 eins dhcpcd[262]: enp3s0: offered 192.168.178.80 from 192.168.178.1
Dez 29 13:47:15 eins dhcpcd[262]: control command: /usr/bin/dhcpcd -q -w enp3s0
Dez 29 13:47:15 eins dhcpcd[262]: enp3s0: adding host route to 192.168.178.80 via 127.0.0.1
Dez 29 13:47:15 eins dhcpcd[262]: enp3s0: adding route to 192.168.0.0/16
Dez 29 13:47:15 eins dhcpcd[262]: enp3s0: deleting host route to 169.254.17.44 via 127.0.0.1
Dez 29 13:47:15 eins dhcpcd[262]: enp3s0: deleting route to 169.254.0.0/16

dhcpcd@enp3s0 has the following problem:

$ systemctl status dhcpcd@enp3s0
dhcpcd@enp3s0.service - dhcpcd on enp3s0
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled)
   Active: failed (Result: resources) since So 2013-12-29 14:11:27 CET; 12s ago
  Process: 638 ExecStart=/usr/bin/dhcpcd -q -w %I (code=exited, status=0/SUCCESS)

Dez 29 14:11:27 eins systemd[1]: PID file /run/dhcpcd-enp3s0.pid not readable (yet?) after start.
Dez 29 14:11:27 eins systemd[1]: Failed to start dhcpcd on enp3s0.
Dez 29 14:11:27 eins systemd[1]: Unit dhcpcd@enp3s0.service entered failed state.

If I forgot something please ask me.
Thanks for any help in advance!

EDIT:
here is my /etc/resolv.conf :

$ cat /etc/resolv.conf 
# Generated by resolvconf
nameserver fd00::2665:11ff:fe18:7dd0

Last edited by Just1number (2014-01-02 02:02:55)

Just1number · 2013-12-30 00:10:21

Well I did nothing but shutdown the system and start it up again a few hours later and now everything is working. I still dont know the problem.

ewaller · 2013-12-30 01:13:25

My guess would be that you had updated the kernel, but had not rebooted. The kernel needed dome module that was no longer available as the modules had been replaced by those for the new kernel whilst you were still running the old kernel. Just a guess.

Just1number · 2014-01-02 02:17:22

The problem occoured just after installing arch.
There was actually no problem using the live medium.
I had this problem with two different machines in the same network and it solved itself after a while in both cases,
so I'm just going to assume, that there is a problem with the router not linking arch.

Arch Linux

#1 2013-12-29 13:17:05

[Solved] Ipv4 not working while ipv6 works fine

#2 2013-12-30 00:10:21

Re: [Solved] Ipv4 not working while ipv6 works fine

#3 2013-12-30 01:13:25

Re: [Solved] Ipv4 not working while ipv6 works fine

#4 2014-01-02 02:17:22

Re: [Solved] Ipv4 not working while ipv6 works fine

Board footer