Package Details: private-internet-access-vpn 3.4-3

Git Clone URL: https://aur.archlinux.org/private-internet-access-vpn.git (read-only, click to copy)
Package Base: private-internet-access-vpn
Description: Installs VPN profiles for Private Internet Access Service
Upstream URL: https://www.privateinternetaccess.com/
Keywords: connman networkmanager openvpn python vpn
Licenses: GPL
Conflicts: xawtv
Submitter: flamusdiu
Maintainer: Auerhuhn
Last Packager: Auerhuhn
Votes: 86
Popularity: 0.000008
First Submitted: 2014-08-14 01:22 (UTC)
Last Updated: 2024-04-14 17:12 (UTC)

Pinned Comments

Auerhuhn commented on 2023-10-27 08:23 (UTC) (edited on 2023-10-27 08:23 (UTC) by Auerhuhn)

Note that this package provides only VPN profiles but not the vendor’s software.

The package version refers to the python-pia tool by @flamusdiu, which may lag behind the vendor’s own VPN software version.

Please do not flag this package out-of-date unless @flamusdiu releases a new stable python-pia version.

Thank you!

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 48 Next › Last »

Cavsfan commented on 2017-01-16 15:18 (UTC)

@flamusdio, I'll give that a try and report back. Thank you

flamusdiu commented on 2017-01-16 15:01 (UTC)

@Cavslan: Should be 3.3.1. However in the error you posted, it was showing 3.3b for some reason. I went back and check to make sure that I didn't leave something in the code for the version (I have a bad habit of doing that) but didn't notice anything. Can you remove the package and make sure there isn't a version still installed through pip after removal?

Cavsfan commented on 2017-01-16 14:56 (UTC)

Here's what I get: $ pia --version 3.3 No errors.

flamusdiu commented on 2017-01-16 03:27 (UTC)

@Cavslan: what do you get when you do `pia --version`?

Cavsfan commented on 2017-01-15 19:04 (UTC)

I had ConnMan installed already so I started it and entered "sudo pia -a". These are the errors I got and pretty sure the same as I got before: $ sudo pia -a Traceback (most recent call last): File "/usr/bin/pia", line 11, in <module> load_entry_point('pia==3.3b0', 'console_scripts', 'pia')() File "/usr/lib/python3.6/site-packages/pia/command_line.py", line 23, in main pia.run.run() File "/usr/lib/python3.6/site-packages/pia/run.py", line 53, in run properties.parse_conf_file() File "/usr/lib/python3.6/site-packages/pia/conf/properties.py", line 271, in parse_conf_file props.port = getattr(configure_section, "port", [props.default_port])[0] File "/usr/lib/python3.6/site-packages/pia/conf/properties.py", line 158, in port config = self._config_lookup[self._port_lookup[value]['config']] KeyError: 'UDP/1197' Guess, I'll just stick to OpenVPN for now at least.

bennysdad commented on 2017-01-12 19:45 (UTC) (edited on 2017-01-13 01:05 (UTC) by bennysdad)

Hopefully, this will help someone. I could not connect after the last update and sudo pia -a did not help. Neither did a reboot or systemctl restart NetworkManager. I'm lazy and did not want to manually edit all 36 config files as Cavsfan did, so I waited... I'm not patient either... So, it turns out all I had to do was edit one. When I used the NetworkManager "Configure VPN" on the VPN host I usually use, it was looking for the CA Certificate in the old location. Once I told it the new location is /etc/openvpn/client, all the other hosts magically became available with the correct certificate location too. Could the problem have occurred because I had that VPN host connected when I updated the first time?

flamusdiu commented on 2017-01-11 20:09 (UTC) (edited on 2017-01-11 20:09 (UTC) by flamusdiu)

TUN/TAP is just how VPNs work. Any VPN software will create these interfaces to push traffic through (which then gets the traffic encrypted). Yes, OpenVPN works from the CLI. Only ConnMan and NM will work from a GUI. It's all a matter of pref.

Cavsfan commented on 2017-01-11 19:45 (UTC)

@flamusdio, I see that OpenVPN is designed to work with the TUN/TAP virtual networking interface. I guess I am OK using OpenVPN right? I also see that OpenVPN Allows running configurations from command-line (from above). Which is probably why I have only CLI options.

flamusdiu commented on 2017-01-11 04:06 (UTC)

@Cavsfan: yeah, I run OpenVPN directly for testing but use Connman usually. You can also use nm-cli or connmanctl as well. Plenty of options depending on what your needs are.

Cavsfan commented on 2017-01-10 14:11 (UTC) (edited on 2017-01-10 14:13 (UTC) by Cavsfan)

@flamusdio, as I stated I did run from terminal 'sudo pia -a' and I got some errors. But, it all worked out after I took the steps I mentioned. I'm pretty sure it uses OpenVPN as I see that in the terminal output when connecting but, when I connect and look at Network Manager it says I'm connected with Interface: tun0 and the terminal says "TUN/TAP device tun0 opened". I guess I'm good with the cli connection method.