ping issues but network is fine

archsavedme · 2022-03-24 10:22:06

Hello everyone, I have a strange issue with my pc. Basically, the network works but can't ping anything even in my local network. I don't know what to look for. I apologize for my ignorance but I'm no expert.
I don't think I have some active firewall that could give problems
If I try to ping this PC from another device it replies but not the contrary.
I tried an ssh connection and it works in both directions
I tried port scanning and still no problem

I put some of the outputs

# ping 192.168.43.1
PING 192.168.43.1 (192.168.43.1) 56(124) bytes of data.

--- 192.168.43.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2107ms

user@archlinux ~> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(124) bytes of data.

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2099ms

I tried to check with tracepath and this is the result:

archlinux ~ [1]> tracepath 192.168.43.1
 1?: [LOCALHOST]                      pmtu 1500
 1:  _gateway                                              6.114ms reached
 1:  _gateway                                              4.442ms reached
     Resume: pmtu 1500 hops 1 back 1

device in the local network

archlinux ~> tracepath 192.168.43.242
 1?: [LOCALHOST]                      pmtu 1500
 1:  raspberrypi                                         305.114ms reached
 1:  raspberrypi                                           8.649ms reached
     Resume: pmtu 1500 hops 1 back 1

ping this machine from another device :

pi@raspberrypi:~ $ ping -c 3 192.168.43.26
PING 192.168.43.26 (192.168.43.26) 56(84) bytes of data.
64 bytes from 192.168.43.26: icmp_seq=1 ttl=64 time=4.09 ms
64 bytes from 192.168.43.26: icmp_seq=2 ttl=64 time=205 ms
64 bytes from 192.168.43.26: icmp_seq=3 ttl=64 time=178 ms

--- 192.168.43.26 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 4.090/129.515/205.737/89.372 ms

I tried to disable the network manager and use wpa_supplicat but the result is the same.

I haven't found online this kind of issue, does anyone have any advice about where to look for a solution.

Ok here the information that looks more relevant
lspci -k

07:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
        Subsystem: Lenovo Qualcomm Atheros QCA9377 Wireless Network Adapter
        Kernel driver in use: ath10k_pci
        Kernel modules: ath10k_pci
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Lenovo Device 38b4
        Kernel driver in use: r8169
        Kernel modules: r8169

IP link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 8c:16:45:96:cc:2e brd ff:ff:ff:ff:ff:ff
3: wlp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 50:5b:c2:d7:6d:f7 brd ff:ff:ff:ff:ff:ff

IP address

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: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 8c:16:45:96:cc:2e brd ff:ff:ff:ff:ff:ff
3: wlp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 50:5b:c2:d7:6d:f7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.26/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp7s0
       valid_lft 3323sec preferred_lft 3323sec
    inet6 fe80::6fac:fe7c:5712:2b38/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

IP route

default via 192.168.43.1 dev wlp7s0 proto dhcp metric 600
192.168.43.0/24 dev wlp7s0 proto kernel scope link src 192.168.43.26 metric 600

IP -6 route

::1 dev lo proto kernel metric 256 pref medium
fe80::/64 dev wlp7s0 proto kernel metric 1024 pref medium

iptables -nvL

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

/etc/hosts is empty (just two comments)

Thank you for your help!

Last edited by archsavedme (2022-04-04 22:36:35)

Lone_Wolf · 2022-03-24 12:01:18

Please post of output of

$ ping 127.0.0.1
$ ping localhost

Incase those don't have 0% loss :
boot to a live environment like arch install iso and verify if that does have internet .

Assuming the 2 commands above succeed without losses :

post

$ lspci -k
$ ip link
$ ip address
$ ip route
$ ip -6 route

seth · 2022-03-24 13:08:06

Is the raspi a pihole?

archsavedme · 2022-03-29 14:52:07

also:

PING 127.0.0.1 (127.0.0.1) 56(124) bytes of data.

--- 127.0.0.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2114ms

ping localhost

is not recognized as a valid command (print the help page)

I tried to book from a live environment and it worked. Also, with this environment, I tried to disable the nework manager and connect through wpa_supplicant and it's still doesn't respond.

About the raspberry: I don't use it to affect the network.
I tried to connect to the raspberry through ssh and vice-versa and it worked in both directions

seth · 2022-03-29 15:00:14

Lone_Wolf wrote:

$ lspci -k
$ ip link
$ ip address
$ ip route
$ ip -6 route

And add

sudo journalctl -b
iptables -nvL
nft list ruleset

to that.

ping localhost is not recognized as a valid command (print the help page)

And your /etc/hosts

Zod · 2022-03-29 15:04:51

At times I've wondered why the official Arch installation instructions no longer address /etc/hosts.

Myself, I continue to edit it and add what used to be suggested.

Last edited by Zod (2022-03-29 15:05:29)

seth · 2022-03-29 15:19:58

https://wiki.archlinux.org/title/Networ … resolution
https://bugs.archlinux.org/task/56684#comment164441

Zod wrote:

Myself, I continue to edit it and add what used to be suggested.

What is a sensible idea indeed.

Arch Linux

#1 2022-03-24 10:22:06

ping issues but network is fine

#2 2022-03-24 12:01:18

Re: ping issues but network is fine

#3 2022-03-24 13:08:06

Re: ping issues but network is fine

#4 2022-03-29 14:52:07

Re: ping issues but network is fine

#5 2022-03-29 15:00:14

Re: ping issues but network is fine

#6 2022-03-29 15:04:51

Re: ping issues but network is fine

#7 2022-03-29 15:19:58

Re: ping issues but network is fine

Board footer