[SOLVED] Can ping google.com but not github.com

sw372 · 2021-06-19 17:50:16

Hi all,

Trying to set up arch on my old netbook, using systemd-networkd, systemd-resolved, and iwd.
Seemed like everything was fine but as soon as I needed to install something from the AUR, it didn't work. Realized that I had only tried to ping sites like ArchLinux.org, google.com, youtube.com.
I can't ping github.com or some other sites like idk askubuntu.com.
I've done some searching but can't find a solution. It was suggested that something similar I found could be an ipv4 issue and someone suggested "ping -4 youtube.com" to test. I've done that and it works fine.
I've also seen it could be some kind of DNS issue. I don't know how to test that and wouldn't know how to resolve it if that was the case.

Appreciate any assistance.

Last edited by sw372 (2021-06-20 05:59:36)

ewaller · 2021-06-19 17:53:43

Do you have an IPv4 address? What is the output of ip addr ?

sw372 · 2021-06-19 18:02:44

I believe that I do. I've got one called inet and one called inet6, the one called inet is in ipv4 format I believe. I'm very inexperienced at this stuff though.

1: lo <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisk noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00: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
3: wlan0: <BROADCASE,MULTICAST,UP,LOWER_UP> mtu 1500 qdisk noqueue state UP group default qlen 1000
link/ether b8:86:87:96:1f:db brd ff:ff:ff:ff:ff:ff
inet 192.168.1.12/24 brd 192.168.1.255 scope global dynamic wlan0
valid_lft 86391sec preferred_lft 86391 sec
inet6 fe80::ba86:87ff:fe96:1fdb/64 scope link
valid_lft forever preferred_lft forever

ewaller · 2021-06-19 18:20:00

You do. I know Google and Arch support IPv6. If you only had an IPv6 address, they would still work.

Not the problem though.
What is the output of dig github.com ?

marquesine · 2021-06-19 18:22:43

This happens to me also, with google and some others it works, with another ones it doesn't.

I found out that this is probably a DNS error. I don't exactly know what causes that, but for me the following solved the problem:

(sudo) systemctl restart NetworkManager

Last edited by marquesine (2021-06-19 18:23:07)

tucuxi · 2021-06-19 18:24:13

tracepath github.com

sw372 · 2021-06-19 18:24:20

; <<>> DiG 9.16.18 <<>> github.com
;; global options: +cmd
;; connection timed out; no servers could be reached

So I take it to mean this is a DNS issue?

sw372 · 2021-06-19 18:29:53

tracepath also times out.

I didn't have the networkmanager package installed, tried to do that but I think it basically does the same thing as systemd-resolved? After starting it even google wouldn't ping, so I turned it off and started systemd-resolved again and now I'm back to the same state as before.

tucuxi · 2021-06-19 18:31:49

tracepath 140.82.121.3

sw372 · 2021-06-19 18:35:53

oh okay I just needed to wait for tracepath

1?: [LOCALHOST] pmtu 1500
1: _gateway
1: _gateway
2: 10.85.160.1
3: 100.127.74.88
4: 100.120.100.12
5: langbpr j01-ae1-ae1.rd.la.cox.net
6: no reply
7: ae20.cs2.lax112.us.zip.zayo.com
8: ae12.cs2.dfw2.us.zip.zayo.com
9: ae17.cs1.atl10.us.eth.zayo.com
10: ae21.cs4.iad93.us.zip.zayo.com
11: ae2.ter1.iad10.us.zip.zayo.com
12-30: no reply
too many hops: pmtu 1500
resume: pmtu 1500

sw372 · 2021-06-19 18:38:17

okay the first tracepath output was to github.com.

This one is to 140.82.121.3, and it would take a while to type out but basically the same thing.

Hop 18 is ae1.mcs1.fra6.de.eth.zayo.com
hops 19-30 are no reply and it ends by saying too many hops again.

This time it ran much faster though and I saw output immediately as the hops happened.

progandy · 2021-06-19 18:40:37

Let's see if it is a dns configuration issue. For systemd-resolved you'll have to configure /etc/resolv.conf as a symlink: https://wiki.archlinux.org/title/System … figuration

$ getent hosts github.com
$ dig github.com
$ resolvectl status
$ resolvectl query github.com
$ ls -l /etc/resolv.conf
$ cat /etc/resolv.conf

by the way, please use code tags

[code]$ the_command
... your output ...
... your output ...
[/code]

Last edited by progandy (2021-06-19 18:41:15)

sw372 · 2021-06-19 18:59:02

$ gitent hosts github.com
140.82.113.3    github.com

$ dig github.com
; <<>> DiG 9.16.18 <<>> github.com
;; global options: +cmd
;; connection timed out; no servers could be reached

$ resolvectl status
Global
Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
Fallback DNS Serverss: 1.1.1.1 9.9.9.10 8.8.8.8 2606:4700:4700::1111 2620:fe::10 2001:4860:4860::8888

Link 3 (wlan0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1

$ resolvectl query github.com
github.com: resolve call failed: Connection timed out

$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 65 May 31 00:39 /etc/resolv.conf

$ cat /etc/resolv.conf
# Resolver confirguation file.
# See resolv.conf(5) for details.

So my resolv.conf is empty, the tutorial I was following didn't mention that file.
I'm not sure how configure it as a symlink.
Thanks for all the help everybody.

Slithery · 2021-06-19 19:12:36

sw372 wrote:

So my resolv.conf is empty, the tutorial I was following didn't mention that file.

And that's exactly why we don't support installations done using 3rd party tutorials. If you want any further help please reinstall your system following the Installation Guide on our wiki.

Closing - For deletion.

ewaller · 2021-06-19 20:39:17

I have been contacted by the OP, who made a rational argument that they had followed the official guide. I reviewed the guide and agree, that file is not obviously addressed -- if it is, it could be missed. Apparently a secondary reference, a youtube video, also walked through that same guide and did not yield any differences.

I am going to give the OP the benefit of the doubt, reopen the thread, and move it to "Newbie Corner", with the caveat that, should I be proven incorrect, the thread will again be closed without fanfare by any moderator who makes the determination.

Last edited by ewaller (2021-06-19 20:40:17)

progandy · 2021-06-19 21:15:52

sw372 wrote:

So my resolv.conf is empty, the tutorial I was following didn't mention that file.
I'm not sure how configure it as a symlink.
Thanks for all the help everybody.

In post #12 I have provided a link that explains it.

The one thing that puzzles me is the output of resolvectl query github.com. I have no idea why that failed.

ewaller wrote:

I reviewed the guide and agree, that file is not obviously addressed -- if it is, it could be missed.

/etc/resolv.conf is mentioned when you click through from Installation Guide -> Network Configuration -> systemd-networkd -> systemd-resolved. That might be missed if you have to navigate that deep for each and every step of the installation guide.

Arch Wiki: Systemd-networkd#Required_services_and_setup wrote:

It is optional to also configure systemd-resolved, which is a network name resolution service to local applications, considering the following points:
* It is important to understand how resolv.conf and systemd-resolved interact to properly configure the DNS that will be used, some explanations are provided in systemd-resolved.
...

That links to the systemd-resolved page that describes how to create the symlink, but the language could be misleading (optional ... considering ...)

Last edited by progandy (2021-06-19 21:22:27)

sw372 · 2021-06-19 23:09:14

https://www.youtube.com/watch?v=cM2UDz8BepU&t=1516s

Here is the tutorial I was referencing. It is a 2021 guide that walks through each step of the installation guide on the wiki.

I was reading through the wiki install guide, every step. The tutorial didn't cover wifi setup as he was connected via ethernet, so I did it manually, using the wiki.

ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

Yes, I seem to have missed that line, apologies. I have tried it.

$ ;s -l /etc/resolv.conf
lrwxrwxrwx 1 root root 37 Jun 19 20:28 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf

for "cat /etc/resolv.conf", there are comments saying it's a symlink etc, then:

nameserver 127.0.0.53
options edns0 trust-ad
search .

However, I'm still getting the issue unable to ping.

$ resolvectl query github.com
github.com: resolve call failed: Connection timed out

Last edited by sw372 (2021-06-20 05:40:10)

jasonwryan · 2021-06-19 23:20:20

sw372 wrote:

https://www.youtube.com/watch?v=cM2UDz8BepU&t=1516s
Here is the tutorial I was referencing. It is a 2021 guide that walks through each step of the installation guide on the wiki.

No-one is going to sit through that, and all of the ads, just to determine how accuate it is. The default assumption, based on countless yt videos, is that it is shit.

sw372 wrote:

I was reading through the wiki install guide, every step. The tutorial didn't cover wifi setup as he was connected via ethernet, so I did it manually, using the wiki.
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
Yes, I seem to have missed that line, apologies. I have tried it.
$ ;s -l /etc/resolv.conf
lrwxrwxrwx 1 root root 37 Jun 19 20:28 /etc/resolv.conf -> /run/systemd/resolve/stuf-resolve.conf

WTF is stuf-resolve.conf?

sw372 · 2021-06-19 23:59:03

jasonwryan wrote:

sw372 wrote:
https://www.youtube.com/watch?v=cM2UDz8BepU&t=1516s
Here is the tutorial I was referencing. It is a 2021 guide that walks through each step of the installation guide on the wiki.
No-one is going to sit through that, and all of the ads, just to determine how accuate it is. The default assumption, based on countless yt videos, is that it is shit.
sw372 wrote:
I was reading through the wiki install guide, every step. The tutorial didn't cover wifi setup as he was connected via ethernet, so I did it manually, using the wiki.
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
Yes, I seem to have missed that line, apologies. I have tried it.
$ ;s -l /etc/resolv.conf
lrwxrwxrwx 1 root root 37 Jun 19 20:28 /etc/resolv.conf -> /run/systemd/resolve/stuf-resolve.conf
WTF is stuf-resolve.conf?

I'm not expecting anybody to watch it, as I said it didn't even cover wifi setup. I'm just posting the link because the thread was only reopened because I said I used the wiki alongside a tutorial that stepped through the wiki.

and oops, it's stub-resolv.conf, not stuf-resolve.conf, excuse the typo.

sw372 · 2021-06-20 05:36:09

It was suggested on reddit that I attempt to change my wlan0 MTU. It was at 1500, I changed it to 1400, 1492, and 1000, using "ip link set wlan0 mtu xxxx". This did not help.

I also considered just nuking the installation altogether, so I booted from my installation USB into the live environment. Following the wiki, I got to the "Connect to the internet" section, unblocked with rfkill, and connected to wlan0 via iwctl. I then verified my connection with "ping archlinux.org", and it worked as it had originally. At this point I attempted "ping github.com", again from the live USB environment. It did not work.

tucuxi · 2021-06-20 05:55:29

It's hard to decide if there is more nonsense on Youtube or Reddit.

Why are you so keen on pinging various sites? Is that your main problem or what is the real problem you trying to solve?

To get to the root cause, please describe the steps how your set up your network.

sw372 · 2021-06-20 05:58:10

I think I fixed it!

I edited /etc/systemd/resolved.conf, to set my DNS to 8.8.8.8.

After restarting systemd-resolved, it was able to ping github! Firefox can also navigate to github, reddit, etc.

Thank you to everybody who helped out and responded. Hopefully someday I'll know enough to pass some Arch/Linux knowledge forward.

Arch Linux

#1 2021-06-19 17:50:16

[SOLVED] Can ping google.com but not github.com

#2 2021-06-19 17:53:43

Re: [SOLVED] Can ping google.com but not github.com

#3 2021-06-19 18:02:44

Re: [SOLVED] Can ping google.com but not github.com

#4 2021-06-19 18:20:00

Re: [SOLVED] Can ping google.com but not github.com

#5 2021-06-19 18:22:43

Re: [SOLVED] Can ping google.com but not github.com

#6 2021-06-19 18:24:13

Re: [SOLVED] Can ping google.com but not github.com

#7 2021-06-19 18:24:20

Re: [SOLVED] Can ping google.com but not github.com

#8 2021-06-19 18:29:53

Re: [SOLVED] Can ping google.com but not github.com

#9 2021-06-19 18:31:49

Re: [SOLVED] Can ping google.com but not github.com

#10 2021-06-19 18:35:53

Re: [SOLVED] Can ping google.com but not github.com

#11 2021-06-19 18:38:17

Re: [SOLVED] Can ping google.com but not github.com

#12 2021-06-19 18:40:37

Re: [SOLVED] Can ping google.com but not github.com

#13 2021-06-19 18:59:02

Re: [SOLVED] Can ping google.com but not github.com

#14 2021-06-19 19:12:36

Re: [SOLVED] Can ping google.com but not github.com

#15 2021-06-19 20:39:17

Re: [SOLVED] Can ping google.com but not github.com

#16 2021-06-19 21:15:52

Re: [SOLVED] Can ping google.com but not github.com

#17 2021-06-19 23:09:14

Re: [SOLVED] Can ping google.com but not github.com

#18 2021-06-19 23:20:20

Re: [SOLVED] Can ping google.com but not github.com

#19 2021-06-19 23:59:03

Re: [SOLVED] Can ping google.com but not github.com

#20 2021-06-20 05:36:09

Re: [SOLVED] Can ping google.com but not github.com

#21 2021-06-20 05:55:29

Re: [SOLVED] Can ping google.com but not github.com

#22 2021-06-20 05:58:10

Re: [SOLVED] Can ping google.com but not github.com

Board footer