With Wireguard hitting 1.0 and becoming part of the Linux 5.6+ kernel, I'd like to request Wireguard be added in addition or in place of OpenVPN. Mostly for its decreased overhead on CPU limited hosts.
I like it. Just saw the release myself. I've read a couple of blogs about this along the way as it has seemed relevant to this project and you know, just linux computing in general.
I don't have a complete overview on what that would mean for this project though. I can read up, but if you have some knowledge I'm all ears.
The providers have to support it and it's a separate set of configs I guess? Or is there some interoperability here (sounds too good to be true).
Hi, I'm also using Wireguard.
As you've pointed out, the VPN provider have to support it because the config file is completely different, it's a conf file with just something like this
[Interface]
PrivateKey = ....
Address = ....
DNS = ....
[Peer]
PublicKey = ....
PresharedKey = ....
Endpoint = ....
AllowedIPs = ....
PersistentKeepalive = ....
PIA supports it but has not provided any guidance on setting it up outside of their official clients. https://www.privateinternetaccess.com/forum/discussion/38293/wireguard-on-linux
Indeed, PIA's client has option to use the WireGuard protocol.
Not seen similar update yet for the likes of ExpressVPN client, VPNunlimited client, nor external clients.
Looks like NordVPN is officially supporting WireGuard natively now: https://nordvpn.com/blog/one-very-strong-reason-to-be-excited-about-nordlynx/
PrivateVPN are doing testing currently
Mullvad is also supporting and advising Wireguard:
https://mullvad.net/en/help/tag/wireguard/
Torguard also supports Wireguard, and the speed difference is significant. An option to use Wireguard instead of OpenVPN would be awesome.
vpnunlimited also supports wireguard with config file option
FYI VPN.ac also support Wireguard since March last year: https://vpn.ac/knowledgebase/120/WireGuard-Status.html
Windscribe also support WireGuard.
I too would like to see this docker start using wireguard. I've looked into this, and I found some scripts that will do the connection and get the tokens for wireguard to connect. I hope these scripts will come in handy, really looking forward to using wireguard in this docker!
PIA:
https://gist.github.com/triffid/da48f3c99f1ff334571ae49be80d591b
https://serverlist.piaservers.net/vpninfo/servers/new
Cheers, and thanks for the great work!
That's fantastic work @PaulR1978. @haugene I'd be happy to lend a hand on implementation.
There are a few wireguard docker containers which might be a good guidance how wireguard could be configured in a docker context, i.e. https://hub.docker.com/r/linuxserver/wireguard
Great stuff 馃憤 Thanks for posting, I think these links will be great during implementation!
I'm really looking forward to implementing this and would love some assistance @mattstrayer.
As for the timeline. I think it will still be postponed a few weeks, but we should get this in during the autumn.
There are two reasons I want to wait just a little. One of them is that I live in the North (Oslo) and we're probably getting the last wave of warm weather these days. So it's a bit selfish, but the rain and cold is coming and then there will be more time for coding then. Unnecessary sacrifice of points with the gf to insist on locking myself in my room in the sun.
But, secondly and more important. We are doing a rewrite of the project structure now. That work has begun on the dev branch and I have another feature branch in the works. The idea is to make the project more modularised so that everything isn't such a "lump" as it is today. The scripts have just grown with new features and now is the time to extract some of the functionality and handle it more generally. At the end of this I also think that the separation between openvpn and transmission will be clearer, so it would be easier to swap the startup from openvpn to wireguard.
Once I have merged the next big feature branch I will create a feature branch for wireguard, and then I'm happy to accept and play with any PRs to see how we can build this. But I think there will be many merge conflicts if we start before that. Anyways, let's aim for having Wireguard a part of the 3.0 release of the image 馃槃
Awesome !!! :medal_sports:
Hi Guys,
Me again, Looks like PIA put out scripts as of a couple days ago. Should really help with implementing wireguard into this Docker.
Scripts are at https://github.com/pia-foss/manual-connections
That's fantastic news, thanks for sharing @PaulR1978 !
Excuse my ignorance, I'm still not 100% sure how GitHub works.
So, I need to run Mullvad Wireguard to bypass Virgin Media VPN throttling here in the UK.
So is it as simple as changing the "-e "OPENVPN_CONFIG= " to a different config name?
If so, where can I find the wire guard config names?
@b055k060644 wireguard is not added yet. this is a feature request discussion
Here is another github project for a docker that allows you to run transmission over wireguard: https://github.com/SebDanielsson/docker-wireguard-transmission
I must admit that I much prefer this project due to all the additional configuration of transmission it allows, but the other project might be good inspiration for how to go about adding wireguard support to this container.
VPNUnlimited also supports it. +1 for feature request.
VPNUnlimited also supports it. +1 for feature request.
already mentioned
Hello @haugene no rush please take your time but any update on this, is there any beta tag :) Thanks
The focus is on bug fixing right now for the 3.x release. Next up is separating provider configs from the main repo so they can be updated independently.
Most helpful comment
Great stuff 馃憤 Thanks for posting, I think these links will be great during implementation!
I'm really looking forward to implementing this and would love some assistance @mattstrayer.
As for the timeline. I think it will still be postponed a few weeks, but we should get this in during the autumn.
There are two reasons I want to wait just a little. One of them is that I live in the North (Oslo) and we're probably getting the last wave of warm weather these days. So it's a bit selfish, but the rain and cold is coming and then there will be more time for coding then. Unnecessary sacrifice of points with the gf to insist on locking myself in my room in the sun.
But, secondly and more important. We are doing a rewrite of the project structure now. That work has begun on the dev branch and I have another feature branch in the works. The idea is to make the project more modularised so that everything isn't such a "lump" as it is today. The scripts have just grown with new features and now is the time to extract some of the functionality and handle it more generally. At the end of this I also think that the separation between openvpn and transmission will be clearer, so it would be easier to swap the startup from openvpn to wireguard.
Once I have merged the next big feature branch I will create a feature branch for wireguard, and then I'm happy to accept and play with any PRs to see how we can build this. But I think there will be many merge conflicts if we start before that. Anyways, let's aim for having Wireguard a part of the 3.0 release of the image 馃槃