search

zfl9 / ipt2socks

将 iptables/nftables 传入的透明代理流量转为 socks5 流量的实用工具
GNU Affero General Public License v3.0
439 stars 101 forks source link

运行一段时间后 进程丢失 #10

Closed killbus closed 4 years ago

killbus commented 4 years ago

有点奇怪，跑了几次都出现，看内存也不高，也不是很懂 alpine 怎么调试，看不到 kill 或 oom 的记录。换v2ray dokodemo-door 不会出现。

运行环境

docker -> alpine

Linux version 5.0.2-aml-s905 (root@vbox) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05)) #5.77 SMP PREEMPT Mon Apr 1 17:41:33 MSK 2019

运行参数

ipt2socks -s 127.0.0.1 -p 1080

socks 服务

trojan 1.14.0

最后一段日志

2020-01-18 12:42:08 INF: [tcp_socket_listen_cb] try to connect to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:08 INF: [tcp_socks5_tcp_connect_cb] connected to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:08 INF: [tcp_socks5_tcp_connect_cb] send authreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:08 INF: [tcp_socks5_auth_read_cb] send proxyreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:08 INF: [tcp_socks5_resp_read_cb] connected to target host, start forwarding
2020-01-18 12:42:08 INF: [tcp_stream_read_cb] tcp connection has been closed in both directions
2020-01-18 12:42:09 INF: [udp_socket_listen_cb] recv 40 bytes data from 192.168.5.254#23431
2020-01-18 12:42:09 INF: [udp_socket_listen_cb] try to connect to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:09 INF: [udp_socks5_tcp_connect_cb] connected to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:09 INF: [udp_socks5_tcp_connect_cb] send authreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:09 INF: [udp_socks5_auth_read_cb] send proxyreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:09 INF: [udp_socks5_resp_read_cb] udp tunnel is open, try to send packet via socks5
2020-01-18 12:42:09 INF: [udp_socks5_resp_read_cb] send 40 bytes data to 8.8.8.8#53 via socks5
2020-01-18 12:42:09 INF: [udp_client_recv_cb] recv 56 bytes data from 8.8.8.8#53 via socks5
2020-01-18 12:42:09 INF: [udp_client_recv_cb] send 56 bytes data to 192.168.5.254#23431 via tproxy
2020-01-18 12:42:09 INF: [tcp_socket_listen_cb] accept new tcp connection: 192.168.5.191#39917
2020-01-18 12:42:09 INF: [tcp_socket_listen_cb] original destination addr: 216.58.199.106#443
2020-01-18 12:42:09 INF: [tcp_socket_listen_cb] try to connect to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:09 INF: [tcp_socks5_tcp_connect_cb] connected to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:09 INF: [tcp_socks5_tcp_connect_cb] send authreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:09 INF: [tcp_socks5_auth_read_cb] send proxyreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:09 INF: [tcp_socks5_resp_read_cb] connected to target host, start forwarding
2020-01-18 12:42:22 INF: [tcp_stream_read_cb] tcp connection has been closed in both directions
2020-01-18 12:42:23 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:25 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:25 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:25 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:25 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:27 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:30 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:30 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:31 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:31 INF: [udp_svrentry_timer_cb] udp server idle timeout, release related resources
2020-01-18 12:42:32 INF: [udp_svrentry_timer_cb] udp server idle timeout, release related resources
2020-01-18 12:42:32 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:36 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:37 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:37 INF: [udp_svrentry_timer_cb] udp server idle timeout, release related resources
2020-01-18 12:42:39 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:39 INF: [tcp_socket_listen_cb] accept new tcp connection: 192.168.5.191#41563
2020-01-18 12:42:39 INF: [tcp_socket_listen_cb] original destination addr: 192.229.237.96#443
2020-01-18 12:42:39 INF: [tcp_socket_listen_cb] try to connect to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:39 INF: [tcp_socks5_tcp_connect_cb] connected to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:39 INF: [tcp_socks5_tcp_connect_cb] send authreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:39 INF: [tcp_socks5_auth_read_cb] send proxyreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:39 INF: [tcp_socks5_resp_read_cb] connected to target host, start forwarding
2020-01-18 12:42:39 INF: [tcp_socket_listen_cb] accept new tcp connection: 192.168.5.191#41565
2020-01-18 12:42:39 INF: [tcp_socket_listen_cb] original destination addr: 192.229.237.96#443
2020-01-18 12:42:39 INF: [tcp_socket_listen_cb] try to connect to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:39 INF: [tcp_socks5_tcp_connect_cb] connected to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:39 INF: [tcp_socks5_tcp_connect_cb] send authreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:39 INF: [tcp_socks5_auth_read_cb] send proxyreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:39 INF: [tcp_socks5_resp_read_cb] connected to target host, start forwarding
2020-01-18 12:42:41 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:41 INF: [udp_svrentry_timer_cb] udp server idle timeout, release related resources
2020-01-18 12:42:46 INF: [udp_cltentry_timer_cb] udp client idle timeout, release related resources
2020-01-18 12:42:53 INF: [udp_socket_listen_cb] recv 22 bytes data from 192.168.5.254#61082
2020-01-18 12:42:53 INF: [udp_socket_listen_cb] try to connect to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:53 INF: [udp_socks5_tcp_connect_cb] connected to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:53 INF: [udp_socks5_tcp_connect_cb] send authreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:53 INF: [udp_socks5_auth_read_cb] send proxyreq to socks5 server: 127.0.0.1#1080
2020-01-18 12:42:53 INF: [udp_socks5_resp_read_cb] udp tunnel is open, try to send packet via socks5
2020-01-18 12:42:53 INF: [udp_socks5_resp_read_cb] send 22 bytes data to 8.8.8.8#53 via socks5
2020-01-18 12:42:54 INF: [udp_client_recv_cb] recv 86 bytes data from 8.8.8.8#53 via socks5
bash-5.0#
cattyhouse commented 4 years ago

https://github.com/zfl9/ipt2socks/issues/9

zfl9 commented 4 years ago

如果不想换的话，临时解决办法就是加个守护。挂了自动重启下就行了。目前没时间重构。