Connected to wifi but internet not working

[mr1di0t]

Hello everyone,
I’m using Manjaro for last 6 months it was working fine. But tomorrow I had a really terrible network connection and I tried to install some packages using yay and as the network is terrible so it errored out for so many times and I retried too but after couple of retries the network just went off and not working anymore. Like as one would thought may be network problem so I changed my network (BTW I’m using android Wi-Fi) to another network. But the same error popped out. I tried reconnecting using nmcli. Although it shows successfully connected to the network but internet not working.

I also edited /etc/resolv.conf file

when I tried to ping google,com it shows
ping: google,com: Name or Service not known

but when I ping 8.8.8.8 it just stucks and doesn’t show any output

I tried all solutions regarding
ping: google,com: Name or Service not known.
##Ans also I don’t know how to embeed picture into a post it just shows you cannot embeed picture in this post.
Please help me with that. Thanks in advance.

[TriMoon]

Hi and welcome to the Forum

---

First off please see, especially how to post output of commands:

[HowTo] Provide System Information

This tutorial is superseded by this one. Remember all Tutorials are wiki posts that can be edited by TL2 (Trust Level 2) members and above. Welcome to Manjaro! To allow all of us helpful people on this forum TO HELP YOU, we need some basic information about your system. This probably means you described the symptoms of your problem, but now we need some more information to know where the origin of your issue is exactly. Someone else probably linked you to…

After reading that please provide the output of these commands:

1. networkctl status --all
   

2. ip addr
   

3. ip route
   

@mr1di0t

(BTW I’m using android Wi-Fi) to another network.

You should also describe in details how you connected to your Android WiFi…

@mr1di0t

I also edited /etc/resolv.conf file

Also provide the contents of this file…

@mr1di0t

when I tried to ping google,com it shows
ping: google,com: Name or Service not known

but when I ping 8.8.8.8 it just stucks and doesn’t show any output

Being able to ping and resolve hostnames, although related to network connectivity, are not the same things…

[mr1di0t]

Hello thanks for the reply.

@TriMoon

First off please see, especially how to post output of commands:

I didn’t find any help here but I know a little bit of MarkDown language so I tried my best to answer all your questions.

The output of the commands are as follows.

networkctl status --all

󰣇  mrkk ~ ✓  networkctl status --all
WARNING: systemd-networkd is not running, output will be incomplete.

Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not found.
Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not found.
Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not found.
Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not found.
Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not found.
Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not found.
Failed to query link DHCP leases: Unit dbus-org.freedesktop.network1.service not found.
● 1: lo
                     Link File: n/a
                  Network File: n/a
                         State: n/a (unmanaged)
                  Online state: unknown
                          Type: loopback
              Hardware Address: 00:00:00:00:00:00
                           MTU: 65536
                         QDisc: noqueue
  IPv6 Address Generation Mode: eui64
      Number of Queues (Tx/Rx): 1/1
                       Address: 127.0.0.1
                                ::1
Failed to query link DHCP leases: Unit dbus-org.freedesktop.network1.service not found.

● 2: enp5s0
                     Link File: /usr/lib/systemd/network/99-default.link
                  Network File: n/a
                         State: n/a (unmanaged)
                  Online state: unknown
                          Type: ether
                          Path: pci-0000:05:00.0
                        Driver: r8169
                        Vendor: Realtek Semiconductor Co., Ltd.
                         Model: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (Onboard Ethernet)
              Hardware Address: b4:2e:99:e1:f7:bf (GIGA-BYTE TECHNOLOGY CO.,LTD.)
                           MTU: 1500 (min: 68, max: 9194)

ip addr

󰣇  mrkk ~ ✓  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: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether b4:2e:99:e1:f7:bf brd ff:ff:ff:ff:ff:ff
3: pvpnksintrf0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 26:31:62:c4:87:01 brd ff:ff:ff:ff:ff:ff
    inet 100.85.0.1/24 brd 100.85.0.255 scope global noprefixroute pvpnksintrf0
       valid_lft forever preferred_lft forever
    inet6 fdeb:446c:912d:8da::/64 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::69ed:121f:5742:a309/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::dd8a:7de3:fab9:6495/64 scope link
       valid_lft forever preferred_lft forever
4: ipv6leakintrf0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether d6:d7:48:75:c1:a1 brd ff:ff:ff:ff:ff:ff
    inet6 fdeb:446c:912d:8da::/64 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::21be:a268:a8be:f2b2/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::7062:c31c:6b49:f4ce/64 scope link
       valid_lft forever preferred_lft forever
5: pvpnroutintrf0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether e6:a0:2f:b9:80:71 brd ff:ff:ff:ff:ff:ff
    inet 100.85.0.1/24 brd 100.85.0.255 scope global noprefixroute pvpnroutintrf0
       valid_lft forever preferred_lft forever
    inet6 fdeb:446c:912d:8da::/64 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::f2cf:89a7:1d13:27ca/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::dc20:7af1:73c2:663a/64 scope link
       valid_lft forever preferred_lft forever
6: wlp0s20f0u7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:1e:a6:99:75:b5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.64/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp0s20f0u7
       valid_lft 3457sec preferred_lft 3457sec
    inet 192.168.43.65/24 brd 192.168.43.255 scope global secondary dynamic noprefixroute wlp0s20f0u7
       valid_lft 3465sec preferred_lft 3015sec
    inet6 2402:3a80:1a48:1809:1496:b52d:8bfb:da89/64 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 2402:3a80:1a48:1809:7454:2f3f:ab59:b21f/64 scope global mngtmpaddr noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::d8be:ea65:5ad7:c2c7/64 scope link
       valid_lft forever preferred_lft forever
    inet6 fe80::268:fcbb:f22d:edf0/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

ip route

󰣇  mrkk ~ ✓  ip route
0.0.0.0/1 dev pvpnroutintrf0 proto static scope link metric 97
default via 100.85.0.1 dev pvpnksintrf0 proto static metric 98
default via 192.168.43.1 dev wlp0s20f0u7 proto dhcp src 192.168.43.65 metric 3006
100.85.0.0/24 dev pvpnroutintrf0 proto kernel scope link src 100.85.0.1 metric 97
100.85.0.0/24 dev pvpnksintrf0 proto kernel scope link src 100.85.0.1 metric 98
128.0.0.0/2 dev pvpnroutintrf0 proto static scope link metric 97
192.0.0.0/4 dev pvpnroutintrf0 proto static scope link metric 97
192.168.43.0/24 dev wlp0s20f0u7 proto dhcp scope link src 192.168.43.65 metric 3006
208.0.0.0/6 dev pvpnroutintrf0 proto static scope link metric 97
212.0.0.0/13 dev pvpnroutintrf0 proto static scope link metric 97
212.8.0.0/17 dev pvpnroutintrf0 proto static scope link metric 97
212.8.128.0/18 dev pvpnroutintrf0 proto static scope link metric 97
212.8.192.0/19 dev pvpnroutintrf0 proto static scope link metric 97
212.8.224.0/20 dev pvpnroutintrf0 proto static scope link metric 97
212.8.240.0/21 dev pvpnroutintrf0 proto static scope link metric 97
212.8.248.0/23 dev pvpnroutintrf0 proto static scope link metric 97
212.8.250.0/25 dev pvpnroutintrf0 proto static scope link metric 97
212.8.250.128/27 dev pvpnroutintrf0 proto static scope link metric 97
212.8.250.160/28 dev pvpnroutintrf0 proto static scope link metric 97
212.8.250.176/29 dev pvpnroutintrf0 proto static scope link metric 97
212.8.250.184/30 dev pvpnroutintrf0 proto static scope link metric 97
212.8.250.188/31 dev pvpnroutintrf0 proto static scope link metric 97
212.8.250.190 dev pvpnroutintrf0 proto static scope link metric 97
212.8.250.192/26 dev pvpnroutintrf0 proto static scope link metric 97
212.8.251.0/24 dev pvpnroutintrf0 proto static scope link metric 97
212.8.252.0/22 dev pvpnroutintrf0 proto static scope link metric 97
212.9.0.0/16 dev pvpnroutintrf0 proto static scope link metric 97
212.10.0.0/15 dev pvpnroutintrf0 proto static scope link metric 97
212.12.0.0/14 dev pvpnroutintrf0 proto static scope link metric 97
212.16.0.0/12 dev pvpnroutintrf0 proto static scope link metric 97
212.32.0.0/11 dev pvpnroutintrf0 proto static scope link metric 97
212.64.0.0/10 dev pvpnroutintrf0 proto static scope link metric 97
212.128.0.0/9 dev pvpnroutintrf0 proto static scope link metric 97
213.0.0.0/8 dev pvpnroutintrf0 proto static scope link metric 97
214.0.0.0/7 dev pvpnroutintrf0 proto static scope link metric 97
216.0.0.0/5 dev pvpnroutintrf0 proto static scope link metric 97
224.0.0.0/3 dev pvpnroutintrf0 proto static scope link metric 97

I connected the wifi using:

nmcli dev wifi list

sudo nmcli dev wifi connect <Network SSID>

It’s not like I’m connecting it for the first time. I just never had the issue previously. I always connect with my android device

@TriMoon

Also provide the contents of this file…

The contents of /etc/resolv.conf are as follows

# Generated by resolvconf
nameserver 192.168.43.1
nameserver 2402:3a80:1fff:40::4
nameserver 2001:4860:4860::6464

One thing I wanted to say that this file is changing every time I’m rebooting the Computer.

Answer to your suggestion

@TriMoon

Being able to ping and resolve hostnames, although related to network connectivity, are not the same things…

I know I’m just asking if it’s the problem of DNS or something.
Thank you waiting for your reply .

[TriMoon]

@mr1di0t

One thing I wanted to say that this file is changing every time I’m rebooting the Computer.

That is expected behaviour, because of DHCP.

Looking at the rest of the info you provided, it is obviously a problem with your VPN config, because all your network connections are routed through it.
So try to disable your VPN and check again.
If that works, fix your VPN config

You won’t be able to resolve any domain names, until your VPN connection is working…

[mr1di0t]

@TriMoon

Looking at the rest of the info you provided, it is obviously a problem with your VPN config, because all your network connections are routed through it.
So try to disable your VPN and check again.
If that works, fix your VPN config

Hello Mr. Moon
Just wanted to say that I also thought of this that’s why I removed the vpn.
It was proton vpn.
I removed it through pamac

sudo pamac remove protonvpn

[TriMoon]

@mr1di0t

Hello Mr. Moon
Just wanted to say that I also thought of this that’s why I removed the vpn.
It was proton vpn.
I removed it through pamac

It’s “Ms.Moon”
But if you removed that package then why does your routing table still show:

@mr1di0t

0.0.0.0/1 dev pvpnroutintrf0 proto static scope link metric 97
default via 100.85.0.1 dev pvpnksintrf0 proto static metric 98

And all the other mentions of pvpn*
Maybe you need to reboot and check the output of those commands again…

[mr1di0t]

@TriMoon

But if you removed that package then why does your routing table still show:

Thanks Ms. Moon for the reply.
That’s what I’m also thinking
When I do

nmcli con show

it shows this which has the entries for protonvpn

󰣇  mrkk ~ ✓  nmcli con show
NAME                          UUID                                  TYPE      DEVICE
pvpn-killswitch               60ea5ff5-a2ba-4b66-af40-470367a7e3d1  dummy     pvpnksintrf0
pvpn-ipv6leak-protection      a38172e1-69f0-4004-8d21-61b22646e8b0  dummy     ipv6leakintrf0
Galaxy A12AFA8          2037dd13-c5fb-4c44-bce0-59432ea00400  wifi      wlp0s20f0u7
pvpn-routed-killswitch        be331b8c-f979-4cab-8c1a-150386e191ae  dummy     pvpnroutintrf0

@TriMoon

Maybe you need to reboot and check the output of those commands again…

I actually rebooted the pc over 50 times no work.
Is there any other way to remove pamac aur softwares. Thanks Again
And also sorry for being late actually I’m in a dual boot with windows11 so I had to go back to manjaro and collect the info of the command nmcli. And then after coming back windows also suffered from the same problem my wifi was connected but no internet so I removed the vpn and it worked again. May be you are right Vpn is the main culprit. So is there any other way to completely remove the vpn from Manjaro.
Thank You for your generous help

[TriMoon]

Those entries, like you said yourself, are configurations from NetworkManager (nmcli is the user command to interact with it), so you need to remove those configs.
Those configs are separate from a package you install/remove.

Normally a well written package removes that kind of config that it creates itself when being removed.
But looks like you need to remove those manually in this case…
I have no idea how todo things using nmcli because i use systemd network units for all my configs…

[mr1di0t]

@TriMoon

But looks like you need to remove those manually in this case…

Hello Ms. Moon after your advice I search for the deletion of Vpn configs from NetworkManager and I came across an article HERE and it resolved the problem.

Those in future want to know the solution it’s as follows:
First list the networks using

nmcli con show

then find the proton vpn networks and delete them one by one. In my case:

nmcli c delete pvpn-killswitch

nmcli c delete pvpn-ipv6leak-protection

nmcli c delete pvpn-routed-killswitch

Then reconnect using

sudo nmcli dev wifi connect <Network SSID>

And thats all.

And lastly thanks to Ms. @TriMoon for the right guidance .