You are not logged in.

#1 2021-04-21 08:26:56

Tar3k Hasan
Member
Registered: 2021-03-19
Posts: 22

[SOLVED]Network Issue

Hello,
I'm facing some kind of network issue. My wifi stays connected but it stops working for couple of second. Here is what it's looks like
Input

 ping google.com 

Output

PING google.com (216.58.200.142) 56(84) bytes of data.
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=1 ttl=116 time=61.8 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=2 ttl=116 time=66.8 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=3 ttl=116 time=64.0 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=4 ttl=116 time=63.5 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=5 ttl=116 time=61.8 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=6 ttl=116 time=64.2 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=7 ttl=116 time=64.8 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=8 ttl=116 time=63.5 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=9 ttl=116 time=63.0 ms
From tareks-arch (192.168.133.110) icmp_seq=10 Destination Host Unreachable
From tareks-arch (192.168.133.110) icmp_seq=11 Destination Host Unreachable
From tareks-arch (192.168.133.110) icmp_seq=12 Destination Host Unreachable
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=13 ttl=116 time=2147 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=14 ttl=116 time=1107 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=15 ttl=116 time=66.8 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=16 ttl=116 time=62.9 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=17 ttl=116 time=63.4 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=18 ttl=116 time=63.0 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=19 ttl=116 time=64.0 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=20 ttl=116 time=62.6 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=21 ttl=116 time=62.9 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=22 ttl=116 time=63.1 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=23 ttl=116 time=274 ms
From tareks-arch (192.168.133.110) icmp_seq=24 Destination Host Unreachable
From tareks-arch (192.168.133.110) icmp_seq=25 Destination Host Unreachable
From tareks-arch (192.168.133.110) icmp_seq=26 Destination Host Unreachable
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=27 ttl=116 time=2148 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=28 ttl=116 time=1108 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=29 ttl=116 time=67.6 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=30 ttl=116 time=65.0 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=31 ttl=116 time=63.3 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=32 ttl=116 time=63.0 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=33 ttl=116 time=63.6 ms
From tareks-arch (192.168.133.110) icmp_seq=34 Destination Host Unreachable
From tareks-arch (192.168.133.110) icmp_seq=35 Destination Host Unreachable
From tareks-arch (192.168.133.110) icmp_seq=36 Destination Host Unreachable
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=37 ttl=116 time=2109 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=38 ttl=116 time=1029 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=39 ttl=116 time=63.3 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=40 ttl=116 time=62.2 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=41 ttl=116 time=164 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=42 ttl=116 time=62.6 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=43 ttl=116 time=64.3 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=44 ttl=116 time=63.7 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=45 ttl=116 time=63.7 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=46 ttl=116 time=64.0 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=47 ttl=116 time=63.9 ms
From tareks-arch (192.168.133.110) icmp_seq=48 Destination Host Unreachable
From tareks-arch (192.168.133.110) icmp_seq=49 Destination Host Unreachable
From tareks-arch (192.168.133.110) icmp_seq=50 Destination Host Unreachable
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=51 ttl=116 time=1958 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=52 ttl=116 time=878 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=53 ttl=116 time=60.8 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=54 ttl=116 time=63.7 ms
64 bytes from maa05s10-in-f14.1e100.net (216.58.200.142): icmp_seq=55 ttl=116 time=64.8 ms
^C
--- google.com ping statistics ---
55 packets transmitted, 43 received, +12 errors, 21.8182% packet loss, time 59268ms
rtt min/avg/max/mdev = 60.805/349.381/2147.538/624.578 ms, pipe 4

Did anyone faced this issue? Today I got an update for network manager from networkmanager 1.30.2-1===>1.30.4-1(maybe). After that update I'm facing this problem. So I downgraded to 1.30.2-1 sometims ago but the problem is still here. When I use facebook on my laptop a pop up comes that I'm offline and few seconds later another pop up comes out and it says that network was restored. What should I do?
NOTE: I'm using Arch kde and I'm in 5.10.31-1-lts kernel.

[EDIT]: Downgrading networkmanager seems to fix the issue. But I had to remove my wifi from KDE settings and reconnect again. I haven't tried with the new version of NetworkManager.

Last edited by Tar3k Hasan (2021-04-22 14:10:28)

Offline

#2 2021-04-21 15:16:43

seth
Member
Registered: 2012-09-03
Posts: 21,273

Re: [SOLVED]Network Issue

Let's rule the #1 cause for this, please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Offline

#3 2021-04-22 11:03:11

Tar3k Hasan
Member
Registered: 2021-03-19
Posts: 22

Re: [SOLVED]Network Issue

seth wrote:

Let's rule the #1 cause for this, please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

The Output is

bluetooth.service                        | bluetooth.target.wants
cronie.service                           | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pamac-cleancache.timer                   | timers.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
tlp.service                              | multi-user.target.wants
ufw.service                              | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

Offline

#4 2021-04-22 11:46:46

seth
Member
Registered: 2012-09-03
Posts: 21,273

Re: [SOLVED]Network Issue

Nope, there's only one network managing service (NM)
Please post a complete systme journal covering a boot with such incidents (eg. "sudo journalctl -b -5" for five boots ago)

Offline

#5 2021-04-22 12:59:40

Tar3k Hasan
Member
Registered: 2021-03-19
Posts: 22

Re: [SOLVED]Network Issue

seth wrote:

Nope, there's only one network managing service (NM)
Please post a complete systme journal covering a boot with such incidents (eg. "sudo journalctl -b -5" for five boots ago)

I ran sudo journalctl -b -5 and the output is

-- Journal begins at Thu 2021-04-08 11:51:36 +06, ends at Thu 2021-04-22 18:56:51 +06. --
Apr 20 15:18:40 tareks-arch kernel: microcode: microcode updated early to revision 0xde, date = 2020-05-27
Apr 20 15:18:40 tareks-arch kernel: Linux version 5.10.31-1-lts (linux-lts@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binut>
Apr 20 15:18:40 tareks-arch kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts root=UUID=ab13b5f7-2a24-49c6-85ab-7>
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Apr 20 15:18:40 tareks-arch kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' fo>
Apr 20 15:18:40 tareks-arch kernel: BIOS-provided physical RAM map:
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007a5a3fff] usable
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000007a5a4000-0x000000007a5a4fff] ACPI NVS
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000007a5a5000-0x000000007a5a5fff] reserved
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000007a5a6000-0x000000008a552fff] usable
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000008a553000-0x000000008a8cefff] reserved
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000008a8cf000-0x000000008a912fff] ACPI data
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000008a913000-0x000000008ae8afff] ACPI NVS
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000008ae8b000-0x000000008b52ffff] reserved
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000008b530000-0x000000008b5fdfff] type 20
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000008b5fe000-0x000000008b5fefff] usable
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x000000008b5ff000-0x000000008f7fffff] reserved
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 20 15:18:40 tareks-arch kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved

But It seems like the issue has been fixed for now. I updated networkmanager again today after that it's working great. Thank You.

Offline

#6 2021-04-22 13:06:13

seth
Member
Registered: 2012-09-03
Posts: 21,273

Re: [SOLVED]Network Issue

That's only the head of the journal, please see the first link in my signature and don't copy-and-paste out of the pager in case the issue re-emerges.

Otherwise please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB