linux-cli-community
linux-cli-community copied to clipboard
Rafficer
[BUG]Successfully connected but the internet doesn't work.
Describe the bug VPN gets connected but can not access internet, ping doesn't work either.
To Reproduce Steps to reproduce the behavior:
- sudo protonvpn c -f
- ping whatever.com
Expected behavior I expected my internet to work using protonvpn-cli.
Desktop :
- OS: Manjaro 20.2
- Python Version: 3.8.6
- ProtonVPN-CLI Version: 2.2.4
Additional context Hi there, I am trying to connect proton VPN on my manjaro system, VPN gets connected but the net doesn't work. Nothing gets loading, no ping, nothing. Tried UDP & TCP both, the issue remains the same. I didn't try the manual connection via NetworkManager & openvpn because the proton vpn tool is supposed to provide easy way for connection.
PS: It's the free version
I got the same issue, but I purchase ProtonVPN Plus
Yeah, what if someone can't purchase right now?
It means: not work with P2P and Secure Core servers, besides normal servers
Hello, I have the same problem on fedora 33 and a ProtonVPN Plus account. I can't ping an address like google.com but I can ping an IP address so it seems to be a DNS issue. Can you try to ping an IP address like 1.1.1.1 to see if the issue is the same ?
I don't have a problem using Network Manager (https://protonvpn.com/support/linux-vpn-setup/)
Here are the "resolvectl dns" commands:
Without vpn connection :
resolvectl dns
Global:
Link 2 (wlp3s0): 212.27.40.241 212.27.40.240
Link 3 (virbr0):
Link 4 (virbr0-nic):
VPN using Network Manager :
resolvectl dns
Global:
Link 2 (wlp3s0):
Link 3 (virbr0):
Link 4 (virbr0-nic):
Link 24 (tun0): 10.19.0.1
VPN using protonvpn-cli :
resolvectl dns
Global:
Link 2 (wlp3s0): 212.27.40.241 212.27.40.240
Link 3 (virbr0):
Link 4 (virbr0-nic):
Link 25 (proton0):
Hey all 👋🏻
The linux clients are currently being rewritten, so no new commits will be pushed to fix actual issues.
@ImAReplicant I have the exact same issue, ping on 1.1.1.1 will work but not on "www.google.com", I'm on Fedora 33 and I have the issue only since 2 or 3 days max.
@calexandru2018 Well that's pretty good news but since this issue makes the protonvpn-cli unusable, could you tell us what time will it take to rewrite the clients ? That would be great because I'm not very confortable using VPN through Network Manager...
Well... it seems to be working again, I have no clues what fixed the issue for me, no update or what.
One thing's a bit weird, I still cannot "ping www.google.com", 100% packet loss, but I'm able to connect to google.com on Firefox so...
Hello, I have the same problem on fedora 33 and a ProtonVPN Plus account. I can't ping an address like google.com but I can ping an IP address so it seems to be a DNS issue. Can you try to ping an IP address like 1.1.1.1 to see if the issue is the same ?
I don't have a problem using Network Manager (https://protonvpn.com/support/linux-vpn-setup/)
Here are the "resolvectl dns" commands:
Without vpn connection :
resolvectl dns Global: Link 2 (wlp3s0): 212.27.40.241 212.27.40.240 Link 3 (virbr0): Link 4 (virbr0-nic):VPN using Network Manager :
resolvectl dns Global: Link 2 (wlp3s0): Link 3 (virbr0): Link 4 (virbr0-nic): Link 24 (tun0): 10.19.0.1VPN using protonvpn-cli :
resolvectl dns Global: Link 2 (wlp3s0): 212.27.40.241 212.27.40.240 Link 3 (virbr0): Link 4 (virbr0-nic): Link 25 (proton0):
OK, I don't have a problem using Network Manager (https://protonvpn.com/support/linux-vpn-setup/), why should I use Network Manager when the Client exists?
Plus user here: I'm facing a similar issue after an update on Arch Linux, it seems. Not sure which update broke the CLI tool, but it happened in the past 2-4 days. (It was finals week for me when it happened and I didn't have the time to debug it when it started failing.)
➜ ~ sudo protonvpn d
Disconnected.
➜ ~ resolvectl dns
Global: 192.168.0.1 192.168.0.113
Link 2 (enp3s0):
Link 3 (wlp2s0): 192.168.0.1 192.168.0.113
➜ ~ ip r
default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.112 metric 600
➜ ~ sudo protonvpn c -f
Connecting to US-VA#4 via UDP...
Connected!
➜ ~ resolvectl dns
Global: 10.17.0.1
Link 2 (enp3s0):
Link 3 (wlp2s0): 192.168.0.1 192.168.0.113
Link 6 (proton0):
➜ ~ ip r
0.0.0.0/1 via 10.17.0.1 dev proton0
default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600
10.17.0.0/16 dev proton0 proto kernel scope link src 10.17.0.2
128.0.0.0/1 via 10.17.0.1 dev proton0
162.210.192.160 via 192.168.0.1 dev wlp2s0
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.112 metric 600
➜ ~ ping google.com
ping: google.com: Name or service not known
➜ ~ ping 10.17.0.1
PING 10.17.0.1 (10.17.0.1) 56(84) bytes of data.
64 bytes from 10.17.0.1: icmp_seq=1 ttl=64 time=41.3 ms
64 bytes from 10.17.0.1: icmp_seq=2 ttl=64 time=20.1 ms
64 bytes from 10.17.0.1: icmp_seq=3 ttl=64 time=20.1 ms
64 bytes from 10.17.0.1: icmp_seq=4 ttl=64 time=19.2 ms
^C
--- 10.17.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 19.159/25.178/41.346/9.342 ms
➜ ~
I'm aware that there's lack of IPv6 support from ProtonVPN and that they just block all IPv6 because of that. This doesn't seem to be related to that. I'm able to ping the DNS server, but it seems that it's not resolving domains at all...
Curiously, pulse-secure (AUR), the VPN I use with my university, also broke. It segfaults.
I just did a little bit of digging and found that systemd-resolvconf was updated 2020-12-14 to 247.1-4 (core repository on Arch Linux). However, downgrading to 246.6-1 didn't fix it even after rebooting.
This is the stuff I found installed for DNS if it helps anyone at Proton figure out what's going on.
➜ ~ pacman -Qs resolv
local/libmicrodns 0.2.0-1
Minimal mDNS resolver library
local/systemd-resolvconf 247.1-4
systemd resolvconf replacement (for use with systemd-resolved)
Edit: Just tried downgrading protonvpn-cli-ng (AUR) to 2.2.4 and that didn't work either. My current suspicion is something with all of the Python 3.9 updates.
Hello, I have the same problem on fedora 33 and a ProtonVPN Plus account. I can't ping an address like google.com but I can ping an IP address so it seems to be a DNS issue. Can you try to ping an IP address like 1.1.1.1 to see if the issue is the same ?
I don't have a problem using Network Manager (https://protonvpn.com/support/linux-vpn-setup/)
Here are the "resolvectl dns" commands:
Without vpn connection :
resolvectl dns Global: Link 2 (wlp3s0): 212.27.40.241 212.27.40.240 Link 3 (virbr0): Link 4 (virbr0-nic):VPN using Network Manager :
resolvectl dns Global: Link 2 (wlp3s0): Link 3 (virbr0): Link 4 (virbr0-nic): Link 24 (tun0): 10.19.0.1VPN using protonvpn-cli :
resolvectl dns Global: Link 2 (wlp3s0): 212.27.40.241 212.27.40.240 Link 3 (virbr0): Link 4 (virbr0-nic): Link 25 (proton0):
get recked, even the network manager method doesn't work.
I don't understand, why none of the devs have responded to this?
I don't understand, why none of the devs have responded to this?
I reported this issue through the ProtonVPN portal, so maybe that'll trigger something to prioritize fixing this.
Hey all 👋
There will be no further commits to the community version as Proton now has an official client. You can find more info here: https://protonvpn.com/blog/linux-vpn-cli-beta/
Hey all
There will be no further commits to the community version as Proton now has an official client. You can find more info here: https://protonvpn.com/blog/linux-vpn-cli-beta/
Wait, this was the community version? No wonder why I was not getting a response, I am sorry, I didn't know that.
There will be no further commits to the community version as Proton now has an official client.
But what if we don't run Debian, Ubuntu, or Linux Mint? (Also, Kali is just a penetration testing environment...I don't know anyone who runs it seriously as a daily driver, nor should they because of built-in security vulnerabilities...)
If I'm running a different distro and you're no longer making updates to this repository, what do I do about not being able to connect at all anymore? What's the time frame for support for other distros?
There will be no further commits to the community version as Proton now has an official client.
But what if we don't run Debian, Ubuntu, or Linux Mint? (Also, Kali is just a penetration testing environment...I don't know anyone who runs it seriously as a daily driver, nor should they because of built-in security vulnerabilities...)
If I'm running a different distro and you're no longer making updates to this repository, what do I do about not being able to connect at all anymore? What's the time frame for support for other distros?
As the blog says, this is just the beta. I think we should wait for a little. And I totally agree with your point, developers who develop apps for the Linux world just assume that everyone is running debian/ubuntu based distro. Can't believe I am saying this, but proton should make a snap package.
Further support for rpm and arch based systems will be added in the upcoming weeks, as setting up the infrastructure for supporting all three base distros at launch was not possible.
@JCDetwiler can you post the output of resolvectl status?
My problem was that for my real link device (wlan0) I had ~. in the DNS Domain setting/the DefaultRoute option enabled and DNS queries were being routed through that device instead of proton0. I believe it's NetworkManager pushing those settings.
Using nslookup or dig was working fine but ping/my browser was failing to lookup names.
I was getting:
$ sudo resolvectl query github.com -4
github.com: resolve call failed: All attempts to contact name servers or networks failed
I had to use:
sudo resolvectl domain wlan0 "" # or whatever, as long as it doesn't include "~."
sudo resolvectl domain proton0 "~."
for things to work.
@michaelbeaumont I don't even understand what that did, but I had the same problem, and changing the DNS Domain fixed it for me too.
The OpenVPN configs work too by the way, but they leak DNS queries for me.