Can't connect to internet

It was working normally but when I booted today it won’t connect to internet. Although wifi is connected and I tried also per LAN cable. Both don’t work.

Last time I used I connected to Protonvpn maybe it’s somehow related to that.

Could you suggest what to do?

Does your router have internet?

Of course, I am writing from other laptop now

Then, you could post the output of 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: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 84:a9:38:51:2b:13 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:45:e2:8a:6a:01 brd ff:ff:ff:ff:ff:ff
    inet 192.168.188.20/24 brd 192.168.188.255 scope global dynamic noprefixroute wlan0
       valid_lft 863994sec preferred_lft 863994sec
    inet6 fe80::f4a6:2206:b4b7:27f9/64 scope link noprefixroute 
       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 f2:f6:32:98:9c:7c brd ff:ff:ff:ff:ff:ff
    inet6 fdeb:446c:912d:8da::/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::d673:7f8e:afa9:bd93/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet 10.22.0.7/16 brd 10.22.255.255 scope global noprefixroute tun0
       valid_lft forever preferred_lft forever
    inet6 fe80::55b3:eb5e:dcd9:309a/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever

In a terminal, enter

ip addr

should get on item 2 something like this:

2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 70:85:c2:d5:80:87 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.107/24 brd 192.168.0.255 scope global dynamic noprefixroute enp8s0
       valid_lft 4626sec preferred_lft 4626sec
    inet6 fe80::5a75:9bc7:b708:d679/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

enp8s0 is the device name for the ethernet device. it will vary from computer to computer
inet 192.168.0.107/24 is the IP address the router assigned via DHCP
192.168.0.107

next enter

ip route

default via 192.168.0.1 dev enp8s0 proto dhcp src 192.168.0.107 metric 100 
192.168.0.0/24 dev enp8s0 proto kernel scope link src 192.168.0.107 metric 100 

default via 192.168.0.1 is the gateway through the router

next ping

ping 8.8.8.8

should see successful packets
next

ping endeavouros.com

should see sucessful packets

this should give some feel where the problem is.

Pudge

EDIT:
Ooops, ivanhoe beat me to it.

Sorry for that. Seems, he’s on a VM trying to connect via WiFi?

It was showing connected to VPN, so I disabled, now it looks like

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: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 84:a9:38:51:2b:13 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:45:e2:8a:6a:01 brd ff:ff:ff:ff:ff:ff
    inet 192.168.188.20/24 brd 192.168.188.255 scope global dynamic noprefixroute wlan0
       valid_lft 863637sec preferred_lft 863637sec
    inet6 fe80::f4a6:2206:b4b7:27f9/64 scope link noprefixroute 
       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 f2:f6:32:98:9c:7c brd ff:ff:ff:ff:ff:ff
    inet6 fdeb:446c:912d:8da::/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::d673:7f8e:afa9:bd93/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever



Sorry is not necessary. I have to applaud your speedy typing.

In your last post, with vpn disabled, DHCP is still not assigning a IP address to your computer

try

ping 127.0.0.1

which according to ip addr is your loopback

If you can ping 127.0.0.1 then something is wrong between your computer and the router.

Pudge

I can ping. I will restart the router.

If that doesn’t work, you’d have to completely uninstall the Proton VPN and reboot your computer, I’m afraid to think… just to see a working condition again.

After that, you can proceed to re-install that VPN…

1 Like

It’s not fault of router, I have tried to connect with mobile hotspot and it won’t work either. Do I have to remove openvpn packages also?

I’d do that, to make the whole process of re-installing sweet and short, before you begin loosing your faith in between several reboots… :wink:

I think I will just export package list and reinstall os. Thank you for your support, have a good weekend.

1 Like

As a general hint: Don’t trust VPNs advertised as “for free”, please.

They tend to mess up your system (network-setup) quicker than you’re able to tell. (Aside from selling your data to shady sources, or even worse.)

The one you named has a “known history” for that, not only on this forum…

:wink:

1 Like

:+1: thank you for information

1 Like

Welcome!

If re-installing doesn’t work, come back and we will tackle this again.

Pudge

3 Likes

Thanks!

Okay, time for lessons learned for orderly troubleshooting of internet connection problems.

  1. As ivanhoe suggested, if running through a VM or a VPN, get back to a bare metal OS with out VM or VPN.

  2. Start with ip address. Item 1 will give the computer’s loopback IP, item 2 will show if the computer’s ethernet device talked to the router and was assigned a IP addr through DHCP

  3. check the computer first by pinging the loopback IP. This is a pretty good check of the computer’s hardware.

  4. If you know the LAN side IP address of the router, try to ping that address to see if the router is reachable. If one can ping the loopback IP and cannot ping the router, then the problem is not the computer.

  5. If you can ping the router’s LAN address, then start looking at the router itself, then look at devices farther away from the computer such as the cable modem. Can you ping the LAN side address of the cable modem. If there is no VPN involved, the cable modem should ping OK.

  6. if all looks good on your premise, try to ping 8.8.8.8 (IP address of Google) and if successful, try to ping google.com
    If 8.8.8.8 pings OK and google.com does not, then you have DNS problems.

If anyone has any additions or suggestions, let us know.

EDIT:
On a side note, item 3 of the ip addr command shows that wlan0 device did talk to the WiFi controller and did so on inet 192.168.188.20. Which further makes me think this problem was not the computer itself.

Pudge

1 Like