3 ms·
https://github.com/noisysockets/noisysockets https://github.com/noisysockets/noisysockets With that, you can replace a Dialer in Go that connects sockets, effe
by eclark 3y ago
https://github.com/noisysockets/noisysockets https://github.com/noisysockets/noisysockets
With that, you can replace a Dialer in Go that connects sockets, effectively wrapping sockets with Wireguard. Since it does that in userspace, you get no tun/tap. This is all open-sourced by @dpeckett
With those things, he also built a userspace wireguard gateway that includes DNS resolution. https://github.com/noisysockets/gateway https://github.com/noisysockets/gateway
https://news.ycombinator.com/user?id=dpeckett https://news.ycombinator.com/user?id=dpeckett
- ignoramous 3y agoUpstream WireGuard (golang) has had this capability for a few years now: https://github.com/WireGuard/wireguard-go/tree/master/tun/netstack/examples https://github.com/WireGuard/wireguard-go/tree/master/tun/ne...
- dpeckett 3y agoYep noisysockets is based originally off wireguard-go but is an attempt to simplify and make things a lot more idiomatic for library use. Filling in the gaps etc and improving the ergonomics. Hoping to build a bit of an ecosystem of supporting projects around it, eg. I'm currently working on a STUN server implementation based on the approach described in https://nordsecurity.com/blog/reaching-beyond-1gbps https://nordsecurity.com/blog/reaching-beyond-1gbps One of the recent feature divergences from upstream is support for network exit nodes / gateways.