- [sing-box](https://github.com/SagerNet/sing-box)
- [clash-meta](https://github.com/muink/Clash.Meta) and other clash-based clients
- [xray](https://github.com/xtls/xray-core)
Close-sourced client include [Surge Mac/iOS](https://nssurge.com/).Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
21–30 of 67 posts
Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#22Earlier quoted context omitted.
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).
By vanilla, I mean `ssh -D`, as opposed to anything else that can offer a SOCKS port without actually transporting over ssh (ex. this project). Last time I compared, that was noticeably slower than wireguard, which yeah I attributed to TCP over TCP being kinda awful.
SOCKS existed before SSH did, and there are SOCKS server implementations that don't rely on SSH.
Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#23Nice! I was just thinking it would be sweet to have something like this to proxy all my Thunderbird email connections through my Tailscale exit node, without having to direct all my traffic through the exit node.
Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#24Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#25Earlier quoted context omitted.
By vanilla, I mean `ssh -D`, as opposed to anything else that can offer a SOCKS port without actually transporting over ssh (ex. this project). Last time I compared, that was noticeably slower than wireguard, which yeah I attributed to TCP over TCP being kinda awful.
I'm curious why you refer to 'ssh -D' as 'vanilla SOCKS'? SOCKS existed before SSH did, and there are SOCKS server implementations that don't rely on SSH.
Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#26Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#27Isn't this already easily achievable with ssh? with 'ssh -D[port] foo@somehost' ssh will act as a SOCKS server.
Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#28Isn't this already easily achievable with ssh? with 'ssh -D[port] foo@somehost' ssh will act as a SOCKS server.
That's fine if you control the endpoint and want to expose ssh on it, but WireGuard endpoints are also commonly available from VPN providers who don't provide shell access.
Added to that their official client has heaps of functionality I have no use for, and wireproxy does everything I want for this usecase with a comparatively tiny amount of code(5MB vs 400MB built). I started the evening with a wg-quick generated config that required root, and ended it using a simple unprivileged daemon that I can toggle easily.
Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#29Several multi-protocol proxy clients support this functionality, some notable open-source examples include: - [sing-box](https://github.com/SagerNet/sing-box) - [clash-meta](https://github.com/muink/Clash.Meta) and other clash-based clients - [xray](https://github.com/xtls/xray-core) Close-sourced client include [Surge Mac/iOS]( https://nssurge.com/ ).
Re: Wireproxy: WireGuard client that exposes itself as a HTTP/SOCKS5 proxy
#30Great little tool! I use it to selectively proxy Firefox tabs using multi-account containers to a home router that speaks Wireguard (but no application-layer proxying protocol or SSH).