3 ms·
Almost every problem I've seen someone have with WireGuard comes down to one of two things: 1. They misunderstand what AllowedIPs actually does 2. They don't
by LambdaComplex 5y ago
Almost every problem I've seen someone have with WireGuard comes down to one of two things:
1. They misunderstand what AllowedIPs actually does
2. They don't understand networking.
WireGuard is _incredibly_ simple. Not easy. Simple. You configure your peering on each side, and what you end up with is--as far as userspace can tell--a perfectly normal layer 3 interface. You are then free to configure your firewall rules and route tables however you like in order to achieve your goals.
If you understand networking (and how to perform network configuration on Linux), then this is a powerful tool.
If you don't understand networking, then you end up writing posts like this.
- nvr219 5y agoThanks for feedback. Yes - I don't understand networking, and OpenVPN works for me, so it wins... That's all I can say. I will update my post to clarify that I also don't understand networking.
- sam_dal 5y agoTry https://tailscale.com/ https://tailscale.com/ implementation of wireguard if you are a noob.
- nvr219 5y agoNice one! Thanks.
- mobilio 5y agoHere is probably BEST explanation of WireGuard parameters: https://stackoverflow.com/questions/65444747/what-is-the-difference-between-endpoint-and-allowedips-fields-in-wireguard-confi https://stackoverflow.com/questions/65444747/what-is-the-dif...