@miek
as in something like
```
ssh -v -CqND 8081 192.168.2.3
```
to set up a listening port ( :8081 ) on local machine that would tunnel traffic to 192.168.2.3
```
curl --socks5 localhost:8081 http://localhost:9100/metrics
```
and then use the tunnel ( localhost:8081 ) to connect to remote server ( 192.168.2.3 ) and access a localhost only webserver
@bradbeam ah. Yes. But i control the client too, so I can just make it talk ssh too.
@miek establish the ssh connection first and the tunnel the http traffic through it via SOCKS_PROXY env var