logoalt Hacker News

gonzalohmyesterday at 6:31 PM4 repliesview on HN

Or just use wireguard directly. I get it that it's a pain in the ass to configure it, but there are plenty of open source config generators


Replies

bradfitzyesterday at 6:34 PM

(Author here)

WireGuard doesn't do NAT traversal. That's the main thing this adds. And this also adds a CLI tool + library to do streams over WireGuard w/o installing kernel routings, requiring root, etc.

fodkodraszyesterday at 9:04 PM

IPSec may be a pain... but WireGuard is as simple as it gets in my opinion. Yeah, you may need to know basic IP concepts, like MTU...

NAT traversal is a different topic, WG won't help in that, and that can actually be a pain. I guess we should be using IPv6 already, and this tool would be largely redundant already. (not completely, encrypted access to isolated networks is a valid use case)

show 1 reply
zikduruqeyesterday at 7:51 PM

> it's a pain in the ass to configure it

Public/private key pairs are hard? It's no more terrible than other projects that require configs.

show 1 reply
mystifyingpoiyesterday at 6:43 PM

> pain in the ass to configure it

Idk? I found it pretty easy to configure by blindly following the tutorials and copy-pasting keys. The only footgun is the keepalive setting, which will screw up the tunnel if one end is behind NAT, that tripped me hard, but besides this, no issues at all.