Arch Linux

CannaPLUS

Member

Registered: 2016-02-05

Posts: 6

[Solved] Can ping google.com but not 8.8.8.8

I have been searching for quite some time now as to why this is happening. Fresh install. Since the beginning I wasn't able to ping 8.8.8.8 and I thought I had no internet connection what so ever because of it, however, I attempted www.google.com and it ping'd just fine. I was abled to download the arch base and base devel files as well as any packages - I still can. I go to chromium and find www.google.com, www.facebook.com, www.yahoo.com... but www.archlinux.org cannot be found along with many searched websites.

This was impossible to search for considering the millions of posts and questions on the internet that say "Can ping 8.8.8.8 but not google.com" and not the other way around. I am fairly new to linux, but not a complete newb, so be gentle on me. I wasn't enitrely sure what I needed to post as far as information goes, but I will give you what I could think of:

# lspci -v
...
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
	Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
	Flags: bus master, fast devsel, latency 0, IRQ 38
	Memory at f6300000 (32-bit, non-prefetchable) [size=128K]
	Memory at f6339000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at f040 [size=32]
	Capabilities: [c8] Power Management version 2
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] PCI Advanced Features
	Kernel driver in use: e1000e
	Kernel modules: e1000e
...

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 60:a4:4c:af:54:d0 brd ff:ff:ff:ff:ff:ff
    inet6 2602:306:32dd:6c80:156e:f0e0:8fb6:cc61/64 scope global mngtmpaddr noprefixroute dynamic 
       valid_lft 2591886sec preferred_lft 604686sec
    inet6 fe80::934c:23e5:4710:ac17/64 scope link 
       valid_lft forever preferred_lft forever

I would appreciate any help.

Edit: I alos thought I should show you exactly what happens:

# ping -c 3 www.google.com
PING www.google.com(lax17s15-in-x04.1e100.net (2607:f8b0:4007:80c::2004)) 56 data bytes
64 bytes from lax17s15-in-x04.1e100.net (2607:f8b0:4007:80c::2004): icmp_seq=1 ttl=55 time=71.4 ms
64 bytes from lax17s15-in-x04.1e100.net (2607:f8b0:4007:80c::2004): icmp_seq=2 ttl=55 time=70.9 ms
64 bytes from lax17s15-in-x04.1e100.net (2607:f8b0:4007:80c::2004): icmp_seq=3 ttl=55 time=70.8 ms

--- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms

# ping -c 3 8.8.8.8
connect: Network is unreachable

Last edited by CannaPLUS (2016-12-05 23:12:05)

Conker

Member

Registered: 2010-06-22

Posts: 4

Re: [Solved] Can ping google.com but not 8.8.8.8

Your eno1 interface has only an IPv6 address assigned and no IPv4, which is why you won't be able to ping / communicate with 8.8.8.8 or any other v4. How's networking configured? Doing dhcp on boot?

paulkerry

Member

From: Sheffield, UK

Registered: 2014-10-02

Posts: 611

Re: [Solved] Can ping google.com but not 8.8.8.8

How have you setup your networking? Are you using a static or dhcp assigned ip? If dhcp, which client? Have you enabled more than one client by mistake?

Have you taken a look at https://wiki.archlinux.org/index.php/Ne … figuration especially section 5?

CannaPLUS

Member

Registered: 2016-02-05

Posts: 6

Re: [Solved] Can ping google.com but not 8.8.8.8

How have you setup your networking? Are you using a static or dhcp assigned ip? If dhcp, which client? Have you enabled more than one client by mistake?

Have you taken a look at https://wiki.archlinux.org/index.php/Ne … figuration especially section 5?

To the best of my knowledge I haven't messed with any other client.
I have checked that out. That is where I first tried to solve my issue. Anytime I go about the wiki style of starting dhcpcd I get:

# dhcpcd eno1
sending commands to master dhcpcd process
#

How's networking configured? Doing dhcp on boot?

I am not entirely sure where to look to figure out how my network is configured. However, I did confirm dhcp is running on boot:

# systemctl status dhcpcd 
* dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2016-12-01 18:10:51 CST; 19h ago
  Process: 711 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
 Main PID: 717 (dhcpcd)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/dhcpcd.service
           `-717 /usr/bin/dhcpcd -q -b

Dec 02 13:36:03 haley dhcpcd[717]: eno1: offered 192.168.1.83 from 192.168.1.254
Dec 02 13:36:03 haley dhcpcd[717]: eno1: NAK: from 192.168.1.254
Dec 02 13:36:53 haley dhcpcd[717]: control command: dhcpcd eno1
Dec 02 13:37:03 haley dhcpcd[717]: eno1: soliciting a DHCP lease
Dec 02 13:37:03 haley dhcpcd[717]: eno1: offered 192.168.1.79 from 192.168.1.254
Dec 02 13:37:03 haley dhcpcd[717]: eno1: NAK: from 192.168.1.254
Dec 02 13:37:31 haley dhcpcd[717]: control command: dhcpcd eno1
Dec 02 13:38:03 haley dhcpcd[717]: eno1: soliciting a DHCP lease
Dec 02 13:38:03 haley dhcpcd[717]: eno1: offered 192.168.1.83 from 192.168.1.254
Dec 02 13:38:03 haley dhcpcd[717]: eno1: NAK: from 192.168.1.254

Last edited by CannaPLUS (2016-12-02 19:50:08)

CannaPLUS

Member

Registered: 2016-02-05

Posts: 6

Re: [Solved] Can ping google.com but not 8.8.8.8

Is this what you need?

# nano /etc/dhcpcd.conf

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
noipv4ll

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,208

Re: [Solved] Can ping google.com but not 8.8.8.8

What happens with ping -6 google.com   versus  ping -4 google.com   ?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

CannaPLUS

Member

Registered: 2016-02-05

Posts: 6

Re: [Solved] Can ping google.com but not 8.8.8.8

What happens with ping -6 google.com   versus  ping -4 google.com   ?

$ ping -6 google.com
PING google.com(dfw06s47-in-x0e.1e100.net (2607:f8b0:4000:80b::200e)) 56 data bytes
64 bytes from dfw06s47-in-x0e.1e100.net (2607:f8b0:4000:80b::200e): icmp_seq=1 ttl=55 time=38.0 ms
64 bytes from dfw06s47-in-x0e.1e100.net (2607:f8b0:4000:80b::200e): icmp_seq=2 ttl=55 time=39.2 ms
64 bytes from dfw06s47-in-x0e.1e100.net (2607:f8b0:4000:80b::200e): icmp_seq=3 ttl=55 time=39.3 ms
^X64 bytes from dfw06s47-in-x0e.1e100.net (2607:f8b0:4000:80b::200e): icmp_seq=4 ttl=55 time=38.3 ms
64 bytes from dfw06s47-in-x0e.1e100.net (2607:f8b0:4000:80b::200e): icmp_seq=5 ttl=55 time=37.9 ms
^C
--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 37.999/38.605/39.302/0.600 ms
$ ping  -4 google.com
connect: Network is unreachable
$ 

I was also advised to restart the machine and power cycle the router and modem. This did not result in a solution.

paulkerry

Member

From: Sheffield, UK

Registered: 2014-10-02

Posts: 611

Re: [Solved] Can ping google.com but not 8.8.8.8

To summarise, it looks like ipv6 networking is working for you, but not ipv4. Is it possible to try your setup on an alternative network?

If not. have you tried an alternative client? There are alternatives listed on the network configuration link, plus networkmanager. Remember when switching clients to disable the others.

You could try searching for "ipv4 not working"...

CannaPLUS

Member

Registered: 2016-02-05

Posts: 6

Re: [Solved] Can ping google.com but not 8.8.8.8

So after thinking about it for some time, my friend that advised me to restart my modem was looking in the right direction. I kept looking at the

$ systemctl status dhcpcd

and that is when I realized that the modem was rejecting the IP. So I went into my modem settings and found that it wanted a specific IP: xx.xx.xx.100. So I changed the configuration to "private pool of xx.xx.xx.0" and that seems to have fixed it. Darn AT&T modems... making their own settings. Thanks for the help everything. Marking solved.