[portsup]

What sort of issues are there with it or is it basically all good?

I am using PIA and a r7000.

[egc]

I have been using it for some time and it works without any problem, I Use commercial providers (KeepSolid and Azire) and host my own WG server to connect with Android phones and windows clients.

Speed is over three times OpenVPN.

Unfortunately PIA does not support it (yet?) on the router.

Drawback when using a commercial WG provider you use a static IP so are more "traceable" (some provider are hiding this by creating an extra NAT layer)

So if privacy is a major concern stick with OpenVPN otherwise WG is fine.

See my signature for some links

[portsup]

Do you mean you can't change internal or external IP at all? I would guess the PIA system works the same as their port forward, when you ask for a new access token that also gives you new IPs like it does a port.

PIA seems to be supporting WG on other devices now. They have just released some scripts for port forwarding and connecting with WG on linux devices and ddwrt in particular. I can't say I could make them work for the port forwarding when I tried earlier, but I could probably now as I was missing some binaries.

[egc]

You get a fixed ip address from your provider so they know your ip address.

Openvpn will get you a dynamic ip address

[eibgrad]

Caveat emptor.

What makes WG different is that unlike OpenVPN and most other VPNs that run in user-space, it runs in the *kernel*, giving it a significant speed advantage (place OpenVPN in the kernel and you'd see similar performance improvements). But that's a double-edged sword. It also means that if there are unknown vulnerabilities, it has the *potential* to lead (at least in the worst case) to remote code execution!

It's also simpler because it eliminates certain functionality, like bridged tunnels. But ironically, bridged tunnels are actually simpler to implement, at least when dealing w/ your own VPN server. It's all the routing and firewall issues w/ routed VPN tunnels that cause the headaches. And I suspect w/ time, feature-creep will set in and it will become as bloated and complex as every other VPN.

Basically, WG is being given *privileged* status in Linux. Why, I don't know. As I said, OpenVPN (and any other VPNs) could benefit similarly from such privileged status. But you usually don't do this because of the risk of opening the kernel to corruption.

I'm NOT saying don't use it. But you need to be aware that in the real-world, WG is far from proven. Given the small user base so far (at least compared to something like OpenVPN), it's currently not much of a target, and whether it's free of such vulnerabilities remains an open question. Only time will tell. Anyone using it today should consider themselves an early adopter, and all that implies.

[portsup]

It is given privileged status because like most things kernal Linus took to liking it. It is coded very well and small, things most will appreciate.

I dont see any reason in theory you cant change ip. Even if you have static routes setup they could implement a system to change them.

[portsup]

From what I have seen now I have made a wireguard connection
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=330429&start=15
pia gives you a new internal ip when you generate a new connection. The external ip must be shared.

[kernel-panic69]

I still cannot believe someone over at FreshTomato even thought porting WG to Linux 2.6 was a good idea. Definitely not, IMHO. And it's not even being maintained. Sorry, my Tourette's almost kicked in.

[portsup]

Thats an old kernel. You never know what obscure hardware it's running on. I might be something military or nasa and they now want the power of wireguard lol

[kernel-panic69]

I guess the words "FreshTomato" (firmware) just got completely ignored or glazed over. Most WiFi5 router stock firmwares use a Linux 2.6 kernel. There's a lot of things that still use, or did use a Linux 2.6 kernel until recently.

[the-joker]

On other news and while I stumbled on this post.

Just today a wireguard patch went in, this was authored by egc

https://github.com/mirror/dd-wrt/pull/76 for information on what it addresses.

respective merge upstream https://svn.dd-wrt.com/changeset/47602 and follow up commits.

up to and including https://svn.dd-wrt.com/changeset/47605

have a nice one, be well.

[portsup]

interesting thanks