trying to pipe my remote node connections through a local ssh tunnel loopback (127.0.0.1) but running into routing issues. using the tool because its background network stack handles socket isolation really well when running multiple client sessions concurrently. the problem is the second i bind the traffic to a local port, the inner proxy engine drops the connection and fails to resolve the host headers. do i need to force a socks5 fallback in the DNS resolution settings or change the path to bind with the local daemon properly?   submitted by   /u/Howard_Mildred [link]   [comments]