morpheusthewhite / nordpy

A gui application to connect automatically to the recommended NordVPN server
GNU General Public License v3.0
105 stars 16 forks source link

Manjaro linux - Not able to disconnect properly #26

Closed sorryusernameisalreadytaken closed 4 years ago

sorryusernameisalreadytaken commented 4 years ago

Before Posting an issue

The bug When I connect to any vpn and then diconnect my network is broken. I need todo a rebot to get my network working again.

To Reproduce Steps to reproduce the behavior:

  1. Install manjaro (with kde-PLASMA and kernel 4.19.85-1-MANJARO)
  2. Install the latest nordpy with trizen
  3. put in your credentials and leave all the settings to default-values
  4. Connect to any server
  5. Disconnect from any server

Sadly I did not know how I can give you some logs. If you tell me that I will do this. It would be awesome if we can bring it to run. I did not change a lot on this manjaro install.

morpheusthewhite commented 4 years ago

This is a problem I am myself encountering in the past weeks

morpheusthewhite commented 4 years ago

It is caused by the DNS configuration (which is set up by manually modifying the resolv.conf file after some DNS leaks). I need to find a workaround for using resolvconf or autoconf on all systems (which I had previously used by had problems in private networks which presented a login page)

morpheusthewhite commented 4 years ago

At the moment I am not able to replicate the problem.

Can you provide me the following informations?

  1. DNS configuration before VPN connection (just cat /etc/resolv.conf)
  2. Iptables before VPN connection (sudo iptables --list)
  3. DNS configuration after VPN connection
  4. Iptables after VPN connection
  5. What is the connection error when you open a browser?
  6. What is the output of ping github.com? What is the output of ping 8.8.8.8?
MuffinCollector commented 4 years ago

I've been dealing with this on and off as well on my Arch installation. I can't seem to reproduce at the moment, but last time I experienced this, I checked my resolv.conf and it looked appropriate (contained my router address which I use as my DNS server and is how it normally appears when not connected) and my iptables list. iptables when not connected for me is blank. When I became unable to connect to the internet, it instead appeared to be the same as when I'm connected to my VPN. While I failed to note the specifics at that time, I was able to regain my connection without reboot by flushing iptables and then restarting the iptables service.

morpheusthewhite commented 4 years ago

This should be fixed with https://github.com/morpheusthewhite/nordpy/commit/80ab4f9477ca80b9f670af015e47279e3271498d

larry77 commented 4 years ago

I am experiencing the same issue on debian stable + wicd network manager + TCP when the wifi goes down. If it happens again, I will post more.

morpheusthewhite commented 4 years ago

Are you using the latest version?

morpheusthewhite commented 4 years ago

Oh wait if the wifi goes down and then comes back again I think it's obvious it won't work, it's actually a problem related to openvpn

larry77 commented 4 years ago

yes, I am using the latest version. I have issues even if I just disconnect from the vpn using the app. Before the vpn connection

~$ cat /etc/resolv.conf domain hotspot.ec.europa.eu search hotspot.ec.europa.eu nameserver 147.67.12.18 nameserver 147.67.250.18

~$ sudo iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination

Chain FORWARD (policy ACCEPT) target prot opt source destination

Chain OUTPUT (policy ACCEPT) target prot opt source destination

After the VPN connection (TCP)

~$ cat /etc/resolv.conf

Appended by NordPy

nameserver 103.86.96.100 nameserver 103.86.99.100 domain hotspot.ec.europa.eu search hotspot.ec.europa.eu

~$ sudo iptables --list Chain INPUT (policy DROP) target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT all -- 172.17.192.0/18 anywhere
ACCEPT tcp -- 5.180.62.93 anywhere tcp spt:https ACCEPT all -- anywhere anywhere

Chain FORWARD (policy ACCEPT) target prot opt source destination

Chain OUTPUT (policy DROP) target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere 172.17.192.0/18
ACCEPT tcp -- anywhere 5.180.62.93 tcp dpt:https ACCEPT all -- anywhere anywhere

Warning: iptables-legacy tables present, use iptables-legacy to see them

~$ sudo iptables-legacy --list Chain INPUT (policy ACCEPT) target prot opt source destination

Chain FORWARD (policy ACCEPT) target prot opt source destination

Chain OUTPUT (policy ACCEPT) target prot opt source destination

larry77 commented 4 years ago

I cannot reproduce the issue easily. It appears that part of the problem was my closing the app instead of properly disconnecting. I will post more when (if) this becomes fully reproducible on my system.

morpheusthewhite commented 4 years ago

Closing the application should not cause any problems since all needed information are stored in files

larry77 commented 4 years ago

Hello, Again, after losing the connection there was no way I could re-establish it (with or without vpn). Wicd told me I was connected, nordpy said I was not and finally the only way to get back online was a full reboot. Before that I tried disconnecting manually using nordpy's interface and reconnecting and this is what I saw on the console

Turning off killswitch looking for iptables in /home/lorenzo/nordpy-master/stored_iptables Selected a particular country: Germany resulting url: https://nordvpn.com/wp-admin/admin-ajax.php?action=servers_recommendations&filters={%22servers_groups%22:11,%22country_id%22:81} Selected a particular country: Germany resulting url: https://nordvpn.com/wp-admin/admin-ajax.php?action=servers_recommendations&filters={%22servers_groups%22:11,%22country_id%22:81}

but finally I was not able to get back online.

morpheusthewhite commented 4 years ago

@larry77 are you experiencing this problem only when the wifi goes down?

larry77 commented 4 years ago

Hello, I experienced this mostly at work with a wifi connection. The connection used to go down every now and then for a few seconds only.

On Fri, Apr 17, 2020 at 12:40:25AM -0700, morpheusthewhite wrote:

@larry77 are you experiencing this problem only when the wifi goes down?

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/morpheusthewhite/nordpy/issues/26#issuecomment-615094948