search

xjasonlyu / tun2socks

tun2socks - powered by gVisor TCP/IP stack
https://github.com/xjasonlyu/tun2socks/wiki
GNU General Public License v3.0
2.84k stars 403 forks source link

[Bug] The tun2socks always to use a new port to connect to tcp server #346

Closed muxi01 closed 3 months ago

muxi01 commented 3 months ago

Verify steps

Version

tun2socks-2.5.2 linux/amd64, go1.20.11, 2b494a7

What OS are you seeing the problem on?

Linux

Description

v2ray is used to connect to internet (outof china), tun2socks is used to proxy whole requests of networking. while i do testing for connecting, the curl report errors of 'curl: (35) error:0A000126:SSL routines::unexpected eof while reading', the tun2socks output logs , that contain of contents of '

7 time="2024-03-12T06:40:13Z" level=info msg="[STACK] tun://tun0 <-> socks5://127.0.0.1:9600"
8 time="2024-03-12T06:40:18Z" level=info msg="[DIALER] bind to interface: enp3s0"
9 time="2024-03-12T06:40:18Z" level=info msg="[STACK] tun://tun0 <-> socks5://127.0.0.1:9600"

time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43678 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43694 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43704 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43710 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43720 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43728 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43734 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43754 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43750 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43758 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43756 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43768 <-> 183.240.220.249:29011" time="2024-03-12T06:59:52Z" level=info msg="[TCP] 198.18.0.1:43770 <-> 183.240.220.249:29011" '

CLI or Config

tun0 set up

sudo ip tuntap add mode tun dev tun0 sudo ip addr add 198.18.0.1/15 dev tun0 sudo ip link set dev tun0 up

service v2ray start

sudo ip route del default sudo tun2socks -device tun0 -proxy socks5://127.0.0.1:9600 -interface enp3s0 >> /dev/null & sudo ip route add default via 198.18.0.1 dev tun0 metric 1

Logs

1 time="2024-03-12T06:38:03Z" level=info msg="[DIALER] bind to interface: enp3s0"                                                                                                                                2 time="2024-03-12T06:38:03Z" level=fatal msg="[ENGINE] failed to start: create tun: device or resource busy"
    3 time="2024-03-12T06:38:28Z" level=info msg="[DIALER] bind to interface: enp3s0"
    4 time="2024-03-12T06:38:28Z" level=info msg="[STACK] tun://tun0 <-> socks5://127.0.0.1:10808"
    5 time="2024-03-12T06:38:59Z" level=warning msg="[TCP] dial 151.101.128.223:443: connect to 127.0.0.1:10808: dial tcp 127.0.0.1:10808: connect: connection refused"

------------------------------------------------------------------------------------------------------
The listen port of v2ray is setting to 9600, so the request port is equal 10808 is refused.

    6 time="2024-03-12T06:40:13Z" level=info msg="[DIALER] bind to interface: enp3s0"
    7 time="2024-03-12T06:40:13Z" level=info msg="[STACK] tun://tun0 <-> socks5://127.0.0.1:9600"
    8 time="2024-03-12T06:40:18Z" level=info msg="[DIALER] bind to interface: enp3s0"
    9 time="2024-03-12T06:40:18Z" level=info msg="[STACK] tun://tun0 <-> socks5://127.0.0.1:9600"
   10 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:57538 <-> 151.101.192.223:443"
   11 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41062 <-> 183.236.53.120:29011"
   12 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41076 <-> 183.236.53.120:29011"
   13 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41080 <-> 183.236.53.120:29011"
   14 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41096 <-> 183.236.53.120:29011"
   15 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41098 <-> 183.236.53.120:29011"
   16 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41102 <-> 183.236.53.120:29011"
   17 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41108 <-> 183.236.53.120:29011"
   18 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41114 <-> 183.236.53.120:29011"
   19 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41126 <-> 183.236.53.120:29011"
   20 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41130 <-> 183.236.53.120:29011"
   21 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41132 <-> 183.236.53.120:29011"
   22 time="2024-03-12T06:40:26Z" level=info msg="[TCP] 198.18.0.1:41140 <-> 183.236.53.120:29011"
   23 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41142 <-> 183.236.53.120:29011"
   24 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41144 <-> 183.236.53.120:29011"
   25 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41152 <-> 183.236.53.120:29011"
   26 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41154 <-> 183.236.53.120:29011"
   27 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41162 <-> 183.236.53.120:29011"
   28 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41172 <-> 183.236.53.120:29011"
   29 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41180 <-> 183.236.53.120:29011"
   30 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41194 <-> 183.236.53.120:29011"
   31 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41198 <-> 183.236.53.120:29011"
   32 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41208 <-> 183.236.53.120:29011"
   33 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41220 <-> 183.236.53.120:29011"
   34 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41236 <-> 183.236.53.120:29011"
   35 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41246 <-> 183.236.53.120:29011"
   36 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41250 <-> 183.236.53.120:29011"
   37 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41256 <-> 183.236.53.120:29011"
   38 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41260 <-> 183.236.53.120:29011"
   39 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41264 <-> 183.236.53.120:29011"
   40 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41278 <-> 183.236.53.120:29011"
   41 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41288 <-> 183.236.53.120:29011"
   42 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41294 <-> 183.236.53.120:29011"
   43 time="2024-03-12T06:40:27Z" level=info msg="[TCP] 198.18.0.1:41306 <-> 183.236.53.120:29011"

How to Reproduce

No response

muxi01 commented 3 months ago

the requests are from tun0, Not generated by tun2socks