Vicio59

> You are having a dead loop, you need to bypass 192.168.0.4, so that it will not go through hev-socks5-tunnel's tun interface. Hi, thanks for your help, I replaced the...

Sorry, I closed inadvertently, unfortunately I still can't use this script.

sudo docker run --name curl --network=container:tun2socks5 curlimages/curl -v 1.1.1.1 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0...

What could it be? It's the first time I've had a problem with tun2socks, it doesn't seem to work only with Google Cloud VPS, thanks

In what sense? if I run ifconfig inside the tun2socks container the only interfaces I see are: eth0, lo and tun0. Do you mean if I manually bound the container...

Do you mean if I tested my proxy by running curl inside the tun2socks container? No, I couldn't do it because curl is not installed inside the tun2socks container, I...

Ok, I managed to install curl on the tun2socks container but previously it still didn't work even with curl 1.1.1.1. After playing with the ip rule and ip route rules...

ok, I tried with: / # curl -v 1.1.1.1 --proxy socks5://MYUSER:MYPASS@SERVERIP:PORT --interface eth0 * Trying SERVERIP:PORT... * socket successfully bound to interface 'eth0' After which it stops like this, while...