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.
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
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…
Okay, time for lessons learned for orderly troubleshooting of internet connection problems.
As ivanhoe suggested, if running through a VM or a VPN, get back to a bare metal OS with out VM or VPN.
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
check the computer first by pinging the loopback IP. This is a pretty good check of the computer’s hardware.
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.
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.
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.