LinuxQuestions.org - [SOLVED] Can't ping from root, yet network still available

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Can't ping from root, yet network still available (https://www.linuxquestions.org/questions/slackware-14/cant-ping-from-root-yet-network-still-available-4175683657/)

Can't ping from root, yet network still available

I'm having a problem here. As I said in the title, root can't ping google, yet seamonkey has no trouble connecting to google whatever. I have some output I can show you.:

Code:

root@caitlyn:~/RetroArch# ping www.google.com

PING www.google.com (216.58.193.132) 56(84) bytes of data.

^C

--- www.google.com ping statistics ---

13 packets transmitted, 0 received, 100% packet loss, time 11999ms



root@caitlyn:~/RetroArch#

What is going on here? I can obviously use the network, assuming that this posts without a problem, but I can't seem to ping anyone out there. I recently got a new modem, which seems to provide more reliable connections, but meanwhile I can't update my systems because I can't ping anybody. Please help!

Quote:

Originally Posted by maschelsea (Post 6175433)

I'm having a problem here. As I said in the title, root can't ping google, yet seamonkey has no trouble connecting to google whatever. I have some output I can show you.:

Code:

root@caitlyn:~/RetroArch# ping www.google.com

PING www.google.com (216.58.193.132) 56(84) bytes of data.

^C

--- www.google.com ping statistics ---

13 packets transmitted, 0 received, 100% packet loss, time 11999ms



root@caitlyn:~/RetroArch#

Have you other machines on your local network? Can you ping those?
My immediate thought is that icmp echo is being filtered.
Check with your ISP, perhaps?

Thanks
--
KarlMag

I can successfully ping a device within my network, but I still can't ping google, or rsync.gentoo.org, or www.slackware.com.

Code:

root@caitlyn:~# ping 192.168.0.16

PING 192.168.0.16 (192.168.0.16) 56(84) bytes of data.

64 bytes from 192.168.0.16: icmp_seq=1 ttl=64 time=0.260 ms

64 bytes from 192.168.0.16: icmp_seq=2 ttl=64 time=0.171 ms

64 bytes from 192.168.0.16: icmp_seq=3 ttl=64 time=0.176 ms

^C

--- 192.168.0.16 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 1999ms

rtt min/avg/max/mdev = 0.171/0.202/0.260/0.042 ms

root@caitlyn:~#

Have you tried pinging an external IP? That could help determine if it's a DNS issue with root vs something else.

You could try Google or Cloudflare's DNS servers, 8.8.8.8 or 1.1.1.1 respectively.

ifconfig

cat /etc/resolv.conf

Code:

root@caitlyn:~# ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

^C

--- 8.8.8.8 ping statistics ---

13 packets transmitted, 0 received, 100% packet loss, time 11999ms



root@caitlyn:~# ping 1.1.1.1

PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.

^C

--- 1.1.1.1 ping statistics ---

10 packets transmitted, 0 received, 100% packet loss, time 8999ms



root@caitlyn:~#

Code:

root@caitlyn:~# ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.0.10  netmask 255.255.255.0  broadcast 192.168.0.255

        inet6 fe80::9e5c:8eff:fe87:d39e  prefixlen 64  scopeid 0x20<link>

        ether 9c:5c:8e:87:d3:9e  txqueuelen 1000  (Ethernet)

        RX packets 284495  bytes 382320918 (364.6 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 131867  bytes 12810939 (12.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 1  (Local Loopback)

        RX packets 831  bytes 2165423 (2.0 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 831  bytes 2165423 (2.0 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



root@caitlyn:~# cat /etc/resolv.conf

# Generated by dhcpcd from eth0.dhcp

# /etc/resolv.conf.head can replace this line

domain hitronhub.home

nameserver 192.168.0.1

# /etc/resolv.conf.tail can replace this line

root@caitlyn:~#

I don't know what that hitronhub.home thing is about. I didn't add that.

A quick web search indicates that domain hitronhub.home is from hitronhub routers. The resolv.conf file indicates using dhcpcd and the file is being updated dynamically from the router based on the DHCP exchange.

To be useful the nameserver 192.168.0.1 entry means there needs to be a DNS name server at that address. Likely this IP address is the router.

A simple test is connecting the computer directly to the ISP and bypassing the router. Then ping test.

How do I do that? How do I connect directly to the ISP without going through the router? The router is the cable modem. The ISP supplied it.

Code:

root@caitlyn:~# ping 192.168.0.1

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.07 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.829 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.02 ms

^C

--- 192.168.0.1 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 2001ms

rtt min/avg/max/mdev = 0.829/0.977/1.077/0.106 ms

root@caitlyn:~#

Quote:

How do I connect directly to the ISP without going through the router?

With an Ethernet cable.

Quote:

ping 192.168.0.1

Try dig +trace www.google.com and traceroute www.google.com. The commands should provide some clues.

Code:

root@caitlyn:~# dig +trace www.google.com



; <<>> DiG 9.11.22 <<>> +trace www.google.com

;; global options: +cmd

;; connection timed out; no servers could be reached

root@caitlyn:~# traceroute www.google.com

traceroute to www.google.com (216.58.193.132), 30 hops max, 60 byte packets

 1  hitronhub.home (192.168.0.1)  1.484 ms  1.663 ms  1.852 ms

 2  * * *

 3  * * *

 4  * * *

 5  * * *

 6  * * *

 7  * * *

 8  * * *

 9  * * *

10  * * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  * * *

26  * * *

27  * * *

28  * * *

29  * * *

30  * * *

root@caitlyn:~#

Quote:

Originally Posted by upnort (Post 6175464)

With an Ethernet cable.

What's the ethernet cable connecting to. On one end we have my PC. I have no idea what the other end would connect to.

Can you show the dig and traceroute commands with a regular user?

Code:

michael@caitlyn 13 $ dig +trace www.google.com



; <<>> DiG 9.11.22 <<>> +trace www.google.com

;; global options: +cmd

.                        275924        IN        NS        i.root-servers.net.

.                        275924        IN        NS        f.root-servers.net.

.                        275924        IN        NS        l.root-servers.net.

.                        275924        IN        NS        g.root-servers.net.

.                        275924        IN        NS        e.root-servers.net.

.                        275924        IN        NS        j.root-servers.net.

.                        275924        IN        NS        c.root-servers.net.

.                        275924        IN        NS        d.root-servers.net.

.                        275924        IN        NS        k.root-servers.net.

.                        275924        IN        NS        a.root-servers.net.

.                        275924        IN        NS        b.root-servers.net.

.                        275924        IN        NS        m.root-servers.net.

.                        275924        IN        NS        h.root-servers.net.

;; Received 239 bytes from 192.168.0.1#53(192.168.0.1) in 307 ms



com.                        172800        IN        NS        a.gtld-servers.net.

com.                        172800        IN        NS        b.gtld-servers.net.

com.                        172800        IN        NS        c.gtld-servers.net.

com.                        172800        IN        NS        d.gtld-servers.net.

com.                        172800        IN        NS        e.gtld-servers.net.

com.                        172800        IN        NS        f.gtld-servers.net.

com.                        172800        IN        NS        g.gtld-servers.net.

com.                        172800        IN        NS        h.gtld-servers.net.

com.                        172800        IN        NS        i.gtld-servers.net.

com.                        172800        IN        NS        j.gtld-servers.net.

com.                        172800        IN        NS        k.gtld-servers.net.

com.                        172800        IN        NS        l.gtld-servers.net.

com.                        172800        IN        NS        m.gtld-servers.net.

com.                        86400        IN        DS        30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766

com.                        86400        IN        RRSIG        DS 8 1 86400 20201027170000 20201014160000 26116 . ucnLvgkEKkjf0gTDVViQ4Tl1Lz7k9F60w4nrxfJlm9aHLqd+MrVaJ/AI 6reCXPhmQBvb7wq+tEIlewMCGnEFle9tfmymATTa5V2O4oyAW6BvjCvR M0nHoRaW5wFQJOnNCBA/3z2MJ+WkkDFAVendmI5QeHHSLsqsmv/IFP03 8vNPb68eerQuMpN1TZek1ipfh3d8p9doX4jbJbjSDt0LBhDnxXdhSTAe NG25lFcSoGaqa+ZN2Z0SqCP820DXAmXSzDJ2filWDRVwKexpdh8tOuNl /hQxiXR+2No138Fw/Ej1QpkUeCJ1op5yJw8CKIvreB5kl4oz0Bx3vz5U C5dvng==

couldn't get address for 'm.gtld-servers.net': failure

;; Received 1174 bytes from 199.7.91.13#53(d.root-servers.net) in 45 ms



google.com.                172800        IN        NS        ns2.google.com.

google.com.                172800        IN        NS        ns1.google.com.

google.com.                172800        IN        NS        ns3.google.com.

google.com.                172800        IN        NS        ns4.google.com.

CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A NS SOA RRSIG DNSKEY NSEC3PARAM

CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20201020044147 20201013033147 24966 com. glqlnylc6am2Iyk0X/Nfj944Do6IXXMDqT+9FYp+Vua0j3pz0gVfZECx LkyQtVxRDbq8fobKrEeam4uYc9hEKHooF49vAzOGsORtjCCnGoZf0hI3 IuDZ5r1ivkCi3nd1H1iK260O1lrcMlgZU61ActCW5ioguyT/uEa+sigh 3C0GotKDajpnJ1TnObvnwrqsw2FOZBiN4PrB5TOmZD4hlA==

S84BDVKNH5AGDSI7F5J0O3NPRHU0G7JQ.com. 86400 IN NSEC3 1 1 0 - S84CDVS9VPREADFD6KK7PDADH0M6IO8H NS DS RRSIG

S84BDVKNH5AGDSI7F5J0O3NPRHU0G7JQ.com. 86400 IN RRSIG NSEC3 8 2 86400 20201021043553 20201014032553 24966 com. WaeQDfsAlFgwy9gMGND5F2by8WnvGO0q3kLo66gLpWSXw3pPNMdDW8sb /jTJ7imrnsaeHDuFZKMIWJifd255s2NAR8zrpBgbXsED1fOuRYC8Osgx ru3nqFRoHKMepg7nQqEFr8WtOKcwBrAbqMFIExzXKkPwV9MwTSlgxXcB CXOHdU9snr51HhRWSzq5/nyM1tAkKRn5oCeNiP9rtTJ7aQ==

;; Received 840 bytes from 192.52.178.30#53(k.gtld-servers.net) in 51 ms



www.google.com.                300        IN        A        172.217.9.132

;; Received 59 bytes from 216.239.34.10#53(ns2.google.com) in 37 ms



michael@caitlyn 13 $ traceroute www.google.com

traceroute to www.google.com (216.58.193.132), 30 hops max, 60 byte packets

 1  hitronhub.home (192.168.0.1)  1.502 ms  1.691 ms  1.825 ms

 2  * * *

 3  * * *

 4  * * *

 5  * * *

 6  * * *

 7  * * *

 8  * * *

 9  * * *

10  * * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  * * *

26  * * *

27  * * *

28  * * *

29  * * *

30  * * *

michael@caitlyn 13 $

Quote:

What's the ethernet cable connecting to. On one end we have my PC. I have no idea what the other end would connect to.

The PC connects directly to the ISP modem. Unplug the Ethernet cable between the modem and router and connect the modem to the PC.

Quote:

traceroute www.google.com

The traceroute is not getting past the router. At the least reboot the sucker.