5 ms·

What's your recommended wireguard setup?

CharlesW 5y ago
As a happy user, I can highly recommend trying Tailscale. https://tailscale.com/kb/1086/tailscale-vs-wireguard/ https://tailscale.com/kb/1086/tailscale-vs-wireguard/
kube-system 5y ago
Vanilla WireGuard is not hard to use at all, it's by far the easiest to configure VPN software. Some routers have it built in, and some have packages to install it, and the official GUI clients work well: https://www.wireguard.com/install/ https://www.wireguard.com/install/ If you can't run it on your router, you can just set it up on a linux VM and forward a port as necessary. The configuration file is quite simple once you get the hang of it, you've basically just got: 1. a public/private key that you exchange between connected machines 2. the address of the tunnel, locally 3. the address/port to get to the other end 4. what traffic you want to send over the tunnel
- daemoens 5y ago
  An easier method is to just use PiVPN https://www.pivpn.io https://www.pivpn.io. It's much faster to setup and easier to manage with extremely simple commands.
  - kube-system 5y ago
    I've looked at PiVPN, but it looks like more work than many of the packages available for routers. e.g. dd-wrt, pfsense, opnsense all have point-and-click configuration pages.
    - EricE 5y ago
      Not at all. Maybe three terminal commands tops to configure and add a user for yourself. Once the text config file is generated just import it on your client and you are done. As long as you have forwarded the appropriate port through your firewall that's literally all it is to it. Of course if you have a firewall with it built in, then use that. However for pfSense and OpnSense wireguard runs in user mode and not the kernel, so depending on your traffic the pi may be faster since wireguard is compiled into the kernel with piVPN. Which can cause fun issues if there is a kernel update you aren't prepared for - was my only real problem with piVPN/Wireguard but it wasn't too hard to recover once I figured out what was going on :)
    - artificialLimbs 5y ago
      I'm not sure how this is possible. With pivpn: install pivpn, open router port & forward (automatically configured and optionally changed during setup), type 'pivpn add' at the command line for every device I want. Copy the outputted config files to device and import into wg client. Done.
- viraptor 5y ago
  ZeroTier is even easier. 1. Install the package, 2. zerotier-cli join (your network id), 3. Flip the new node state to enabled in the control panel. No other config need unless you want specific network config/filters.
1MachineElf 5y ago
You might want to look into Tailscale if you're just starting out. Configure a small VM to act as a Tailscale subnet router for whatever network your macOS VMs are on, after which you will be ready to access them remotely from the coffee shop. If you prefer to have access to ESXi from a separate VLAN/network, then get the Pro plan and setup a 2nd subnet router for your hypervisor, NAS, etc.
artificialLimbs 5y ago
1.) Install wireguard. 2.) Install pivpn. 3.) (Optional) Modify makeCONF.sh/removeCONF.sh if needed.

As a happy user, I can highly recommend trying Tailscale. https://tailscale.com/kb/1086/tailscale-vs-wireguard/ https://tailscale.com/kb/1086/tailscale-vs-wireguard/

kube-system 5y ago

Vanilla WireGuard is not hard to use at all, it's by far the easiest to configure VPN software. Some routers have it built in, and some have packages to install it, and the official GUI clients work well: https://www.wireguard.com/install/ https://www.wireguard.com/install/ If you can't run it on your router, you can just set it up on a linux VM and forward a port as necessary. The configuration file is quite simple once you get the hang of it, you've basically just got: 1. a public/private key that you exchange between connected machines 2. the address of the tunnel, locally 3. the address/port to get to the other end 4. what traffic you want to send over the tunnel

daemoens 5y ago
An easier method is to just use PiVPN https://www.pivpn.io https://www.pivpn.io. It's much faster to setup and easier to manage with extremely simple commands.
- kube-system 5y ago
  I've looked at PiVPN, but it looks like more work than many of the packages available for routers. e.g. dd-wrt, pfsense, opnsense all have point-and-click configuration pages.
  - EricE 5y ago
    Not at all. Maybe three terminal commands tops to configure and add a user for yourself. Once the text config file is generated just import it on your client and you are done. As long as you have forwarded the appropriate port through your firewall that's literally all it is to it. Of course if you have a firewall with it built in, then use that. However for pfSense and OpnSense wireguard runs in user mode and not the kernel, so depending on your traffic the pi may be faster since wireguard is compiled into the kernel with piVPN. Which can cause fun issues if there is a kernel update you aren't prepared for - was my only real problem with piVPN/Wireguard but it wasn't too hard to recover once I figured out what was going on :)
  - artificialLimbs 5y ago
    I'm not sure how this is possible. With pivpn: install pivpn, open router port & forward (automatically configured and optionally changed during setup), type 'pivpn add' at the command line for every device I want. Copy the outputted config files to device and import into wg client. Done.
viraptor 5y ago
ZeroTier is even easier. 1. Install the package, 2. zerotier-cli join (your network id), 3. Flip the new node state to enabled in the control panel. No other config need unless you want specific network config/filters.

1MachineElf 5y ago

You might want to look into Tailscale if you're just starting out. Configure a small VM to act as a Tailscale subnet router for whatever network your macOS VMs are on, after which you will be ready to access them remotely from the coffee shop. If you prefer to have access to ESXi from a separate VLAN/network, then get the Pro plan and setup a 2nd subnet router for your hypervisor, NAS, etc.

artificialLimbs 5y ago

1.) Install wireguard. 2.) Install pivpn. 3.) (Optional) Modify makeCONF.sh/removeCONF.sh if needed.