Comments (61)
Yep, I can confirm this too.
--nat-info <local_ip>:<global_ip>
helps.
from mtproxy.
I ran into a similar problem.
Long Long Log
[root@ubuntu-vm]:~$ mtproto-proxy -u nobody -p 8888 -H 443 -S `cat /usr/local/etc/mtproto-proxy/proxy-pass` --aes-pwd /usr/local/etc/mtproto-proxy/proxy-secret /usr/local/etc/mtproto-proxy/proxy-multi.conf -M 1 -v
[31923][2018-06-02 04:42:56.106325 local] Invoking engine mtproxy-0.01 compiled at May 31 2018 20:15:25 by gcc 7.3.0 64-bit after commit 129ad2f93bfdaec897e60abea2335c6db457c3b7
[31923][2018-06-02 04:42:56.106462 local] config_filename = '/usr/local/etc/mtproto-proxy/proxy-multi.conf'
[31923][2018-06-02 04:42:56.106514 local] /etc/hosts changed, reloaded
[31923][2018-06-02 04:42:56.106681 local] config loaded!
[31923][2018-06-02 04:42:56.106742 local] creating 1 workers
[31923][2018-06-02 04:42:56.106868 local] loaded 128 bytes from password file /usr/local/etc/mtproto-proxy/proxy-secret
[31924][2018-06-02 04:42:56.106979 local] loaded 128 bytes from password file /usr/local/etc/mtproto-proxy/proxy-secret
[31923][2018-06-02 04:42:56.107462 local] using main IP 192.168.10.10/24 at interface eth0
[31923][2018-06-02 04:42:56.107669 local] using main IP 2002:8045:c8d5::215:5dff:fe0a:221/64 at interface eth0
[31924][2018-06-02 04:42:56.107676 local] using main IP 192.168.10.10/24 at interface eth0
[31924][2018-06-02 04:42:56.107795 local] using main IP 2002:8045:c8d5::215:5dff:fe0a:221/64 at interface eth0
[31923][2018-06-02 04:42:56.110397 local] Started as [192.168.10.10:8888:31923:1527914576]
[31924][2018-06-02 04:42:56.110517 local] Started as [192.168.10.10:8888:31924:1527914576]
[31923][2018-06-02 04:42:56.110773 local] configuration file /usr/local/etc/mtproto-proxy/proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[31923][2018-06-02 04:42:56.110825 local] opened tcp socket
[31923][2018-06-02 04:42:56.110848 local] Server started
[31924][2018-06-02 04:42:56.110869 local] configuration file /usr/local/etc/mtproto-proxy/proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[31923][2018-06-02 04:42:56.110878 local] main loop
[31924][2018-06-02 04:42:56.110900 local] Server started
[31924][2018-06-02 04:42:56.111003 local] main loop
[31923][2018-06-02 04:42:56.116384 local] Creating NEW connection to 149.154.175.50:8888
[31924][2018-06-02 04:42:56.116487 local] Creating NEW connection to 149.154.175.50:8888
[31923][2018-06-02 04:42:56.116554 local] New connection 192.168.10.10:40292 -> 149.154.175.50:8888
[31923][2018-06-02 04:42:56.116595 local] Creating NEW connection to 149.154.175.50:8888
[31924][2018-06-02 04:42:56.116670 local] New connection 192.168.10.10:40294 -> 149.154.175.50:8888
[31924][2018-06-02 04:42:56.116717 local] Creating NEW connection to 149.154.175.50:8888
[31923][2018-06-02 04:42:56.116742 local] New connection 192.168.10.10:40296 -> 149.154.175.50:8888
[31923][2018-06-02 04:42:56.116774 local] Creating NEW connection to 149.154.175.50:8888
[31924][2018-06-02 04:42:56.116882 local] New connection 192.168.10.10:40298 -> 149.154.175.50:8888
[31923][2018-06-02 04:42:56.116903 local] New connection 192.168.10.10:40300 -> 149.154.175.50:8888
[31923][2018-06-02 04:42:56.116915 local] Creating NEW connection to 149.154.175.50:8888
[31924][2018-06-02 04:42:56.116914 local] Creating NEW connection to 149.154.175.50:8888
[31923][2018-06-02 04:42:56.117090 local] New connection 192.168.10.10:40302 -> 149.154.175.50:8888
[31924][2018-06-02 04:42:56.117089 local] New connection 192.168.10.10:40304 -> 149.154.175.50:8888
[31923][2018-06-02 04:42:56.117125 local] Creating NEW connection to 91.108.4.136:8888
[31924][2018-06-02 04:42:56.117127 local] Creating NEW connection to 149.154.175.50:8888
[31923][2018-06-02 04:42:56.117304 local] New connection 192.168.10.10:37252 -> 91.108.4.136:8888
[31924][2018-06-02 04:42:56.117330 local] New connection 192.168.10.10:40308 -> 149.154.175.50:8888
[31923][2018-06-02 04:42:56.117337 local] Creating NEW connection to 91.108.4.136:8888
[31924][2018-06-02 04:42:56.117412 local] Creating NEW connection to 91.108.4.136:8888
[31923][2018-06-02 04:42:56.117534 local] New connection 192.168.10.10:37256 -> 91.108.4.136:8888
[31923][2018-06-02 04:42:56.117568 local] Creating NEW connection to 91.108.4.136:8888
[31924][2018-06-02 04:42:56.117573 local] New connection 192.168.10.10:37258 -> 91.108.4.136:8888
[31924][2018-06-02 04:42:56.117640 local] Creating NEW connection to 91.108.4.136:8888
[31923][2018-06-02 04:42:56.117755 local] New connection 192.168.10.10:37260 -> 91.108.4.136:8888
[31923][2018-06-02 04:42:56.117781 local] Creating NEW connection to 91.108.4.136:8888
[31924][2018-06-02 04:42:56.117785 local] New connection 192.168.10.10:37262 -> 91.108.4.136:8888
[31924][2018-06-02 04:42:56.117841 local] Creating NEW connection to 91.108.4.136:8888
[31923][2018-06-02 04:42:56.117951 local] New connection 192.168.10.10:37264 -> 91.108.4.136:8888
[31923][2018-06-02 04:42:56.117995 local] Creating NEW connection to 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118004 local] New connection 192.168.10.10:37266 -> 91.108.4.136:8888
[31924][2018-06-02 04:42:56.118030 local] Creating NEW connection to 91.108.4.136:8888
[31923][2018-06-02 04:42:56.118176 local] New connection 192.168.10.10:42562 -> 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118186 local] New connection 192.168.10.10:37270 -> 91.108.4.136:8888
[31924][2018-06-02 04:42:56.118219 local] Creating NEW connection to 91.108.4.186:8888
[31923][2018-06-02 04:42:56.118222 local] Creating NEW connection to 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118354 local] New connection 192.168.10.10:42566 -> 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118387 local] Creating NEW connection to 91.108.4.186:8888
[31923][2018-06-02 04:42:56.118388 local] New connection 192.168.10.10:42568 -> 91.108.4.186:8888
[31923][2018-06-02 04:42:56.118403 local] Creating NEW connection to 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118549 local] New connection 192.168.10.10:42570 -> 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118572 local] Creating NEW connection to 91.108.4.186:8888
[31923][2018-06-02 04:42:56.118574 local] New connection 192.168.10.10:42572 -> 91.108.4.186:8888
[31923][2018-06-02 04:42:56.118600 local] Creating NEW connection to 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118735 local] New connection 192.168.10.10:42574 -> 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118767 local] Creating NEW connection to 91.108.4.186:8888
[31923][2018-06-02 04:42:56.118778 local] New connection 192.168.10.10:42576 -> 91.108.4.186:8888
[31923][2018-06-02 04:42:56.118819 local] Creating NEW connection to 149.154.165.250:8888
[31924][2018-06-02 04:42:56.118924 local] New connection 192.168.10.10:42578 -> 91.108.4.186:8888
[31924][2018-06-02 04:42:56.118959 local] Creating NEW connection to 149.154.165.250:8888
[31923][2018-06-02 04:42:56.119012 local] New connection 192.168.10.10:42806 -> 149.154.165.250:8888
[31923][2018-06-02 04:42:56.119041 local] Creating NEW connection to 149.154.165.250:8888
[31924][2018-06-02 04:42:56.119147 local] New connection 192.168.10.10:42808 -> 149.154.165.250:8888
[31924][2018-06-02 04:42:56.119189 local] Creating NEW connection to 149.154.165.250:8888
[31923][2018-06-02 04:42:56.119211 local] New connection 192.168.10.10:42810 -> 149.154.165.250:8888
[31923][2018-06-02 04:42:56.119230 local] Creating NEW connection to 149.154.165.250:8888
[31924][2018-06-02 04:42:56.119343 local] New connection 192.168.10.10:42812 -> 149.154.165.250:8888
[31924][2018-06-02 04:42:56.119385 local] Creating NEW connection to 149.154.165.250:8888
[31923][2018-06-02 04:42:56.119409 local] New connection 192.168.10.10:42814 -> 149.154.165.250:8888
[31923][2018-06-02 04:42:56.119462 local] Creating NEW connection to 149.154.165.250:8888
[31924][2018-06-02 04:42:56.119510 local] New connection 192.168.10.10:42816 -> 149.154.165.250:8888
[31924][2018-06-02 04:42:56.119547 local] Creating NEW connection to 149.154.165.250:8888
[31923][2018-06-02 04:42:56.119626 local] New connection 192.168.10.10:42818 -> 149.154.165.250:8888
[31923][2018-06-02 04:42:56.119663 local] Creating NEW connection to 91.108.56.140:8888
[31924][2018-06-02 04:42:56.119702 local] New connection 192.168.10.10:42820 -> 149.154.165.250:8888
[31924][2018-06-02 04:42:56.119734 local] Creating NEW connection to 91.108.56.140:8888
[31923][2018-06-02 04:42:56.119793 local] New connection 192.168.10.10:42158 -> 91.108.56.140:8888
[31923][2018-06-02 04:42:56.119828 local] Creating NEW connection to 91.108.56.140:8888
[31924][2018-06-02 04:42:56.119916 local] New connection 192.168.10.10:42160 -> 91.108.56.140:8888
[31924][2018-06-02 04:42:56.119973 local] Creating NEW connection to 91.108.56.140:8888
[31923][2018-06-02 04:42:56.119990 local] New connection 192.168.10.10:42162 -> 91.108.56.140:8888
[31923][2018-06-02 04:42:56.120026 local] Creating NEW connection to 91.108.56.140:8888
[31924][2018-06-02 04:42:56.120111 local] New connection 192.168.10.10:42164 -> 91.108.56.140:8888
[31924][2018-06-02 04:42:56.120141 local] Creating NEW connection to 91.108.56.140:8888
[31923][2018-06-02 04:42:56.120160 local] New connection 192.168.10.10:42166 -> 91.108.56.140:8888
[31923][2018-06-02 04:42:56.120197 local] Creating NEW connection to 91.108.56.140:8888
[31924][2018-06-02 04:42:56.120294 local] New connection 192.168.10.10:42168 -> 91.108.56.140:8888
[31924][2018-06-02 04:42:56.120325 local] Creating NEW connection to 91.108.56.140:8888
[31923][2018-06-02 04:42:56.120349 local] New connection 192.168.10.10:42170 -> 91.108.56.140:8888
[31923][2018-06-02 04:42:56.120391 local] Creating NEW connection to 149.154.175.100:8888
[31924][2018-06-02 04:42:56.120479 local] New connection 192.168.10.10:42172 -> 91.108.56.140:8888
[31924][2018-06-02 04:42:56.120515 local] Creating NEW connection to 149.154.175.100:8888
[31923][2018-06-02 04:42:56.120517 local] New connection 192.168.10.10:37064 -> 149.154.175.100:8888
[31923][2018-06-02 04:42:56.120528 local] Creating NEW connection to 149.154.175.100:8888
[31924][2018-06-02 04:42:56.120677 local] New connection 192.168.10.10:37066 -> 149.154.175.100:8888
[31923][2018-06-02 04:42:56.120680 local] New connection 192.168.10.10:37068 -> 149.154.175.100:8888
[31923][2018-06-02 04:42:56.120712 local] Creating NEW connection to 149.154.175.100:8888
[31924][2018-06-02 04:42:56.120713 local] Creating NEW connection to 149.154.175.100:8888
[31923][2018-06-02 04:42:56.120861 local] New connection 192.168.10.10:37070 -> 149.154.175.100:8888
[31924][2018-06-02 04:42:56.120887 local] New connection 192.168.10.10:37072 -> 149.154.175.100:8888
[31923][2018-06-02 04:42:56.120895 local] Creating NEW connection to 149.154.175.100:8888
[31924][2018-06-02 04:42:56.120902 local] Creating NEW connection to 149.154.175.100:8888
[31923][2018-06-02 04:42:56.121021 local] New connection 192.168.10.10:37074 -> 149.154.175.100:8888
[31924][2018-06-02 04:42:56.121042 local] New connection 192.168.10.10:37076 -> 149.154.175.100:8888
[31923][2018-06-02 04:42:56.121051 local] Creating NEW connection to 91.108.56.197:8888
[31924][2018-06-02 04:42:56.121098 local] Creating NEW connection to 149.154.175.100:8888
[31923][2018-06-02 04:42:56.121214 local] New connection 192.168.10.10:58484 -> 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121249 local] Creating NEW connection to 91.108.56.197:8888
[31924][2018-06-02 04:42:56.121261 local] New connection 192.168.10.10:37080 -> 149.154.175.100:8888
[31924][2018-06-02 04:42:56.121276 local] Creating NEW connection to 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121384 local] New connection 192.168.10.10:58488 -> 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121405 local] Creating NEW connection to 91.108.56.197:8888
[31924][2018-06-02 04:42:56.121488 local] New connection 192.168.10.10:58490 -> 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121535 local] New connection 192.168.10.10:58492 -> 91.108.56.197:8888
[31924][2018-06-02 04:42:56.121539 local] Creating NEW connection to 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121556 local] Creating NEW connection to 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121731 local] New connection 192.168.10.10:58496 -> 91.108.56.197:8888
[31924][2018-06-02 04:42:56.121765 local] New connection 192.168.10.10:58494 -> 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121768 local] Creating NEW connection to 91.108.4.139:8888
[31924][2018-06-02 04:42:56.121780 local] Creating NEW connection to 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121923 local] New connection 192.168.10.10:55478 -> 91.108.4.139:8888
[31924][2018-06-02 04:42:56.121942 local] New connection 192.168.10.10:58500 -> 91.108.56.197:8888
[31923][2018-06-02 04:42:56.121945 local] Creating NEW connection to 91.108.4.139:8888
[31924][2018-06-02 04:42:56.121956 local] Creating NEW connection to 91.108.56.197:8888
[31923][2018-06-02 04:42:56.122071 local] New connection 192.168.10.10:55482 -> 91.108.4.139:8888
[31923][2018-06-02 04:42:56.122111 local] Creating NEW connection to 91.108.4.139:8888
[31924][2018-06-02 04:42:56.122141 local] New connection 192.168.10.10:58504 -> 91.108.56.197:8888
[31924][2018-06-02 04:42:56.122188 local] Creating NEW connection to 91.108.4.139:8888
[31923][2018-06-02 04:42:56.122252 local] New connection 192.168.10.10:55486 -> 91.108.4.139:8888
[31923][2018-06-02 04:42:56.122289 local] Creating NEW connection to 91.108.4.139:8888
[31924][2018-06-02 04:42:56.122390 local] New connection 192.168.10.10:55488 -> 91.108.4.139:8888
[31923][2018-06-02 04:42:56.122442 local] New connection 192.168.10.10:55490 -> 91.108.4.139:8888
[31924][2018-06-02 04:42:56.122442 local] Creating NEW connection to 91.108.4.139:8888
[31923][2018-06-02 04:42:56.122458 local] Creating NEW connection to 91.108.4.169:8888
[31923][2018-06-02 04:42:56.122604 local] New connection 192.168.10.10:60076 -> 91.108.4.169:8888
[31923][2018-06-02 04:42:56.122637 local] Creating NEW connection to 91.108.4.169:8888
[31924][2018-06-02 04:42:56.122638 local] New connection 192.168.10.10:55494 -> 91.108.4.139:8888
[31924][2018-06-02 04:42:56.122663 local] Creating NEW connection to 91.108.4.139:8888
[31923][2018-06-02 04:42:56.122794 local] New connection 192.168.10.10:60080 -> 91.108.4.169:8888
[31923][2018-06-02 04:42:56.122816 local] Creating NEW connection to 91.108.4.169:8888
[31924][2018-06-02 04:42:56.122847 local] New connection 192.168.10.10:55498 -> 91.108.4.139:8888
[31924][2018-06-02 04:42:56.122904 local] Creating NEW connection to 91.108.4.139:8888
[31923][2018-06-02 04:42:56.122967 local] New connection 192.168.10.10:60084 -> 91.108.4.169:8888
[31923][2018-06-02 04:42:56.123013 local] Creating NEW connection to 91.108.4.169:8888
[31924][2018-06-02 04:42:56.123106 local] New connection 192.168.10.10:55502 -> 91.108.4.139:8888
[31924][2018-06-02 04:42:56.123159 local] Creating NEW connection to 91.108.4.169:8888
[31923][2018-06-02 04:42:56.123195 local] New connection 192.168.10.10:60088 -> 91.108.4.169:8888
[31923][2018-06-02 04:42:56.123230 local] Creating NEW connection to 149.154.162.26:80
[31924][2018-06-02 04:42:56.123330 local] New connection 192.168.10.10:60090 -> 91.108.4.169:8888
[31924][2018-06-02 04:42:56.123382 local] Creating NEW connection to 91.108.4.169:8888
[31923][2018-06-02 04:42:56.123388 local] New connection 192.168.10.10:56666 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.123400 local] Creating NEW connection to 149.154.162.26:80
[31924][2018-06-02 04:42:56.123538 local] New connection 192.168.10.10:60094 -> 91.108.4.169:8888
[31923][2018-06-02 04:42:56.123549 local] New connection 192.168.10.10:56670 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.123611 local] Creating NEW connection to 149.154.162.26:80
[31924][2018-06-02 04:42:56.123612 local] Creating NEW connection to 91.108.4.169:8888
[31923][2018-06-02 04:42:56.123806 local] New connection 192.168.10.10:56672 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.123835 local] Creating NEW connection to 149.154.162.26:80
[31924][2018-06-02 04:42:56.123875 local] New connection 192.168.10.10:60100 -> 91.108.4.169:8888
[31924][2018-06-02 04:42:56.123914 local] Creating NEW connection to 91.108.4.169:8888
[31923][2018-06-02 04:42:56.123967 local] New connection 192.168.10.10:56676 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.124000 local] Creating NEW connection to 91.108.4.202:8888
[31924][2018-06-02 04:42:56.124118 local] New connection 192.168.10.10:60104 -> 91.108.4.169:8888
[31923][2018-06-02 04:42:56.124167 local] New connection 192.168.10.10:38538 -> 91.108.4.202:8888
[31923][2018-06-02 04:42:56.124182 local] Creating NEW connection to 91.108.4.202:8888
[31924][2018-06-02 04:42:56.124185 local] Creating NEW connection to 149.154.162.26:80
[31923][2018-06-02 04:42:56.124305 local] New connection 192.168.10.10:38540 -> 91.108.4.202:8888
[31923][2018-06-02 04:42:56.124337 local] Creating NEW connection to 91.108.4.202:8888
[31924][2018-06-02 04:42:56.124393 local] New connection 192.168.10.10:56684 -> 149.154.162.26:80
[31924][2018-06-02 04:42:56.124427 local] Creating NEW connection to 149.154.162.26:80
[31923][2018-06-02 04:42:56.124541 local] New connection 192.168.10.10:38544 -> 91.108.4.202:8888
[31923][2018-06-02 04:42:56.124570 local] Creating NEW connection to 91.108.4.202:8888
[31924][2018-06-02 04:42:56.124675 local] New connection 192.168.10.10:56688 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.124723 local] New connection 192.168.10.10:38548 -> 91.108.4.202:8888
[31924][2018-06-02 04:42:56.124727 local] Creating NEW connection to 149.154.162.26:80
[31923][2018-06-02 04:42:56.124791 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.124947 local] New connection 192.168.10.10:34626 -> 149.154.162.35:80
[31924][2018-06-02 04:42:56.124949 local] New connection 192.168.10.10:56694 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.124977 local] Creating NEW connection to 149.154.162.35:80
[31924][2018-06-02 04:42:56.124984 local] Creating NEW connection to 149.154.162.26:80
[31924][2018-06-02 04:42:56.125146 local] New connection 192.168.10.10:56696 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.125160 local] New connection 192.168.10.10:34632 -> 149.154.162.35:80
[31924][2018-06-02 04:42:56.125187 local] Creating NEW connection to 91.108.4.202:8888
[31923][2018-06-02 04:42:56.125191 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.125329 local] New connection 192.168.10.10:34634 -> 149.154.162.35:80
[31924][2018-06-02 04:42:56.125354 local] New connection 192.168.10.10:38560 -> 91.108.4.202:8888
[31923][2018-06-02 04:42:56.125365 local] Creating NEW connection to 149.154.162.35:80
[31924][2018-06-02 04:42:56.125374 local] Creating NEW connection to 91.108.4.202:8888
[31923][2018-06-02 04:42:56.125496 local] New connection 192.168.10.10:34638 -> 149.154.162.35:80
[31923][2018-06-02 04:42:56.125528 local] Creating NEW connection to 91.108.4.130:8888
[31924][2018-06-02 04:42:56.125529 local] New connection 192.168.10.10:38564 -> 91.108.4.202:8888
[31924][2018-06-02 04:42:56.125547 local] Creating NEW connection to 91.108.4.202:8888
[31923][2018-06-02 04:42:56.125664 local] New connection 192.168.10.10:43614 -> 91.108.4.130:8888
[31923][2018-06-02 04:42:56.125697 local] Creating NEW connection to 91.108.4.130:8888
[31924][2018-06-02 04:42:56.125721 local] New connection 192.168.10.10:38568 -> 91.108.4.202:8888
[31924][2018-06-02 04:42:56.125767 local] Creating NEW connection to 91.108.4.202:8888
[31923][2018-06-02 04:42:56.125825 local] New connection 192.168.10.10:43618 -> 91.108.4.130:8888
[31923][2018-06-02 04:42:56.125836 local] Creating NEW connection to 91.108.4.130:8888
[31924][2018-06-02 04:42:56.125962 local] New connection 192.168.10.10:38572 -> 91.108.4.202:8888
[31923][2018-06-02 04:42:56.125971 local] New connection 192.168.10.10:43622 -> 91.108.4.130:8888
[31924][2018-06-02 04:42:56.125999 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.125998 local] Creating NEW connection to 91.108.4.130:8888
[31924][2018-06-02 04:42:56.126148 local] New connection 192.168.10.10:34652 -> 149.154.162.35:80
[31923][2018-06-02 04:42:56.126152 local] New connection 192.168.10.10:43626 -> 91.108.4.130:8888
[31924][2018-06-02 04:42:56.126180 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.126183 local] Creating NEW connection to 91.108.4.221:8888
[31923][2018-06-02 04:42:56.126306 local] New connection 192.168.10.10:33264 -> 91.108.4.221:8888
[31923][2018-06-02 04:42:56.126337 local] Creating NEW connection to 91.108.4.221:8888
[31924][2018-06-02 04:42:56.126338 local] New connection 192.168.10.10:34658 -> 149.154.162.35:80
[31924][2018-06-02 04:42:56.126353 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.126467 local] New connection 192.168.10.10:33268 -> 91.108.4.221:8888
[31923][2018-06-02 04:42:56.126500 local] Creating NEW connection to 91.108.4.221:8888
[31924][2018-06-02 04:42:56.126512 local] New connection 192.168.10.10:34662 -> 149.154.162.35:80
[31924][2018-06-02 04:42:56.126528 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.126629 local] New connection 192.168.10.10:33272 -> 91.108.4.221:8888
[31923][2018-06-02 04:42:56.126655 local] Creating NEW connection to 91.108.4.221:8888
[31924][2018-06-02 04:42:56.126713 local] New connection 192.168.10.10:34666 -> 149.154.162.35:80
[31924][2018-06-02 04:42:56.126748 local] Creating NEW connection to 91.108.4.130:8888
[31923][2018-06-02 04:42:56.126781 local] New connection 192.168.10.10:33276 -> 91.108.4.221:8888
[31923][2018-06-02 04:42:56.126809 local] Creating NEW connection to 91.108.4.191:8888
[31924][2018-06-02 04:42:56.126880 local] New connection 192.168.10.10:43642 -> 91.108.4.130:8888
[31924][2018-06-02 04:42:56.126914 local] Creating NEW connection to 91.108.4.130:8888
[31923][2018-06-02 04:42:56.126964 local] New connection 192.168.10.10:36716 -> 91.108.4.191:8888
[31923][2018-06-02 04:42:56.127002 local] Creating NEW connection to 91.108.4.191:8888
[31924][2018-06-02 04:42:56.127044 local] New connection 192.168.10.10:43646 -> 91.108.4.130:8888
[31924][2018-06-02 04:42:56.127056 local] Creating NEW connection to 91.108.4.130:8888
[31923][2018-06-02 04:42:56.127135 local] New connection 192.168.10.10:36720 -> 91.108.4.191:8888
[31923][2018-06-02 04:42:56.127170 local] Creating NEW connection to 91.108.4.191:8888
[31924][2018-06-02 04:42:56.127199 local] New connection 192.168.10.10:43650 -> 91.108.4.130:8888
[31924][2018-06-02 04:42:56.127234 local] Creating NEW connection to 91.108.4.130:8888
[31923][2018-06-02 04:42:56.127297 local] New connection 192.168.10.10:36724 -> 91.108.4.191:8888
[31923][2018-06-02 04:42:56.127328 local] Creating NEW connection to 91.108.4.191:8888
[31924][2018-06-02 04:42:56.127380 local] New connection 192.168.10.10:43654 -> 91.108.4.130:8888
[31924][2018-06-02 04:42:56.127414 local] Creating NEW connection to 91.108.4.221:8888
[31923][2018-06-02 04:42:56.127454 local] New connection 192.168.10.10:36728 -> 91.108.4.191:8888
[31923][2018-06-02 04:42:56.127488 local] Creating NEW connection to 91.108.4.193:8888
[31924][2018-06-02 04:42:56.127543 local] New connection 192.168.10.10:33294 -> 91.108.4.221:8888
[31924][2018-06-02 04:42:56.127574 local] Creating NEW connection to 91.108.4.221:8888
[31923][2018-06-02 04:42:56.127675 local] New connection 192.168.10.10:35492 -> 91.108.4.193:8888
[31923][2018-06-02 04:42:56.127716 local] Creating NEW connection to 91.108.4.193:8888
[31924][2018-06-02 04:42:56.127736 local] New connection 192.168.10.10:33298 -> 91.108.4.221:8888
[31924][2018-06-02 04:42:56.127751 local] Creating NEW connection to 91.108.4.221:8888
[31924][2018-06-02 04:42:56.127875 local] New connection 192.168.10.10:33302 -> 91.108.4.221:8888
[31923][2018-06-02 04:42:56.127880 local] New connection 192.168.10.10:35496 -> 91.108.4.193:8888
[31924][2018-06-02 04:42:56.127913 local] Creating NEW connection to 91.108.4.221:8888
[31923][2018-06-02 04:42:56.127917 local] Creating NEW connection to 91.108.4.193:8888
[31924][2018-06-02 04:42:56.128037 local] New connection 192.168.10.10:33304 -> 91.108.4.221:8888
[31924][2018-06-02 04:42:56.128064 local] Creating NEW connection to 91.108.4.191:8888
[31923][2018-06-02 04:42:56.128063 local] New connection 192.168.10.10:35502 -> 91.108.4.193:8888
[31923][2018-06-02 04:42:56.128096 local] Creating NEW connection to 91.108.4.193:8888
[31924][2018-06-02 04:42:56.128234 local] New connection 192.168.10.10:36744 -> 91.108.4.191:8888
[31923][2018-06-02 04:42:56.128250 local] New connection 192.168.10.10:35506 -> 91.108.4.193:8888
[31924][2018-06-02 04:42:56.128268 local] Creating NEW connection to 91.108.4.191:8888
[31923][2018-06-02 04:42:56.128272 local] Creating NEW connection to 91.108.4.158:8888
[31923][2018-06-02 04:42:56.128456 local] New connection 192.168.10.10:57944 -> 91.108.4.158:8888
[31923][2018-06-02 04:42:56.128488 local] Creating NEW connection to 91.108.4.158:8888
[31923][2018-06-02 04:42:56.128645 local] New connection 192.168.10.10:57946 -> 91.108.4.158:8888
[31923][2018-06-02 04:42:56.128660 local] Creating NEW connection to 91.108.4.158:8888
[31923][2018-06-02 04:42:56.128822 local] New connection 192.168.10.10:57948 -> 91.108.4.158:8888
[31923][2018-06-02 04:42:56.128837 local] Creating NEW connection to 91.108.4.158:8888
[31923][2018-06-02 04:42:56.128977 local] New connection 192.168.10.10:57950 -> 91.108.4.158:8888
[31923][2018-06-02 04:42:56.128993 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.129138 local] New connection 192.168.10.10:50990 -> 149.154.164.250:8888
[31923][2018-06-02 04:42:56.129150 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.129278 local] New connection 192.168.10.10:50992 -> 149.154.164.250:8888
[31923][2018-06-02 04:42:56.129291 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.129412 local] New connection 192.168.10.10:50994 -> 149.154.164.250:8888
[31923][2018-06-02 04:42:56.129425 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.129548 local] New connection 192.168.10.10:50996 -> 149.154.164.250:8888
[31923][2018-06-02 04:42:56.144340 local] got error for tcp socket #12, [91.108.4.136]:8888 : No route to host
[31923][2018-06-02 04:42:56.144407 local] Disconnected from RPC Middle-End (fd=12)
[31923][2018-06-02 04:42:56.144437 local] Closing connection socket #12
[31923][2018-06-02 04:42:56.145740 local] got error for tcp socket #13, [91.108.4.136]:8888 : No route to host
[31923][2018-06-02 04:42:56.145795 local] Disconnected from RPC Middle-End (fd=13)
[31923][2018-06-02 04:42:56.145810 local] Closing connection socket #13
[31923][2018-06-02 04:42:56.146968 local] got error for tcp socket #14, [91.108.4.136]:8888 : No route to host
[31923][2018-06-02 04:42:56.147029 local] Disconnected from RPC Middle-End (fd=14)
[31923][2018-06-02 04:42:56.147046 local] Closing connection socket #14
[31923][2018-06-02 04:42:56.147667 local] got error for tcp socket #15, [91.108.4.136]:8888 : No route to host
[31923][2018-06-02 04:42:56.147709 local] Disconnected from RPC Middle-End (fd=15)
[31923][2018-06-02 04:42:56.147721 local] Closing connection socket #15
[31923][2018-06-02 04:42:56.148637 local] got error for tcp socket #16, [91.108.4.186]:8888 : No route to host
[31923][2018-06-02 04:42:56.148680 local] Disconnected from RPC Middle-End (fd=16)
[31923][2018-06-02 04:42:56.148693 local] Closing connection socket #16
[31923][2018-06-02 04:42:56.149140 local] got error for tcp socket #17, [91.108.4.186]:8888 : No route to host
[31923][2018-06-02 04:42:56.149185 local] got error for tcp socket #18, [91.108.4.186]:8888 : No route to host
[31923][2018-06-02 04:42:56.149198 local] Disconnected from RPC Middle-End (fd=17)
[31924][2018-06-02 04:42:56.149280 local] New connection 192.168.10.10:36764 -> 91.108.4.191:8888
[31923][2018-06-02 04:42:56.149294 local] Disconnected from RPC Middle-End (fd=18)
[31924][2018-06-02 04:42:56.149309 local] Creating NEW connection to 91.108.4.191:8888
[31923][2018-06-02 04:42:56.149310 local] Closing connection socket #17
[31923][2018-06-02 04:42:56.149402 local] Closing connection socket #18
[31924][2018-06-02 04:42:56.149487 local] New connection 192.168.10.10:36766 -> 91.108.4.191:8888
[31924][2018-06-02 04:42:56.149525 local] Creating NEW connection to 91.108.4.191:8888
[31923][2018-06-02 04:42:56.149550 local] got error for tcp socket #19, [91.108.4.186]:8888 : No route to host
[31923][2018-06-02 04:42:56.149571 local] Disconnected from RPC Middle-End (fd=19)
[31923][2018-06-02 04:42:56.149611 local] Closing connection socket #19
[31924][2018-06-02 04:42:56.149659 local] New connection 192.168.10.10:36768 -> 91.108.4.191:8888
[31924][2018-06-02 04:42:56.149696 local] Creating NEW connection to 91.108.4.193:8888
[31923][2018-06-02 04:42:56.149795 local] got error for tcp socket #36, [91.108.4.139]:8888 : No route to host
[31924][2018-06-02 04:42:56.149839 local] New connection 192.168.10.10:35530 -> 91.108.4.193:8888
[31924][2018-06-02 04:42:56.149851 local] Creating NEW connection to 91.108.4.193:8888
[31923][2018-06-02 04:42:56.149847 local] got error for tcp socket #38, [91.108.4.139]:8888 : No route to host
[31923][2018-06-02 04:42:56.149896 local] got error for tcp socket #37, [91.108.4.139]:8888 : No route to host
[31923][2018-06-02 04:42:56.149932 local] Disconnected from RPC Middle-End (fd=36)
[31923][2018-06-02 04:42:56.149971 local] Disconnected from RPC Middle-End (fd=38)
[31923][2018-06-02 04:42:56.149982 local] Disconnected from RPC Middle-End (fd=37)
[31923][2018-06-02 04:42:56.150000 local] Closing connection socket #36
[31923][2018-06-02 04:42:56.150023 local] Closing connection socket #38
[31924][2018-06-02 04:42:56.150031 local] New connection 192.168.10.10:35532 -> 91.108.4.193:8888
[31923][2018-06-02 04:42:56.150050 local] Closing connection socket #37
[31924][2018-06-02 04:42:56.150055 local] Creating NEW connection to 91.108.4.193:8888
[31923][2018-06-02 04:42:56.150188 local] got error for tcp socket #39, [91.108.4.139]:8888 : No route to host
[31923][2018-06-02 04:42:56.150233 local] got error for tcp socket #42, [91.108.4.169]:8888 : No route to host
[31924][2018-06-02 04:42:56.150237 local] New connection 192.168.10.10:35534 -> 91.108.4.193:8888
[31923][2018-06-02 04:42:56.150246 local] got error for tcp socket #41, [91.108.4.169]:8888 : No route to host
[31923][2018-06-02 04:42:56.150257 local] got error for tcp socket #40, [91.108.4.169]:8888 : No route to host
[31923][2018-06-02 04:42:56.150267 local] Disconnected from RPC Middle-End (fd=39)
[31924][2018-06-02 04:42:56.150273 local] Creating NEW connection to 91.108.4.193:8888
[31923][2018-06-02 04:42:56.150278 local] Disconnected from RPC Middle-End (fd=42)
[31923][2018-06-02 04:42:56.150285 local] Disconnected from RPC Middle-End (fd=41)
[31923][2018-06-02 04:42:56.150293 local] Disconnected from RPC Middle-End (fd=40)
[31923][2018-06-02 04:42:56.150315 local] Closing connection socket #39
[31923][2018-06-02 04:42:56.150359 local] Closing connection socket #42
[31923][2018-06-02 04:42:56.150381 local] Closing connection socket #41
[31923][2018-06-02 04:42:56.150393 local] Closing connection socket #40
[31924][2018-06-02 04:42:56.150431 local] New connection 192.168.10.10:35536 -> 91.108.4.193:8888
[31924][2018-06-02 04:42:56.150445 local] Creating NEW connection to 91.108.4.158:8888
[31923][2018-06-02 04:42:56.150479 local] got error for tcp socket #43, [91.108.4.169]:8888 : No route to host
[31923][2018-06-02 04:42:56.150497 local] got error for tcp socket #56, [91.108.4.130]:8888 : No route to host
[31923][2018-06-02 04:42:56.150527 local] got error for tcp socket #51, [91.108.4.202]:8888 : No route to host
[31923][2018-06-02 04:42:56.150538 local] got error for tcp socket #50, [91.108.4.202]:8888 : No route to host
[31923][2018-06-02 04:42:56.150554 local] got error for tcp socket #49, [91.108.4.202]:8888 : No route to host
[31923][2018-06-02 04:42:56.150568 local] got error for tcp socket #48, [91.108.4.202]:8888 : No route to host
[31923][2018-06-02 04:42:56.150597 local] Disconnected from RPC Middle-End (fd=43)
[31923][2018-06-02 04:42:56.150604 local] Disconnected from RPC Middle-End (fd=56)
[31924][2018-06-02 04:42:56.150601 local] New connection 192.168.10.10:57974 -> 91.108.4.158:8888
[31923][2018-06-02 04:42:56.150610 local] Disconnected from RPC Middle-End (fd=51)
[31923][2018-06-02 04:42:56.150616 local] Disconnected from RPC Middle-End (fd=50)
[31923][2018-06-02 04:42:56.150622 local] Disconnected from RPC Middle-End (fd=49)
[31923][2018-06-02 04:42:56.150636 local] Disconnected from RPC Middle-End (fd=48)
[31924][2018-06-02 04:42:56.150622 local] Creating NEW connection to 91.108.4.158:8888
[31923][2018-06-02 04:42:56.150667 local] Closing connection socket #43
[31923][2018-06-02 04:42:56.150681 local] Closing connection socket #56
[31923][2018-06-02 04:42:56.150692 local] Closing connection socket #51
[31923][2018-06-02 04:42:56.150721 local] Closing connection socket #50
[31923][2018-06-02 04:42:56.150733 local] Closing connection socket #49
[31923][2018-06-02 04:42:56.150761 local] Closing connection socket #48
[31924][2018-06-02 04:42:56.150840 local] New connection 192.168.10.10:57976 -> 91.108.4.158:8888
[31923][2018-06-02 04:42:56.150855 local] got error for tcp socket #57, [91.108.4.130]:8888 : No route to host
[31923][2018-06-02 04:42:56.150875 local] got error for tcp socket #58, [91.108.4.130]:8888 : No route to host
[31924][2018-06-02 04:42:56.150875 local] Creating NEW connection to 91.108.4.158:8888
[31923][2018-06-02 04:42:56.150886 local] Disconnected from RPC Middle-End (fd=57)
[31923][2018-06-02 04:42:56.150921 local] Disconnected from RPC Middle-End (fd=58)
[31923][2018-06-02 04:42:56.150949 local] Closing connection socket #57
[31923][2018-06-02 04:42:56.150968 local] Closing connection socket #58
[31924][2018-06-02 04:42:56.151036 local] New connection 192.168.10.10:57978 -> 91.108.4.158:8888
[31923][2018-06-02 04:42:56.151068 local] got error for tcp socket #59, [91.108.4.130]:8888 : No route to host
[31924][2018-06-02 04:42:56.151082 local] Creating NEW connection to 91.108.4.158:8888
[31923][2018-06-02 04:42:56.151084 local] Disconnected from RPC Middle-End (fd=59)
[31923][2018-06-02 04:42:56.151130 local] Closing connection socket #59
[31924][2018-06-02 04:42:56.151227 local] New connection 192.168.10.10:57980 -> 91.108.4.158:8888
[31924][2018-06-02 04:42:56.151263 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.151366 local] got error for tcp socket #60, [91.108.4.221]:8888 : No route to host
[31923][2018-06-02 04:42:56.151401 local] Disconnected from RPC Middle-End (fd=60)
[31923][2018-06-02 04:42:56.151420 local] Closing connection socket #60
[31924][2018-06-02 04:42:56.151426 local] New connection 192.168.10.10:51020 -> 149.154.164.250:8888
[31924][2018-06-02 04:42:56.151439 local] Creating NEW connection to 149.154.164.250:8888
[31924][2018-06-02 04:42:56.151589 local] New connection 192.168.10.10:51022 -> 149.154.164.250:8888
[31924][2018-06-02 04:42:56.151626 local] Creating NEW connection to 149.154.164.250:8888
[31924][2018-06-02 04:42:56.151793 local] New connection 192.168.10.10:51024 -> 149.154.164.250:8888
[31924][2018-06-02 04:42:56.151830 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.151937 local] got error for tcp socket #61, [91.108.4.221]:8888 : No route to host
[31924][2018-06-02 04:42:56.151966 local] New connection 192.168.10.10:51026 -> 149.154.164.250:8888
[31923][2018-06-02 04:42:56.151970 local] Disconnected from RPC Middle-End (fd=61)
[31923][2018-06-02 04:42:56.151981 local] Closing connection socket #61
[31924][2018-06-02 04:42:56.152119 local] got error for tcp socket #11, [91.108.4.136]:8888 : No route to host
[31923][2018-06-02 04:42:56.152149 local] got error for tcp socket #62, [91.108.4.221]:8888 : No route to host
[31924][2018-06-02 04:42:56.152171 local] got error for tcp socket #50, [91.108.4.202]:8888 : No route to host
[31923][2018-06-02 04:42:56.152171 local] Disconnected from RPC Middle-End (fd=62)
[31924][2018-06-02 04:42:56.152184 local] got error for tcp socket #49, [91.108.4.202]:8888 : No route to host
[31923][2018-06-02 04:42:56.152185 local] Closing connection socket #62
[31924][2018-06-02 04:42:56.152195 local] got error for tcp socket #48, [91.108.4.202]:8888 : No route to host
[31924][2018-06-02 04:42:56.152205 local] got error for tcp socket #47, [91.108.4.202]:8888 : No route to host
[31924][2018-06-02 04:42:56.152234 local] got error for tcp socket #42, [91.108.4.169]:8888 : No route to host
[31924][2018-06-02 04:42:56.152263 local] got error for tcp socket #41, [91.108.4.169]:8888 : No route to host
[31924][2018-06-02 04:42:56.152281 local] got error for tcp socket #40, [91.108.4.169]:8888 : No route to host
[31924][2018-06-02 04:42:56.152302 local] got error for tcp socket #38, [91.108.4.139]:8888 : No route to host
[31924][2018-06-02 04:42:56.152333 local] got error for tcp socket #39, [91.108.4.169]:8888 : No route to host
[31924][2018-06-02 04:42:56.152361 local] got error for tcp socket #37, [91.108.4.139]:8888 : No route to host
[31924][2018-06-02 04:42:56.152388 local] got error for tcp socket #36, [91.108.4.139]:8888 : No route to host
[31924][2018-06-02 04:42:56.152421 local] got error for tcp socket #35, [91.108.4.139]:8888 : No route to host
[31924][2018-06-02 04:42:56.152466 local] got error for tcp socket #18, [91.108.4.186]:8888 : No route to host
[31924][2018-06-02 04:42:56.152494 local] got error for tcp socket #17, [91.108.4.186]:8888 : No route to host
[31924][2018-06-02 04:42:56.152521 local] got error for tcp socket #16, [91.108.4.186]:8888 : No route to host
[31924][2018-06-02 04:42:56.152553 local] got error for tcp socket #15, [91.108.4.186]:8888 : No route to host
[31924][2018-06-02 04:42:56.152581 local] got error for tcp socket #14, [91.108.4.136]:8888 : No route to host
[31924][2018-06-02 04:42:56.152596 local] got error for tcp socket #13, [91.108.4.136]:8888 : No route to host
[31924][2018-06-02 04:42:56.152623 local] got error for tcp socket #12, [91.108.4.136]:8888 : No route to host
[31924][2018-06-02 04:42:56.152646 local] Disconnected from RPC Middle-End (fd=11)
[31924][2018-06-02 04:42:56.152672 local] Disconnected from RPC Middle-End (fd=50)
[31924][2018-06-02 04:42:56.152679 local] Disconnected from RPC Middle-End (fd=49)
[31924][2018-06-02 04:42:56.152685 local] Disconnected from RPC Middle-End (fd=48)
[31924][2018-06-02 04:42:56.152705 local] Disconnected from RPC Middle-End (fd=47)
[31924][2018-06-02 04:42:56.152712 local] Disconnected from RPC Middle-End (fd=42)
[31924][2018-06-02 04:42:56.152717 local] Disconnected from RPC Middle-End (fd=41)
[31924][2018-06-02 04:42:56.152722 local] Disconnected from RPC Middle-End (fd=40)
[31924][2018-06-02 04:42:56.152727 local] Disconnected from RPC Middle-End (fd=38)
[31924][2018-06-02 04:42:56.152732 local] Disconnected from RPC Middle-End (fd=39)
[31924][2018-06-02 04:42:56.152752 local] Disconnected from RPC Middle-End (fd=37)
[31924][2018-06-02 04:42:56.152759 local] Disconnected from RPC Middle-End (fd=36)
[31924][2018-06-02 04:42:56.152764 local] Disconnected from RPC Middle-End (fd=35)
[31924][2018-06-02 04:42:56.152769 local] Disconnected from RPC Middle-End (fd=18)
[31924][2018-06-02 04:42:56.152792 local] Disconnected from RPC Middle-End (fd=17)
[31924][2018-06-02 04:42:56.152814 local] Disconnected from RPC Middle-End (fd=16)
[31924][2018-06-02 04:42:56.152836 local] Disconnected from RPC Middle-End (fd=15)
[31924][2018-06-02 04:42:56.152857 local] Disconnected from RPC Middle-End (fd=14)
[31924][2018-06-02 04:42:56.152879 local] Disconnected from RPC Middle-End (fd=13)
[31924][2018-06-02 04:42:56.152921 local] Disconnected from RPC Middle-End (fd=12)
[31924][2018-06-02 04:42:56.152998 local] Closing connection socket #11
[31923][2018-06-02 04:42:56.153006 local] got error for tcp socket #63, [91.108.4.221]:8888 : No route to host
[31923][2018-06-02 04:42:56.153041 local] Disconnected from RPC Middle-End (fd=63)
[31924][2018-06-02 04:42:56.153044 local] Closing connection socket #50
[31923][2018-06-02 04:42:56.153109 local] Closing connection socket #63
[31924][2018-06-02 04:42:56.153154 local] Closing connection socket #49
[31924][2018-06-02 04:42:56.153210 local] Closing connection socket #48
[31924][2018-06-02 04:42:56.153258 local] Closing connection socket #47
[31924][2018-06-02 04:42:56.153312 local] Closing connection socket #42
[31924][2018-06-02 04:42:56.153347 local] Closing connection socket #41
[31924][2018-06-02 04:42:56.153389 local] Closing connection socket #40
[31924][2018-06-02 04:42:56.153452 local] Closing connection socket #38
[31924][2018-06-02 04:42:56.153492 local] Closing connection socket #39
[31924][2018-06-02 04:42:56.153561 local] Closing connection socket #37
[31924][2018-06-02 04:42:56.153615 local] Closing connection socket #36
[31924][2018-06-02 04:42:56.153649 local] Closing connection socket #35
[31924][2018-06-02 04:42:56.153669 local] Closing connection socket #18
[31924][2018-06-02 04:42:56.153716 local] Closing connection socket #17
[31924][2018-06-02 04:42:56.153773 local] Closing connection socket #16
[31923][2018-06-02 04:42:56.153794 local] got error for tcp socket #64, [91.108.4.191]:8888 : No route to host
[31924][2018-06-02 04:42:56.153803 local] Closing connection socket #15
[31923][2018-06-02 04:42:56.153835 local] Disconnected from RPC Middle-End (fd=64)
[31924][2018-06-02 04:42:56.153839 local] Closing connection socket #14
[31923][2018-06-02 04:42:56.153936 local] Closing connection socket #64
[31924][2018-06-02 04:42:56.153976 local] Closing connection socket #13
[31924][2018-06-02 04:42:56.154012 local] Closing connection socket #12
[31924][2018-06-02 04:42:56.154196 local] got error for tcp socket #55, [91.108.4.130]:8888 : No route to host
[31924][2018-06-02 04:42:56.154245 local] got error for tcp socket #56, [91.108.4.130]:8888 : No route to host
[31924][2018-06-02 04:42:56.154258 local] Disconnected from RPC Middle-End (fd=55)
[31924][2018-06-02 04:42:56.154267 local] Disconnected from RPC Middle-End (fd=56)
[31924][2018-06-02 04:42:56.154277 local] Closing connection socket #55
[31923][2018-06-02 04:42:56.154310 local] got error for tcp socket #65, [91.108.4.191]:8888 : No route to host
[31924][2018-06-02 04:42:56.154311 local] Closing connection socket #56
[31923][2018-06-02 04:42:56.154329 local] Disconnected from RPC Middle-End (fd=65)
[31923][2018-06-02 04:42:56.154372 local] Closing connection socket #65
[31924][2018-06-02 04:42:56.154628 local] got error for tcp socket #57, [91.108.4.130]:8888 : No route to host
[31924][2018-06-02 04:42:56.154663 local] Disconnected from RPC Middle-End (fd=57)
[31924][2018-06-02 04:42:56.154674 local] Closing connection socket #57
[31923][2018-06-02 04:42:56.154920 local] got error for tcp socket #66, [91.108.4.191]:8888 : No route to host
[31923][2018-06-02 04:42:56.154967 local] Disconnected from RPC Middle-End (fd=66)
[31923][2018-06-02 04:42:56.154979 local] Closing connection socket #66
[31924][2018-06-02 04:42:56.155111 local] got error for tcp socket #58, [91.108.4.130]:8888 : No route to host
[31924][2018-06-02 04:42:56.155146 local] Disconnected from RPC Middle-End (fd=58)
[31923][2018-06-02 04:42:56.155153 local] got error for tcp socket #67, [91.108.4.191]:8888 : No route to host
[31924][2018-06-02 04:42:56.155166 local] Closing connection socket #58
[31923][2018-06-02 04:42:56.155184 local] Disconnected from RPC Middle-End (fd=67)
[31923][2018-06-02 04:42:56.155212 local] Closing connection socket #67
[31924][2018-06-02 04:42:56.155306 local] got error for tcp socket #61, [91.108.4.221]:8888 : No route to host
[31924][2018-06-02 04:42:56.155357 local] Disconnected from RPC Middle-End (fd=61)
[31924][2018-06-02 04:42:56.155387 local] Closing connection socket #61
[31924][2018-06-02 04:42:56.155656 local] got error for tcp socket #59, [91.108.4.221]:8888 : No route to host
[31924][2018-06-02 04:42:56.155689 local] Disconnected from RPC Middle-End (fd=59)
[31924][2018-06-02 04:42:56.155701 local] Closing connection socket #59
[31923][2018-06-02 04:42:56.155885 local] got error for tcp socket #68, [91.108.4.193]:8888 : No route to host
[31924][2018-06-02 04:42:56.155901 local] got error for tcp socket #60, [91.108.4.221]:8888 : No route to host
[31923][2018-06-02 04:42:56.155905 local] got error for tcp socket #74, [91.108.4.158]:8888 : No route to host
[31924][2018-06-02 04:42:56.155924 local] got error for tcp socket #62, [91.108.4.221]:8888 : No route to host
[31923][2018-06-02 04:42:56.155929 local] got error for tcp socket #69, [91.108.4.193]:8888 : No route to host
[31924][2018-06-02 04:42:56.155936 local] Disconnected from RPC Middle-End (fd=60)
[31923][2018-06-02 04:42:56.155941 local] got error for tcp socket #73, [91.108.4.158]:8888 : No route to host
[31924][2018-06-02 04:42:56.155944 local] Disconnected from RPC Middle-End (fd=62)
[31923][2018-06-02 04:42:56.155952 local] Disconnected from RPC Middle-End (fd=68)
[31924][2018-06-02 04:42:56.155954 local] Closing connection socket #60
[31923][2018-06-02 04:42:56.155957 local] Disconnected from RPC Middle-End (fd=74)
[31923][2018-06-02 04:42:56.155963 local] Disconnected from RPC Middle-End (fd=69)
[31924][2018-06-02 04:42:56.155966 local] Closing connection socket #62
[31923][2018-06-02 04:42:56.155968 local] Disconnected from RPC Middle-End (fd=73)
[31923][2018-06-02 04:42:56.155983 local] Closing connection socket #68
[31923][2018-06-02 04:42:56.155998 local] Closing connection socket #74
[31923][2018-06-02 04:42:56.156010 local] Closing connection socket #69
[31923][2018-06-02 04:42:56.156020 local] Closing connection socket #73
[31924][2018-06-02 04:42:56.156081 local] got error for tcp socket #63, [91.108.4.191]:8888 : No route to host
[31924][2018-06-02 04:42:56.156107 local] Disconnected from RPC Middle-End (fd=63)
[31924][2018-06-02 04:42:56.156137 local] Closing connection socket #63
[31923][2018-06-02 04:42:56.156141 local] got error for tcp socket #70, [91.108.4.193]:8888 : No route to host
[31923][2018-06-02 04:42:56.156153 local] Disconnected from RPC Middle-End (fd=70)
[31923][2018-06-02 04:42:56.156162 local] Closing connection socket #70
[31923][2018-06-02 04:42:56.156275 local] got error for tcp socket #71, [91.108.4.193]:8888 : No route to host
[31923][2018-06-02 04:42:56.156307 local] Disconnected from RPC Middle-End (fd=71)
[31923][2018-06-02 04:42:56.156317 local] Closing connection socket #71
[31923][2018-06-02 04:42:56.156759 local] got error for tcp socket #72, [91.108.4.158]:8888 : No route to host
[31923][2018-06-02 04:42:56.156796 local] got error for tcp socket #75, [91.108.4.158]:8888 : No route to host
[31923][2018-06-02 04:42:56.156808 local] Disconnected from RPC Middle-End (fd=72)
[31923][2018-06-02 04:42:56.156815 local] Disconnected from RPC Middle-End (fd=75)
[31923][2018-06-02 04:42:56.156843 local] Closing connection socket #72
[31923][2018-06-02 04:42:56.156856 local] Closing connection socket #75
[31924][2018-06-02 04:42:56.159668 local] got error for tcp socket #64, [91.108.4.191]:8888 : No route to host
[31924][2018-06-02 04:42:56.159699 local] Disconnected from RPC Middle-End (fd=64)
[31924][2018-06-02 04:42:56.159709 local] Closing connection socket #64
[31924][2018-06-02 04:42:56.160054 local] got error for tcp socket #65, [91.108.4.191]:8888 : No route to host
[31924][2018-06-02 04:42:56.160089 local] Disconnected from RPC Middle-End (fd=65)
[31924][2018-06-02 04:42:56.160101 local] Closing connection socket #65
[31924][2018-06-02 04:42:56.160211 local] got error for tcp socket #66, [91.108.4.191]:8888 : No route to host
[31924][2018-06-02 04:42:56.160245 local] Disconnected from RPC Middle-End (fd=66)
[31924][2018-06-02 04:42:56.160261 local] Closing connection socket #66
[31924][2018-06-02 04:42:56.160393 local] got error for tcp socket #67, [91.108.4.193]:8888 : No route to host
[31924][2018-06-02 04:42:56.160427 local] Disconnected from RPC Middle-End (fd=67)
[31924][2018-06-02 04:42:56.160440 local] Closing connection socket #67
[31924][2018-06-02 04:42:56.160613 local] got error for tcp socket #68, [91.108.4.193]:8888 : No route to host
[31924][2018-06-02 04:42:56.160651 local] Disconnected from RPC Middle-End (fd=68)
[31924][2018-06-02 04:42:56.160664 local] Closing connection socket #68
[31924][2018-06-02 04:42:56.161145 local] got error for tcp socket #69, [91.108.4.193]:8888 : No route to host
[31924][2018-06-02 04:42:56.161184 local] Disconnected from RPC Middle-End (fd=69)
[31924][2018-06-02 04:42:56.161194 local] Closing connection socket #69
[31924][2018-06-02 04:42:56.161420 local] got error for tcp socket #70, [91.108.4.193]:8888 : No route to host
[31924][2018-06-02 04:42:56.161464 local] got error for tcp socket #71, [91.108.4.158]:8888 : No route to host
[31924][2018-06-02 04:42:56.161474 local] Disconnected from RPC Middle-End (fd=70)
[31924][2018-06-02 04:42:56.161480 local] Disconnected from RPC Middle-End (fd=71)
[31924][2018-06-02 04:42:56.161490 local] Closing connection socket #70
[31924][2018-06-02 04:42:56.161521 local] Closing connection socket #71
[31924][2018-06-02 04:42:56.161881 local] got error for tcp socket #72, [91.108.4.158]:8888 : No route to host
[31924][2018-06-02 04:42:56.161913 local] Disconnected from RPC Middle-End (fd=72)
[31924][2018-06-02 04:42:56.161924 local] Closing connection socket #72
[31924][2018-06-02 04:42:56.162071 local] got error for tcp socket #73, [91.108.4.158]:8888 : No route to host
[31924][2018-06-02 04:42:56.162108 local] Disconnected from RPC Middle-End (fd=73)
[31924][2018-06-02 04:42:56.162161 local] Closing connection socket #73
[31924][2018-06-02 04:42:56.162324 local] got error for tcp socket #74, [91.108.4.158]:8888 : No route to host
[31924][2018-06-02 04:42:56.162348 local] Disconnected from RPC Middle-End (fd=74)
[31924][2018-06-02 04:42:56.162360 local] Closing connection socket #74
[31924][2018-06-02 04:42:56.393328 local] socket 19: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.393426 local] Disconnected from RPC Middle-End (fd=19)
[31924][2018-06-02 04:42:56.393457 local] Creating NEW connection to 149.154.165.250:8888
[31924][2018-06-02 04:42:56.393779 local] New connection 192.168.10.10:43046 -> 149.154.165.250:8888
[31924][2018-06-02 04:42:56.393852 local] Closing connection socket #19
[31924][2018-06-02 04:42:56.405752 local] socket 22: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.405840 local] Disconnected from RPC Middle-End (fd=22)
[31924][2018-06-02 04:42:56.405868 local] Creating NEW connection to 149.154.165.250:8888
[31924][2018-06-02 04:42:56.406220 local] New connection 192.168.10.10:43048 -> 149.154.165.250:8888
[31924][2018-06-02 04:42:56.406289 local] Closing connection socket #22
[31924][2018-06-02 04:42:56.409678 local] socket 21: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.409754 local] Disconnected from RPC Middle-End (fd=21)
[31924][2018-06-02 04:42:56.409782 local] Creating NEW connection to 149.154.165.250:8888
[31924][2018-06-02 04:42:56.410090 local] New connection 192.168.10.10:43050 -> 149.154.165.250:8888
[31924][2018-06-02 04:42:56.410163 local] Closing connection socket #21
[31924][2018-06-02 04:42:56.433473 local] socket 20: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.433590 local] Disconnected from RPC Middle-End (fd=20)
[31924][2018-06-02 04:42:56.433675 local] Closing connection socket #20
[31923][2018-06-02 04:42:56.436998 local] socket 21: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.437117 local] Disconnected from RPC Middle-End (fd=21)
[31923][2018-06-02 04:42:56.437150 local] Creating NEW connection to 149.154.165.250:8888
[31923][2018-06-02 04:42:56.437452 local] New connection 192.168.10.10:43052 -> 149.154.165.250:8888
[31923][2018-06-02 04:42:56.437529 local] Closing connection socket #21
[31923][2018-06-02 04:42:56.437709 local] socket 23: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.437784 local] socket 47: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.437805 local] socket 46: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.437842 local] socket 22: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.437895 local] socket 44: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.437926 local] Disconnected from RPC Middle-End (fd=23)
[31923][2018-06-02 04:42:56.437972 local] Disconnected from RPC Middle-End (fd=47)
[31923][2018-06-02 04:42:56.437987 local] Disconnected from RPC Middle-End (fd=46)
[31923][2018-06-02 04:42:56.438000 local] Disconnected from RPC Middle-End (fd=22)
[31923][2018-06-02 04:42:56.438043 local] Disconnected from RPC Middle-End (fd=44)
[31923][2018-06-02 04:42:56.438068 local] Creating NEW connection to 149.154.165.250:8888
[31923][2018-06-02 04:42:56.438443 local] New connection 192.168.10.10:43054 -> 149.154.165.250:8888
[31923][2018-06-02 04:42:56.438517 local] Creating NEW connection to 149.154.165.250:8888
[31923][2018-06-02 04:42:56.438953 local] New connection 192.168.10.10:43056 -> 149.154.165.250:8888
[31923][2018-06-02 04:42:56.439066 local] Creating NEW connection to 149.154.162.26:80
[31923][2018-06-02 04:42:56.439406 local] New connection 192.168.10.10:56828 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.439472 local] Creating NEW connection to 149.154.162.26:80
[31923][2018-06-02 04:42:56.439873 local] New connection 192.168.10.10:56830 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.439941 local] Creating NEW connection to 149.154.162.26:80
[31923][2018-06-02 04:42:56.440281 local] New connection 192.168.10.10:56832 -> 149.154.162.26:80
[31923][2018-06-02 04:42:56.440357 local] Closing connection socket #23
[31923][2018-06-02 04:42:56.440428 local] Closing connection socket #47
[31923][2018-06-02 04:42:56.440528 local] Closing connection socket #46
[31923][2018-06-02 04:42:56.440636 local] Closing connection socket #22
[31923][2018-06-02 04:42:56.440714 local] Closing connection socket #44
[31924][2018-06-02 04:42:56.441769 local] socket 43: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.441840 local] Disconnected from RPC Middle-End (fd=43)
[31924][2018-06-02 04:42:56.441866 local] Creating NEW connection to 149.154.162.26:80
[31924][2018-06-02 04:42:56.442234 local] New connection 192.168.10.10:56834 -> 149.154.162.26:80
[31924][2018-06-02 04:42:56.442305 local] Closing connection socket #43
[31923][2018-06-02 04:42:56.445000 local] socket 45: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.445012 local] socket 44: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.445144 local] socket 76: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.445212 local] socket 52: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.445211 local] socket 45: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.445234 local] Disconnected from RPC Middle-End (fd=45)
[31923][2018-06-02 04:42:56.445247 local] Disconnected from RPC Middle-End (fd=76)
[31924][2018-06-02 04:42:56.445246 local] socket 46: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.445258 local] Disconnected from RPC Middle-End (fd=52)
[31923][2018-06-02 04:42:56.445341 local] Creating NEW connection to 149.154.164.250:8888
[31924][2018-06-02 04:42:56.445341 local] Disconnected from RPC Middle-End (fd=44)
[31924][2018-06-02 04:42:56.445400 local] Disconnected from RPC Middle-End (fd=45)
[31924][2018-06-02 04:42:56.445421 local] Disconnected from RPC Middle-End (fd=46)
[31924][2018-06-02 04:42:56.445459 local] Closing connection socket #44
[31924][2018-06-02 04:42:56.445602 local] Closing connection socket #45
[31924][2018-06-02 04:42:56.445693 local] Closing connection socket #46
[31923][2018-06-02 04:42:56.445711 local] New connection 192.168.10.10:51048 -> 149.154.164.250:8888
[31923][2018-06-02 04:42:56.445776 local] Creating NEW connection to 149.154.162.35:80
[31924][2018-06-02 04:42:56.445914 local] socket 52: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.446024 local] socket 51: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.446134 local] Disconnected from RPC Middle-End (fd=52)
[31924][2018-06-02 04:42:56.446221 local] Disconnected from RPC Middle-End (fd=51)
[31923][2018-06-02 04:42:56.446242 local] New connection 192.168.10.10:34772 -> 149.154.162.35:80
[31924][2018-06-02 04:42:56.446273 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.446328 local] Closing connection socket #45
[31923][2018-06-02 04:42:56.446377 local] Closing connection socket #76
[31923][2018-06-02 04:42:56.446422 local] Closing connection socket #52
[31923][2018-06-02 04:42:56.446598 local] socket 79: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.446693 local] Disconnected from RPC Middle-End (fd=79)
[31924][2018-06-02 04:42:56.446723 local] New connection 192.168.10.10:34774 -> 149.154.162.35:80
[31923][2018-06-02 04:42:56.446750 local] Creating NEW connection to 149.154.164.250:8888
[31924][2018-06-02 04:42:56.446773 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.447127 local] New connection 192.168.10.10:51054 -> 149.154.164.250:8888
[31924][2018-06-02 04:42:56.447189 local] New connection 192.168.10.10:34778 -> 149.154.162.35:80
[31923][2018-06-02 04:42:56.447211 local] Closing connection socket #79
[31924][2018-06-02 04:42:56.447229 local] Closing connection socket #52
[31924][2018-06-02 04:42:56.447278 local] Closing connection socket #51
[31923][2018-06-02 04:42:56.448499 local] socket 78: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.448542 local] Disconnected from RPC Middle-End (fd=78)
[31923][2018-06-02 04:42:56.448556 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.448756 local] New connection 192.168.10.10:51058 -> 149.154.164.250:8888
[31924][2018-06-02 04:42:56.448759 local] socket 53: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.448791 local] Disconnected from RPC Middle-End (fd=53)
[31923][2018-06-02 04:42:56.448792 local] Closing connection socket #78
[31924][2018-06-02 04:42:56.448802 local] Creating NEW connection to 149.154.162.35:80
[31924][2018-06-02 04:42:56.448954 local] New connection 192.168.10.10:34782 -> 149.154.162.35:80
[31924][2018-06-02 04:42:56.448988 local] Closing connection socket #53
[31923][2018-06-02 04:42:56.452810 local] socket 54: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.452815 local] socket 76: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.452836 local] socket 77: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.452838 local] socket 75: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.452861 local] socket 53: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.452892 local] socket 78: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.452894 local] Disconnected from RPC Middle-End (fd=54)
[31923][2018-06-02 04:42:56.452911 local] Disconnected from RPC Middle-End (fd=77)
[31923][2018-06-02 04:42:56.452917 local] Disconnected from RPC Middle-End (fd=53)
[31924][2018-06-02 04:42:56.452915 local] Disconnected from RPC Middle-End (fd=76)
[31924][2018-06-02 04:42:56.452941 local] Disconnected from RPC Middle-End (fd=75)
[31924][2018-06-02 04:42:56.452947 local] Disconnected from RPC Middle-End (fd=78)
[31923][2018-06-02 04:42:56.452946 local] Creating NEW connection to 149.154.162.35:80
[31924][2018-06-02 04:42:56.452999 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.453095 local] New connection 192.168.10.10:34784 -> 149.154.162.35:80
[31923][2018-06-02 04:42:56.453128 local] Creating NEW connection to 149.154.162.35:80
[31923][2018-06-02 04:42:56.453273 local] New connection 192.168.10.10:34788 -> 149.154.162.35:80
[31923][2018-06-02 04:42:56.453309 local] Closing connection socket #54
[31924][2018-06-02 04:42:56.453285 local] New connection 192.168.10.10:51064 -> 149.154.164.250:8888
[31924][2018-06-02 04:42:56.453327 local] Creating NEW connection to 149.154.164.250:8888
[31923][2018-06-02 04:42:56.453329 local] Closing connection socket #77
[31923][2018-06-02 04:42:56.453378 local] Closing connection socket #53
[31923][2018-06-02 04:42:56.453498 local] socket 55: disconnected (epoll_ready=2005), cleaning
[31923][2018-06-02 04:42:56.453539 local] Disconnected from RPC Middle-End (fd=55)
[31923][2018-06-02 04:42:56.453556 local] Closing connection socket #55
[31924][2018-06-02 04:42:56.453571 local] New connection 192.168.10.10:51068 -> 149.154.164.250:8888
[31924][2018-06-02 04:42:56.453625 local] Creating NEW connection to 149.154.164.250:8888
[31924][2018-06-02 04:42:56.453838 local] New connection 192.168.10.10:51070 -> 149.154.164.250:8888
[31924][2018-06-02 04:42:56.453894 local] Closing connection socket #76
[31924][2018-06-02 04:42:56.453950 local] Closing connection socket #75
[31924][2018-06-02 04:42:56.454030 local] Closing connection socket #78
[31924][2018-06-02 04:42:56.454264 local] socket 77: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.454302 local] socket 54: disconnected (epoll_ready=2005), cleaning
[31924][2018-06-02 04:42:56.454339 local] Disconnected from RPC Middle-End (fd=77)
[31924][2018-06-02 04:42:56.454363 local] Disconnected from RPC Middle-End (fd=54)
[31924][2018-06-02 04:42:56.454393 local] Closing connection socket #77
[31924][2018-06-02 04:42:56.454430 local] Closing connection socket #54
^C[pid 31924] [time 1527914576] SIGINT handled.
[pid 31923] [time 1527914576] SIGINT handled.
[31924][2018-06-02 04:42:56.519962 local] Terminated by SIGINT.
[pid 31923] [time 1527914576] received signal 17
[31923][2018-06-02 04:42:56.521658 local] Terminated by SIGINT.
`
A virtual machine on a hypervisor Hyper-V in a home network. Telegram Servers are available through the VPN. Clients can not connect.
`[root@ubuntu-vm]:~$ telnet 149.154.164.250 8888
Trying 149.154.164.250...
Connected to 149.154.164.250.
Escape character is '^]'.
hello world
Connection closed by foreign host.
from mtproxy.
Same for me. Docker image not working on VPS(Centos 7 x86_64) at vscale.io, but same config is working on dedicated server(Centos 7 x86_64) at hetzner.
It is successfully started, backend servers list is loaded, but client cannot connect, port is open.
from mtproxy.
It is code for forwarding packet from client connection, as far as I see.
In my case there're no client connections yet (not even attempts). All the connections, including the one in log, are attempts to establish connection from proxy to telegram servers.
from mtproxy.
I wonder where the developers are? because a large number of people have different problems with this proxy, and accordingly they can not help fight for Internet freedom!
P.s. For developers. Guys, thank you for your work, I'm sure everyone here appreciates it. We will provide you with all information that you need, in order to fix bugs) Just don't forget about us
from mtproxy.
Ok, I can confirm that --nat-info <local_ip>:<global_ip>
fixed the issue with conntrack overflow on my server. Server is indeed behind nat and only has local IP addresses on interfaces. During startup mtproxy picks one of them (for some reason, from tun0 instead of eth0) and maybe that was a problem, I am not sure.
The biggest question is why mtproxy requires something like this parameter at all. It is quite easy to figure out the proper network interface and global IP.
from mtproxy.
@coolermister where server located? ips from https://core.telegram.org/getProxyConfig available?
from mtproxy.
Btw, I the same issue was for me. It starts, shows good logs but I can't connect at all. Doesn't work with docker either. And I noticed, that it doesnt work only on servers located in Russia (SimpleCloud). For Hetzner and even for OVH (which now blocks telegram servers btw) it was OK!. I even tried to use it within VPN - no profit at all.
And as for https://core.telegram.org/getProxyConfig - it was ok for all servers (even without vpn)
for author of this subject: use Hetzner cloud, I can prove that it works OK.
from mtproxy.
so, it's the same issue on native linux. i've add -v
to command, and i saw same picture as @againDDM.
detailed_log.txt
Example error:
[13484][2018-06-02 17:01:09.006332 local] New connection 10.10.158.230:44914 -> 91.108.4.185:8888
[13484][2018-06-02 17:01:09.006352 local] Closing connection socket 51
[13485][2018-06-02 17:01:09.011161 local] socket 34: disconnected (epoll_ready=2005), cleaning
[13485][2018-06-02 17:01:09.011201 local] Disconnected from RPC Middle-End (fd=34)
[13485][2018-06-02 17:01:09.011218 local] Creating NEW connection to 149.154.162.36:80
[13485][2018-06-02 17:01:09.011353 local] New connection 10.10.158.230:37210 -> 149.154.162.36:80
[13485][2018-06-02 17:01:09.011369 local] Closing connection socket 34
[13484][2018-06-02 17:01:09.012370 local] socket 57: disconnected (epoll_ready=2005), cleaning
[13484][2018-06-02 17:01:09.012390 local] Disconnected from RPC Middle-End (fd=57)
[13484][2018-06-02 17:01:09.012410 local] Creating NEW connection to 149.154.165.109:8888
[13483][2018-06-02 17:01:09.012439 local] socket 14: disconnected (epoll_ready=2005), cleaning
[13483][2018-06-02 17:01:09.^C[pid 13486] [time 1527948069] SIGINT handled.
[13486][2018-06-02 17:01:09.033171 local] Closing connection socket 35
@againDDM can you reduce your huge log?) or may be upload it as file, or something
So this proxy does Dos attack on router) it creates connection to telegram servers, the connection is dropped, but it isn't close connection successfully, so it remains in the routing table of router. And all start all over again
from mtproxy.
@coolermister I believe I had the same problem '--nat-info ' param to MTProxy server fixed the issue.
from mtproxy.
Same issue with conntrack here. Looks like mtproxy makes thousands of outgoing connections and for some reason they end up in TIME_WAIT state in conntrack filling it up until server cannot make new connections at all.
from mtproxy.
Guys, can the problem be in the cpu instructions of the AES?
For example, my CPU's don't have hardware aes
i7-950 don't have it
But i7-980 have it
from mtproxy.
I had exactly the same issue with rapid multiple disconnections, only this time it was KVM-based VPS with Genoo Linux on it and public routable IP addresses, no NAT and no firewals/filters so the problem was not in any kind of filtering. Moreover, MTProxy worked fine in my another Gentoo box at the same datacenter. I fixed the problem by upgrading the Linux kernel to 4.9.95.
from mtproxy.
@shadowlmd Just read my comments. This behavior is random. I've successfully used it for 19 days, it have rebooted every night to take new configs, and everything was fine.
But after server reboot it gave me this very problem. It is definitely a bug.
Now I'm using python version of MTProxy from here: https://github.com/alexbers/mtprotoproxy
It renews its configs automatically, no need to make some cron jobs.
from mtproxy.
@seega server is located in Belarus, so it's avaliable. I did everything as it is written in readme file, and all seems to be ok.
@p1ratrulezzz all these is really strange) did you compare results of getProxyConfig? may be they answer different subnets for different countries?
from mtproxy.
Hm, no, didnt compare. But i tried to copy them from one server to another, anyway no result with it. Also possible that there is a dependency on virtualization and server processor. But in both cases it was KVM I believe. And port was open actually, but telegram could not connect to it.
from mtproxy.
hm. Interesting theory. And made sense, because they use asm insertions. I use vmware esxi 6.5. Tomorrow i will try to compile it on native linux machine
from mtproxy.
There is a docker image also. Maybe also you could try this setup
PC with vmware esxi --> router (vpn client-->some other country), I have a theory that this software ignores routing table completely but not sure
from mtproxy.
i've tried docker image also. have the same issue as here #50 . But, machine with docker, also works on esxi)
Esxi server have 2x opteron 6172.
I will answer here as I will test this on native linux, with intel) maybe they use some instructions, which amd isn't provide, or as you said, maybe it's virtualization.. but in sources, i found only sse instructions, which is standart. And again, they use asm includes, and i don't know x86_64 asm, only avr)
from mtproxy.
Same problem at docker for windows (intel) with home router
from mtproxy.
So, i don't know that else i can find out and say about this issue.. Waiting for developers)
from mtproxy.
I have the same issue. In a very verbose log I have:
[425][2018-06-02 18:28:12.043363 local] received mtproto packet of 40 bytes
[425][2018-06-02 18:28:12.043369 local] nowhere to forward user query from connection 11, dropping
[425][2018-06-02 18:28:12.043371 local] free_msg_buffer(40)
[425][2018-06-02 18:28:12.043374 local] ext_rpcs_execute: cannot forward mtproto packet
from mtproxy.
Because of Telegram servers listening on 8888
port ( Check https://core.telegram.org/getProxyConfig )
Make sure port 8888
is open in your firewall (CSF, ip tables, etc...) so your server can connect to Telegram servers
from mtproxy.
@itsMoji yes, the port is open, and it can connect. And in my country Telegram servers isn't blocked.
Log with -vv option:
verbose log.txt
from mtproxy.
@portah
Well, it partially helped. Now it have different error.
When i trying to connect whith in local network.
[2522][2018-06-04 01:12:45.313851 local] Connected to RPC Middle-End (fd=26)
[2525][2018-06-04 01:12:45.315138 local] Connected to RPC Middle-End (fd=26)
[2523][2018-06-04 01:12:45.315510 local] Connected to RPC Middle-End (fd=25)
[2524][2018-06-04 01:12:45.318356 local] Connected to RPC Middle-End (fd=34)
[2524][2018-06-04 01:13:04.738829 local] New connection 10.10.158.43:50945 -> 10.10.158.233:8888
[2523][2018-06-04 01:13:04.738829 local] New connection 10.10.158.43:50946 -> 10.10.158.233:8888
[2523][2018-06-04 01:13:04.739255 local] trying to determine connection type
[2524][2018-06-04 01:13:04.742620 local] New connection 10.10.158.43:50947 -> 10.10.158.233:8888
[2524][2018-06-04 01:13:04.742743 local] trying to determine connection type
[pid 2522] [time 1528063984] received signal 17
[pid 2522] [time 1528063984] received signal 17
[2522][2018-06-04 01:13:05.004845 local] Child 2523 terminated, aborting
[pid 2525] [time 1528063985] SIGTERM handled.
[2525][2018-06-04 01:13:05.005244 local] Terminated by SIGTERM.
[pid 2522] [time 1528063985] received signal 17
The same is when i connect using public ip, but in New connection
i see router address
from mtproxy.
And same error as here #50, but ports are open
from mtproxy.
Same for me. I have server in Hetzner, ports are open, but I cannot connect to proxy. I tried to start docker image and self-compiled build in host system, but neither works.
It just enters some busyloop endlessly reconnecting telegram servers and doesn't work.
Specifying --address
or --nat-info
changed nothing.
from mtproxy.
@torkve, as for me on hetzner it works fine ( i use cloud server in finland). Also on a dedicated server with i7-980 cpu it works great. Check my fork for this repo it has patch for binding ip address ( clone sources and make the same way) And try running it using --address 11.22.33.44 - with your address from ifconfig
from mtproxy.
@p1ratrulezzz I use dedicated server on hetzner. Tried your fork, but still no luck with or without --address
and/or --nat-info
.
However I was able to start proxy on two other servers, one of which is connecting telegram through the VPN over that very hetzner server. I didn't check if the proxy works well on them, but at least they successfully establish the connection and do not fall into busyloop.
The commands I used to start proxy:
- (FAIL) Hetzner:
./mtproto-proxy -v -p 2398 -H 7958 -M 1 -C 60000 --aes-pwd aes backend.conf --allow-skip-dh --address $HETZNER_IP -S $SECRET
- (OK) VPN over hetzner:
./mtproto-proxy -v -p 2398 -H 7958 -M 1 -C 60000 backend.conf --aes-pwd aes --address $TUN_IP --nat-info $TUN_IP:$HETZNER_IP --allow-skip-dh -S $SECRET
- (OK) other server:
./mtproto-proxy -v -p 2398 -H 7958 -M 1 -C 60000 backend.conf --aes-pwd aes --allow-skip-dh -S $SECRET
from mtproxy.
from mtproxy.
Intel Core i7-950
from mtproxy.
worked on:
model name : Intel(R) Xeon(R) CPU L5640 @ 2.27GHz (vmware) arubacloud
not worked on:
model name : Intel(R) Xeon(R) CPU E5-2670 v3 @ 2.30GHz (kvm) vscale.io
from mtproxy.
@torkve, very strange, I have i7-980 and it works fine. Maybe need to check for some differences in instruction sets... Just buy a cloud server on hetzner (you can test for 1 hour and then remove the server and pay only for 1h)
from mtproxy.
I first assumed that it could be somehow related to asm intrinsics, but as far as I see, asm is used (except for memory barriers) only in crc32 calculation, and in case of error in crc32 calculation mtproxy would print corresponding error message.
So I tried to inspect full log. It is not very meaningful, but now I have an impression that state machine can be somehow broken or just race condition encountered. Here is a history of one fd for example:
[32709][2018-06-05 12:34:41.783546 local] Creating NEW connection to 149.154.165.250:8888
[32709][2018-06-05 12:34:41.783561 local] <59 send buffer was 16384, now 16777216
[32709][2018-06-05 12:34:41.783586 local] >59 receive buffer was 87380, now 16777216
[32709][2018-06-05 12:34:41.783613 local] <59 send buffer was 425984, now 16777216
[32709][2018-06-05 12:34:41.783623 local] >59 receive buffer was 425984, now 16777216
[32709][2018-06-05 12:34:41.783651 local] New connection 176.9.x.x:37772 -> 149.154.165.250:8888 (fd 59)
[32709][2018-06-05 12:34:41.783662 local] rpcc_init_outbound (59)
[32709][2018-06-05 12:34:41.783667 local] tcp_rpcc_default_check_perm(59): [176.9.x.x]:37772 -> [149.154.165.250]:8888
[32709][2018-06-05 12:34:41.783678 local] epoll_mod(6,0x00000007,59,59,8000200f)
[32709][2018-06-05 12:34:41.799705 local] fd=59 state=39 ready=1026 epoll_ready=4
[32709][2018-06-05 12:34:41.799732 local] END processing connection 59, flags=33554433
[32709][2018-06-05 12:34:41.799743 local] readv from 59: -1 read out of 262144
[32709][2018-06-05 12:34:41.799823 local] tcp_rpcc_default_check_perm(59): [176.9.x.x]:37772 -> [149.154.165.250]:8888
[32709][2018-06-05 12:34:41.799827 local] RPC connection #59: [176.9.x.x]:37772 -> [149.154.165.250]:8888 connected, crypto_flags = 10
[32709][2018-06-05 12:34:41.799837 local] tcp_rpc_conn_send: sending message of size 32 to conn fd=59
[32709][2018-06-05 12:34:41.800072 local] END processing connection 59, flags=33554449
[32709][2018-06-05 12:34:41.800084 local] send/writev() to 59: 44 written out of 44 in 1 chunks
[32709][2018-06-05 12:34:41.800090 local] socket_server_writer: written 44 bytes to 59, flags=0x02000011
So the connection is being stopped, read fails, and then it is marked as connected and starts sending data.
P.s. I see no reason to test cloud server, since you confirm that everything works in your hetzner case.
from mtproxy.
https://github.com/TelegramMessenger/MTProxy/blob/cc7b7097a5bc1681d0f4c05d5f07576c8b279fc4/mtproto/mtproto-proxy.c line 1740 - rpc_target_choose_random_connections doesnt work I guess in our cases
from mtproxy.
Sounds like a good guess to me.
from mtproxy.
Funny thing, I too have aes in cpu flags on server where the problem occurs. On two other servers where there is no problem I don't have aes in cpu flags.
from mtproxy.
Not working on KVM
Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl eagerfpu pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat
from mtproxy.
@UrsusArctos your idea rocks.
I had kernel 4.11.0-2 on Debian, after upgrade to 4.16.0-2 the problem disappeared.
I cannot be absolutely sure that it was kernel, since I upgraded all the packages, but it can be that.
The other two working systems I tested earlier have stock 4.15.0-23/Ubuntu and rather old custom 3.10.69-25/Ubuntu, so I have no idea where the problem lies exactly.
from mtproxy.
Tried everything before I found this. Yes, --nat-info key really solved it!
from mtproxy.
Same issue, but --nat-info doesn't work. If there any other solutions? Ubuntu 16.06 x 64 server in Russia.
from mtproxy.
19 days of good work, rebooted server and problem arises again, and now --nat-info <local_ip>:<global_ip>
doesn't help.
from mtproxy.
Having same problem with VPS on OpenVZ. All of the suggested settings doesn't help.
from mtproxy.
@d-makarenko, can you show the command line you are using to start mtproto-proxy and also the output of curl https://bsrealm.net/ip.php
and ip a
commands?
from mtproxy.
Command:
./mtproto-proxy -u nobody -p 1500 -H 10234 -S 222343dbdccdef4a54ebab1c6b0a6781 --aes-pwd proxy-secret proxy-multi.conf -M 1
External IP:
curl https://bsrealm.net/ip.php
23.94.173.93
Interfaces:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: gre0: <NOARP> mtu 1476 qdisc noop state DOWN
link/gre 0.0.0.0 brd 0.0.0.0
3: gretap0: <BROADCAST,MULTICAST> mtu 1476 qdisc noop state DOWN qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/void
inet 127.0.0.1/32 scope host venet0
inet 23.94.173.93/32 brd 23.94.173.93 scope global venet0:0
5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100
link/none
inet 10.8.0.1/24 brd 10.8.0.255 scope global tun0
from mtproxy.
Ouch! You'll have to change your proxy secret after this. Anyway, I see that your server is not behind NAT so the problem is different. Can you show the output of sudo conntrack -L | wc -l
?
from mtproxy.
Yep, my bad.
When I'm starting mtproxy it starts to grow up to 65k and then I'm getting my server suspended by sp.
this is before mtproxy is started
[root@vps MTProxy]# cat /proc/net/nf_conntrack | wc -l
41
and here it is
[root@vps MTProxy]# cat /proc/net/nf_conntrack | wc -l
2647
[root@vps MTProxy]# cat /proc/net/nf_conntrack | wc -l
3676
[root@vps MTProxy]# cat /proc/net/nf_conntrack | wc -l
4559
[root@vps MTProxy]# cat /proc/net/nf_conntrack | wc -l
5320
[root@vps MTProxy]# cat /proc/net/nf_conntrack | wc -l
7176
[root@vps MTProxy]# cat /proc/net/nf_conntrack | wc -l
7174
[root@vps MTProxy]# cat /proc/net/nf_conntrack | wc -l
from mtproxy.
This is weird. Just wonder, what happens if you add --nat-info 23.94.173.93:23.94.173.93
to parameters?
from mtproxy.
Yep, already tried that, sadly it didn't help. The strange thing is that it worked before, somewhere around fcb804c, but then it got broken, and even if I build from fcb804c, it still overflow conntrack table.
Other thing that was changed since then is proxy configuration file, but have no older revisions.
from mtproxy.
Do you see a lot of connections in TIME_WAIT state in conntrack -L
output? All of them to Telegram servers and 8888 port?
from mtproxy.
Yes most of them in TIME_WAIT and to the telegram servers.
Small chunk of the conntrack -L output
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.216 sport=58854 dport=8888 src=91.108.4.216 dst=23.94.173.93 sport=8888 dport=58854 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.160 sport=57464 dport=8888 src=91.108.4.160 dst=23.94.173.93 sport=8888 dport=57464 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=149.154.162.33 sport=34214 dport=80 src=149.154.162.33 dst=23.94.173.93 sport=80 dport=34214 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=149.154.164.250 sport=54640 dport=8888 src=149.154.164.250 dst=23.94.173.93 sport=8888 dport=54640 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=149.154.162.33 sport=33970 dport=80 src=149.154.162.33 dst=23.94.173.93 sport=80 dport=33970 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.131 sport=35026 dport=8888 src=91.108.4.131 dst=23.94.173.93 sport=8888 dport=35026 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.217 sport=56978 dport=8888 src=91.108.4.217 dst=23.94.173.93 sport=8888 dport=56978 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.160 sport=57546 dport=8888 src=91.108.4.160 dst=23.94.173.93 sport=8888 dport=57546 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.173 sport=36366 dport=8888 src=91.108.4.173 dst=23.94.173.93 sport=8888 dport=36366 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=149.154.164.250 sport=57044 dport=8888 src=149.154.164.250 dst=23.94.173.93 sport=8888 dport=57044 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.216 sport=58814 dport=8888 src=91.108.4.216 dst=23.94.173.93 sport=8888 dport=58814 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=149.154.162.33 sport=32782 dport=80 src=149.154.162.33 dst=23.94.173.93 sport=80 dport=32782 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.185 sport=36206 dport=8888 src=91.108.4.185 dst=23.94.173.93 sport=8888 dport=36206 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.131 sport=33490 dport=8888 src=91.108.4.131 dst=23.94.173.93 sport=8888 dport=33490 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=149.154.165.109 sport=48340 dport=8888 src=149.154.165.109 dst=23.94.173.93 sport=8888 dport=48340 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.185 sport=36174 dport=8888 src=91.108.4.185 dst=23.94.173.93 sport=8888 dport=36174 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.131 sport=35828 dport=8888 src=91.108.4.131 dst=23.94.173.93 sport=8888 dport=35828 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=149.154.162.40 sport=49432 dport=80 src=149.154.162.40 dst=23.94.173.93 sport=80 dport=49432 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 29 LAST_ACK src=23.94.173.93 dst=91.108.4.180 sport=55486 dport=8888 src=91.108.4.180 dst=23.94.173.93 sport=8888 dport=55486 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=149.154.175.100 sport=44736 dport=8888 src=149.154.175.100 dst=23.94.173.93 sport=8888 dport=44736 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.131 sport=35828 dport=8888 src=91.108.4.131 dst=23.94.173.93 sport=8888 dport=35828 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=149.154.162.40 sport=49432 dport=80 src=149.154.162.40 dst=23.94.173.93 sport=80 dport=49432 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 29 LAST_ACK src=23.94.173.93 dst=91.108.4.180 sport=55486 dport=8888 src=91.108.4.180 dst=23.94.173.93 sport=8888 dport=55486 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=149.154.175.100 sport=44736 dport=8888 src=149.154.175.100 dst=23.94.173.93 sport=8888 dport=44736 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.180 sport=53854 dport=8888 src=91.108.4.180 dst=23.94.173.93 sport=8888 dport=53854 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.216 sport=33428 dport=8888 src=91.108.4.216 dst=23.94.173.93 sport=8888 dport=33428 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=149.154.162.33 sport=34938 dport=80 src=149.154.162.33 dst=23.94.173.93 sport=80 dport=34938 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.185 sport=35188 dport=8888 src=91.108.4.185 dst=23.94.173.93 sport=8888 dport=35188 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.216 sport=59648 dport=8888 src=91.108.4.216 dst=23.94.173.93 sport=8888 dport=59648 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.56.198 sport=59636 dport=8888 src=91.108.56.198 dst=23.94.173.93 sport=8888 dport=59636 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.217 sport=56776 dport=8888 src=91.108.4.217 dst=23.94.173.93 sport=8888 dport=56776 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.216 sport=32846 dport=8888 src=91.108.4.216 dst=23.94.173.93 sport=8888 dport=32846 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=149.154.162.33 sport=33530 dport=80 src=149.154.162.33 dst=23.94.173.93 sport=80 dport=33530 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.133 sport=37880 dport=8888 src=91.108.4.133 dst=23.94.173.93 sport=8888 dport=37880 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.133 sport=36232 dport=8888 src=91.108.4.133 dst=23.94.173.93 sport=8888 dport=36232 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.56.198 sport=59518 dport=8888 src=91.108.56.198 dst=23.94.173.93 sport=8888 dport=59518 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 7 CLOSE src=23.94.173.93 dst=91.108.56.198 sport=57568 dport=8888 src=91.108.56.198 dst=23.94.173.93 sport=8888 dport=57568 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.216 sport=59060 dport=8888 src=91.108.4.216 dst=23.94.173.93 sport=8888 dport=59060 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.182 sport=38590 dport=8888 src=91.108.4.182 dst=23.94.173.93 sport=8888 dport=38590 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.185 sport=34796 dport=8888 src=91.108.4.185 dst=23.94.173.93 sport=8888 dport=34796 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.185 sport=34634 dport=8888 src=91.108.4.185 dst=23.94.173.93 sport=8888 dport=34634 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.180 sport=53212 dport=8888 src=91.108.4.180 dst=23.94.173.93 sport=8888 dport=53212 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.180 sport=53212 dport=8888 src=91.108.4.180 dst=23.94.173.93 sport=8888 dport=53212 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.180 sport=53474 dport=8888 src=91.108.4.180 dst=23.94.173.93 sport=8888 dport=53474 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=91.108.4.182 sport=36140 dport=8888 src=91.108.4.182 dst=23.94.173.93 sport=8888 dport=36140 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 299 ESTABLISHED src=23.94.173.93 dst=91.108.4.182 sport=39518 dport=8888 src=91.108.4.182 dst=23.94.173.93 sport=8888 dport=39518 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=91.108.4.133 sport=37022 dport=8888 src=91.108.4.133 dst=23.94.173.93 sport=8888 dport=37022 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 118 TIME_WAIT src=23.94.173.93 dst=149.154.175.100 sport=44196 dport=8888 src=149.154.175.100 dst=23.94.173.93 sport=8888 dport=44196 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 29 LAST_ACK src=23.94.173.93 dst=91.108.4.131 sport=36840 dport=8888 src=91.108.4.131 dst=23.94.173.93 sport=8888 dport=36840 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=149.154.162.33 sport=32952 dport=80 src=149.154.162.33 dst=23.94.173.93 sport=80 dport=32952 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.131 sport=36780 dport=8888 src=91.108.4.131 dst=23.94.173.93 sport=8888 dport=36780 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=149.154.175.50 sport=35572 dport=8888 src=149.154.175.50 dst=23.94.173.93 sport=8888 dport=35572 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=149.154.164.250 sport=54290 dport=8888 src=149.154.164.250 dst=23.94.173.93 sport=8888 dport=54290 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.226 sport=49284 dport=8888 src=91.108.4.226 dst=23.94.173.93 sport=8888 dport=49284 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=91.108.4.216 sport=60794 dport=8888 src=91.108.4.216 dst=23.94.173.93 sport=8888 dport=60794 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=149.154.175.100 sport=44574 dport=8888 src=149.154.175.100 dst=23.94.173.93 sport=8888 dport=44574 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=149.154.162.33 sport=60952 dport=80 src=149.154.162.33 dst=23.94.173.93 sport=80 dport=60952 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 119 TIME_WAIT src=23.94.173.93 dst=149.154.175.100 sport=44574 dport=8888 src=149.154.175.100 dst=23.94.173.93 sport=8888 dport=44574 [ASSURED] mark=0 secmark=0 use=2
ipv4 2 tcp 6 117 TIME_WAIT src=23.94.173.93 dst=149.154.162.33 sport=60952 dport=80 src=149.154.162.33 dst=23.94.173.93 sport=80 dport=60952 [ASSURED] mark=0 secmark=0 use=2
from mtproxy.
And of course you can telnet to these addresses/ports without problem? I guess, something is totally broken in MTProxy network implementation then.
from mtproxy.
And of course you can telnet to these addresses/ports without problem?
Yes, telnet connected without any problem.
It is definitely something is broken, but it affects only small part of (perhaps) incorrectly configured vps. Also, yesterday my SP started to SIGKILL every process with the name 3proxy
so it might be some kind of deliberate decision to block any proxy server on the vps. They didn't respond to the ticket yet though.
from mtproxy.
@d-makarenko, I've just thought about a workaround. I see that your vps does not have IPv6, so you can create a tunnel with https://tunnelbroker.net for example. Then you can use curl -s https://core.telegram.org/getProxyConfigV6 -o proxy-multi.conf
to generate IPv6-only upstream endpoints and see if that works for you. If your SP was filtering IPv4 traffic, most probably it will not try filtering 6in4 tunneled traffic.
from mtproxy.
Yep, it might work, but sit
is not enabled on my VPS, I'll ask my SP if it can be enabled, but this is out of topic.
The question is why MTProxy is behaving this way, while other proxy and vpn services are working fine on this vps.
from mtproxy.
Wow, you have the most weird VPS I ever seen. :)
Anyway it's really hard to understand why MTProxy behaves this way (I don't really understand C, and developers do not seem to be interested). But you mentioned that SP may filter traffic, and this could be the reason of connections being in TIME-WAIT state. And if that's the case, tunneling is the best option you have. Another option is VPN, but that seem completely pointless.
from mtproxy.
Wow, you have the most weird VPS I ever seen. :)
Good thing is that I got it dirt cheap.
Well at least good old 3proxy is doing good.
from mtproxy.
@Revertron, well, I'm running it on 3 servers, had problem only on one of them that was behind NAT, and the problem was resolved with --nat-info
parameter. So I can only guess that something is not working right on your server. Maybe traffic is being filtered, maybe something else, I don't know.
Alternative solutions are ok, but they are not official and can get broken at some point. MTProxy is implemented in a very weird/buggy way, but it is official, so most people will stick with it.
from mtproxy.
@shadowlmd Yep, my problem was on a NAT'ed server too, but the --nat-info
parameter worked for 19 days, and didn't work after that. Magic? :)
from mtproxy.
Hello, I suggest you test it
sudo ufw allow 440
Proxy with a 440-foot port
ufw reset -y
Reboot the proxy again
from mtproxy.
Try sync the server clock:
ntpdate pool.ntp.org
Mine were a couple of minutes ahead; Errors disappeared after synchronization.
from mtproxy.
Related Issues (20)
- MTProxy Admin Bot申请不了代理tag,有人懂怎么回事嘛? HOT 2
- @MTproxybot
- Bk
- Proxy sponsor registration error
- Placing a proxy inside the channel for seen
- Head trick
- G
- couldn't get stats HOT 1
- https://github.com/TelegramMessenger/MTProxy/blame/dc0c7f3de40530053189c572936ae4fd1567269b/common/common-stats.h#L4
- ⭐🤑سیگنال طلا ترید روزانه فارکس 🤑⭐
- 𝕳
- J
- Compile failure on Ubuntu 24.04 HOT 1
- Telegram
- Problem with service
- Compilation Failed HOT 1
- R
- آژانس دیجیتال مارکتینگ طوسی ادز HOT 1
- make: *** [Makefile:94: objs/bin/mtproto-proxy] Error 1 HOT 2
- سیگنال فیوچرز تحلیل کریپتو رایگان اموزش ترید
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mtproxy.