Live data from Hacker News

Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy

github.com

1–10 of 67 posts

Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy

#4
post #3
post #2

Does it support OpenVPN?

... Um.. what? It's wireguard. It does the wireguard. Are you looking for tunsocks?

tunsocks would work, there also seems to be an openvpn fork with that functionality built in: https://github.com/bendlas/openvpn-tuna

Otherwise you may be able to use SSH's SOCKS proxy mode if you can directly SSH, e.g. ssh -D 3128 user@host .. will listen on port 3128 as a SOCKS proxy.

Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy

#7
How's the performance? My memory is that "vanilla" SOCKS is really easy to do (just run ssh with the right option and tell your application to use it) but really slow. I suspect this is mostly for cases where you don't have a normal SOCKS/ssh server, but I'm curious if it offers a benefit there too.

Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy

#8

Is there completely userspace server implementation? Without tun/tap devices, etc. I guess some kind of userspace IP stack is necessary for that, although not sure.

It's really completely in userspace and doesn't need any kernel modules or even superuser permissions for managing TUN/TAP devices (like e.g. OpenSSH's TUN device mode does)!

It uses a userspace TCP/IP stack by Google, as far as I understand.

Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy

#9

Is there completely userspace server implementation? Without tun/tap devices, etc. I guess some kind of userspace IP stack is necessary for that, although not sure.

Maybe https://github.com/cloudflare/boringtun or https://github.com/WireGuard/wireguard-go ?

Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy

#10

How's the performance? My memory is that "vanilla" SOCKS is really easy to do (just run ssh with the right option and tell your application to use it) but really slow. I suspect this is mostly for cases where you don't have a normal SOCKS/ssh server, but I'm curious if it offers a benefit there too.

What do you mean by "vanilla" SOCKS, i.e. as opposed to what other type of SOCKS implementation?

For me, SOCKS over SSH has always been pretty performant, unlike e.g. OpenSSH's TUN mode (since that ends up doing TCP over TCP).

Post reply on HN