local_port端口被占用时应该进行提示 about redsocks HOT 31 CLOSED

第一次使用redsocks，发现原来现在有重试机制，端口占用的时候是会不断重试的。这个应该是原版提供的功能。
现在在openwrt上使用redsocks2，出现很多下面的错误：
431181643.744693 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 853
1431181644.748061 main.c:184 main(...) redsocks started
1431181649.746692 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 920
1431181650.750045 main.c:184 main(...) redsocks started
1431181655.748696 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 980
1431181656.754433 main.c:184 main(...) redsocks started
1431181661.751689 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 1036
1431181662.755197 main.c:184 main(...) redsocks started

根据您回复别人的帖子，是配置文件有问题，但是我精简过了配置文件，还是同样的错误。基本可以排除是配置文件的问题。不知道再怎么判断问题的原因？可否远程指导下？qq84615567

from redsocks.

我遇到过这个问题，在redsocks2在运行的时候，再开redsocks2，能打开进程，然后ps后能看到三个redsocks2进程，后来发现是我的脚本运行导致redsocks2启动了两次，改了就好了

2015-05-09 22:31 GMT+08:00 1294822 [email protected]:

第一次使用redsocks，发现原来现在有重试机制，端口占用的时候是会不断重试的。这个应该是原版提供的功能。
现在在openwrt上使用redsocks2，出现很多下面的错误：
431181643.744693 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 853
1431181644.748061 main.c:184 main(...) redsocks started
1431181649.746692 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 920
1431181650.750045 main.c:184 main(...) redsocks started
1431181655.748696 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 980
1431181656.754433 main.c:184 main(...) redsocks started
1431181661.751689 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 1036
1431181662.755197 main.c:184 main(...) redsocks started

根据您回复别人的帖子，是配置文件有问题，但是我精简过了配置文件，还是同样的错误。基本可以排除是配置文件的问题。不知道再怎么判断问题的原因？可否远程指导下？qq84615567

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

我没有使用脚本去启动redsocks2，手工运行了他。
刚运行的时候，会有两个进程，配置的local_port也会成功打开。但是一会就关闭了。然后就出现了上面的错误。此时就只有一个进程了。

from redsocks.

我现在已经能正常翻墙，但是运行日志一大堆这种错误，以前用shadowsocks就有遇到这种情况，不知道你有遇到这种没有
May 9 22:26:20 redsocks[4643]: [192.168.1.108:52491->216.58.221.161:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:26:21 redsocks[4643]: [192.168.1.108:52491->216.58.221.161:443]:
shutdown(client, SHUT_WR): Transport endpoint is not connected
May 9 22:26:30 redsocks[4643]: [192.168.1.108:52503->216.58.221.161:443]:
shutdown(client, SHUT_WR): Transport endpoint is not connected
May 9 22:26:41 redsocks[4643]: [192.168.1.108:52530->54.173.153.162:443]:
shutdown(client, SHUT_WR): Transport endpoint is not connected
May 9 22:27:10 redsocks[4643]: [192.168.1.108:52579->192.30.252.136:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:27:11 redsocks[4643]: [192.168.1.108:52599->54.173.153.162:443]:
shutdown(client, SHUT_WR): Transport endpoint is not connected
May 9 22:28:10 redsocks[4643]: [192.168.1.108:52648->192.30.252.136:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:28:10 redsocks[4643]: [192.168.1.108:52649->192.30.252.136:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:28:50 redsocks[4643]: [192.168.1.108:52695->203.208.50.141:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:28:50 redsocks[4643]: [192.168.1.108:52689->216.58.221.161:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:28:50 redsocks[4643]: [192.168.1.108:52697->203.208.50.153:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected

在 2015年5月9日 下午10:33，李鑫 [email protected]写道：

我遇到过这个问题，在redsocks2在运行的时候，再开redsocks2，能打开进程，然后ps后能看到三个redsocks2进程，后来发现是我的脚本运行导致redsocks2启动了两次，改了就好了

2015-05-09 22:31 GMT+08:00 1294822 [email protected]:

第一次使用redsocks，发现原来现在有重试机制，端口占用的时候是会不断重试的。这个应该是原版提供的功能。
现在在openwrt上使用redsocks2，出现很多下面的错误：
431181643.744693 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 853
1431181644.748061 main.c:184 main(...) redsocks started
1431181649.746692 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 920
1431181650.750045 main.c:184 main(...) redsocks started
1431181655.748696 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 980
1431181656.754433 main.c:184 main(...) redsocks started
1431181661.751689 base.c:365 myproc(...) Failed to send SIGUSR2 to pid
1036
1431181662.755197 main.c:184 main(...) redsocks started

根据您回复别人的帖子，是配置文件有问题，但是我精简过了配置文件，还是同样的错误。基本可以排除是配置文件的问题。不知道再怎么判断问题的原因？可否远程指导下？qq84615567

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

from redsocks.

没有呢，我刚开始用。看到介绍很强大所以试用了下。会不会跟ss的服务端时间设置有关系，纯猜测。

from redsocks.

不清楚呢，实在不行我还是开ss-local，暂时不用redsocks的shadowsocks功能

在 2015年5月9日 下午10:41，1294822 [email protected]写道：

没有呢，我刚开始用。看到介绍很强大所以试用了下。会不会跟ss的服务端时间设置有关系，纯猜测。

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

我之前用的是ss-redir。我现在的问题应该还是出在redsocks本身上。

from redsocks.

这个 log完全不影响传用 是一种正常的情况

Semigod King
2015年5月9日 下午10:37于 "sadoneli" [email protected]写道：

我现在已经能正常翻墙，但是运行日志一大堆这种错误，以前用shadowsocks就有遇到这种情况，不知道你有遇到这种没有
May 9 22:26:20 redsocks[4643]: [192.168.1.108:52491->216.58.221.161:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:26:21 redsocks[4643]: [192.168.1.108:52491->216.58.221.161:443]:
shutdown(client, SHUT_WR): Transport endpoint is not connected
May 9 22:26:30 redsocks[4643]: [192.168.1.108:52503->216.58.221.161:443]:
shutdown(client, SHUT_WR): Transport endpoint is not connected
May 9 22:26:41 redsocks[4643]: [192.168.1.108:52530->54.173.153.162:443]:
shutdown(client, SHUT_WR): Transport endpoint is not connected
May 9 22:27:10 redsocks[4643]: [192.168.1.108:52579->192.30.252.136:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:27:11 redsocks[4643]: [192.168.1.108:52599->54.173.153.162:443]:
shutdown(client, SHUT_WR): Transport endpoint is not connected
May 9 22:28:10 redsocks[4643]: [192.168.1.108:52648->192.30.252.136:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:28:10 redsocks[4643]: [192.168.1.108:52649->192.30.252.136:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:28:50 redsocks[4643]: [192.168.1.108:52695->203.208.50.141:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:28:50 redsocks[4643]: [192.168.1.108:52689->216.58.221.161:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected
May 9 22:28:50 redsocks[4643]: [192.168.1.108:52697->203.208.50.153:443]:
shutdown(client, SHUT_RD): Transport endpoint is not connected

在 2015年5月9日 下午10:33，李鑫 [email protected]写道：

我遇到过这个问题，在redsocks2在运行的时候，再开redsocks2，能打开进程，然后ps后能看到三个redsocks2进程，后来发现是我的脚本运行导致redsocks2启动了两次，改了就好了

2015-05-09 22:31 GMT+08:00 1294822 [email protected]:

第一次使用redsocks，发现原来现在有重试机制，端口占用的时候是会不断重试的。这个应该是原版提供的功能。
现在在openwrt上使用redsocks2，出现很多下面的错误：
431181643.744693 base.c:365 myproc(...) Failed to send SIGUSR2 to pid
853
1431181644.748061 main.c:184 main(...) redsocks started
1431181649.746692 base.c:365 myproc(...) Failed to send SIGUSR2 to pid
920
1431181650.750045 main.c:184 main(...) redsocks started
1431181655.748696 base.c:365 myproc(...) Failed to send SIGUSR2 to pid
980
1431181656.754433 main.c:184 main(...) redsocks started
1431181661.751689 base.c:365 myproc(...) Failed to send SIGUSR2 to pid
1036
1431181662.755197 main.c:184 main(...) redsocks started

根据您回复别人的帖子，是配置文件有问题，但是我精简过了配置文件，还是同样的错误。基本可以排除是配置文件的问题。不知道再怎么判断问题的原因？可否远程指导下？qq84615567

—
Reply to this email directly or view it on GitHub
<
https://github.com/semigodking/redsocks/issues/9#issuecomment-100496902>
.

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

有什么原因导致 redsocks进程死掉了。最新版如正确配置后是很难再出现进程死掉的情况的。我暂时无法猜测原因

Semigod King
2015年5月9日 下午10:31于 "1294822" [email protected]写道：

第一次使用redsocks，发现原来现在有重试机制，端口占用的时候是会不断重试的。这个应该是原版提供的功能。
现在在openwrt上使用redsocks2，出现很多下面的错误：
431181643.744693 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 853
1431181644.748061 main.c:184 main(...) redsocks started
1431181649.746692 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 920
1431181650.750045 main.c:184 main(...) redsocks started
1431181655.748696 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 980
1431181656.754433 main.c:184 main(...) redsocks started
1431181661.751689 base.c:365 myproc(...) Failed to send SIGUSR2 to pid 1036
1431181662.755197 main.c:184 main(...) redsocks started

根据您回复别人的帖子，是配置文件有问题，但是我精简过了配置文件，还是同样的错误。基本可以排除是配置文件的问题。不知道再怎么判断问题的原因？可否远程指导下？qq84615567

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

和服务器端时间没有任何关系。

Semigod King
2015年5月9日 下午10:43于 "sadoneli" [email protected]写道：

不清楚呢，实在不行我还是开ss-local，暂时不用redsocks的shadowsocks功能

在 2015年5月9日 下午10:41，1294822 [email protected]写道：

没有呢，我刚开始用。看到介绍很强大所以试用了下。会不会跟ss的服务端时间设置有关系，纯猜测。

—
Reply to this email directly or view it on GitHub
#9 (comment).

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

测试了原版，发现有如下的区别：
1.原版在local_port被占用时，会进行提示。
2.原版可以正常运行，同样的conf文件，redsocks2就报 myproc(...) Failed to send SIGUSR2 to pid 20218

from redsocks.

那个应该也提示了，但你要开 log才能看到。这个以后会考虑一下这种情况。

Semigod King
2015年5月9日 下午10:59于 "1294822" [email protected]写道：

测试了原版，发现有如下的区别：
1.原版在local_port被占用时，会进行提示。
2.原版可以正常运行，同样的conf文件，redsocks2就报 myproc(...) Failed to send SIGUSR2 to pid
20218

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

1431590215.145348 shadowsocks.c:369 ss_instance_init(...) using encryption method: rc4-md5
1431590215.146461 main.c:184 main(...) redsocks started
1431590222.701515 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 0, 0
1431590223.199510 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:17408->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590223.199648 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:17408->0.0.0.0:1053]: dropping request
1431590227.708647 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 0, 0
1431590228.214748 tcpdns.c:94 tcpdns_readcb(...) [127.0.0.1:41523->0.0.0.0:1053]: response size: 102
1431590228.215103 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:41523->0.0.0.0:1053]: dropping request
1431590228.218661 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 0, 506
1431590229.642660 tcpdns.c:94 tcpdns_readcb(...) [127.0.0.1:18725->0.0.0.0:1053]: response size: 128
1431590229.642987 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:18725->0.0.0.0:1053]: dropping request
1431590229.646693 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 506
1431590230.122913 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:57911->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590230.123047 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:57911->0.0.0.0:1053]: dropping request
1431590234.651622 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590235.155999 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:47865->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590235.156133 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:47865->0.0.0.0:1053]: dropping request
1431590239.656645 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590240.091363 tcpdns.c:94 tcpdns_readcb(...) [127.0.0.1:30613->0.0.0.0:1053]: response size: 122
1431590240.091687 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:30613->0.0.0.0:1053]: dropping request
1431590335.240242 redsocks.c:888 redsocks_audit_instance(...) Audit client list for instance 0x89f260(shadowsocks):
1431590335.240336 redsocks.c:909 redsocks_audit_instance(...) End of auditing client list.
1431590337.496665 redsocks.c:795 redsocks_accept_client(...) [192.168.0.249:64510->205.177.196.25:80]: accepted
1431590337.980517 redsocks.c:376 redsocks_start_relay(...) [192.168.0.249:64510->205.177.196.25:80]: data relaying started
1431590337.980716 autoproxy.c:428 process_shutdown_on_write_2(...) [192.168.0.249:64510->205.177.196.25:80]: WCB relay, fs: 0, ts: 0, fin: 856, fout: 0, tin: 0
1431590337.980842 autoproxy.c:276 handle_write_to_relay(...) [192.168.0.249:64510->205.177.196.25:80]: sent: 0, recv: 0, in:856, out:0
1431590337.981062 redsocks.c:287 process_shutdown_on_write_(...) [192.168.0.249:64510->205.177.196.25:80]: WCB client, fs: 0, ts: 0, fin: 0, fout: 856, tin: 856
1431590337.981542 autoproxy.c:428 process_shutdown_on_write_2(...) [192.168.0.249:64510->205.177.196.25:80]: WCB relay, fs: 0, ts: 0, fin: 856, fout: 0, tin: 0
1431590337.981783 autoproxy.c:276 handle_write_to_relay(...) [192.168.0.249:64510->205.177.196.25:80]: sent: 856, recv: 0, in:856, out:0
1431590338.516830 autoproxy.c:388 direct_relay_relayreadcb(...) [192.168.0.249:64510->205.177.196.25:80]: relay in: 465
1431590338.517003 autoproxy.c:187 on_connection_confirmed(...) [192.168.0.249:64510->205.177.196.25:80]: IP Confirmed
1431590338.517445 redsocks.c:287 process_shutdown_on_write_(...) [192.168.0.249:64510->205.177.196.25:80]: WCB client, fs: 0, ts: 0, fin: 0, fout: 0, tin: 0
1431590353.528329 autoproxy.c:615 auto_event_error(...) [192.168.0.249:64510->205.177.196.25:80]: client, errno(0), State: 10002, what: READING|0|EOF|0|0|0|0x0: Success
1431590353.528620 autoproxy.c:428 process_shutdown_on_write_2(...) [192.168.0.249:64510->205.177.196.25:80]: WCB relay, fs: 2, ts: 0, fin: 0, fout: 0, tin: 0
1431590354.030488 autoproxy.c:615 auto_event_error(...) [192.168.0.249:64510->205.177.196.25:80]: relay, errno(0), State: 10002, what: READING|0|EOF|0|0|0|0x0: Success
1431590354.030775 redsocks.c:287 process_shutdown_on_write_(...) [192.168.0.249:64510->205.177.196.25:80]: WCB client, fs: 6, ts: 2, fin: 0, fout: 0, tin: 0
1431590354.031086 redsocks.c:459 redsocks_shutdown(...) [192.168.0.249:64510->205.177.196.25:80]: both client and server disconnected
1431590354.031199 redsocks.c:388 redsocks_drop_client(...) [192.168.0.249:64510->205.177.196.25:80]: dropping client
1431590452.903790 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 435
1431590453.182195 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:47096->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590453.182332 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:47096->0.0.0.0:1053]: dropping request
1431590455.147735 redsocks.c:888 redsocks_audit_instance(...) Audit client list for instance 0x89f260(shadowsocks):
1431590455.147832 redsocks.c:909 redsocks_audit_instance(...) End of auditing client list.
1431590457.509734 redsocks.c:795 redsocks_accept_client(...) [192.168.0.249:64513->205.177.196.25:80]: accepted
1431590457.910396 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590458.077284 redsocks.c:376 redsocks_start_relay(...) [192.168.0.249:64513->205.177.196.25:80]: data relaying started
1431590458.077445 autoproxy.c:428 process_shutdown_on_write_2(...) [192.168.0.249:64513->205.177.196.25:80]: WCB relay, fs: 0, ts: 0, fin: 856, fout: 0, tin: 0
1431590458.077547 autoproxy.c:276 handle_write_to_relay(...) [192.168.0.249:64513->205.177.196.25:80]: sent: 0, recv: 0, in:856, out:0
1431590458.077732 redsocks.c:287 process_shutdown_on_write_(...) [192.168.0.249:64513->205.177.196.25:80]: WCB client, fs: 0, ts: 0, fin: 0, fout: 856, tin: 856
1431590458.078162 autoproxy.c:428 process_shutdown_on_write_2(...) [192.168.0.249:64513->205.177.196.25:80]: WCB relay, fs: 0, ts: 0, fin: 856, fout: 0, tin: 0
1431590458.078385 autoproxy.c:276 handle_write_to_relay(...) [192.168.0.249:64513->205.177.196.25:80]: sent: 856, recv: 0, in:856, out:0
1431590458.152806 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:57746->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590458.152937 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:57746->0.0.0.0:1053]: dropping request
1431590458.621384 autoproxy.c:388 direct_relay_relayreadcb(...) [192.168.0.249:64513->205.177.196.25:80]: relay in: 467
1431590458.621534 autoproxy.c:187 on_connection_confirmed(...) [192.168.0.249:64513->205.177.196.25:80]: IP Confirmed
1431590458.622121 redsocks.c:287 process_shutdown_on_write_(...) [192.168.0.249:64513->205.177.196.25:80]: WCB client, fs: 0, ts: 0, fin: 0, fout: 0, tin: 0
1431590462.911115 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590463.151126 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:63259->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590463.151264 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:63259->0.0.0.0:1053]: dropping request
1431590467.916553 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590468.174980 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:5529->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590468.175117 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:5529->0.0.0.0:1053]: dropping request
1431590472.921386 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590473.287770 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:6982->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590473.287907 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:6982->0.0.0.0:1053]: dropping request
1431590473.627844 autoproxy.c:615 auto_event_error(...) [192.168.0.249:64513->205.177.196.25:80]: client, errno(0), State: 10002, what: READING|0|EOF|0|0|0|0x0: Success
1431590473.628089 autoproxy.c:428 process_shutdown_on_write_2(...) [192.168.0.249:64513->205.177.196.25:80]: WCB relay, fs: 2, ts: 0, fin: 0, fout: 0, tin: 0
1431590474.115830 autoproxy.c:615 auto_event_error(...) [192.168.0.249:64513->205.177.196.25:80]: relay, errno(0), State: 10002, what: READING|0|EOF|0|0|0|0x0: Success
1431590474.116072 redsocks.c:287 process_shutdown_on_write_(...) [192.168.0.249:64513->205.177.196.25:80]: WCB client, fs: 6, ts: 2, fin: 0, fout: 0, tin: 0
1431590474.116369 redsocks.c:459 redsocks_shutdown(...) [192.168.0.249:64513->205.177.196.25:80]: both client and server disconnected
1431590474.116480 redsocks.c:388 redsocks_drop_client(...) [192.168.0.249:64513->205.177.196.25:80]: dropping client
1431590477.926801 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590478.094794 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:46377->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590478.094931 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:46377->0.0.0.0:1053]: dropping request
1431590482.931287 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590483.219645 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:36520->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590483.219781 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:36520->0.0.0.0:1053]: dropping request
1431590487.936635 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS resolvers: 1424, 0
1431590488.252684 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:50584->0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation now in progress
1431590488.252821 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:50584->0.0.0.0:1053]: dropping request

tcpdns {
local_ip = 0.0.0.0;
local_port = 1053;
timeout = 1;
tcpdns1 = 8.8.8.8;
tcpdns2 = 8.8.4.4;
}

dnsmasq dns server: 127.0.0.1#1053

nslookup youtube.com

请问我是设置错了？

from redsocks.

对的，把 timeout改大一点点再试

Semigod King
2015年5月14日 下午4:04于 "leenchan" [email protected]写道：

1431590215.145348 shadowsocks.c:369 ss_instance_init(...) using encryption
method: rc4-md5
1431590215.146461 main.c:184 main(...) redsocks started
1431590222.701515 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 0, 0
1431590223.199510 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:17408->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590223.199648 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:17408->
0.0.0.0:1053]: dropping request
1431590227.708647 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 0, 0
1431590228.214748 tcpdns.c:94 tcpdns_readcb(...) [127.0.0.1:41523->
0.0.0.0:1053]: response size: 102
1431590228.215103 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:41523->
0.0.0.0:1053]: dropping request
1431590228.218661 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 0, 506
1431590229.642660 tcpdns.c:94 tcpdns_readcb(...) [127.0.0.1:18725->
0.0.0.0:1053]: response size: 128
1431590229.642987 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:18725->
0.0.0.0:1053]: dropping request
1431590229.646693 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 506
1431590230.122913 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:57911->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590230.123047 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:57911->
0.0.0.0:1053]: dropping request
1431590234.651622 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590235.155999 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:47865->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590235.156133 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:47865->
0.0.0.0:1053]: dropping request
1431590239.656645 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590240.091363 tcpdns.c:94 tcpdns_readcb(...) [127.0.0.1:30613->
0.0.0.0:1053]: response size: 122
1431590240.091687 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:30613->
0.0.0.0:1053]: dropping request
1431590335.240242 redsocks.c:888 redsocks_audit_instance(...) Audit client
list for instance 0x89f260(shadowsocks):
1431590335.240336 redsocks.c:909 redsocks_audit_instance(...) End of
auditing client list.
1431590337.496665 redsocks.c:795 redsocks_accept_client(...)
[192.168.0.249:64510->205.177.196.25:80]: accepted
1431590337.980517 redsocks.c:376 redsocks_start_relay(...)
[192.168.0.249:64510->205.177.196.25:80]: data relaying started
1431590337.980716 autoproxy.c:428 process_shutdown_on_write_2(...)
[192.168.0.249:64510->205.177.196.25:80]: WCB relay, fs: 0, ts: 0, fin:
856, fout: 0, tin: 0
1431590337.980842 autoproxy.c:276 handle_write_to_relay(...)
[192.168.0.249:64510->205.177.196.25:80]: sent: 0, recv: 0, in:856, out:0
1431590337.981062 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.0.249:64510->205.177.196.25:80]: WCB client, fs: 0, ts: 0, fin:
0, fout: 856, tin: 856
1431590337.981542 autoproxy.c:428 process_shutdown_on_write_2(...)
[192.168.0.249:64510->205.177.196.25:80]: WCB relay, fs: 0, ts: 0, fin:
856, fout: 0, tin: 0
1431590337.981783 autoproxy.c:276 handle_write_to_relay(...)
[192.168.0.249:64510->205.177.196.25:80]: sent: 856, recv: 0, in:856,
out:0
1431590338.516830 autoproxy.c:388 direct_relay_relayreadcb(...)
[192.168.0.249:64510->205.177.196.25:80]: relay in: 465
1431590338.517003 autoproxy.c:187 on_connection_confirmed(...)
[192.168.0.249:64510->205.177.196.25:80]: IP Confirmed
1431590338.517445 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.0.249:64510->205.177.196.25:80]: WCB client, fs: 0, ts: 0, fin:
0, fout: 0, tin: 0
1431590353.528329 autoproxy.c:615 auto_event_error(...)
[192.168.0.249:64510->205.177.196.25:80]: client, errno(0), State: 10002,
what: READING|0|EOF|0|0|0|0x0: Success
1431590353.528620 autoproxy.c:428 process_shutdown_on_write_2(...)
[192.168.0.249:64510->205.177.196.25:80]: WCB relay, fs: 2, ts: 0, fin:
0, fout: 0, tin: 0
1431590354.030488 autoproxy.c:615 auto_event_error(...)
[192.168.0.249:64510->205.177.196.25:80]: relay, errno(0), State: 10002,
what: READING|0|EOF|0|0|0|0x0: Success
1431590354.030775 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.0.249:64510->205.177.196.25:80]: WCB client, fs: 6, ts: 2, fin:
0, fout: 0, tin: 0
1431590354.031086 redsocks.c:459 redsocks_shutdown(...)
[192.168.0.249:64510->205.177.196.25:80]: both client and server
disconnected
1431590354.031199 redsocks.c:388 redsocks_drop_client(...)
[192.168.0.249:64510->205.177.196.25:80]: dropping client
1431590452.903790 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 435
1431590453.182195 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:47096->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590453.182332 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:47096->
0.0.0.0:1053]: dropping request
1431590455.147735 redsocks.c:888 redsocks_audit_instance(...) Audit client
list for instance 0x89f260(shadowsocks):
1431590455.147832 redsocks.c:909 redsocks_audit_instance(...) End of
auditing client list.
1431590457.509734 redsocks.c:795 redsocks_accept_client(...)
[192.168.0.249:64513->205.177.196.25:80]: accepted
1431590457.910396 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590458.077284 redsocks.c:376 redsocks_start_relay(...)
[192.168.0.249:64513->205.177.196.25:80]: data relaying started
1431590458.077445 autoproxy.c:428 process_shutdown_on_write_2(...)
[192.168.0.249:64513->205.177.196.25:80]: WCB relay, fs: 0, ts: 0, fin:
856, fout: 0, tin: 0
1431590458.077547 autoproxy.c:276 handle_write_to_relay(...)
[192.168.0.249:64513->205.177.196.25:80]: sent: 0, recv: 0, in:856, out:0
1431590458.077732 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.0.249:64513->205.177.196.25:80]: WCB client, fs: 0, ts: 0, fin:
0, fout: 856, tin: 856
1431590458.078162 autoproxy.c:428 process_shutdown_on_write_2(...)
[192.168.0.249:64513->205.177.196.25:80]: WCB relay, fs: 0, ts: 0, fin:
856, fout: 0, tin: 0
1431590458.078385 autoproxy.c:276 handle_write_to_relay(...)
[192.168.0.249:64513->205.177.196.25:80]: sent: 856, recv: 0, in:856,
out:0
1431590458.152806 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:57746->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590458.152937 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:57746->
0.0.0.0:1053]: dropping request
1431590458.621384 autoproxy.c:388 direct_relay_relayreadcb(...)
[192.168.0.249:64513->205.177.196.25:80]: relay in: 467
1431590458.621534 autoproxy.c:187 on_connection_confirmed(...)
[192.168.0.249:64513->205.177.196.25:80]: IP Confirmed
1431590458.622121 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.0.249:64513->205.177.196.25:80]: WCB client, fs: 0, ts: 0, fin:
0, fout: 0, tin: 0
1431590462.911115 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590463.151126 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:63259->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590463.151264 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:63259->
0.0.0.0:1053]: dropping request
1431590467.916553 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590468.174980 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:5529->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590468.175117 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:5529->
0.0.0.0:1053]: dropping request
1431590472.921386 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590473.287770 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:6982->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590473.287907 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:6982->
0.0.0.0:1053]: dropping request
1431590473.627844 autoproxy.c:615 auto_event_error(...)
[192.168.0.249:64513->205.177.196.25:80]: client, errno(0), State: 10002,
what: READING|0|EOF|0|0|0|0x0: Success
1431590473.628089 autoproxy.c:428 process_shutdown_on_write_2(...)
[192.168.0.249:64513->205.177.196.25:80]: WCB relay, fs: 2, ts: 0, fin:
0, fout: 0, tin: 0
1431590474.115830 autoproxy.c:615 auto_event_error(...)
[192.168.0.249:64513->205.177.196.25:80]: relay, errno(0), State: 10002,
what: READING|0|EOF|0|0|0|0x0: Success
1431590474.116072 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.0.249:64513->205.177.196.25:80]: WCB client, fs: 6, ts: 2, fin:
0, fout: 0, tin: 0
1431590474.116369 redsocks.c:459 redsocks_shutdown(...)
[192.168.0.249:64513->205.177.196.25:80]: both client and server
disconnected
1431590474.116480 redsocks.c:388 redsocks_drop_client(...)
[192.168.0.249:64513->205.177.196.25:80]: dropping client
1431590477.926801 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590478.094794 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:46377->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590478.094931 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:46377->
0.0.0.0:1053]: dropping request
1431590482.931287 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590483.219645 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:36520->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590483.219781 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:36520->
0.0.0.0:1053]: dropping request
1431590487.936635 tcpdns.c:182 choose_tcpdns(...) Dealy of TCP DNS
resolvers: 1424, 0
1431590488.252684 tcpdns.c:169 tcpdns_event_error(...) [127.0.0.1:50584->
0.0.0.0:1053]: errno(150), what: READING|0|0|0|TIMEOUT|0|0x0: Operation
now in progress
1431590488.252821 tcpdns.c:66 tcpdns_drop_request(...) [127.0.0.1:50584->
0.0.0.0:1053]: dropping request

tcpdns {
local_ip = 0.0.0.0;
local_port = 1053;
timeout = 1;
tcpdns1 = 8.8.8.8;
tcpdns2 = 8.8.4.4;
}

dnsmasq dns server: 127.0.0.1#1053

nslookup youtube.com

请问我是设置错了？

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

用shadowsocks模式试了下，google可上，但是facebook和youtube均打不开，而浏览器直连shadowsocks服务器是可以打开所有这些网站的。截取了连接facebook的日志：
1431773525.348663 redsocks.c:795 redsocks_accept_client(...) [192.168.1.100:58571->78.16.49.15:443]: accepted
1431773533.356351 autoproxy.c:615 auto_event_error(...) [192.168.1.100:58571->78.16.49.15:443]: relay, errno(0), State: 10000, what: 0|WRITING|0|0|TIMEOUT|0|0x0: Success
1431773533.356484 autoproxy.c:194 on_connection_blocked(...) [192.168.1.100:58571->78.16.49.15:443]: IP Blocked
1431773533.356614 autoproxy.c:497 auto_retry(...) [192.168.1.100:58571->78.16.49.15:443]: ADD IP to cache: 78.16.49.15
1431773533.356719 autoproxy.c:473 auto_drop_relay(...) [192.168.1.100:58571->78.16.49.15:443]: dropping relay only
1431773534.549871 redsocks.c:376 redsocks_start_relay(...) [192.168.1.100:58571->78.16.49.15:443]: data relaying started
1431773534.550153 redsocks.c:287 process_shutdown_on_write_(...) [192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 0, ts: 0, fin: 133, fout: 0, tin: 0
1431773534.550386 redsocks.c:287 process_shutdown_on_write_(...) [192.168.1.100:58571->78.16.49.15:443]: WCB client, fs: 0, ts: 0, fin: 0, fout: 156, tin: 0
1431773534.550742 redsocks.c:287 process_shutdown_on_write_(...) [192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 0, ts: 0, fin: 0, fout: 0, tin: 0
1431773597.748822 redsocks.c:486 redsocks_event_error(...) [192.168.1.100:58571->78.16.49.15:443]: relay, what: READING|0|EOF|0|0|0|0x0: Success
1431773597.749080 redsocks.c:287 process_shutdown_on_write_(...) [192.168.1.100:58571->78.16.49.15:443]: WCB client, fs: 2, ts: 0, fin: 0, fout: 0, tin: 0
1431773597.752319 redsocks.c:486 redsocks_event_error(...) [192.168.1.100:58571->78.16.49.15:443]: client, what: READING|0|EOF|0|0|0|0x0: Success
1431773597.752575 redsocks.c:287 process_shutdown_on_write_(...) [192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 6, ts: 2, fin: 0, fout: 0, tin: 0
1431773597.752836 redsocks.c:459 redsocks_shutdown(...) [192.168.1.100:58571->78.16.49.15:443]: both client and server disconnected
1431773597.752956 redsocks.c:388 redsocks_drop_client(...) [192.168.1.100:58571->78.16.49.15:443]: dropping client
1431773597.754751 redsocks.c:795 redsocks_accept_client(...) [192.168.1.100:58633->78.16.49.15:443]: accepted

帮忙看看问题出在何处，版本是最新的一次commit，openwrt上用。
我后来又试了下用redsocks2的socks5模式，同样是只能打开google，其它被墙的网站全打不开，挺奇怪的。

from redsocks.

看了一遍，我没有看到任何问题。连接被转向 Facebook, 两方交互的数据比较少，看似是 HTTPS
协商的过程中止，至于原因我怀疑和浏览器有关，很奇怪。你试一下换个浏览器试下？

Semigod King
2015年5月16日 下午7:08于 "lijunhao731" [email protected]写道：

用shadowsocks模式试了下，google可上，但是facebook和youtube均打不开，而浏览器直连shadowsocks服务器是可以打开所有这些网站的。截取了连接facebook的日志：
1431773525.348663 redsocks.c:795 redsocks_accept_client(...)
[192.168.1.100:58571->78.16.49.15:443]: accepted
1431773526.075887 autoproxy.c:375 direct_relay_clientreadcb(...)
[192.168.1.100:57173->111.221.72.121:443]: client in: 53
1431773526.076358 autoproxy.c:428 process_shutdown_on_write_2(...)
[192.168.1.100:57173->111.221.72.121:443]: WCB relay, fs: 0, ts: 0, fin:
0, fout: 0, tin: 0
1431773526.144309 autoproxy.c:388 direct_relay_relayreadcb(...)
[192.168.1.100:57173->111.221.72.121:443]: relay in: 101
1431773526.144713 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:57173->111.221.72.121:443]: WCB client, fs: 0, ts: 0, fin:
0, fout: 0, tin: 0
1431773533.356351 autoproxy.c:615 auto_event_error(...)
[192.168.1.100:58571->78.16.49.15:443]: relay, errno(0), State: 10000,
what: 0|WRITING|0|0|TIMEOUT|0|0x0: Success
1431773533.356484 autoproxy.c:194 on_connection_blocked(...)
[192.168.1.100:58571->78.16.49.15:443]: IP Blocked
1431773533.356614 autoproxy.c:497 auto_retry(...) [192.168.1.100:58571->
78.16.49.15:443]: ADD IP to cache: 78.16.49.15
1431773533.356719 autoproxy.c:473 auto_drop_relay(...) [192.168.1.100:58571
->78.16.49.15:443]: dropping relay only
1431773534.549871 redsocks.c:376 redsocks_start_relay(...)
[192.168.1.100:58571->78.16.49.15:443]: data relaying started
1431773534.550153 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 0, ts: 0, fin:
133, fout: 0, tin: 0
1431773534.550386 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB client, fs: 0, ts: 0, fin: 0,
fout: 156, tin: 0
1431773534.550742 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 0, ts: 0, fin: 0,
fout: 0, tin: 0
1431773597.748822 redsocks.c:486 redsocks_event_error(...)
[192.168.1.100:58571->78.16.49.15:443]: relay, what:
READING|0|EOF|0|0|0|0x0: Success
1431773597.749080 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB client, fs: 2, ts: 0, fin: 0,
fout: 0, tin: 0
1431773597.752319 redsocks.c:486 redsocks_event_error(...)
[192.168.1.100:58571->78.16.49.15:443]: client, what:
READING|0|EOF|0|0|0|0x0: Success
1431773597.752575 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 6, ts: 2, fin: 0,
fout: 0, tin: 0
1431773597.752836 redsocks.c:459 redsocks_shutdown(...)
[192.168.1.100:58571->78.16.49.15:443]: both client and server
disconnected
1431773597.752956 redsocks.c:388 redsocks_drop_client(...)
[192.168.1.100:58571->78.16.49.15:443]: dropping client
1431773597.754751 redsocks.c:795 redsocks_accept_client(...)
[192.168.1.100:58633->78.16.49.15:443]: accepted

帮忙看看问题出在何处，版本是0.60，openwrt上用

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

你检查下是否你的 DNS 被污染！

root@OpenWrt:~# nslookup Facebook.com
Server: 127.0.0.1
Address 1: 127.0.0.1 localhost

Name: Facebook.com
Address 1: 2a03:2880:2130:cf05:face:b00c:0:1
edge-star6-shv-12-frc3.facebook.com
Address 2: 173.252.120.6 edge-star-shv-12-frc3.facebook.com

Semigod King
2015年5月16日 下午9:10于 "Semigod King" [email protected]写道：

看了一遍，我没有看到任何问题。连接被转向 Facebook, 两方交互的数据比较少，看似是 HTTPS
协商的过程中止，至于原因我怀疑和浏览器有关，很奇怪。你试一下换个浏览器试下？

Semigod King
2015年5月16日 下午7:08于 "lijunhao731" [email protected]写道：

用shadowsocks模式试了下，google可上，但是facebook和youtube均打不开，而浏览器直连shadowsocks服务器是可以打开所有这些网站的。截取了连接facebook的日志：
1431773525.348663 redsocks.c:795 redsocks_accept_client(...)
[192.168.1.100:58571->78.16.49.15:443]: accepted
1431773526.075887 autoproxy.c:375 direct_relay_clientreadcb(...)
[192.168.1.100:57173->111.221.72.121:443]: client in: 53
1431773526.076358 autoproxy.c:428 process_shutdown_on_write_2(...)
[192.168.1.100:57173->111.221.72.121:443]: WCB relay, fs: 0, ts: 0, fin:
0, fout: 0, tin: 0
1431773526.144309 autoproxy.c:388 direct_relay_relayreadcb(...)
[192.168.1.100:57173->111.221.72.121:443]: relay in: 101
1431773526.144713 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:57173->111.221.72.121:443]: WCB client, fs: 0, ts: 0,
fin: 0, fout: 0, tin: 0
1431773533.356351 autoproxy.c:615 auto_event_error(...)
[192.168.1.100:58571->78.16.49.15:443]: relay, errno(0), State: 10000,
what: 0|WRITING|0|0|TIMEOUT|0|0x0: Success
1431773533.356484 autoproxy.c:194 on_connection_blocked(...)
[192.168.1.100:58571->78.16.49.15:443]: IP Blocked
1431773533.356614 autoproxy.c:497 auto_retry(...) [192.168.1.100:58571->
78.16.49.15:443]: ADD IP to cache: 78.16.49.15
1431773533.356719 autoproxy.c:473 auto_drop_relay(...)
[192.168.1.100:58571->78.16.49.15:443]: dropping relay only
1431773534.549871 redsocks.c:376 redsocks_start_relay(...)
[192.168.1.100:58571->78.16.49.15:443]: data relaying started
1431773534.550153 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 0, ts: 0, fin:
133, fout: 0, tin: 0
1431773534.550386 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB client, fs: 0, ts: 0, fin:
0, fout: 156, tin: 0
1431773534.550742 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 0, ts: 0, fin: 0,
fout: 0, tin: 0
1431773597.748822 redsocks.c:486 redsocks_event_error(...)
[192.168.1.100:58571->78.16.49.15:443]: relay, what:
READING|0|EOF|0|0|0|0x0: Success
1431773597.749080 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB client, fs: 2, ts: 0, fin:
0, fout: 0, tin: 0
1431773597.752319 redsocks.c:486 redsocks_event_error(...)
[192.168.1.100:58571->78.16.49.15:443]: client, what:
READING|0|EOF|0|0|0|0x0: Success
1431773597.752575 redsocks.c:287 process_shutdown_on_write_(...)
[192.168.1.100:58571->78.16.49.15:443]: WCB relay, fs: 6, ts: 2, fin: 0,
fout: 0, tin: 0
1431773597.752836 redsocks.c:459 redsocks_shutdown(...)
[192.168.1.100:58571->78.16.49.15:443]: both client and server
disconnected
1431773597.752956 redsocks.c:388 redsocks_drop_client(...)
[192.168.1.100:58571->78.16.49.15:443]: dropping client
1431773597.754751 redsocks.c:795 redsocks_accept_client(...)
[192.168.1.100:58633->78.16.49.15:443]: accepted

帮忙看看问题出在何处，版本是0.60，openwrt上用

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

from redsocks.

谢谢费心帮我看，我想了下应该和dns无关，因为我直连shadowsocks时候一切是正常的，速度还挺快，另外我还试过强制把dns设成8.8.8.8，情况并没有变化。
有一个情况说一下，我的redsocks2和shadowsocks都是装在一台只有单lan口的刷了openwrt的nas（192.168.1.2，lan口网关192.168.1.250 ）上，局域网网关是192.168.1.250，而我的计算机上设的网关是192.168.1.2，就是那台nas，其实我也不明白为什么这样设可以工作，有点不符合理论，但那台nas确实把所有数据都转发给了网关。
我暂时没条件在网关上装redsocks2，nas因为只有单网口所以也做不了网关，所以没法测试是不是由于这样一种特殊的拓扑导致没法用。
我现在想不明白的有两个地方，一个是google是能上的，一个是我在nas上用op官方集成的redsocks（不是redsocks2）的情况下是能访问其它被墙的网站的，这究竟是怎么回事。。。

from redsocks.

不好意思，可能是我记错了，我又去试了一下，用redsocks是一样的情况，除了google其它被墙网站都打不开。

from redsocks.

好像确实是dns污染的问题，我搜了下解析出来的facebook的ip在黑名单里面，http://zh.wikipedia.org/wiki/%E5%9F%9F%E5%90%8D%E6%9C%8D%E5%8A%A1%E5%99%A8%E7%BC%93%E5%AD%98%E6%B1%A1%E6%9F%93
然而我不明的是为啥直接连shadowsocks是好的，应该不涉及dns啊。。。

from redsocks.

强制把dns设成8.8.8.8并不能解决 DNS污染。用 redudp来把 DNS污染解决掉再试

Semigod King
2015年5月16日 下午10:32于 "lijunhao731" [email protected]写道：

谢谢费心帮我看，我想了下应该和dns无关，因为我直连shadowsocks时候一切是正常的，速度还挺快，另外我还试过强制把dns设成8.8.8.8，情况并没有变化。
有一个情况说一下，我的redsocks2和shadowsocks都是装在一台只有单lan口的刷了openwrt的nas（192.168.1.2，lan口网关192.168.1.250
）上，局域网网关是192.168.1.250，而我的计算机上设的网关是192.168.1.250，就是那台nas，其实我也不明白为什么这样设可以工作，有点不符合理论，但那台nas确实把所有数据都转发给了网关。
我暂时没条件在网关上装redsocks2，nas因为只有单网口所以也做不了网关，所以没法测试是不是由于这样一种特殊的拓扑导致没法用。

我现在想不明白的有两个地方，一个是google是能上的，一个是我在nas上用op官方集成的redsocks（不是redsocks2）的情况下是能访问其它被墙的网站的，这究竟是怎么回事。。。

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

@semigodking
还有一个问题 从以前到现在的版本 不知道与 redsocks2 有关不：
路由（192.168.1.1）
iptables 把 所有tcp 转到redsocks2端口，所有客户端都正常，log有记录
但是 192.168.1.1上面 任何网络操作 都没有经过redsocks2， 没有log 记录

from redsocks.

这是正确的。一般情况下，网关上的应用都是用默认出口的，不走nat。除非你的应用明确绑定到局域网IP

Semigod King
2015年5月18日 上午10:15于 "leenchan" [email protected]写道：

@semigodking https://github.com/semigodking
还有一个问题 从以前到现在的版本 不知道与 redsocks2 有关不：
路由（192.168.1.1）
iptables 把 所有tcp 转到redsocks2端口，所有客户端都正常，log有记录
但是 192.168.1.1上面 任何网络操作 都没有经过redsocks2， 没有log 记录

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

好的，謝謝~ 我試改下 iptales.

from redsocks.

@semigodking
看来这个不是我能解决的问题，我说一下我的情况吧：
网关192.168.1.1需要通过redsocks2探测qiang外并且更新qiang外的东西
如果iptables nat表里 直接 转给 ss的端口 是可以的
请问有什么方法能让网关数据通过redsocks2端？

from redsocks.

要使应用走 nat 需要你的应用明确绑定网关 IP或接口，就像 redsocks2中指定本地监听端口一样。 Curl就支持指定
interface啊。你提供出问题时的 redsocks2的 log我可帮你看下是否是 redsocks2的问题。

Semigod King
2015年5月20日 下午9:51于 "leenchan" [email protected]写道：

@semigodking https://github.com/semigodking
看来这个不是我能解决的问题，我说一下我的情况吧：
网关192.168.1.1需要通过redsocks2探测qiang外并且更新qiang外的东西
如果iptables nat表里 直接 转给 ss的端口 是可以的
请问有什么方法能让网关数据通过redsocks2端？

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

你好，根据你的提示 我做了以下操作 临时解决了目前的需求
iptables -t nat -A OUTPUT -o lo -p tcp -j REDIRECT --to-ports $redsocks2_local_port
curl --interface lo http://xxx.com
成功下载 并且 log: 正确显示 127.0.0.1 连接上了

终于弄明白为什么用SS-libev， 网关为什么能下载到数据，因为iptables 把 nat OUTPUT的全部 tcp数据 转到 SS上了，奇怪的是 同样的iptables规则，redsocks2 却不能，想了想，是不是这样设置是死循环了 以下是SS的规则
:SHADOWSOCKS_LAN - [0:0]
:SHADOWSOCKS_WAN - [0:0]
-A OUTPUT -p tcp -j SHADOWSOCKS_WAN
-A SHADOWSOCKS_LAN -p tcp -j SHADOWSOCKS_WAN
-A SHADOWSOCKS_WAN -d 0.0.0.0/8 -j RETURN
-A SHADOWSOCKS_WAN -d 10.0.0.0/8 -j RETURN
-A SHADOWSOCKS_WAN -d 100.64.0.0/10 -j RETURN
-A SHADOWSOCKS_WAN -d 127.0.0.0/8 -j RETURN
-A SHADOWSOCKS_WAN -d 169.254.0.0/16 -j RETURN
-A SHADOWSOCKS_WAN -d 172.16.0.0/12 -j RETURN
-A SHADOWSOCKS_WAN -d 192.0.0.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 192.0.2.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 192.168.0.0/16 -j RETURN
-A SHADOWSOCKS_WAN -d 192.88.99.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 198.18.0.0/15 -j RETURN
-A SHADOWSOCKS_WAN -d 198.51.100.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 203.0.113.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 224.0.0.0/4 -j RETURN
-A SHADOWSOCKS_WAN -d 240.0.0.0/4 -j RETURN
-A SHADOWSOCKS_WAN -d 255.255.255.255/32 -j RETURN
-A SHADOWSOCKS_WAN -d $proxy_ip/32 -j RETURN
-A SHADOWSOCKS_WAN -p tcp -m set --match-set shadowsocks dst -j RETURN
-A SHADOWSOCKS_WAN -p tcp -j REDIRECT --to-ports 443
-A zone_lan_prerouting -p tcp -j SHADOWSOCKS_LAN

from redsocks.

这条去掉

-A SHADOWSOCKS_WAN -d 0.0.0.0/8 -j RETURN

Semigod King
2015年5月21日 下午6:48于 "leenchan" [email protected]写道：

你好，根据你的提示 我做了以下操作 临时解决了目前的需求
iptables -t nat -A OUTPUT -o lo -p tcp -j REDIRECT --to-ports
$redsocks2_local_port
curl --interface lo http://xxx.com
成功下载 并且 log: 正确显示 127.0.0.1 连接上了

终于弄明白为什么用SS-libev， 网关为什么能下载到数据，因为iptables 把 nat OUTPUT的全部 tcp数据 转到
SS上了，奇怪的是 同样的iptables规则，redsocks2 却不能，想了想，是不是这样设置是死循环了 以下是SS的规则
:SHADOWSOCKS_LAN - [0:0]
:SHADOWSOCKS_WAN - [0:0]
-A OUTPUT -p tcp -j SHADOWSOCKS_WAN
-A SHADOWSOCKS_LAN -p tcp -j SHADOWSOCKS_WAN
-A SHADOWSOCKS_WAN -d 0.0.0.0/8 -j RETURN
-A SHADOWSOCKS_WAN -d 10.0.0.0/8 -j RETURN
-A SHADOWSOCKS_WAN -d 100.64.0.0/10 -j RETURN
-A SHADOWSOCKS_WAN -d 127.0.0.0/8 -j RETURN
-A SHADOWSOCKS_WAN -d 169.254.0.0/16 -j RETURN
-A SHADOWSOCKS_WAN -d 172.16.0.0/12 -j RETURN
-A SHADOWSOCKS_WAN -d 192.0.0.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 192.0.2.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 192.168.0.0/16 -j RETURN
-A SHADOWSOCKS_WAN -d 192.88.99.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 198.18.0.0/15 -j RETURN
-A SHADOWSOCKS_WAN -d 198.51.100.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 203.0.113.0/24 -j RETURN
-A SHADOWSOCKS_WAN -d 224.0.0.0/4 -j RETURN
-A SHADOWSOCKS_WAN -d 240.0.0.0/4 -j RETURN
-A SHADOWSOCKS_WAN -d 255.255.255.255/32 -j RETURN
-A SHADOWSOCKS_WAN -d $proxy_ip/32 -j RETURN
-A SHADOWSOCKS_WAN -p tcp -m set --match-set shadowsocks dst -j RETURN
-A SHADOWSOCKS_WAN -p tcp -j REDIRECT --to-ports 443
-A zone_lan_prerouting -p tcp -j SHADOWSOCKS_LAN

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.

二位果然是乐此不疲啊，番茄事业任重而道远。对于youtube视频的问题，我使用redsocks2也是这样。对于提到的解析后ip被墙的问题，这个就是咱们redsocks2解决的问题啊，让被墙的ip走ss，所以跟污染没关系（当然如果解析到wpkg另说）。

from redsocks.

二级路由IP 192.168.1.247

:REDSOCKS2_LAN - [0:0]
:REDSOCKS2_WAN - [0:0]
-A REDSOCKS2_LAN -p tcp -j REDSOCKS2_WAN
-A REDSOCKS2_WAN -d 10.0.0.0/8 -j RETURN
-A REDSOCKS2_WAN -d 100.64.0.0/10 -j RETURN
-A REDSOCKS2_WAN -d 127.0.0.0/8 -j RETURN
-A REDSOCKS2_WAN -d 169.254.0.0/16 -j RETURN
-A REDSOCKS2_WAN -d 172.16.0.0/12 -j RETURN
-A REDSOCKS2_WAN -d 192.0.0.0/24 -j RETURN
-A REDSOCKS2_WAN -d 192.0.2.0/24 -j RETURN
-A REDSOCKS2_WAN -d 192.88.99.0/24 -j RETURN
-A REDSOCKS2_WAN -d 198.18.0.0/15 -j RETURN
-A REDSOCKS2_WAN -d 198.51.100.0/24 -j RETURN
-A REDSOCKS2_WAN -d 192.168.0.0/24 -j RETURN
-A REDSOCKS2_WAN -d 203.0.113.0/24 -j RETURN
-A REDSOCKS2_WAN -d 224.0.0.0/4 -j RETURN
-A REDSOCKS2_WAN -d 240.0.0.0/4 -j RETURN
-A REDSOCKS2_WAN -d 255.255.255.255/32 -j RETURN
-A REDSOCKS2_WAN -d $proxy_ip/32 -j RETURN
-A REDSOCKS2_WAN -p tcp -j REDIRECT --to-ports 443
-A zone_lan_prerouting -p tcp -j REDSOCKS2_LAN
客户端一切正常
log:
https://raw.githubusercontent.com/leenchan/openwrt/master/redsocks2_1.log

添加：
-A OUTPUT -p tcp -j REDSOCKS2_WAN
客户端不能打开网页
log:
https://raw.githubusercontent.com/leenchan/openwrt/master/redsocks2_2.log

from redsocks.

这个我看不出什么来

Semigod King
2015年5月23日 上午12:18于 "leenchan" [email protected]写道：

二级路由IP 192.168.1.247

:REDSOCKS2_LAN - [0:0]
:REDSOCKS2_WAN - [0:0]
-A REDSOCKS2_LAN -p tcp -j REDSOCKS2_WAN
-A REDSOCKS2_WAN -d 10.0.0.0/8 -j RETURN
-A REDSOCKS2_WAN -d 100.64.0.0/10 -j RETURN
-A REDSOCKS2_WAN -d 127.0.0.0/8 -j RETURN
-A REDSOCKS2_WAN -d 169.254.0.0/16 -j RETURN
-A REDSOCKS2_WAN -d 172.16.0.0/12 -j RETURN
-A REDSOCKS2_WAN -d 192.0.0.0/24 -j RETURN
-A REDSOCKS2_WAN -d 192.0.2.0/24 -j RETURN
-A REDSOCKS2_WAN -d 192.88.99.0/24 -j RETURN
-A REDSOCKS2_WAN -d 198.18.0.0/15 -j RETURN
-A REDSOCKS2_WAN -d 198.51.100.0/24 -j RETURN
-A REDSOCKS2_WAN -d 192.168.0.0/24 -j RETURN
-A REDSOCKS2_WAN -d 203.0.113.0/24 -j RETURN
-A REDSOCKS2_WAN -d 224.0.0.0/4 -j RETURN
-A REDSOCKS2_WAN -d 240.0.0.0/4 -j RETURN
-A REDSOCKS2_WAN -d 255.255.255.255/32 -j RETURN
-A REDSOCKS2_WAN -d $proxy_ip/32 -j RETURN
-A REDSOCKS2_WAN -p tcp -j REDIRECT --to-ports 443
-A zone_lan_prerouting -p tcp -j REDSOCKS2_LAN
客户端一切正常
log:
https://raw.githubusercontent.com/leenchan/openwrt/master/redsocks2_1.log

添加：
-A OUTPUT -p tcp -j REDSOCKS2_WAN
客户端不能打开网页
log:
https://raw.githubusercontent.com/leenchan/openwrt/master/redsocks2_2.log

—
Reply to this email directly or view it on GitHub
#9 (comment).

from redsocks.