[SOLVED] Can't ping static IP address

Trilby · 2017-12-13 18:15:28

In the context in which I was originally looking for it, the following would be useful:

mtr -rc1 archlinux.org

As that address could be pinged bu allegedly got a reply from "google.com".

More recent information in the thread, however, has all but removed the utility of the information you'd get from mtr. I'm pretty sure there'd just be one or two steps ending in the device at 192.168.66.1. If that is not the case, then please do share the mtr output.

EDIT: note, the above mtr command may take several (maybe 10s of) seconds to complete.

Last edited by Trilby (2017-12-13 18:18:25)

peanutbutter144 · 2017-12-13 20:01:08

seth wrote:

Examine the IP of the windows PC (run "ipconfig" in cmd.exe and post the output here) so we can see the working network setup.

Windows IP Configuration


Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::e51d:4a8f:d2c0:1076%6
   IPv4 Address. . . . . . . . . . . : 192.168.56.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::3d1e:d09d:ef20:1ff7%7
   IPv4 Address. . . . . . . . . . . : 192.168.0.9
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

Wireless LAN adapter Wi-Fi:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 13:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Ethernet 4:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Ethernet 5:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Ethernet 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 4:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:30db:7f7:ae99:b6cf
   Link-local IPv6 Address . . . . . : fe80::30db:7f7:ae99:b6cf%10
   Default Gateway . . . . . . . . . : ::

Tunnel adapter isatap.{1E7DA0FD-8BFB-4C4A-9D7F-FE88D7279CA1}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{19A1EB9E-B81B-4C8D-AE1B-FF3D95233194}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

seth · 2017-12-13 20:25:31

Ethernet adapter VirtualBox Host-Only Network:
IPv4 Address. . . . . . . . . . . : 192.168.56.1
Ethernet adapter Ethernet:
IPv4 Address. . . . . . . . . . . : 192.168.0.9
Default Gateway . . . . . . . . . : 192.168.0.1

So your route on the archlinuxbox is clearly nuts - if that info is received via dhcp, there's another dhcp server.
Stop dhcpcd and run "sudo dhcpcd -d", check the output on which server responds and figure what that is if it's not 192.168.0.1

You can also configure a static setup: https://wiki.archlinux.org/index.php/Ne … IP_address

Edit: demark virtualbox, there's no indication you're running one on arch or arch in one.

Last edited by seth (2017-12-13 20:26:21)

Slithery · 2017-12-13 20:29:45

Is this either a VM guest or a VM host ???

peanutbutter144 · 2017-12-14 08:10:18

slithery wrote:

Is this either a VM guest or a VM host ???

VM host. I have VirtualBox installed on my Windows partition.

seth · 2017-12-14 08:18:45

The posted journal does not refer to loaded vbox modules; since the reference to your Windows partition makes little sense itr please clarify: does your archlinux installation run inside a virtual machine or do you run a virtual machine on the archlinux installation or neither?

peanutbutter144 · 2017-12-14 16:35:57

seth wrote:

The posted journal does not refer to loaded vbox modules; since the reference to your Windows partition makes little sense itr please clarify: does your archlinux installation run inside a virtual machine or do you run a virtual machine on the archlinux installation or neither?

Neither.

peanutbutter144 · 2017-12-14 18:51:00

seth wrote:

Ethernet adapter VirtualBox Host-Only Network:
IPv4 Address. . . . . . . . . . . : 192.168.56.1
Ethernet adapter Ethernet:
IPv4 Address. . . . . . . . . . . : 192.168.0.9
Default Gateway . . . . . . . . . : 192.168.0.1
So your route on the archlinuxbox is clearly nuts - if that info is received via dhcp, there's another dhcp server.
Stop dhcpcd and run "sudo dhcpcd -d", check the output on which server responds and figure what that is if it's not 192.168.0.1
You can also configure a static setup: https://wiki.archlinux.org/index.php/Ne … IP_address
Edit: demark virtualbox, there's no indication you're running one on arch or arch in one.

dhcpcd-6.11.5 starting
dev: loaded udev
wlp5s0: disabling kernel IPv6 RA support
enp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
enp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
wlp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
wlp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
DUID 00:01:00:01:21:bb:a7:f3:a4:db:30:87:3e:e1
enp2s0: IAID b5:88:5c:46
enp2s0: delaying IPv6 router solicitation for 0.6 seconds
enp2s0: delaying IPv4 for 0.3 seconds
wlp5s0: waiting for carrier
wlp5s0: carrier acquired
wlp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
wlp5s0: IAID 30:87:3e:e1
wlp5s0: adding address fe80::4c6a:f9dc:736a:43e7
wlp5s0: pltime infinity, vltime infinity
wlp5s0: delaying IPv6 router solicitation for 1.0 seconds
wlp5s0: delaying IPv4 for 0.2 seconds
wlp5s0: carrier lost
wlp5s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
wlp5s0: deleting address fe80::4c6a:f9dc:736a:43e7
enp2s0: reading lease `/var/lib/dhcpcd/dhcpcd-enp2s0.lease'
enp2s0: rebinding lease of 192.168.66.107
enp2s0: sending REQUEST (xid 0x26eb4325), next in 3.4 seconds
enp2s0: reject NAK via 192.168.0.1
enp2s0: acknowledged 192.168.66.107 from 192.168.66.1
enp2s0: leased 192.168.66.107 for 315360000 seconds
enp2s0: renew in 157680000 seconds, rebind in 275940000 seconds
enp2s0: writing lease `/var/lib/dhcpcd/dhcpcd-enp2s0.lease'
enp2s0: IP address 192.168.66.107/24 already exists
enp2s0: changing route to 192.168.66.0/24
enp2s0: changing default route via 192.168.66.1
enp2s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' BOUND
forking to background
forked to background, child pid 538

progandy · 2017-12-14 18:59:35

You have a rogue DHCP server and the wrong IP is cached in your dhcp configuration. Where are you using 192.168.66.1? If it is a virtual network for some VMs, make sure that the dhcp server is inaccessible from your normal network.

A quick fix would probably be to release your IP (dhcpcd -k) and the restart dhcp. Now you have a 50% chance that you'll get the right dhcp server to answer first. Repeat this until you get the right IP. You should still remove the second server from the network or you never know when the problem will resurface.

Last edited by progandy (2017-12-14 19:21:11)

peanutbutter144 · 2017-12-16 09:47:33

progandy wrote:

You have a rogue DHCP server and the wrong IP is cached in your dhcp configuration. Where are you using 192.168.66.1? If it is a virtual network for some VMs, make sure that the dhcp server is inaccessible from your normal network.
A quick fix would probably be to release your IP (dhcpcd -k) and the restart dhcp. Now you have a 50% chance that you'll get the right dhcp server to answer first. Repeat this until you get the right IP. You should still remove the second server from the network or you never know when the problem will resurface.

dhdpcd -k fixed it. Thanks!

seth · 2017-12-16 13:51:11

You still have a rogue dhcp server around. Until you get rid of that, this problem will re-emerge time and again.

Arch Linux

#26 2017-12-13 18:15:28

Re: [SOLVED] Can't ping static IP address

#27 2017-12-13 20:01:08

Re: [SOLVED] Can't ping static IP address

#28 2017-12-13 20:25:31

Re: [SOLVED] Can't ping static IP address

#29 2017-12-13 20:29:45

Re: [SOLVED] Can't ping static IP address

#30 2017-12-14 08:10:18

Re: [SOLVED] Can't ping static IP address

#31 2017-12-14 08:18:45

Re: [SOLVED] Can't ping static IP address

#32 2017-12-14 16:35:57

Re: [SOLVED] Can't ping static IP address

#33 2017-12-14 18:51:00

Re: [SOLVED] Can't ping static IP address

#34 2017-12-14 18:59:35

Re: [SOLVED] Can't ping static IP address

#35 2017-12-16 09:47:33

Re: [SOLVED] Can't ping static IP address

#36 2017-12-16 13:51:11

Re: [SOLVED] Can't ping static IP address

Board footer