Live data from Hacker News

A userspace WireGuard client that exposes itself as a proxy

github.com

11–20 of 91 posts

Re: A userspace WireGuard client that exposes itself as a proxy

#11

Earlier quoted context omitted.

"things" ?

Things. I have tailscale running on a lot of devices. Servers, workstations, raspberry pi, various other appliances, SFPs.

You are running tailscale on an SFP???

Re: A userspace WireGuard client that exposes itself as a proxy

#14

Why wouldn’t you just run ssh -D to the remote machine? The effect is the same and you don’t need wire guard or wire proxy.

Presumably you'd use it on a machine that doesn't expose SSH. That said, I really like sshuttle for this use case when SSH is available.

Re: A userspace WireGuard client that exposes itself as a proxy

#15

Excellent. I've been wanting something like this for a while to use with Mullvad, but had to resort to docker containers instead. This plays well with proxychains to make proxy-naive programs use SOCKS5 proxies.

Mullvad exposes socks proxies over wireguard.

Re: A userspace WireGuard client that exposes itself as a proxy

#16

Why wouldn’t you just run ssh -D to the remote machine? The effect is the same and you don’t need wire guard or wire proxy.

I made it because my friends and I use wireguard to have a private network, and they don't feel comfortable running a ssh server on their machines. It can also be used with a vpn provider like Mullvad without setting up a new nic or requiring special privs.

Re: A userspace WireGuard client that exposes itself as a proxy

#17

Earlier quoted context omitted.

Things. I have tailscale running on a lot of devices. Servers, workstations, raspberry pi, various other appliances, SFPs.

You are running tailscale on an SFP???

I had to look it up: https://en.m.wikipedia.org/wiki/Small_form-factor_pluggable_...

Re: A userspace WireGuard client that exposes itself as a proxy

#18

Why wouldn’t you just run ssh -D to the remote machine? The effect is the same and you don’t need wire guard or wire proxy.

One simple reason is that the serverside might not want to expose a shell to its clients, and instead just provide network connectivity; you can configure something like that with SSH, but it's a pain, and WireGuard is approximately as simple to set up as SSH, which is the primary reason it's so popular.
Post reply on HN