I’m sure there’s a post about this already, but I don’t really know how to search for it to find the answer, so I apologize in advance for that.
I have some self hosted services in 2 separate houses that are 2 hours away from each other. I use tailscale to access them on my devices, but I’ve experienced some nuances with Tailscale that would be impossible to walk other members of the two households through trouble shooting.
I want to avoid port forwarding if I can.
There are docker services at house A at 192.168.86.5 that I would like the users of house B at 192.168.4.x to be able to access without extra software being added to each phone, TV, and computer.
Would anyone be able to point me in the right direction, either by search keywords or even links to how to do this?
You must log in or register to comment.
What you’re looking for is called vpn. Get a couple routers that support IPsec vpn. You can even build your own.
zerotier may be an option really easy on the user end. Not easy to self host though, but free for the normal version.
best solution. very easy to self host in docker.
You may want to look into running your own router at both sites, then you can iniate a link between them via a tunnel/vpn/your pick and they route between the two sites.
If your looking for tutorials, I’d highly recommend haveing a look at some videos from Lawrence Systems on how to set up something like pfsense.
Router is the key!
- install wireguard on both ends, one will be the server other is the client.
- add necessary iptables rules on server and client.
- if you have a router, without gateway route destination network requests to the local wireguard host.
- if you have a router, route destination network requests to local wireguard host.ient in the local network. ( your local wireguard host as gateway)
Doesn’t this require port forwarding? Or does running wg on the router eliminate the need for port forwarding?
I’ve port forwarded in the past with no issues. But in learning more about networking and such, it seems that port forwarding is riskier than it’s worth, and am trying to find best practices to use going forward.
if the Asus router has wireguard server capabilities, you’re in luck.
on house B, port forwarding is not necessary because the router will handle it.
on house A, because pfSense will work as a client port forwarding is not necessary either.
