This is the eduVPN/Let's Connect! documentation repository. This repository targets administrators and developers. It contains information on how to deploy the VPN software on a server, but also (technical) details about the implementation needed to (better) integrate it in existing infrastructure, and how to modify the software for one's own needs.
For more information see:
NOTE: if you are an end-user of eduVPN and want to contact someone, please try to find the contact information of your organization here. If you don't know where to go, then simply contact us at firstname.lastname@example.org.
This is an (incomplete) list of features of the VPN software:
See Client Compatibility for more information about the supported OpenVPN clients.
NOTE: if you plan to install and run a eduVPN/Let's Connect! server please subscribe to the "deployers" mailing list here. It will be used for announcements of updates and discussion about running eduVPN/Let's Connect!.
You can also join IRC for technical questions/discussions/feedback on
#eduvpn. Please stick around for
a while to wait for a response!
You can also easily use the Web Chat if you can't be bothered to setup an IRC client. See you there!
Currently we do NOT support CentOS & Red Hat Enterprise Linux 8. We are waiting for this to be resolved. We avoid using third party PHP repositories to prevent having to support these repositories in the future.
NOTE: we expect ALL software updates to be installed and the server rebooted before you install the software!
NOTE: if you want to deploy on multiple machines for load balancing, please follow these instructions!
aarch64) (Only available through the "development" repository)
You can use the
aarch64 packages on e.g. the Raspberry Pi.
If you want to set up your own server development environment see DEVELOPMENT_SETUP.
This work (this documentation repository) is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
The VPN server software is licensed under the AGPLv3+.
If you find a security problem in the code, the deployed service(s) and want to
report it responsibly, contact email@example.com.
You can use PGP. My key is
0x9C5EDD645A571EB2. The full fingerprint is
6237 BAF1 418A 907D AA98 EAA7 9C5E DD64 5A57 1EB2.