Repository navigation
Proxies other way around #175
Description
I have usecase where my wireguard peer (running wireproxy) is the one which can connect to some hosts.
I would like to allow connections from peers inside wg network to connect to other hosts (mainly http/https on this case) via wireproxy.
So, consider this as feature request where I would like to see SOCKS5 and/or HTTP proxy published to wg network, routing traffic to outside network via wireproxy.
Anyways, thanks for creating wireproxy, it is a great tool!
Activity
supernovaw commentedon May 28, 2025
Hi @savikko,
If I understand what you said correctly, this is already a feature. Use
[TCPServerTunnel]to specify the port on which the WG peer should be listening (ListenPort) and the destination host (Target). This exposes TCP sockets that would otherwise only be accessible to the machine running wireproxy to the rest of your WG VPN.Also, in this scenario, the initial connection is incoming, which means it will fail unless wireproxy begins by sending some packet(s) to the WG server to establish a connection to the WG server. You would want to use
PersistentKeepalivein your[Peer]section to ensure an outgoing packet is always sent first and the WG server can send you data back when somebody connects.