WireGuard Bounce Server Setup
gitlab.com
WireGuard Bounce Server Setup
1–10 of 80 posts
Re: WireGuard Bounce Server Setup
#2Seems like a good tutorial. I've been using this type of set up for about 6 months now and it works well for me. I wish I had a straight forward explanation like this when I was first learning how to use WireGuard.
Re: WireGuard Bounce Server Setup
#3I must be missing something. Why go through all of this when you can just buy a domain name, setup dynamic dns on the natted network (to keep the IP updated), and then setup wireguard to route to the domain name? If you have two different networks then just use two different domains or subdomains.
Re: WireGuard Bounce Server Setup
#4I was hoping this was some kind of stun mechanism for wireguard. No, it's just setting up a cheap wireguard server on AWS.
Anyone have anything like an introduction server to help wg peers behind nat find each other?
Re: WireGuard Bounce Server Setup
#5I must be missing something. Why go through all of this when you can just buy a domain name, setup dynamic dns on the natted network (to keep the IP updated), and then setup wireguard to route to the domain name? If you have two different networks then just use two different domains or subdomains.
(Author here, AMA.)
If that does what you need, then it is a reasonable alternative. I would prefer the shorter routing you get. But if one of your NATs is corporate, a phone carrier, it might not work.
If you might want to provide other services, particularly a remote exit node or web service, the bounce node is a good start on that.
Re: WireGuard Bounce Server Setup
#6I was hoping this was some kind of stun mechanism for wireguard. No, it's just setting up a cheap wireguard server on AWS. Anyone have anything like an introduction server to help wg peers behind nat find each other?
That’s kinda what Tailscale does, amongst other things.
Re: WireGuard Bounce Server Setup
#7I must be missing something. Why go through all of this when you can just buy a domain name, setup dynamic dns on the natted network (to keep the IP updated), and then setup wireguard to route to the domain name? If you have two different networks then just use two different domains or subdomains.
Would that setup punch trough the nat tho?
Re: WireGuard Bounce Server Setup
#8Seems like a good tutorial. I've been using this type of set up for about 6 months now and it works well for me. I wish I had a straight forward explanation like this when I was first learning how to use WireGuard.
Same! I set up something similar with DigitalOcean by combining a couple of tutorials together. I pretty much followed the same steps until the `nftables` stuff.
Re: WireGuard Bounce Server Setup
#9I was hoping this was some kind of stun mechanism for wireguard. No, it's just setting up a cheap wireguard server on AWS. Anyone have anything like an introduction server to help wg peers behind nat find each other?
That’s kinda what Tailscale does, amongst other things.
Yup, it's definitely one of the things Tailscale does.
Not an intro or tutorial, but I've not found a better write-up than on their blog:
https://tailscale.com/blog/how-nat-traversal-works/
(personally, I'd just do what the author did... it's a ton less work to setup and maintain)
Re: WireGuard Bounce Server Setup
#10I must be missing something. Why go through all of this when you can just buy a domain name, setup dynamic dns on the natted network (to keep the IP updated), and then setup wireguard to route to the domain name? If you have two different networks then just use two different domains or subdomains.
OPs method would allow for remoting into your home network without port forwarding, since home network would establish a connection to the 'bounce' node, which would facilitate communication between the 3rd WG client