-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Gen4 Network #45
Comments
Thanks for the heads up, stobiewan. I'll have to do some research on what the "nextgen" configuration looks like and if it's still possible to use PIA via network-manager |
I made a Bash-script that updates the PIA configuration files to Gen4. |
In addition to Saltani's nice script, I found this page that links to an "official" manual connection set up script: https://www.privateinternetaccess.com/helpdesk/kb/articles/manual-connection-and-port-forwarding-scripts Might be a bit before I can update pypia to work with the "nextgen" networks, so perhaps people can use Saltani's script or this one in the mean time. |
@Saltani - FYI, you may want to update you instructions to have the user first install using pypia and then run your script as I found an issue on a new server where the certificates were not deployed with your script causing to VPN connections to fail. |
I have updated the script so it should no longer be nessesary to install PyPia for the VPN to work. Note however, that it has only been testet on my Fedora 33 laptop. It worked well during my own testing but there are no guarantees. Use it at your own risk!. |
@Saltani - New version works well with just a small tweak needed. I made a note on your gist. |
@JavaScriptDude - I have (hopefully) fixed the bug and replied to your note. |
PIA are upgrading their network and the majority of servers no longer work with pypia, especially initialise doesn't work. See https://www.privateinternetaccess.com/helpdesk/news/posts/decommissioning-of-legacy-network. I think the generation of network manager files needs to be updated to support nextgen.
The text was updated successfully, but these errors were encountered: