3 ms·
If you want to document "How I access my home network remotely" but you're really spending a few paragraphs repeating the wireguard docs before moving on to oth
by harshreality 8y ago
If you want to document "How I access my home network remotely" but you're really spending a few paragraphs repeating the wireguard docs before moving on to other things like your choice of IPs, your logging setup, how to retrieve mail, how to ssh places, and stuff like that, please realize that none of that other stuff has anything to do with wireguard. You could just as easily be documenting those things with an OpenVPN or IPsec vpn or even an unencrypted tunnel. That's why those things are not in the wireguard docs.
If there's something that involves wireguard itself that's missing from or unclear in the docs, could you please clarify?
- StavrosK 8y ago> none of that other stuff has anything to do with wireguard Sure, none of it is specific to Wireguard, but my personal use case was "hey, Wireguard looks cool, maybe I could use it to access my home LAN when I'm away. Hmm, how do I talk to the other machines from the VPN server?". It's like saying "if you want to bake a cake, none of the baking has anything to do with our flour". You're technically right, but it'll benefit you to put a recipe on the box.
- harshreality 8y ago"How do I talk to the other machines from the vpn server" The same way you would if everything on your side of the VPN tunnel was on the other side of the VPN tunnel, there was no VPN, and the VPN server was just a router joining the two subnets.
- StavrosK 8y ago"I don't know how to do that, oh well, too bad, Wireguard would have been nice"