I am facing issue with my internet connection. I am using Ubuntu 18.04.3 LTS.
Issue:-
I am using HOXX vpn extension on firefox browser. For few months it was working good. Now i am facing issue when i disconnect VPN, i am not able to access internet on firefox browser. When i connect it works fine.
I thought it is browser related issue, so i tried with opera and facing same issue.
So i think my network related settings got changed and it is not allowing to access internet.
If anyone can help it will be great.
Is it possible that you unintentionally activated some sort of kill-switch through the vpn-settings?
Have you tried uninstalling the extension to see if this changes the situation?
Done update and other installations as you suggested.
Here are the outputs:
When VPN is connected:
ip a
Blockquote
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: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 40:49:0f:44:61:4f brd ff:ff:ff:ff:ff:ff
inet 192.168.43.140/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp4s0
valid_lft 2958sec preferred_lft 2958sec
inet6 2409:4051:393:64ee:6916:d9d3:ffac:bcf/64 scope global temporary dynamic
valid_lft 3407sec preferred_lft 3407sec
inet6 2409:4051:393:64ee:5038:93b3:d222:7e97/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 3407sec preferred_lft 3407sec
inet6 fe80::26a5:62e6:4cb:b23c/64 scope link noprefixroute
valid_lft forever preferred_lft forever
<Blockquote
ip route
Blockquote
default via 192.168.43.185 dev wlp4s0 proto dhcp metric 600
169.254.0.0/16 dev wlp4s0 scope link metric 1000
192.168.43.0/24 dev wlp4s0 proto kernel scope link src 192.168.43.140 metric 600
traceroute 8.8.8.8
Blockquote
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 _gateway (192.168.43.185) 2.685 ms 2.610 ms 3.220 ms
2 * * *
3 10.72.115.19 (10.72.115.19) 48.728 ms 10.72.115.2 (10.72.115.2) 48.712 ms 10.72.115.18 (10.72.115.18) 49.072 ms
4 172.26.10.143 (172.26.10.143) 48.997 ms 49.489 ms 172.26.10.139 (172.26.10.139) 54.835 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * 74.125.243.97 (74.125.243.97) 88.458 ms 108.170.251.113 (108.170.251.113) 88.272 ms
10 72.14.232.95 (72.14.232.95) 88.272 ms dns.google (8.8.8.8) 68.319 ms 172.253.67.87 (172.253.67.87) 69.085 ms
Blockquote
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: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 40:49:0f:44:61:4f brd ff:ff:ff:ff:ff:ff
inet 192.168.43.140/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp4s0
valid_lft 2381sec preferred_lft 2381sec
inet6 2409:4051:393:64ee:6916:d9d3:ffac:bcf/64 scope global temporary dynamic
valid_lft 3227sec preferred_lft 3227sec
inet6 2409:4051:393:64ee:5038:93b3:d222:7e97/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 3227sec preferred_lft 3227sec
inet6 fe80::26a5:62e6:4cb:b23c/64 scope link noprefixroute
valid_lft forever preferred_lft forever
ip route
Blockquote
default via 192.168.43.185 dev wlp4s0 proto dhcp metric 600
169.254.0.0/16 dev wlp4s0 scope link metric 1000
192.168.43.0/24 dev wlp4s0 proto kernel scope link src 192.168.43.140 metric 600
traceroute 8.8.8.8
Blockquote
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 _gateway (192.168.43.185) 218.748 ms 218.691 ms 218.971 ms
2 * * *
3 10.72.115.3 (10.72.115.3) 266.260 ms 10.72.115.18 (10.72.115.18) 266.177 ms 10.72.115.3 (10.72.115.3) 266.511 ms
4 172.26.10.143 (172.26.10.143) 266.068 ms 172.26.10.139 (172.26.10.139) 265.914 ms 172.26.10.143 (172.26.10.143) 265.673 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 108.170.251.113 (108.170.251.113) 71.171 ms 51.929 ms *
10 172.253.67.85 (172.253.67.85) 89.608 ms 72.14.232.95 (72.14.232.95) 89.651 ms 209.85.252.71 (209.85.252.71) 89.339 ms
11 dns.google (8.8.8.8) 89.202 ms 89.323 ms 89.155 ms
As you can see, there is no difference on the system when the VPN is connected/disconnected. You also can connect to the internet, when connected and disconnected.
Usually a VPN changes at least the routes on the computer but not even those are changed. Are you sure you are using a VPN, at all? Clarify, if you are maybe actually using a simple proxy forward.
Uninstall the extension and see if that changes anything.
The internet needs to work now, as otherwise it would be impossible to use the extension, because you have to log in to use it. So if you are not connected to the internet, you cannot use it.
In the worst case scenario, attach a LAN cable to your device.