[SOLVED] Connected to my home wifi network but can't ping anything

kucukhr · 2020-09-27 12:51:45

Hello,

I am using NetworkManager for connections. Until yesterday I did not have any problems. I don't know what did I change, but I can't reach any server now. I cannot ping neither google.com nor 8.8.8.8. I dug through the internet to find a solution but I could not cover any ground. This is my first post on this forum.

So let me begin by posting some outputs:

ping archlinux.org

ping: archlinux.org: Temporary failure in name resolution

Okay... Maybe a DNS issue? Let's ping google's ip address:

ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
(and now just waits forever - no more output)

Okay - I have no idea how to proceed. I went to through many Q&As and many pages on our wiki... But I could not get one step closer to a solution. Well actually, at some point I installed dhcpcd and started its unit server alongside with NetworkManager's. The result? I was able to reach to internet but the wifi kept dropping after every 2 seconds... Apparently two unit services were racing against one another. I am just telling this 'development' to give you more information. Maybe it will light a bulb in someone's head... The weird thing is dhcpcd.service is enabled right now as well, but the connection is stable yet I cannot reach any network. It is like my Archlinux feels capricious one day but very productive another day....

Anyways, before it gets long, let me share some more output:

ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 54:ee:75:86:55:e1 brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 60:57:18:98:6b:b0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.103/24 brd 192.168.2.255 scope global dynamic noprefixroute wlp4s0
       valid_lft 258876sec preferred_lft 258876sec
    inet 192.168.2.101/24 brd 192.168.2.255 scope global secondary dynamic noprefixroute wlp4s0
       valid_lft 258883sec preferred_lft 226483sec
    inet6 fe80::7b85:5b21:df9:3f8d/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::4be6:7f8:a8d:a78d/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: wwp0s20u4: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether e2:6b:95:8d:da:57 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::abec:51e1:dcdc:a090/64 scope link 
       valid_lft forever preferred_lft forever

In the system units below, you will see systemd-resolved.service and dhcpcd.service - I think it is not supposed to be that way. However just for the record, the situation was just the same before they were enabled/started....

systemctl list-unit-files --state=enabled --no-pager

UNIT FILE                               STATE   VENDOR PRESET
org.cups.cupsd.path                     enabled disabled     
avahi-daemon.service                    enabled disabled     
canberra-system-bootup.service          enabled disabled     
canberra-system-shutdown-reboot.service enabled disabled     
canberra-system-shutdown.service        enabled disabled     
dhcpcd.service                          enabled disabled     
getty@.service                          enabled enabled      
hostapd.service                         enabled disabled     
lightdm.service                         enabled disabled     
NetworkManager-dispatcher.service       enabled disabled     
NetworkManager-wait-online.service      enabled disabled     
NetworkManager.service                  enabled disabled     
org.cups.cupsd.service                  enabled disabled     
systemd-resolved.service                enabled enabled      
systemd-timesyncd.service               enabled enabled      
avahi-daemon.socket                     enabled disabled     
org.cups.cupsd.socket                   enabled disabled     
remote-fs.target                        enabled enabled      

18 unit files listed.

ip route

default via 192.168.2.1 dev wlp4s0 proto dhcp src 192.168.2.101 metric 303 
192.168.2.0/24 dev wlp4s0 proto dhcp scope link src 192.168.2.101 metric 303 
192.168.2.0/24 dev wlp4s0 proto kernel scope link src 192.168.2.103 metric 600

cat /etc/resolv.conf

# Generated by resolvconf
nameserver 192.168.2.1

There is another problem I having since a long time but I have a workaround. I don't know if it will help: Everytime after boot, the wifi interface is simply not loaded. When I run "ip link", I only see "lo" device. After I hit the kill switch of wifi adaptor twice (this is a laptop) to turn it off and on again, the interface wlp4s0 comes back and NetworkManager automatically connects to a wifi point if it knows the password etc....

Let me give you a final information that might help: I am creating a hotspot from my mobile phone's network and connecting to it. Then I can simply browse the web, ping etc... So apparently when the mobile phone handles routing/dns etc, it works. But my archlinux fails to manage such things by itself... (No worries, I was connected to my home network while I was printing above outputs...)

BTW, I am using all these obscure pronouns to describe the situation because my networking knowledge is really terrible. The only reason why I use Archlinux is because I like doing things the harder way - it just feels right because it creates this feeling of control. However I feel really helpless in such sitations where things get broken and I have no clue why...

Thanks for your time.

Last edited by kucukhr (2020-09-27 17:21:19)

Zod · 2020-09-27 13:27:27

After just a quick glance I can't help but notice that you have dhcpcd and networkmanager enabled.

If I were you I would pick one or the other.

kucukhr · 2020-09-27 13:31:10

All due respect, I already told that the situation is exactly the same when I pick either one of them. Here I disabled dhcpcd and rebooted the laptop. The ping results are just the same - no output.

systemctl list-units | grep -iE '(wicd|dhcp|net|conn)'

  sys-devices-pci0000:00-0000:00:14.0-usb2-2\x2d4-2\x2d4:1.0-net-wwp0s20u4.device          loaded active plugged   Sierra_Wireless_EM7345_4G_LTE                                                
  sys-devices-pci0000:00-0000:00:19.0-net-enp0s25.device                                   loaded active plugged   Ethernet Connection (3) I218-V                                               
  sys-devices-pci0000:00-0000:00:1c.1-0000:04:00.0-net-wlp4s0.device                       loaded active plugged   Wireless 7265 (Dual Band Wireless-AC 7265)                                   
  sys-subsystem-net-devices-enp0s25.device                                                 loaded active plugged   Ethernet Connection (3) I218-V                                               
  sys-subsystem-net-devices-wlp4s0.device                                                  loaded active plugged   Wireless 7265 (Dual Band Wireless-AC 7265)                                   
  sys-subsystem-net-devices-wwp0s20u4.device                                               loaded active plugged   Sierra_Wireless_EM7345_4G_LTE                                                
  sys-fs-fuse-connections.mount                                                            loaded active mounted   FUSE Control File System                                                     
  NetworkManager-wait-online.service                                                       loaded active exited    Network Manager Wait Online                                                  
  NetworkManager.service                                                                   loaded active running   Network Manager                                                              
  systemd-resolved.service                                                                 loaded active running   Network Name Resolution                                                      
  systemd-timesyncd.service                                                                loaded active running   Network Time Synchronization                                                 
  network-online.target                                                                    loaded active active    Network is Online                                                            
  network.target                                                                           loaded active active    Network                                                                      
  nss-lookup.target                                                                        loaded active active    Host and Network Name Lookups

Zod · 2020-09-27 13:37:01

All due respect, have you configured networkmanager?

https://wiki.archlinux.org/index.php/NetworkManager

kucukhr · 2020-09-27 13:51:15

For one thing, I have installed fresh Archlinux many times to several laptops and desktops since I met with it in 2016. Never I had to configure NetworkManager other than to start its unit service (NetworkManager.service).

However because of this recent issue I run into, I did have to get my feet wet with NM's configuration. But so far I did not change much. Because I mean, I don't believe there is anything to do with configuration.

Here are some more outputs:

cat /etc/NetworkManager/conf.d/dhcp-client.conf

cat /etc/NetworkManager/conf.d/dns.conf

[main]
dns=none
systemd-resolved=false

cat /etc/NetworkManager/NetworkManager.conf

# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.

cat /etc/hosts

# Static table lookup for hostnames.
# See hosts(5) for details.
127.0.0.1 localhost
::1 localhost
127.0.1.1 MyComputer.localdomain MyComputer

cat /etc/hostname 
MyComputer

My computer's hostname is actually "MyComputer", it is not an edit

seth · 2020-09-27 14:36:37

There is another problem I having since a long time but I have a workaround. I don't know if it will help: Everytime after boot, the wifi interface is simply not loaded. When I run "ip link", I only see "lo" device. After I hit the kill switch of wifi adaptor twice (this is a laptop) to turn it off and on again, the interface wlp4s0 comes back and NetworkManager automatically connects to a wifi point if it knows the password etc....

Please post a complete system journal ("sudo journalctl -b", you can use the tip from the first link in my signature)

kucukhr · 2020-09-27 15:07:48

Thank you for your support.

So I run the journalCTL command and uploaded it to ix.io - Here are the things I did before running the command, so it maybe a little more semantical:

Boot the laptop like I usually do, login, choose the session, arrive at XFCE4 desktop. Notice the network interface is indeed not loaded like usual. Hit wifi adapter kill switch twice. Interface is back, NM connects to available home network automatically. Now I run the journalCTL command. Quickly realize that I don't have a healthy internet connection, so ix.io will never respond. Run the command again, pipe the output into a file, 'cat' the file back to ix.io using mobile phone hotspot...

http://ix.io/2yVD

seth · 2020-09-27 15:18:38

Why are you running hostapd? It seems to kck in too early and toggles the interface *a lot*.
Please take it out of the equation and report on the results.

Zod · 2020-09-27 15:43:09

Should systemd-resolved be enabled?

kucukhr · 2020-09-27 15:52:28

@seth, good eye. One problem solved. Now when the I arrive at my desktop, interfaces are up by default I am connected to available network. Thank you very much.

However the main problem persists. @Zod, I am not sure if "systemd-resolved" should be disabled. Well I did disable it and rebooted. But I get the same result.

kucukhr · 2020-09-27 16:13:19

Yesterday when this problem popped up, I was hopelessly trying to find a solution. When a family member asked time to another, instinctively I looked at the hour as well and realized that my laptop's clock was off. Thinking that might be the issue, I entered BIOS and changed the clock there because somehow I could not do it in Archlinux. Meanwhile out of sheer idiocracy, I resetted the BIOS which ruined by dual boot GRUB configuration with windows.

So I got my live USB and arch-chrooted into the laptop. Since I was there, why not pacstrap base, linux and linux-firmware to the chrooted environment? Fixed the issues by setting up GRUB again. Login to archlinux again.

So after that, I installed DHCPCD and got my internet working in this weird loop of connecting and dropping again. When you solve a problem you get this instant dopamine which makes you forget the details... But if I remember correctly here is what happened next: I disable DHCPCD again. In the configuration of NM, I added dhclient and dnsmask to the respective places. And bam! It was working. I finished the night very tired of this issue and woke up in the morning happy, gullible, thinking confidently that I am going to find my computer exactly how I shutdown it yesterday night.

And it is night again and I am stuck in the same issue... I don't know guys... Here is the output of my timedatectl:

timedatectl 

               Local time: Sun 2020-09-27 19:09:30 +03 
           Universal time: Sun 2020-09-27 16:09:30 UTC 
                 RTC time: Sun 2020-09-27 16:09:30     
                Time zone: Europe/Istanbul (+03, +0300)
System clock synchronized: yes                         
              NTP service: active                      
          RTC in local TZ: no

EDIT: Do you reccommend any other network manager? I am okay with connecting through a terminal or something. All I need is a not so complicated way to set up VPN to access my university's intranet. Which is super easy with NM. But only when it works...

Last edited by kucukhr (2020-09-27 16:19:30)

Zod · 2020-09-27 16:31:19

You have dhcpcd installed,yes?

One thing to try is, while leaving it disabled edit the following file..

/etc/NetworkManager/conf.d/dhcp-client.conf

[main]
dhcp=dhcpcd

And consider rebooting.

nl6720 · 2020-09-27 16:38:47

Don't! NetworkManager can't use dhcpcd as a dhcp client anymore. See FS#66231.

Zod · 2020-09-27 16:41:37

Well poops, yeah don't do that!

Other alternatives include using dhclient instead or maybe extracting the default config files from the networkmanager package and comparing them to what you have.

kucukhr · 2020-09-27 16:42:20

Thanks for your answer. Unfortunately it did not fix. Tried dhclient as well. Made double sure that I reboot. No ping whatsoever. Such a hopeless quest. Is there anyway we can actually debug this? I am genuinenly curious what is happening. I am willing to give ssh access to anyone interested - oh but wait... nvrmind...

EDIT: I just realized that this issue is the same when I boot from archlinux live USB. I connect to my home's wifi using iwctl - connection works just fine. But no ping. Did my wifi card became obsolute overnight? But that can't happen, I boot from my windows on the same machine and windows connects just fine...

EDIT2: Are you people sysadmins? How do you keep a life/archlinux balance? I can barely keep a balance of life/studying and archlinux is just as heavy as a university! I really love it but I am about to tip to the dark side... Why does Archlinux' logo looks like pink floyd's triangle? I will weep like a child if I leave archlinux. But I just can't understand.

Last edited by kucukhr (2020-09-27 16:50:20)

Zod · 2020-09-27 16:50:13

Can you ping 127.0.0.1
?

Edit: and your local ip address?

Last edited by Zod (2020-09-27 16:50:58)

kucukhr · 2020-09-27 16:50:38

Zod wrote:

Can you ping 127.0.0.1
?

Yes.

EDIT: Is 'inet' in this 'ip addr' output my local IP address? If so, then yes I can ping it too.

4: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 60:57:18:98:6b:b0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.253/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp4s0
       valid_lft 2918sec preferred_lft 2918sec
    inet6 fe80::1331:16dd:d29d:90ea/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Last edited by kucukhr (2020-09-27 16:52:51)

Zod · 2020-09-27 16:55:55

do..

$ ip addr

and post the results

kucukhr · 2020-09-27 16:57:45

Output while I am connected to my home wifi which does NOT ping:

[archer@MyComputer ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 54:ee:75:86:55:e1 brd ff:ff:ff:ff:ff:ff
3: wwp0s20u4: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether e2:6b:95:8d:da:57 brd ff:ff:ff:ff:ff:ff
4: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 60:57:18:98:6b:b0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.103/24 brd 192.168.2.255 scope global dynamic noprefixroute wlp4s0
       valid_lft 259199sec preferred_lft 259199sec
    inet6 fe80::4be6:7f8:a8d:a78d/64 scope link tentative noprefixroute 
       valid_lft forever preferred_lft forever

Output while I am connected to my mobile phone's hotspot so I can post this message:

[archer@MyComputer ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 54:ee:75:86:55:e1 brd ff:ff:ff:ff:ff:ff
3: wwp0s20u4: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether e2:6b:95:8d:da:57 brd ff:ff:ff:ff:ff:ff
4: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 60:57:18:98:6b:b0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.253/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp4s0
       valid_lft 3562sec preferred_lft 3562sec
    inet6 fe80::1331:16dd:d29d:90ea/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Last edited by kucukhr (2020-09-27 16:57:58)

Zod · 2020-09-27 16:59:38

Do..

$ ip r

kucukhr · 2020-09-27 17:01:09

While connected to home network:

[archer@MyComputer ~]$ ip r
default via 192.168.2.1 dev wlp4s0 proto dhcp metric 20600 
192.168.2.0/24 dev wlp4s0 proto kernel scope link src 192.168.2.103 metric 600

While connected to mobile hotspot:

[archer@MyComputer ~]$ ip r
default via 192.168.43.1 dev wlp4s0 proto dhcp metric 600 
192.168.43.0/24 dev wlp4s0 proto kernel scope link src 192.168.43.253 metric 600

Zod · 2020-09-27 17:04:55

While connected to the home network ping

192.168.2.1

archlinux.org

and while connected to the hotspot ping

192.168.43.1

archlinux.org

kucukhr · 2020-09-27 17:08:39

Okay that was interesting. Hotspot test worked as expected.

However I could not ping 192.168.2.1 while connected to home network. Ping output

[archer@MyComputer ~]$ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
^C
--- 192.168.2.1 ping statistics ---
43 packets transmitted, 0 received, 100% packet loss, time 42567ms

Zod · 2020-09-27 17:09:32

Maybe reboot your home router?

kucukhr · 2020-09-27 17:12:38

Just a quick question because at this point I fall short on terminology when speaking english/turkish. We have something called 'modem' in our home which is what everybody is connected to. That is the router right? I am now unplugging the power and plugging back in again. Will report back in 10 minutes. In case if it works, I just want to say that all windows computers and android mobile phone connect without a problem so far. Anyways let's do it.

Arch Linux

#1 2020-09-27 12:51:45

[SOLVED] Connected to my home wifi network but can't ping anything

#2 2020-09-27 13:27:27

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#3 2020-09-27 13:31:10

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#4 2020-09-27 13:37:01

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#5 2020-09-27 13:51:15

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#6 2020-09-27 14:36:37

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#7 2020-09-27 15:07:48

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#8 2020-09-27 15:18:38

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#9 2020-09-27 15:43:09

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#10 2020-09-27 15:52:28

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#11 2020-09-27 16:13:19

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#12 2020-09-27 16:31:19

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#13 2020-09-27 16:38:47

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#14 2020-09-27 16:41:37

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#15 2020-09-27 16:42:20

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#16 2020-09-27 16:50:13

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#17 2020-09-27 16:50:38

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#18 2020-09-27 16:55:55

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#19 2020-09-27 16:57:45

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#20 2020-09-27 16:59:38

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#21 2020-09-27 17:01:09

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#22 2020-09-27 17:04:55

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#23 2020-09-27 17:08:39

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#24 2020-09-27 17:09:32

Re: [SOLVED] Connected to my home wifi network but can't ping anything

#25 2020-09-27 17:12:38

Re: [SOLVED] Connected to my home wifi network but can't ping anything

Board footer