Replies: 1 comment
-
tun2socks -> localhost cause loop hole, which stop 127.0.0.1 socks server to functioning. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to send all traffic to localhost using tun2socks, then use stunnel to connect to remote server. my stunnel config is:
[squid]
client = yes
cert = stunnel.pem
accept = 127.0.0.1:1080
connect = xx.xx.xx.xx:8888
Then I try to setup my tun as:
sudo tun2socks -device utun123 -proxy 127.0.0.1:1080 -interface en0
sudo ifconfig utun123 198.18.0.1 198.18.0.1 up
sudo route add -net 1.0.0.0/8 198.18.0.1
sudo route add -net 2.0.0.0/7 198.18.0.1
sudo route add -net 4.0.0.0/6 198.18.0.1
sudo route add -net 8.0.0.0/5 198.18.0.1
sudo route add -net 16.0.0.0/4 198.18.0.1
sudo route add -net 32.0.0.0/3 198.18.0.1
sudo route add -net 64.0.0.0/2 198.18.0.1
sudo route add -net 128.0.0.0/1 198.18.0.1
sudo route add -net 198.18.0.0/15 198.18.0.1
but all DNS calls and tcp calls are connection refused.
Beta Was this translation helpful? Give feedback.
All reactions