ssh server and tun2socks

[gpahlevanzadeh]

Sorry for open new thread.
I don't know to I can implement my scenario with tun2socks or not.
I have:

root@debian:~# ip a show  enp0s31f6 
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 54:e1:ad:62:7f:b6 brd ff:ff:ff:ff:ff:ff
    altname enx54e1ad627fb6
    inet 192.168.1.103/24 brd 192.168.1.255 scope global dynamic enp0s31f6
       valid_lft 86008sec preferred_lft 86008sec

It's work fine.
Also I have:

root@debian:~# ip route  show table main
default via 192.168.1.254 dev enp0s31f6 
192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.103 

I tunnel between my enp0s31f6 and my ssh server in out my country via:

ssh -CfND 7777 mohsen@out_of_my_country_server -p 2200 -4

When I test it via Firefox it's work fine and socks5.

Now , I need to route all of my traffic to enp0s31f6 .

How can I implement this scenario?

[xjasonlyu]

Hi there!

Hmm, enp0s31f6 is your default device for routing, so all your traffic already goes to this interface now.

Do you mean that you want all your traffic be proxied through the ssh tunnel?

In this case you may need to first make sure the ssh tunnel or your proxy server can correctly bind to a primary interface, and then just 1) locally run e.g. tun2socks --device tun0 --proxy socks5://<ip:port> --interface enp0s31f6 2) config the routing table.

[realyukii]

hello, I have similar setup (client -> tun2socks -> socks5 -> ssh tunnel), it's first time I use tun2socks and I go through linux example on the wiki page

after editing default gateaway the ssh tunnel get disconnected, maybe I need to make an exception somehow on iptables to route ip and port of ssh server to the primary interface? but i'm not sure how or is this assumption correct or not

[realyukii]

oh wait, I just notice the NOTE section on the wiki:

Note: Please make sure that your proxy server is not running locally, e.g. 127.0.0.1:1080, as this can cause an infinite route loopback problem. Some interface binding techniques can be used to solve this kind of problem, but users need to have enough network knowledge to solve it themselves.

and just realize that my setup is also using loopback interface to host socks5 server on port 1080.

actually, I use chisel for smuggling network packet, so the complete flow might be look like this:

1. establish connection of chisel client-server and bind port 22 on localhost to forward ssh service
2. make an ssh tunnel of socks5 by bind the socks5 proxy to port 1080 and address localhost
   another alternative is:
3. establish connection of chisel client-server and map port 1080 directly to open socks5 proxy: ./chisel_1.10.1_linux_amd64 client -v https://address 1080:socks

what network knowledge I need to solve the tun2socks issue in this scenario?

[gpahlevanzadeh]

I don't how to bind tun0 to my interface. Then I don't know why your default ip? Can you explain in details?