#Vpn guard minecraft install#
#Vpn guard minecraft code#
#Vpn guard minecraft download#

We need 192.168.0.1 because it will be the target VPN address on the remote DSM, and 192.168.1.0/24 so that we will be able to access other devices on the remote network. This refers to the networks that the local Wireguard client will intercept and encrypt onto the VPN. In the Peer section, note the AllowedIPs. The listen ports are also completely arbitrary just don't create conflicts with existing services. The only restrictions are that it should use a private address scheme and not overlap any of the local or remote networks. I'm arbitrarily picking 192.168.0.0/24 as the VPN network. Use the PublicKey that you saved from the first step for the Peer. The section refers to the local device, and the is the remote device. Note that I call the tunnel 'remote' because that is what makes sense in the UI (I'm connecting to the remote site) but the keys are for the local client and network. Then delete the tunnel and create another one. Write down these two keys, which will be for the remote DSM server.

#Vpn guard minecraft download#

The networks are each connected to consumer Internet (dynamic IP) services using port-forwarding capable firewallsįirst, download the Wireguard client for your client device (Windows, Mac etc)Ĭreate a new tunnel, which will compute a Public/Private key combination. While it could work in this case, the Synology implementation cannot be used for more sophisticated or esoteric configurations.

#Vpn guard minecraft code#

I'm not a fan of OpenVPN because the code on Synology is quite old, the configuration is unwieldy, and the interface is dumbed down to the simplest configurations.

#Vpn guard minecraft install#

Typically, we would install OpenVPN Server from Package Center for this. So here are two example use cases where I've been able to make Wireguard work on DSM, exactly as desired, using this dockerfile - they might be of interest to you.Ĭase #1: Remote access to a LAN behind a firewall (which includes a DSM server) This is a simple and quick configuration. Then you install the public key from node A on node B, and vice-versa. Each node of the VPN generates a private key, from which it then computes a public key. The basis of Wireguard is public/private key exchange. So it takes some doing to make Wireguard work beyond the most basic implementations. This isn't as fast as a kernel implementation, but it provides the basis to make Wireguard work on DSM! Unfortunately the documentation and configuration examples are incredibly sparse, and Wireguard is positioned as a microservice whereas OpenVPN artificially embeds routing services (push commands). Unfortunately, it's not an option for DSM, even with Docker, because it requires the Wireguard kernel-mode extensions compiled into the kernel (which we can't easily do).Įnter an obscure docker module 'masipcat/wireguard-go', compiled by an MIT researcher with a userspace (non-kernel) implementation interfacing to the /dev/net/tun device.

It's so innovative that Linus Torvalds has cleared it for direct inclusion into the upcoming Linux kernel 5.6. It's nothing short of amazing and very fast. Unless you've been hiding under a rock, you will probably have heard about Wireguard - an emerging alternative to OpenVPN for quick, simple and secure VPN access.