Giter Site home page Giter Site logo

mtproxy's Introduction

MTProxy

Simple MT-Proto proxy

Building

Install dependencies, you would need common set of tools for building from source, and development packages for openssl and zlib.

On Debian/Ubuntu:

apt install git curl build-essential libssl-dev zlib1g-dev

On CentOS/RHEL:

yum install openssl-devel zlib-devel
yum groupinstall "Development Tools"

Clone the repo:

git clone https://github.com/TelegramMessenger/MTProxy
cd MTProxy

To build, simply run make, the binary will be in objs/bin/mtproto-proxy:

make && cd objs/bin

If the build has failed, you should run make clean before building it again.

Running

  1. Obtain a secret, used to connect to telegram servers.
curl -s https://core.telegram.org/getProxySecret -o proxy-secret
  1. Obtain current telegram configuration. It can change (occasionally), so we encourage you to update it once per day.
curl -s https://core.telegram.org/getProxyConfig -o proxy-multi.conf
  1. Generate a secret to be used by users to connect to your proxy.
head -c 16 /dev/urandom | xxd -ps
  1. Run mtproto-proxy:
./mtproto-proxy -u nobody -p 8888 -H 443 -S <secret> --aes-pwd proxy-secret proxy-multi.conf -M 1

... where:

  • nobody is the username. mtproto-proxy calls setuid() to drop privilegies.
  • 443 is the port, used by clients to connect to the proxy.
  • 8888 is the local port. You can use it to get statistics from mtproto-proxy. Like wget localhost:8888/stats. You can only get this stat via loopback.
  • <secret> is the secret generated at step 3. Also you can set multiple secrets: -S <secret1> -S <secret2>.
  • proxy-secret and proxy-multi.conf are obtained at steps 1 and 2.
  • 1 is the number of workers. You can increase the number of workers, if you have a powerful server.

Also feel free to check out other options using mtproto-proxy --help.

  1. Generate the link with following schema: tg://proxy?server=SERVER_NAME&port=PORT&secret=SECRET (or let the official bot generate it for you).
  2. Register your proxy with @MTProxybot on Telegram.
  3. Set received tag with arguments: -P <proxy tag>
  4. Enjoy.

Random padding

Due to some ISPs detecting MTProxy by packet sizes, random padding is added to packets if such mode is enabled.

It's only enabled for clients which request it.

Add dd prefix to secret (cafe...babe => ddcafe...babe) to enable this mode on client side.

Systemd example configuration

  1. Create systemd service file (it's standard path for the most Linux distros, but you should check it before):
nano /etc/systemd/system/MTProxy.service
  1. Edit this basic service (especially paths and params):
[Unit]
Description=MTProxy
After=network.target

[Service]
Type=simple
WorkingDirectory=/opt/MTProxy
ExecStart=/opt/MTProxy/mtproto-proxy -u nobody -p 8888 -H 443 -S <secret> -P <proxy tag> <other params>
Restart=on-failure

[Install]
WantedBy=multi-user.target
  1. Reload daemons:
systemctl daemon-reload
  1. Test fresh MTProxy service:
systemctl restart MTProxy.service
# Check status, it should be active
systemctl status MTProxy.service
  1. Enable it, to autostart service after reboot:
systemctl enable MTProxy.service

Docker image

Telegram is also providing official Docker image. Note: the image is outdated.

mtproxy's People

Contributors

a1zk avatar dfedin avatar dvvarf avatar levlam avatar libertypaul avatar loskiq avatar picohub avatar savely-krasovsky avatar stek29 avatar vitlav avatar vysheng avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mtproxy's Issues

Can't bind to public ip address

[7864][2018-05-30 18:33:01.612073 local] Invoking engine mtproxy-0.01 compiled at May 30 2018 18:06:31 by gcc 7.3.0 64-bit after commit 2fd27cb0753c62e5766c86db28f2acc1d755547f
[7864][2018-05-30 18:33:01.612530 local] config_filename = 'proxy-multi.conf'
[7864][2018-05-30 18:33:01.613037 local] creating 1 workers
[7864][2018-05-30 18:33:01.615300 local] Bad binded IP address 95.123.456.78, search in ifconfig
[7864][2018-05-30 18:33:01.616752 local] Started as [10.114.26.50:8888:7864:1527697981]
[7864][2018-05-30 18:33:01.617637 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[7864][2018-05-30 18:33:01.619576 local] main loop
[7865][2018-05-30 18:33:01.620906 local] Bad binded IP address 95.123.456.78, search in ifconfig
[7865][2018-05-30 18:33:01.622217 local] Started as [10.114.26.50:8888:7865:1527697981]
[7865][2018-05-30 18:33:01.623401 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[7865][2018-05-30 18:33:01.626701 local] main loop

So i have VPN (openvpn) running on tun0 interface. And the main interface is eth0. I'm trying to set public ip address to listen on it (--address 95.123.456.78) and have this message

tcp_rpcc_send_handshake_packet: Assertion `PID.ip' failed

...
[5969][2018-05-30 14:57:22.710684 local] main loop
mtproto-proxy: net/net-tcp-rpc-client.c:246: tcp_rpcc_send_handshake_packet: Assertion `PID.ip' failed.
[pid 5942] [time 1527706642]
------- Stack Backtrace -------
/home/mtproxy/mtproto-proxy(print_backtrace+0x15)[0x449755]
/home/mtproxy/mtproto-proxy(extended_debug_handler+0x10)[0x4498a0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f23282ec0a0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f2327f82125]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f2327f853a0]
/lib/x86_64-linux-gnu/libc.so.6(__assert_fail+0xf1)[0x7f2327f7b311]
/home/mtproxy/mtproto-proxy(tcp_rpcc_parse_execute+0x963)[0x43b7c3]
/home/mtproxy/mtproto-proxy(cpu_tcp_server_reader+0x190)[0x439280]
/home/mtproxy/mtproto-proxy(cpu_server_read_write+0xb)[0x42fbcb]
/home/mtproxy/mtproto-proxy(do_connection_job+0xd3)[0x4322f3]
/home/mtproxy/mtproto-proxy(unlock_job+0x3e5)[0x421cd5]
/home/mtproxy/mtproto-proxy(run_pending_main_jobs+0x62)[0x422882]
/home/mtproxy/mtproto-proxy(default_engine_server_start+0x145)[0x443db5]
/home/mtproxy/mtproto-proxy(default_main+0x1d3)[0x444483]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f2327f6eead]
/home/mtproxy/mtproto-proxy[0x412f71]
[pid 5942] [time 1527706642] -------------------------------
[pid 5942] [time 1527706642] mtproxy-0.01 compiled at May 30 2018 14:52:35 by gcc 4.7.2 64-bit after commit 2fd27cb0753c62e5766c86db28f2acc1d755547f[pid 5942] [time 1527706642]

mtproto-proxy died right after start.

Debian 2.6.32-042stab127.2
OpenSSL 1.1.0h  27 Mar 2018

error on complie

~/5$ make
fatal: Not a git repository (or any of the parent directories): .git
cc -o objs/bin/mtproto-proxy objs/mtproto/mtproto-proxy.o objs/mtproto/mtproto-config.o objs/net/net-tcp-rpc-ext-server.o objs/lib/libkdb.a objs/lib/libkdb.a -m64 -ggdb -rdynamic -lm -lrt -lcrypto -lz -lpthread -lcrypto
objs/lib/libkdb.a(sha256.o): In function sha256': sha256.c:(.text+0xb6): undefined reference to EVP_MD_CTX_new'
objs/lib/libkdb.a(sha256.o): In function sha256_two_chunks': sha256.c:(.text+0x120): undefined reference to EVP_MD_CTX_new'
objs/lib/libkdb.a(sha256.o): In function sha256': sha256.c:(.text+0xee): undefined reference to EVP_MD_CTX_free'
objs/lib/libkdb.a(sha256.o): In function sha256_two_chunks': sha256.c:(.text+0x16a): undefined reference to EVP_MD_CTX_free'
objs/lib/libkdb.a(net-msg.o): In function rwm_sha1': net-msg.c:(.text+0x2da6): undefined reference to EVP_MD_CTX_new'
net-msg.c:(.text+0x2ddd): undefined reference to EVP_MD_CTX_free' objs/lib/libkdb.a(sha1.o): In function sha1':
sha1.c:(.text+0xb6): undefined reference to EVP_MD_CTX_new' objs/lib/libkdb.a(sha1.o): In function sha1_two_chunks':
sha1.c:(.text+0x120): undefined reference to EVP_MD_CTX_new' objs/lib/libkdb.a(sha1.o): In function sha1':
sha1.c:(.text+0xee): undefined reference to EVP_MD_CTX_free' objs/lib/libkdb.a(sha1.o): In function sha1_two_chunks':
sha1.c:(.text+0x16a): undefined reference to `EVP_MD_CTX_free'
collect2: error: ld returned 1 exit status
Makefile:86: recipe for target 'objs/bin/mtproto-proxy' failed
make: *** [objs/bin/mtproto-proxy] Error 1

i when make see this error
i build other server and copy bin file here and when run i see error

mtproto-proxy: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

Error: READ: Resource temporarily unavailable

After this command:
./mtproto-proxy -u nobody -p 8888 -H 443 -S 69529dc4287accaefedc4aee6cc46eb4 --aes-pwd proxy-secret proxy-multi.conf -M 1

I face this message and client cant connect to the proxy server:

[root@static bin]# ./mtproto-proxy -u nobody -p 8888 -H 443 -S 69529dc4287accaefedc4aee6cc46eb4 --aes-pwd proxy-secret proxy-multi.conf -M 1
[25098][2018-06-01 11:05:28.779760 local] Invoking engine mtproxy-0.01 compiled at Jun 1 2018 03:58:18 by gcc 4.8.5 20150623 (Red Hat 4.8.5-28) 64-bit after commit e231d04
[25098][2018-06-01 11:05:28.780387 local] config_filename = 'proxy-multi.conf'
[25098][2018-06-01 11:05:28.781581 local] creating 1 workers
[25098][2018-06-01 11:05:28.784651 local] Started as [xxx.xxx.xxx.xxx:8888:25098:1527865528]
[25098][2018-06-01 11:05:28.784771 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[25098][2018-06-01 11:05:28.785102 local] main loop
READ: Resource temporarily unavailable
[25099][2018-06-01 11:05:28.796551 local] Started as [xxx.xxx.xxx.xxx:8888:25099:1527865528]
[25099][2018-06-01 11:05:28.796658 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[25099][2018-06-01 11:05:28.796890 local] main loop

Any solution?

google compute engine not working

./mtproto-proxy -u nobody -p 8888 -H 443 -S b1ea1f178cfb27391171d736a54e72fb --aes-pwd proxy-secret proxy-multi.conf -M 1 --nat-info 10.142.0.2:35.227.68.219 -6 -v -l -d

`

  • [15444][2018-05-31 17:41:56.795458 local] Invoking engine mtproxy-0.01 compiled at May 31 2018 15:29:33 by gcc 7.3.0 64-bit after commit e231d04
  • [15444][2018-05-31 17:41:56.795647 local] config_filename = 'proxy-multi.conf'
  • [15444][2018-05-31 17:41:56.795713 local] /etc/hosts changed, reloaded
  • [15444][2018-05-31 17:41:56.795845 local] config loaded!
  • [15444][2018-05-31 17:41:56.795913 local] creating 1 workers
  • [15444][2018-05-31 17:41:56.796087 local] loaded 128 bytes from password file proxy-secret
  • [15444][2018-05-31 17:41:56.796494 local] using main IP 10.142.0.2/31 at interface ens4
  • [15444][2018-05-31 17:41:56.796572 local] using main IP 0:::::::/0 at interface (null)
  • [15444][2018-05-31 17:41:56.797005 local] Started as [10.142.0.2:8888:15444:1527788516]
  • [15444][2018-05-31 17:41:56.797221 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
  • [15444][2018-05-31 17:41:56.797291 local] opened tcp socket
  • [15444][2018-05-31 17:41:56.797333 local] Server started
  • [15444][2018-05-31 17:41:56.797375 local] main loop
  • [15445][2018-05-31 17:41:56.798000 local] loaded 128 bytes from password file proxy-secret
  • [15445][2018-05-31 17:41:56.798445 local] using main IP 10.142.0.2/31 at interface ens4
  • [15445][2018-05-31 17:41:56.798522 local] using main IP 0:::::::/0 at interface (null)
  • [15445][2018-05-31 17:41:56.799013 local] Started as [10.142.0.2:8888:15445:1527788516]
  • [15445][2018-05-31 17:41:56.799216 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
  • [15445][2018-05-31 17:41:56.799267 local] Server started
  • [15445][2018-05-31 17:41:56.799326 local] main loop
  • [15444][2018-05-31 17:41:56.805707 local] Creating NEW connection to 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.805959 local] New connection 10.142.0.2:33376 -> 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.806021 local] Creating NEW connection to 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.806136 local] New connection 10.142.0.2:33378 -> 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.806179 local] Creating NEW connection to 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.806291 local] New connection 10.142.0.2:33380 -> 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.806346 local] Creating NEW connection to 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.806461 local] New connection 10.142.0.2:33382 -> 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.806501 local] Creating NEW connection to 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.806623 local] New connection 10.142.0.2:33724 -> 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.806664 local] Creating NEW connection to 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.806776 local] New connection 10.142.0.2:33726 -> 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.806818 local] Creating NEW connection to 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.807008 local] New connection 10.142.0.2:33728 -> 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.807049 local] Creating NEW connection to 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.807156 local] New connection 10.142.0.2:33730 -> 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.807199 local] Creating NEW connection to 91.108.4.154:8888
  • [15444][2018-05-31 17:41:56.807330 local] New connection 10.142.0.2:32912 -> 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.807233 local] Creating NEW connection to 149.154.162.33:80
  • [15445][2018-05-31 17:41:56.807478 local] New connection 10.142.0.2:33734 -> 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.807504 local] Creating NEW connection to 91.108.4.154:8888
  • [15444][2018-05-31 17:41:56.807632 local] New connection 10.142.0.2:32916 -> 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.807658 local] Creating NEW connection to 149.154.162.33:80
  • [15445][2018-05-31 17:41:56.807783 local] New connection 10.142.0.2:33738 -> 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.807813 local] Creating NEW connection to 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.807872 local] Creating NEW connection to 149.154.162.33:80
  • [15445][2018-05-31 17:41:56.808069 local] New connection 10.142.0.2:33742 -> 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.807971 local] New connection 10.142.0.2:32920 -> 91.108.4.154:8888
  • [15444][2018-05-31 17:41:56.808153 local] Creating NEW connection to 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.808177 local] Creating NEW connection to 149.154.162.33:80
  • [15445][2018-05-31 17:41:56.808302 local] New connection 10.142.0.2:33744 -> 149.154.162.33:80
  • [15444][2018-05-31 17:41:56.808397 local] New connection 10.142.0.2:32926 -> 91.108.4.154:8888
  • [15444][2018-05-31 17:41:56.808471 local] Creating NEW connection to 149.154.166.120:8888
  • [15445][2018-05-31 17:41:56.808444 local] Creating NEW connection to 149.154.175.50:8888
  • [15445][2018-05-31 17:41:56.808613 local] New connection 10.142.0.2:41852 -> 149.154.175.50:8888
  • [15444][2018-05-31 17:41:56.808709 local] New connection 10.142.0.2:51352 -> 149.154.166.120:8888
  • [15445][2018-05-31 17:41:56.808768 local] Creating NEW connection to 149.154.175.50:8888
  • [15444][2018-05-31 17:41:56.808795 local] Creating NEW connection to 149.154.166.120:8888
  • [15445][2018-05-31 17:41:56.808924 local] New connection 10.142.0.2:41856 -> 149.154.175.50:8888
  • [15444][2018-05-31 17:41:56.809022 local] New connection 10.142.0.2:51356 -> 149.154.166.120:8888
  • [15444][2018-05-31 17:41:56.809080 local] Creating NEW connection to 149.154.166.120:8888
  • [15444][2018-05-31 17:41:56.809207 local] New connection 10.142.0.2:51358 -> 149.154.166.120:8888
  • [15445][2018-05-31 17:41:56.809103 local] Creating NEW connection to 149.154.175.50:8888
  • [15445][2018-05-31 17:41:56.809351 local] New connection 10.142.0.2:41862 -> 149.154.175.50:8888
  • [15445][2018-05-31 17:41:56.809390 local] Creating NEW connection to 149.154.175.50:8888
  • [15445][2018-05-31 17:41:56.809508 local] New connection 10.142.0.2:41864 -> 149.154.175.50:8888
  • [15444][2018-05-31 17:41:56.809413 local] Creating NEW connection to 149.154.166.120:8888
  • [15444][2018-05-31 17:41:56.809654 local] New connection 10.142.0.2:51364 -> 149.154.166.120:8888
  • [15444][2018-05-31 17:41:56.809717 local] Creating NEW connection to 91.108.56.164:8888
  • [15445][2018-05-31 17:41:56.809684 local] Creating NEW connection to 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.809858 local] New connection 10.142.0.2:32944 -> 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.809991 local] Creating NEW connection to 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.810096 local] New connection 10.142.0.2:32948 -> 91.108.4.154:8888
  • [15444][2018-05-31 17:41:56.809961 local] New connection 10.142.0.2:42242 -> 91.108.56.164:8888
  • [15444][2018-05-31 17:41:56.810172 local] Creating NEW connection to 91.108.56.164:8888
  • [15444][2018-05-31 17:41:56.810277 local] New connection 10.142.0.2:42246 -> 91.108.56.164:8888
  • [15445][2018-05-31 17:41:56.810305 local] Creating NEW connection to 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.810427 local] New connection 10.142.0.2:32952 -> 91.108.4.154:8888
  • [15444][2018-05-31 17:41:56.810455 local] Creating NEW connection to 91.108.56.164:8888
  • [15444][2018-05-31 17:41:56.810581 local] New connection 10.142.0.2:42250 -> 91.108.56.164:8888
  • [15445][2018-05-31 17:41:56.810609 local] Creating NEW connection to 91.108.4.154:8888
  • [15445][2018-05-31 17:41:56.810733 local] New connection 10.142.0.2:32956 -> 91.108.4.154:8888
  • [15444][2018-05-31 17:41:56.810761 local] Creating NEW connection to 91.108.56.164:8888
  • [15444][2018-05-31 17:41:56.810943 local] New connection 10.142.0.2:42254 -> 91.108.56.164:8888
  • [15445][2018-05-31 17:41:56.810997 local] Creating NEW connection to 149.154.166.120:8888
  • [15445][2018-05-31 17:41:56.811139 local] New connection 10.142.0.2:51382 -> 149.154.166.120:8888
  • [15444][2018-05-31 17:41:56.811171 local] Creating NEW connection to 149.154.175.100:8888
  • [15444][2018-05-31 17:41:56.811298 local] New connection 10.142.0.2:33096 -> 149.154.175.100:8888
  • [15445][2018-05-31 17:41:56.811329 local] Creating NEW connection to 149.154.166.120:8888
  • [15445][2018-05-31 17:41:56.811454 local] New connection 10.142.0.2:51386 -> 149.154.166.120:8888
  • [15444][2018-05-31 17:41:56.811483 local] Creating NEW connection to 149.154.175.100:8888
  • [15444][2018-05-31 17:41:56.811614 local] New connection 10.142.0.2:33100 -> 149.154.175.100:8888
  • [15445][2018-05-31 17:41:56.811641 local] Creating NEW connection to 149.154.166.120:8888
  • [15445][2018-05-31 17:41:56.811774 local] New connection 10.142.0.2:51390 -> 149.154.166.120:8888
  • [15444][2018-05-31 17:41:56.811800 local] Creating NEW connection to 149.154.175.100:8888
  • [15444][2018-05-31 17:41:56.811932 local] New connection 10.142.0.2:33104 -> 149.154.175.100:8888
  • [15445][2018-05-31 17:41:56.811961 local] Creating NEW connection to 149.154.166.120:8888
  • [15445][2018-05-31 17:41:56.812088 local] New connection 10.142.0.2:51394 -> 149.154.166.120:8888
  • [15444][2018-05-31 17:41:56.812114 local] Creating NEW connection to 149.154.175.100:8888
  • [15444][2018-05-31 17:41:56.812241 local] New connection 10.142.0.2:33108 -> 149.154.175.100:8888
  • [15445][2018-05-31 17:41:56.812272 local] Creating NEW connection to 91.108.56.164:8888
  • [15445][2018-05-31 17:41:56.812400 local] New connection 10.142.0.2:42272 -> 91.108.56.164:8888
  • [15444][2018-05-31 17:41:56.812430 local] Creating NEW connection to 91.108.56.127:8888
  • [15444][2018-05-31 17:41:56.812556 local] New connection 10.142.0.2:38672 -> 91.108.56.127:8888
  • [15445][2018-05-31 17:41:56.812587 local] Creating NEW connection to 91.108.56.164:8888
  • [15445][2018-05-31 17:41:56.812716 local] New connection 10.142.0.2:42276 -> 91.108.56.164:8888
  • [15444][2018-05-31 17:41:56.812742 local] Creating NEW connection to 91.108.56.127:8888
  • [15444][2018-05-31 17:41:56.812876 local] New connection 10.142.0.2:38676 -> 91.108.56.127:8888
  • [15445][2018-05-31 17:41:56.812908 local] Creating NEW connection to 91.108.56.164:8888
  • [15445][2018-05-31 17:41:56.813048 local] New connection 10.142.0.2:42280 -> 91.108.56.164:8888
  • [15444][2018-05-31 17:41:56.813081 local] Creating NEW connection to 91.108.56.127:8888
  • [15444][2018-05-31 17:41:56.813225 local] New connection 10.142.0.2:38680 -> 91.108.56.127:8888
  • [15445][2018-05-31 17:41:56.813254 local] Creating NEW connection to 91.108.56.164:8888
  • [15445][2018-05-31 17:41:56.813389 local] New connection 10.142.0.2:42284 -> 91.108.56.164:8888
  • [15444][2018-05-31 17:41:56.813418 local] Creating NEW connection to 91.108.56.127:8888
  • [15444][2018-05-31 17:41:56.813545 local] New connection 10.142.0.2:38684 -> 91.108.56.127:8888
  • [15445][2018-05-31 17:41:56.813572 local] Creating NEW connection to 149.154.175.100:8888
  • [15445][2018-05-31 17:41:56.813703 local] New connection 10.142.0.2:33126 -> 149.154.175.100:8888
  • [15444][2018-05-31 17:41:56.813731 local] Creating NEW connection to 91.108.4.217:8888
  • [15444][2018-05-31 17:41:56.813855 local] New connection 10.142.0.2:43632 -> 91.108.4.217:8888
  • [15445][2018-05-31 17:41:56.813883 local] Creating NEW connection to 149.154.175.100:8888
  • [15445][2018-05-31 17:41:56.814020 local] New connection 10.142.0.2:33130 -> 149.154.175.100:8888
  • [15444][2018-05-31 17:41:56.814050 local] Creating NEW connection to 91.108.4.217:8888
  • [15444][2018-05-31 17:41:56.814186 local] New connection 10.142.0.2:43636 -> 91.108.4.217:8888
  • [15445][2018-05-31 17:41:56.814211 local] Creating NEW connection to 149.154.175.100:8888
  • [15445][2018-05-31 17:41:56.814334 local] New connection 10.142.0.2:33134 -> 149.154.175.100:8888
  • [15444][2018-05-31 17:41:56.814362 local] Creating NEW connection to 91.108.4.217:8888
  • [15444][2018-05-31 17:41:56.814486 local] New connection 10.142.0.2:43640 -> 91.108.4.217:8888
  • [15445][2018-05-31 17:41:56.814511 local] Creating NEW connection to 149.154.175.100:8888
  • [15445][2018-05-31 17:41:56.814636 local] New connection 10.142.0.2:33138 -> 149.154.175.100:8888
  • [15444][2018-05-31 17:41:56.814665 local] Creating NEW connection to 91.108.4.217:8888
  • [15444][2018-05-31 17:41:56.814790 local] New connection 10.142.0.2:43644 -> 91.108.4.217:8888
  • [15445][2018-05-31 17:41:56.814819 local] Creating NEW connection to 91.108.56.127:8888
  • [15445][2018-05-31 17:41:56.814966 local] New connection 10.142.0.2:38702 -> 91.108.56.127:8888
  • [15444][2018-05-31 17:41:56.814997 local] Creating NEW connection to 149.154.175.50:8888
  • [15444][2018-05-31 17:41:56.815125 local] New connection 10.142.0.2:41934 -> 149.154.175.50:8888
  • [15445][2018-05-31 17:41:56.815155 local] Creating NEW connection to 91.108.56.127:8888
  • [15445][2018-05-31 17:41:56.815281 local] New connection 10.142.0.2:38706 -> 91.108.56.127:8888
  • [15444][2018-05-31 17:41:56.815307 local] Creating NEW connection to 149.154.175.50:8888
  • [15444][2018-05-31 17:41:56.815430 local] New connection 10.142.0.2:41938 -> 149.154.175.50:8888
  • [15445][2018-05-31 17:41:56.815458 local] Creating NEW connection to 91.108.56.127:8888
  • [15445][2018-05-31 17:41:56.815581 local] New connection 10.142.0.2:38710 -> 91.108.56.127:8888
  • [15444][2018-05-31 17:41:56.815609 local] Creating NEW connection to 149.154.175.50:8888
  • [15444][2018-05-31 17:41:56.815734 local] New connection 10.142.0.2:41942 -> 149.154.175.50:8888
  • [15445][2018-05-31 17:41:56.815764 local] Creating NEW connection to 91.108.56.127:8888
  • [15445][2018-05-31 17:41:56.815888 local] New connection 10.142.0.2:38714 -> 91.108.56.127:8888
  • [15444][2018-05-31 17:41:56.815922 local] Creating NEW connection to 149.154.175.50:8888
  • [15444][2018-05-31 17:41:56.816049 local] New connection 10.142.0.2:41946 -> 149.154.175.50:8888
  • [15445][2018-05-31 17:41:56.816076 local] Creating NEW connection to 91.108.4.217:8888
  • [15445][2018-05-31 17:41:56.816206 local] New connection 10.142.0.2:43662 -> 91.108.4.217:8888
  • [15444][2018-05-31 17:41:56.816233 local] Creating NEW connection to 91.108.4.161:8888
  • [15444][2018-05-31 17:41:56.816358 local] New connection 10.142.0.2:59856 -> 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.816386 local] Creating NEW connection to 91.108.4.217:8888
  • [15445][2018-05-31 17:41:56.816516 local] New connection 10.142.0.2:43666 -> 91.108.4.217:8888
  • [15444][2018-05-31 17:41:56.816545 local] Creating NEW connection to 91.108.4.161:8888
  • [15444][2018-05-31 17:41:56.816672 local] New connection 10.142.0.2:59860 -> 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.816698 local] Creating NEW connection to 91.108.4.217:8888
  • [15445][2018-05-31 17:41:56.816821 local] New connection 10.142.0.2:43670 -> 91.108.4.217:8888
  • [15444][2018-05-31 17:41:56.816849 local] Creating NEW connection to 91.108.4.161:8888
  • [15444][2018-05-31 17:41:56.816987 local] New connection 10.142.0.2:59864 -> 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.817014 local] Creating NEW connection to 91.108.4.217:8888
  • [15445][2018-05-31 17:41:56.817138 local] New connection 10.142.0.2:43674 -> 91.108.4.217:8888
  • [15444][2018-05-31 17:41:56.817163 local] Creating NEW connection to 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.817222 local] Creating NEW connection to 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.817411 local] New connection 10.142.0.2:59870 -> 91.108.4.161:8888
  • [15444][2018-05-31 17:41:56.817316 local] New connection 10.142.0.2:59868 -> 91.108.4.161:8888
  • [15444][2018-05-31 17:41:56.817489 local] Creating NEW connection to 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.817608 local] New connection 10.142.0.2:39966 -> 91.108.4.142:8888
  • [15445][2018-05-31 17:41:56.817513 local] Creating NEW connection to 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.817744 local] New connection 10.142.0.2:59874 -> 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.817798 local] Creating NEW connection to 91.108.4.161:8888
  • [15444][2018-05-31 17:41:56.817771 local] Creating NEW connection to 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.817944 local] New connection 10.142.0.2:39970 -> 91.108.4.142:8888
  • [15445][2018-05-31 17:41:56.818036 local] New connection 10.142.0.2:59878 -> 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.818097 local] Creating NEW connection to 91.108.4.161:8888
  • [15445][2018-05-31 17:41:56.818216 local] New connection 10.142.0.2:59880 -> 91.108.4.161:8888
  • [15444][2018-05-31 17:41:56.818123 local] Creating NEW connection to 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.818314 local] New connection 10.142.0.2:39976 -> 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.818358 local] Creating NEW connection to 91.108.4.142:8888
  • [15445][2018-05-31 17:41:56.818383 local] Creating NEW connection to 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.818505 local] New connection 10.142.0.2:39978 -> 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.818634 local] Creating NEW connection to 149.154.162.23:80
  • [15445][2018-05-31 17:41:56.818606 local] New connection 10.142.0.2:33536 -> 91.108.4.207:8888
  • [15445][2018-05-31 17:41:56.818706 local] Creating NEW connection to 91.108.4.207:8888
  • [15445][2018-05-31 17:41:56.818912 local] New connection 10.142.0.2:33540 -> 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.818801 local] New connection 10.142.0.2:52480 -> 149.154.162.23:80
  • [15444][2018-05-31 17:41:56.818996 local] Creating NEW connection to 149.154.162.23:80
  • [15444][2018-05-31 17:41:56.819103 local] New connection 10.142.0.2:52484 -> 149.154.162.23:80
  • [15445][2018-05-31 17:41:56.819129 local] Creating NEW connection to 91.108.4.207:8888
  • [15445][2018-05-31 17:41:56.819246 local] New connection 10.142.0.2:33544 -> 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.819271 local] Creating NEW connection to 149.154.162.23:80
  • [15444][2018-05-31 17:41:56.819395 local] New connection 10.142.0.2:52488 -> 149.154.162.23:80
  • [15445][2018-05-31 17:41:56.819421 local] Creating NEW connection to 91.108.4.207:8888
  • [15445][2018-05-31 17:41:56.819534 local] New connection 10.142.0.2:33548 -> 91.108.4.207:8888
  • [15444][2018-05-31 17:41:56.819558 local] Creating NEW connection to 149.154.162.23:80
  • [15444][2018-05-31 17:41:56.819683 local] New connection 10.142.0.2:52492 -> 149.154.162.23:80
  • [15445][2018-05-31 17:41:56.819713 local] Creating NEW connection to 91.108.4.142:8888
  • [15445][2018-05-31 17:41:56.819828 local] New connection 10.142.0.2:39996 -> 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.819856 local] Creating NEW connection to 91.108.4.188:8888
  • [15444][2018-05-31 17:41:56.819987 local] New connection 10.142.0.2:33528 -> 91.108.4.188:8888
  • [15445][2018-05-31 17:41:56.820015 local] Creating NEW connection to 91.108.4.142:8888
  • [15445][2018-05-31 17:41:56.820134 local] New connection 10.142.0.2:40000 -> 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.820161 local] Creating NEW connection to 91.108.4.188:8888
  • [15444][2018-05-31 17:41:56.820285 local] New connection 10.142.0.2:33532 -> 91.108.4.188:8888
  • [15445][2018-05-31 17:41:56.820314 local] Creating NEW connection to 91.108.4.142:8888
  • [15445][2018-05-31 17:41:56.820410 local] New connection 10.142.0.2:40004 -> 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.820437 local] Creating NEW connection to 91.108.4.188:8888
  • [15444][2018-05-31 17:41:56.820560 local] New connection 10.142.0.2:33536 -> 91.108.4.188:8888
  • [15445][2018-05-31 17:41:56.820590 local] Creating NEW connection to 91.108.4.142:8888
  • [15445][2018-05-31 17:41:56.820700 local] New connection 10.142.0.2:40008 -> 91.108.4.142:8888
  • [15444][2018-05-31 17:41:56.820729 local] Creating NEW connection to 91.108.4.188:8888
  • [15444][2018-05-31 17:41:56.820854 local] New connection 10.142.0.2:33540 -> 91.108.4.188:8888
  • [15445][2018-05-31 17:41:56.820880 local] Creating NEW connection to 149.154.162.23:80
  • [15445][2018-05-31 17:41:56.821000 local] New connection 10.142.0.2:52510 -> 149.154.162.23:80
  • [15444][2018-05-31 17:41:56.821029 local] Creating NEW connection to 91.108.4.196:8888
  • [15444][2018-05-31 17:41:56.821158 local] New connection 10.142.0.2:41870 -> 91.108.4.196:8888
  • [15445][2018-05-31 17:41:56.821186 local] Creating NEW connection to 149.154.162.23:80
  • [15445][2018-05-31 17:41:56.821312 local] New connection 10.142.0.2:52514 -> 149.154.162.23:80
  • [15444][2018-05-31 17:41:56.821339 local] Creating NEW connection to 91.108.4.196:8888
  • [15444][2018-05-31 17:41:56.821463 local] New connection 10.142.0.2:41874 -> 91.108.4.196:8888
  • [15445][2018-05-31 17:41:56.821488 local] Creating NEW connection to 149.154.162.23:80
  • [15445][2018-05-31 17:41:56.821614 local] New connection 10.142.0.2:52518 -> 149.154.162.23:80
  • [15444][2018-05-31 17:41:56.821639 local] Creating NEW connection to 91.108.4.196:8888
  • [15444][2018-05-31 17:41:56.821755 local] New connection 10.142.0.2:41878 -> 91.108.4.196:8888
  • [15445][2018-05-31 17:41:56.821793 local] Creating NEW connection to 149.154.162.23:80
  • [15445][2018-05-31 17:41:56.821936 local] New connection 10.142.0.2:52522 -> 149.154.162.23:80
  • [15444][2018-05-31 17:41:56.821965 local] Creating NEW connection to 91.108.4.196:8888
  • [15444][2018-05-31 17:41:56.822080 local] New connection 10.142.0.2:41882 -> 91.108.4.196:8888
  • [15445][2018-05-31 17:41:56.822109 local] Creating NEW connection to 91.108.4.188:8888
  • [15445][2018-05-31 17:41:56.822235 local] New connection 10.142.0.2:33558 -> 91.108.4.188:8888
  • [15444][2018-05-31 17:41:56.822264 local] Creating NEW connection to 91.108.4.180:8888
  • [15444][2018-05-31 17:41:56.822377 local] New connection 10.142.0.2:42072 -> 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.822401 local] Creating NEW connection to 91.108.4.188:8888
  • [15445][2018-05-31 17:41:56.822523 local] New connection 10.142.0.2:33562 -> 91.108.4.188:8888
  • [15444][2018-05-31 17:41:56.822552 local] Creating NEW connection to 91.108.4.180:8888
  • [15444][2018-05-31 17:41:56.822666 local] New connection 10.142.0.2:42076 -> 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.822694 local] Creating NEW connection to 91.108.4.188:8888
  • [15445][2018-05-31 17:41:56.822816 local] New connection 10.142.0.2:33566 -> 91.108.4.188:8888
  • [15444][2018-05-31 17:41:56.822860 local] Creating NEW connection to 91.108.4.180:8888
  • [15444][2018-05-31 17:41:56.822965 local] New connection 10.142.0.2:42080 -> 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.822996 local] Creating NEW connection to 91.108.4.188:8888
  • [15445][2018-05-31 17:41:56.823109 local] New connection 10.142.0.2:33570 -> 91.108.4.188:8888
  • [15444][2018-05-31 17:41:56.823139 local] Creating NEW connection to 91.108.4.180:8888
  • [15444][2018-05-31 17:41:56.823252 local] New connection 10.142.0.2:42084 -> 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.823277 local] Creating NEW connection to 91.108.4.196:8888
  • [15445][2018-05-31 17:41:56.823422 local] New connection 10.142.0.2:41900 -> 91.108.4.196:8888
  • [15444][2018-05-31 17:41:56.823451 local] Creating NEW connection to 91.108.4.222:8888
  • [15444][2018-05-31 17:41:56.823551 local] New connection 10.142.0.2:35838 -> 91.108.4.222:8888
  • [15445][2018-05-31 17:41:56.823579 local] Creating NEW connection to 91.108.4.196:8888
  • [15445][2018-05-31 17:41:56.823702 local] New connection 10.142.0.2:41904 -> 91.108.4.196:8888
  • [15444][2018-05-31 17:41:56.823730 local] Creating NEW connection to 91.108.4.222:8888
  • [15444][2018-05-31 17:41:56.823845 local] New connection 10.142.0.2:35842 -> 91.108.4.222:8888
  • [15445][2018-05-31 17:41:56.823869 local] Creating NEW connection to 91.108.4.196:8888
  • [15445][2018-05-31 17:41:56.824000 local] New connection 10.142.0.2:41908 -> 91.108.4.196:8888
  • [15444][2018-05-31 17:41:56.824025 local] Creating NEW connection to 91.108.4.222:8888
  • [15444][2018-05-31 17:41:56.824130 local] New connection 10.142.0.2:35846 -> 91.108.4.222:8888
  • [15445][2018-05-31 17:41:56.824155 local] Creating NEW connection to 91.108.4.196:8888
  • [15445][2018-05-31 17:41:56.824280 local] New connection 10.142.0.2:41912 -> 91.108.4.196:8888
  • [15444][2018-05-31 17:41:56.824307 local] Creating NEW connection to 91.108.4.222:8888
  • [15444][2018-05-31 17:41:56.824421 local] New connection 10.142.0.2:35850 -> 91.108.4.222:8888
  • [15445][2018-05-31 17:41:56.824448 local] Creating NEW connection to 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.824582 local] New connection 10.142.0.2:42102 -> 91.108.4.180:8888
  • [15444][2018-05-31 17:41:56.824612 local] Creating NEW connection to 91.108.4.211:8888
  • [15444][2018-05-31 17:41:56.824725 local] New connection 10.142.0.2:55388 -> 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.824749 local] Creating NEW connection to 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.824877 local] New connection 10.142.0.2:42106 -> 91.108.4.180:8888
  • [15444][2018-05-31 17:41:56.824902 local] Creating NEW connection to 91.108.4.211:8888
  • [15444][2018-05-31 17:41:56.825009 local] New connection 10.142.0.2:55392 -> 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.825039 local] Creating NEW connection to 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.825174 local] New connection 10.142.0.2:42110 -> 91.108.4.180:8888
  • [15444][2018-05-31 17:41:56.825083 local] Creating NEW connection to 91.108.4.211:8888
  • [15444][2018-05-31 17:41:56.825308 local] New connection 10.142.0.2:55396 -> 91.108.4.211:8888
  • [15444][2018-05-31 17:41:56.825367 local] Creating NEW connection to 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.825338 local] Creating NEW connection to 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.825508 local] New connection 10.142.0.2:42114 -> 91.108.4.180:8888
  • [15445][2018-05-31 17:41:56.825630 local] Creating NEW connection to 91.108.4.222:8888
  • [15444][2018-05-31 17:41:56.825602 local] New connection 10.142.0.2:55400 -> 91.108.4.211:8888
  • [15444][2018-05-31 17:41:56.825702 local] Creating NEW connection to 149.154.165.109:8888
  • [15444][2018-05-31 17:41:56.825891 local] New connection 10.142.0.2:42686 -> 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.825795 local] New connection 10.142.0.2:35868 -> 91.108.4.222:8888
  • [15445][2018-05-31 17:41:56.825973 local] Creating NEW connection to 91.108.4.222:8888
  • [15445][2018-05-31 17:41:56.826093 local] New connection 10.142.0.2:35872 -> 91.108.4.222:8888
  • [15444][2018-05-31 17:41:56.825999 local] Creating NEW connection to 149.154.165.109:8888
  • [15444][2018-05-31 17:41:56.826201 local] New connection 10.142.0.2:42690 -> 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.826230 local] Creating NEW connection to 91.108.4.222:8888
  • [15445][2018-05-31 17:41:56.826374 local] New connection 10.142.0.2:35876 -> 91.108.4.222:8888
  • [15444][2018-05-31 17:41:56.826276 local] Creating NEW connection to 149.154.165.109:8888
  • [15444][2018-05-31 17:41:56.826512 local] New connection 10.142.0.2:42694 -> 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.826550 local] Creating NEW connection to 91.108.4.222:8888
  • [15445][2018-05-31 17:41:56.826686 local] New connection 10.142.0.2:35880 -> 91.108.4.222:8888
  • [15444][2018-05-31 17:41:56.826712 local] Creating NEW connection to 149.154.165.109:8888
  • [15444][2018-05-31 17:41:56.826841 local] New connection 10.142.0.2:42698 -> 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.826872 local] Creating NEW connection to 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.827007 local] New connection 10.142.0.2:55418 -> 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.827068 local] Creating NEW connection to 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.827187 local] New connection 10.142.0.2:55420 -> 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.827230 local] Creating NEW connection to 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.827335 local] New connection 10.142.0.2:55422 -> 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.827376 local] Creating NEW connection to 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.827480 local] New connection 10.142.0.2:55424 -> 91.108.4.211:8888
  • [15445][2018-05-31 17:41:56.827521 local] Creating NEW connection to 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.827626 local] New connection 10.142.0.2:42708 -> 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.827666 local] Creating NEW connection to 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.827769 local] New connection 10.142.0.2:42710 -> 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.827808 local] Creating NEW connection to 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.827922 local] New connection 10.142.0.2:42712 -> 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.827962 local] Creating NEW connection to 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.828069 local] New connection 10.142.0.2:42714 -> 149.154.165.109:8888
  • [15445][2018-05-31 17:41:56.884970 local] Connected to RPC Middle-End (fd=11)
  • [15445][2018-05-31 17:41:56.885355 local] Connected to RPC Middle-End (fd=14)
  • [15445][2018-05-31 17:41:56.886730 local] Connected to RPC Middle-End (fd=13)
  • [15445][2018-05-31 17:41:56.888253 local] Connected to RPC Middle-End (fd=27)
  • [15444][2018-05-31 17:41:56.888681 local] Connected to RPC Middle-End (fd=28)
  • [15444][2018-05-31 17:41:56.889420 local] Connected to RPC Middle-End (fd=31)
  • [15444][2018-05-31 17:41:56.892442 local] Connected to RPC Middle-End (fd=40)
  • [15445][2018-05-31 17:41:56.892557 local] Connected to RPC Middle-End (fd=28)
  • [15444][2018-05-31 17:41:56.940337 local] Connected to RPC Middle-End (fd=29)
  • [15444][2018-05-31 17:41:56.941624 local] Connected to RPC Middle-End (fd=30)
  • [15445][2018-05-31 17:41:56.943558 local] Connected to RPC Middle-End (fd=12)
  • [15445][2018-05-31 17:41:56.943753 local] Connected to RPC Middle-End (fd=29)
  • [15445][2018-05-31 17:41:56.944093 local] Connected to RPC Middle-End (fd=30)
  • [15444][2018-05-31 17:41:56.949509 local] Connected to RPC Middle-End (fd=41)
  • [15444][2018-05-31 17:41:56.949751 local] Connected to RPC Middle-End (fd=42)
  • [15444][2018-05-31 17:41:56.950777 local] Connected to RPC Middle-End (fd=43)
  • [15444][2018-05-31 17:41:57.219236 local] Connected to RPC Middle-End (fd=20)
  • [15444][2018-05-31 17:41:57.220036 local] Connected to RPC Middle-End (fd=19)
  • [15444][2018-05-31 17:41:57.220484 local] Connected to RPC Middle-End (fd=17)
  • [15444][2018-05-31 17:41:57.220963 local] Connected to RPC Middle-End (fd=13)
  • [15445][2018-05-31 17:41:57.221851 local] Connected to RPC Middle-End (fd=10)
  • [15444][2018-05-31 17:41:57.221944 local] Connected to RPC Middle-End (fd=15)
  • [15444][2018-05-31 17:41:57.222092 local] Connected to RPC Middle-End (fd=10)
  • [15445][2018-05-31 17:41:57.222391 local] Connected to RPC Middle-End (fd=9)
  • [15444][2018-05-31 17:41:57.223141 local] Connected to RPC Middle-End (fd=16)
  • [15444][2018-05-31 17:41:57.224309 local] Connected to RPC Middle-End (fd=18)
  • [15444][2018-05-31 17:41:57.225324 local] Connected to RPC Middle-End (fd=11)
  • [15444][2018-05-31 17:41:57.225391 local] Connected to RPC Middle-End (fd=21)
  • [15444][2018-05-31 17:41:57.225538 local] Connected to RPC Middle-End (fd=8)
  • [15444][2018-05-31 17:41:57.225577 local] Connected to RPC Middle-End (fd=23)
  • [15445][2018-05-31 17:41:57.225992 local] Connected to RPC Middle-End (fd=17)
  • [15444][2018-05-31 17:41:57.226407 local] Connected to RPC Middle-End (fd=36)
  • [15445][2018-05-31 17:41:57.226721 local] Connected to RPC Middle-End (fd=35)
  • [15445][2018-05-31 17:41:57.226887 local] Connected to RPC Middle-End (fd=21)
  • [15444][2018-05-31 17:41:57.227099 local] Connected to RPC Middle-End (fd=9)
  • [15445][2018-05-31 17:41:57.227329 local] Connected to RPC Middle-End (fd=19)
  • [15444][2018-05-31 17:41:57.227821 local] Connected to RPC Middle-End (fd=48)
  • [15445][2018-05-31 17:41:57.227904 local] Connected to RPC Middle-End (fd=22)
  • [15444][2018-05-31 17:41:57.228598 local] Connected to RPC Middle-End (fd=46)
  • [15444][2018-05-31 17:41:57.228741 local] Connected to RPC Middle-End (fd=47)
  • [15444][2018-05-31 17:41:57.228874 local] Connected to RPC Middle-End (fd=22)
  • [15445][2018-05-31 17:41:57.229009 local] Connected to RPC Middle-End (fd=40)
  • [15444][2018-05-31 17:41:57.229579 local] Connected to RPC Middle-End (fd=37)
  • [15445][2018-05-31 17:41:57.230011 local] Connected to RPC Middle-End (fd=16)
  • [15444][2018-05-31 17:41:57.230325 local] Connected to RPC Middle-End (fd=50)
  • [15445][2018-05-31 17:41:57.230389 local] Connected to RPC Middle-End (fd=15)
  • [15444][2018-05-31 17:41:57.230612 local] Connected to RPC Middle-End (fd=51)
  • [15445][2018-05-31 17:41:57.230666 local] Connected to RPC Middle-End (fd=39)
  • [15445][2018-05-31 17:41:57.230820 local] Connected to RPC Middle-End (fd=54)
  • [15444][2018-05-31 17:41:57.230921 local] Connected to RPC Middle-End (fd=38)
  • [15444][2018-05-31 17:41:57.231181 local] Connected to RPC Middle-End (fd=39)
  • [15445][2018-05-31 17:41:57.231255 local] Connected to RPC Middle-End (fd=18)
  • [15444][2018-05-31 17:41:57.231414 local] Connected to RPC Middle-End (fd=64)
  • [15444][2018-05-31 17:41:57.231484 local] Connected to RPC Middle-End (fd=45)
  • [15445][2018-05-31 17:41:57.231561 local] Connected to RPC Middle-End (fd=20)
  • [15445][2018-05-31 17:41:57.231682 local] Connected to RPC Middle-End (fd=41)
  • [15444][2018-05-31 17:41:57.231936 local] Connected to RPC Middle-End (fd=55)
  • [15445][2018-05-31 17:41:57.232649 local] Connected to RPC Middle-End (fd=36)
  • [15444][2018-05-31 17:41:57.232728 local] Connected to RPC Middle-End (fd=57)
  • [15444][2018-05-31 17:41:57.233064 local] Connected to RPC Middle-End (fd=53)
  • [15445][2018-05-31 17:41:57.233347 local] Connected to RPC Middle-End (fd=37)
  • [15444][2018-05-31 17:41:57.234615 local] Connected to RPC Middle-End (fd=63)
  • [15445][2018-05-31 17:41:57.234684 local] Connected to RPC Middle-End (fd=42)
  • [15445][2018-05-31 17:41:57.234862 local] Connected to RPC Middle-End (fd=56)
  • [15444][2018-05-31 17:41:57.235248 local] Connected to RPC Middle-End (fd=66)
  • [15444][2018-05-31 17:41:57.235379 local] Connected to RPC Middle-End (fd=59)
  • [15445][2018-05-31 17:41:57.235728 local] Connected to RPC Middle-End (fd=55)
  • [15445][2018-05-31 17:41:57.235947 local] Connected to RPC Middle-End (fd=59)
  • [15444][2018-05-31 17:41:57.236018 local] Connected to RPC Middle-End (fd=56)
  • [15445][2018-05-31 17:41:57.236113 local] Connected to RPC Middle-End (fd=49)
  • [15445][2018-05-31 17:41:57.236255 local] Connected to RPC Middle-End (fd=52)
  • [15444][2018-05-31 17:41:57.236310 local] Connected to RPC Middle-End (fd=44)
  • [15445][2018-05-31 17:41:57.236473 local] Connected to RPC Middle-End (fd=58)
  • [15445][2018-05-31 17:41:57.236601 local] Connected to RPC Middle-End (fd=57)
  • [15444][2018-05-31 17:41:57.236689 local] Connected to RPC Middle-End (fd=72)
  • [15445][2018-05-31 17:41:57.236742 local] Connected to RPC Middle-End (fd=63)
  • [15444][2018-05-31 17:41:57.236806 local] Connected to RPC Middle-End (fd=60)
  • [15444][2018-05-31 17:41:57.236902 local] Connected to RPC Middle-End (fd=12)
  • [15444][2018-05-31 17:41:57.236941 local] Connected to RPC Middle-End (fd=58)
  • [15444][2018-05-31 17:41:57.237054 local] Connected to RPC Middle-End (fd=70)
  • [15445][2018-05-31 17:41:57.237122 local] Connected to RPC Middle-End (fd=38)
  • [15445][2018-05-31 17:41:57.237255 local] Connected to RPC Middle-End (fd=48)
  • [15445][2018-05-31 17:41:57.237295 local] Connected to RPC Middle-End (fd=50)
  • [15445][2018-05-31 17:41:57.237707 local] Connected to RPC Middle-End (fd=61)
  • [15444][2018-05-31 17:41:57.237776 local] Connected to RPC Middle-End (fd=74)
  • [15445][2018-05-31 17:41:57.237854 local] Connected to RPC Middle-End (fd=43)
  • [15445][2018-05-31 17:41:57.237900 local] Connected to RPC Middle-End (fd=67)
  • [15444][2018-05-31 17:41:57.238047 local] Connected to RPC Middle-End (fd=69)
  • [15445][2018-05-31 17:41:57.238260 local] Connected to RPC Middle-End (fd=8)
  • [15445][2018-05-31 17:41:57.238387 local] Connected to RPC Middle-End (fd=44)
  • [15444][2018-05-31 17:41:57.238483 local] Connected to RPC Middle-End (fd=49)
  • [15444][2018-05-31 17:41:57.238777 local] Connected to RPC Middle-End (fd=77)
  • [15444][2018-05-31 17:41:57.238914 local] Connected to RPC Middle-End (fd=78)
  • [15444][2018-05-31 17:41:57.239035 local] Connected to RPC Middle-End (fd=65)
  • [15445][2018-05-31 17:41:57.239081 local] Connected to RPC Middle-End (fd=72)
  • [15444][2018-05-31 17:41:57.239221 local] Connected to RPC Middle-End (fd=76)
  • [15444][2018-05-31 17:41:57.239328 local] Connected to RPC Middle-End (fd=62)
  • [15445][2018-05-31 17:41:57.239479 local] Connected to RPC Middle-End (fd=45)
  • [15444][2018-05-31 17:41:57.239537 local] Connected to RPC Middle-End (fd=68)
  • [15444][2018-05-31 17:41:57.239659 local] Connected to RPC Middle-End (fd=61)
  • [15445][2018-05-31 17:41:57.239774 local] Connected to RPC Middle-End (fd=46)
  • [15445][2018-05-31 17:41:57.240344 local] Connected to RPC Middle-End (fd=60)
  • [15445][2018-05-31 17:41:57.240484 local] Connected to RPC Middle-End (fd=47)
  • [15444][2018-05-31 17:41:57.240556 local] Connected to RPC Middle-End (fd=71)
  • [15445][2018-05-31 17:41:57.240668 local] Connected to RPC Middle-End (fd=62)
  • [15444][2018-05-31 17:41:57.240819 local] Connected to RPC Middle-End (fd=14)
  • [15445][2018-05-31 17:41:57.240901 local] Connected to RPC Middle-End (fd=7)
  • [15444][2018-05-31 17:41:57.241002 local] Connected to RPC Middle-End (fd=67)
  • [15445][2018-05-31 17:41:57.241044 local] Connected to RPC Middle-End (fd=77)
  • [15445][2018-05-31 17:41:57.241465 local] Connected to RPC Middle-End (fd=64)
  • [15445][2018-05-31 17:41:57.241733 local] Connected to RPC Middle-End (fd=70)
  • [15444][2018-05-31 17:41:57.241893 local] Connected to RPC Middle-End (fd=73)
  • [15445][2018-05-31 17:41:57.242272 local] Connected to RPC Middle-End (fd=73)
  • [15445][2018-05-31 17:41:57.242393 local] Connected to RPC Middle-End (fd=65)
  • [15445][2018-05-31 17:41:57.242565 local] Connected to RPC Middle-End (fd=69)
  • [15444][2018-05-31 17:41:57.242704 local] Connected to RPC Middle-End (fd=75)
  • [15445][2018-05-31 17:41:57.243535 local] Connected to RPC Middle-End (fd=75)
  • [15445][2018-05-31 17:41:57.243775 local] Connected to RPC Middle-End (fd=68)
  • [15444][2018-05-31 17:41:57.243969 local] Connected to RPC Middle-End (fd=79)
  • [15445][2018-05-31 17:41:57.244418 local] Connected to RPC Middle-End (fd=74)
  • [15445][2018-05-31 17:41:57.244580 local] Connected to RPC Middle-End (fd=71)
  • [15445][2018-05-31 17:41:57.245293 local] Connected to RPC Middle-End (fd=66)
  • [15445][2018-05-31 17:41:57.245864 local] Connected to RPC Middle-End (fd=78)
  • [15445][2018-05-31 17:41:57.246739 local] Connected to RPC Middle-End (fd=76)
  • [15444][2018-05-31 17:41:57.249264 local] Connected to RPC Middle-End (fd=54)
  • [15445][2018-05-31 17:41:57.251911 local] Connected to RPC Middle-End (fd=53)
  • [15444][2018-05-31 17:41:57.252806 local] Connected to RPC Middle-End (fd=52)
  • [15445][2018-05-31 17:41:57.255153 local] Connected to RPC Middle-End (fd=51)
  • [15444][2018-05-31 17:41:57.477447 local] Connected to RPC Middle-End (fd=33)
  • [15445][2018-05-31 17:41:57.480309 local] Connected to RPC Middle-End (fd=34)
  • [15444][2018-05-31 17:41:57.481054 local] Connected to RPC Middle-End (fd=25)
  • [15444][2018-05-31 17:41:57.481271 local] Connected to RPC Middle-End (fd=24)
  • [15444][2018-05-31 17:41:57.482025 local] Connected to RPC Middle-End (fd=27)
  • [15445][2018-05-31 17:41:57.482255 local] Connected to RPC Middle-End (fd=24)
  • [15444][2018-05-31 17:41:57.482583 local] Connected to RPC Middle-End (fd=26)
  • [15445][2018-05-31 17:41:57.483648 local] Connected to RPC Middle-End (fd=23)
  • [15445][2018-05-31 17:41:57.484063 local] Connected to RPC Middle-End (fd=25)
  • [15444][2018-05-31 17:41:57.484259 local] Connected to RPC Middle-End (fd=32)
  • [15444][2018-05-31 17:41:57.484557 local] Connected to RPC Middle-End (fd=34)
  • [15445][2018-05-31 17:41:57.484642 local] Connected to RPC Middle-End (fd=26)
  • [15444][2018-05-31 17:41:57.485363 local] Connected to RPC Middle-End (fd=35)
  • [15445][2018-05-31 17:41:57.486523 local] Connected to RPC Middle-End (fd=31)
  • [15445][2018-05-31 17:41:57.486722 local] Connected to RPC Middle-End (fd=32)
  • [15445][2018-05-31 17:41:57.487451 local] Connected to RPC Middle-End (fd=33)
  • [15445][2018-05-31 17:42:08.633864 local] New connection 176.114.114.87:52996 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:08.640035 local] trying to determine connection type
  • [15445][2018-05-31 17:42:08.640193 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:10.630300 local] socket 79: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:10.630451 local] Closing connection socket #79
  • [15445][2018-05-31 17:42:10.794791 local] New connection 176.114.114.87:52998 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:10.795818 local] trying to determine connection type
  • [15445][2018-05-31 17:42:10.795913 local] "random" 64-byte header: have 41 bytes, need 23 more bytes to distinguish
  • [15445][2018-05-31 17:42:12.476371 local] socket 79: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:12.476512 local] Closing connection socket #79
  • [15445][2018-05-31 17:42:16.621785 local] New connection 176.114.114.87:53010 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:16.622596 local] New connection 176.114.114.87:53011 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:16.624647 local] trying to determine connection type
  • [15445][2018-05-31 17:42:16.624754 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:16.625479 local] trying to determine connection type
  • [15445][2018-05-31 17:42:16.625558 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:16.631427 local] New connection 176.114.114.87:53014 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:16.632834 local] New connection 176.114.114.87:53013 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:16.634675 local] trying to determine connection type
  • [15445][2018-05-31 17:42:16.634761 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:16.636160 local] trying to determine connection type
  • [15445][2018-05-31 17:42:16.636230 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:16.638197 local] New connection 176.114.114.87:53009 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:16.638867 local] trying to determine connection type
  • [15445][2018-05-31 17:42:16.638924 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:16.649008 local] New connection 176.114.114.87:53012 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:16.650094 local] trying to determine connection type
  • [15445][2018-05-31 17:42:16.650175 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:17.482179 local] socket 84: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:17.482333 local] Closing connection socket #84
  • [15445][2018-05-31 17:42:17.489532 local] socket 81: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:17.489670 local] Closing connection socket #81
  • [15445][2018-05-31 17:42:17.638088 local] New connection 176.114.114.87:53016 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:17.638887 local] trying to determine connection type
  • [15445][2018-05-31 17:42:17.638964 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:17.640207 local] New connection 176.114.114.87:53015 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:17.640855 local] trying to determine connection type
  • [15445][2018-05-31 17:42:17.640950 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:18.614798 local] socket 79: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:18.615002 local] Closing connection socket #79
  • [15445][2018-05-31 17:42:18.615264 local] socket 80: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:18.615379 local] Closing connection socket #80
  • [15445][2018-05-31 17:42:18.635000 local] socket 82: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:18.635154 local] Closing connection socket #82
  • [15445][2018-05-31 17:42:18.635401 local] socket 83: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:18.635456 local] Closing connection socket #83
  • [15445][2018-05-31 17:42:18.767277 local] New connection 176.114.114.87:53017 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:18.768812 local] New connection 176.114.114.87:53018 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:18.773280 local] trying to determine connection type
  • [15445][2018-05-31 17:42:18.773399 local] "random" 64-byte header: have 41 bytes, need 23 more bytes to distinguish
  • [15445][2018-05-31 17:42:18.774943 local] trying to determine connection type
  • [15445][2018-05-31 17:42:18.775029 local] "random" 64-byte header: have 41 bytes, need 23 more bytes to distinguish
  • [15445][2018-05-31 17:42:18.775325 local] New connection 176.114.114.87:53019 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:18.780588 local] trying to determine connection type
  • [15445][2018-05-31 17:42:18.780680 local] "random" 64-byte header: have 41 bytes, need 23 more bytes to distinguish
  • [15445][2018-05-31 17:42:18.788066 local] New connection 176.114.114.87:53020 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:18.792658 local] trying to determine connection type
  • [15445][2018-05-31 17:42:18.792758 local] "random" 64-byte header: have 41 bytes, need 23 more bytes to distinguish
  • [15445][2018-05-31 17:42:19.477583 local] socket 84: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:19.477735 local] Closing connection socket #84
  • [15445][2018-05-31 17:42:19.491169 local] socket 81: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:19.491320 local] Closing connection socket #81
  • [15445][2018-05-31 17:42:19.638636 local] New connection 176.114.114.87:53021 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:19.640632 local] trying to determine connection type
  • [15445][2018-05-31 17:42:19.640786 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:19.653608 local] New connection 176.114.114.87:53022 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:19.655995 local] trying to determine connection type
  • [15445][2018-05-31 17:42:19.656119 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:20.475050 local] socket 79: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:20.475200 local] socket 83: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:20.475263 local] Closing connection socket #79
  • [15445][2018-05-31 17:42:20.475329 local] Closing connection socket #83
  • [15445][2018-05-31 17:42:20.475458 local] socket 82: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:20.475501 local] socket 80: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:20.475541 local] Closing connection socket #82
  • [15445][2018-05-31 17:42:20.475583 local] Closing connection socket #80
  • [15445][2018-05-31 17:42:20.629387 local] New connection 176.114.114.87:53025 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:20.630139 local] trying to determine connection type
  • [15445][2018-05-31 17:42:20.630239 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:20.631431 local] New connection 176.114.114.87:53027 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:20.632104 local] trying to determine connection type
  • [15445][2018-05-31 17:42:20.632163 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:20.645203 local] New connection 176.114.114.87:53024 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:20.647587 local] trying to determine connection type
  • [15445][2018-05-31 17:42:20.647712 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:20.648643 local] New connection 176.114.114.87:53026 -> 10.142.0.2:443
  • [15445][2018-05-31 17:42:20.651093 local] trying to determine connection type
  • [15445][2018-05-31 17:42:20.651192 local] invalid "random" 64-byte header, entering global skip mode
  • [15445][2018-05-31 17:42:21.283670 local] socket 84: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:21.283865 local] Closing connection socket #84
  • [15445][2018-05-31 17:42:21.284021 local] socket 83: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:21.284163 local] Closing connection socket #83
  • [15445][2018-05-31 17:42:21.284289 local] socket 79: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:21.284355 local] Closing connection socket #79
  • [15445][2018-05-31 17:42:21.284517 local] socket 80: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:21.284608 local] Closing connection socket #80
  • [15445][2018-05-31 17:42:21.285112 local] socket 82: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:21.285166 local] Closing connection socket #82
  • [15445][2018-05-31 17:42:21.286437 local] socket 81: disconnected (epoll_ready=2005), cleaning
  • [15445][2018-05-31 17:42:21.286498 local] Closing connection socket #81

`

Started, but not work

OS: Debian 9 amd64

root@ste:~# mtproto-proxy -u nobody -p 8888 -H 443 -S 2897eb720bacfc6b1eeac54f6436d595 --aes-pwd proxy-secret proxy-multi.conf -M 1
[2063][2018-05-30 20:16:08.406341 local] Invoking engine mtproxy-0.01 compiled at May 30 2018 20:01:46 by gcc 6.3.0 20170516 64-bit after commit 2fd27cb0753c62e5766c86db28f2acc1d755547f
[2063][2018-05-30 20:16:08.406579 local] config_filename = 'proxy-multi.conf'
[2063][2018-05-30 20:16:08.406835 local] creating 1 workers
[2063][2018-05-30 20:16:08.408013 local] Started as [10.0.0.4:8888:2063:1527700568]
[2063][2018-05-30 20:16:08.408379 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[2063][2018-05-30 20:16:08.408561 local] main loop
[2064][2018-05-30 20:16:08.414153 local] Started as [10.0.0.4:8888:2064:1527700568]
[2064][2018-05-30 20:16:08.414561 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[2064][2018-05-30 20:16:08.414688 local] main loop

Promoting with unofficial sources.

Hi.
Is there a way to use promotion channel with unofficial sources?
Cause this source does not support windows.
If not will you add it soon?

Static Analyzer Errors

I ran the code through some static analyzers (cppcheck, Clang Static Analyzer) and there are numerous C undefined behavior issues (like bit-shifting a negative value, or pointer calculations on void* type), memory leaks, and also errors and possibly exploitable vulns (i.e. possible NULL pointer dereference, etc.).

I'm not listing the issues, as each reported case need further analyzes, but I encourage the developers to check and fix those issues.

Official mtproto proxy specification

Does it exist? There are many proxy implementations already but they all build just from experiments and some of them doesn't work on android clients at all. Is there any official document that describes how to implement your own mtproto proxy? The packet flow actually is the same as for mtproto, but there are some differences and also it is not clear what to do with proxy tag for your custom implementation

Build failed on Ubuntu

#make
cc -m64 -O2 -std=gnu11 -Wall -mpclmul -march=core2 -mfpmath=sse -mssse3 -fno-strict-aliasing -fno-strict-overflow -fwrapv -DAES=1 -DCOMMIT="e231d049362476be7f3c1cbe8fa0d22b76d698dd" -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -fpic -iquote common -iquote . -c -MP -MD -MF dep/common/sha1.d -MQ objs/common/sha1.o -o objs/common/sha1.o common/sha1.c
In file included from common/sha1.h:20:0,
from common/sha1.c:22:
/usr/include/openssl/evp.h:66:34: fatal error: openssl/opensslconf.h: No such file or directory

include <openssl/opensslconf.h>

                              ^

compilation terminated.
make: *** [objs/common/sha1.o] Error 1

#uname -a
Linux sdbhome 4.4.0-111-generic #134~14.04.1-Ubuntu SMP Mon Jan 15 15:41:00 UTC 2018 i686 i686 i686 GNU/Linux

Build error on Solaris

With GCC 5.5:

make

cc -m64 -O3 -std=gnu11 -Wall -mpclmul -march=native -mfpmath=sse -mssse3 -fno-strict-aliasing -fno-strict-overflow -fwrapv -DAES=1 -DCOMMIT="2fd27cb0753c62e5766c86db28f2acc1d755547f" -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -iquote common -iquote . -c -MP -MD -MF dep/mtproto/mtproto-proxy.d -MQ objs/mtproto/mtproto-proxy.o -o objs/mtproto/mtproto-proxy.o mtproto/mtproto-proxy.c
cc: Warning: GCC option -mpclmul ignored. Suggest using -xarch=aes
cc: Warning: Option -mfpmath=sse passed to ld, if ld is invoked, ignored otherwise
cc: Warning: Option -fno-strict-overflow passed to ld, if ld is invoked, ignored otherwise
cc: Warning: Option -fwrapv passed to ld, if ld is invoked, ignored otherwise
cc: Warning: Option -quote passed to ld, if ld is invoked, ignored otherwise
cc: Warning: Option -quote passed to ld, if ld is invoked, ignored otherwise
cc: refused to overwrite input file by output file: objs/mtproto/mtproto-proxy.o
make: *** [Makefile:78: objs/mtproto/mtproto-proxy.o] Error 1

It seems as Makefile error.

Ah, I see. This is not portable code, will not build on Solaris in any way. Sorry and sadly.

Run on ARM

Can't build on Ubuntu 16.04 ARMv71 (scaleway hosting)

cc: error: unrecognized argument in option ‘-march=core2’
cc: note: valid arguments to ‘-march=’ are: armv2 armv2a armv3 armv3m armv4 armv4t armv5 armv5e armv5t armv5te armv6 armv6-m armv6j armv6k armv6kz armv6s-m armv6t2 armv6z armv6zk armv7 armv7-a armv7-m armv7-r armv7e-m armv7ve armv8-a armv8-a+crc armv8.1-a armv8.1-a+crc iwmmxt iwmmxt2 native
cc: error: unrecognized command line option ‘-m64’
cc: error: unrecognized command line option ‘-mpclmul’
cc: error: unrecognized command line option ‘-mfpmath=sse’
cc: error: unrecognized command line option ‘-mssse3’

Docker image not working same way....

error mtproto-proxy: command not found

Hi all
i try to run this with command
mtproto-proxy -u mahdihk -p 1080 -H 6969 -S 55cf808f42b97f44c2ca09a847d7764c --aes-pwd proxy-secret proxy-multi.conf -M 1
and return
mtproto-proxy: command not found
what can i do?

pointer targets in passing argument 2 of ‘__get_cpuid’ differ in signedness [-Wpointer-sign]

#uname -a
Linux 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux

In file included from common/cpuid.c:21:0:
common/cpuid.c: In function ‘kdb_cpuid’:
common/cpuid.c:36:25: warning: pointer targets in passing argument 2 of ‘__get_cpuid’ differ in signedness [-Wpointer-sign]
assert(__get_cpuid(1, &a, &cached.ebx, &cached.ecx, &cached.edx) != 0);
^
In file included from common/cpuid.c:22:0:
/usr/lib/gcc/x86_64-linux-gnu/6/include/cpuid.h:237:1: note: expected ‘unsigned int *’ but argument is of type ‘int *’
__get_cpuid (unsigned int __leaf,
^~~~~~~~~~~
In file included from common/cpuid.c:21:0:
common/cpuid.c:36:29: warning: pointer targets in passing argument 3 of ‘__get_cpuid’ differ in signedness [-Wpointer-sign]
assert(__get_cpuid(1, &a, &cached.ebx, &cached.ecx, &cached.edx) != 0);
^
In file included from common/cpuid.c:22:0:
/usr/lib/gcc/x86_64-linux-gnu/6/include/cpuid.h:237:1: note: expected ‘unsigned int *’ but argument is of type ‘int *’
__get_cpuid (unsigned int __leaf,
^~~~~~~~~~~
In file included from common/cpuid.c:21:0:
common/cpuid.c:36:42: warning: pointer targets in passing argument 4 of ‘__get_cpuid’ differ in signedness [-Wpointer-sign]
assert(__get_cpuid(1, &a, &cached.ebx, &cached.ecx, &cached.edx) != 0);
^
In file included from common/cpuid.c:22:0:
/usr/lib/gcc/x86_64-linux-gnu/6/include/cpuid.h:237:1: note: expected ‘unsigned int *’ but argument is of type ‘int *’
__get_cpuid (unsigned int __leaf,
^~~~~~~~~~~
In file included from common/cpuid.c:21:0:
common/cpuid.c:36:55: warning: pointer targets in passing argument 5 of ‘__get_cpuid’ differ in signedness [-Wpointer-sign]
assert(__get_cpuid(1, &a, &cached.ebx, &cached.ecx, &cached.edx) != 0);
^
In file included from common/cpuid.c:22:0:
/usr/lib/gcc/x86_64-linux-gnu/6/include/cpuid.h:237:1: note: expected ‘unsigned int *’ but argument is of type ‘int *’
__get_cpuid (unsigned int __leaf,
^~~~~~~~~~~

Publish the Dockerfile

Although it's not that hard to dockerize MTProxy, I think it would be great to publish your Dockerfile that is used in docker hub for folks who want to build a container by themselves.

Proxies being banned in Iran. CHANGE TO TLS PLZ

I am the dev of JSMTProxy : https://github.com/FreedomPrevails/JSMTProxy

As I had guessed it before, Iran's DPI filtering equipment has detected this custom encryption method of MTProto Proxy protocol and they have started to ban the proxy IPs. It is is the end of MTProto Proxy in Iran.
I am pretty sure they are doing it automatically. I had an unpublished proxy running on a server which I was not even using it ! but it was blocked ! may be the telegram client has pinged it in the background.
Why dont you use the standard TLS encryption the same way as HTTPS protocol ? why have you reinvented the wheel ? you need to make the traffic indistinguishable from white listed traffic, not make it different ! yes, current implementation is secure, but it can be detected ! we need something secure and undetectable !

PLEASE CHANGE THE ENCRYPTION TO TLS.
PLEASE UPVOTE THIS FOR VISIBILITY.

Unexpected Termination

Got terminated immediately after started.

Log:

***mtproto-proxy -u nobody -p *** -H *** -S *** --aes-pwd proxy-sec
et proxy-multi.conf -M 1
[12974][2018-05-30 22:27:35.054276 local] Invoking engine mtproxy-
.01 compiled at May 30 2018 22:18:16 by gcc 6.3.0 20170516 64-bit
fter commit 2fd27cb0753c62e5766c86db28f2acc1d755547f
[12974][2018-05-30 22:27:35.054718 local] config_filename = 'proxy
multi.conf'
[12974][2018-05-30 22:27:35.055146 local] creating 1 workers
[12974][2018-05-30 22:27:35.058921 local] Started as [10.243.233.9
:2094:12974:1527690455]
[12974][2018-05-30 22:27:35.059232 local] configuration file proxy
multi.conf re-read successfully (797 bytes parsed), new configuration active
[12974][2018-05-30 22:27:35.059318 local] main loop
[12975][2018-05-30 22:27:35.059437 local] Started as [10.243.233.9
:2094:12975:1527690455]
[12975][2018-05-30 22:27:35.060119 local] configuration file proxy
multi.conf re-read successfully (797 bytes parsed), new configuration active
[12975][2018-05-30 22:27:35.060322 local] main loop
[12974][2018-05-30 22:27:36.004512 local] Child 12975 terminated, aborting

Active session show my home ip-adress, not proxy ip

I succesful run my MTProxy builded from source, I see "connected" in proxy settings and shield icon in Telegram Andoid interface. But I see that my device connected form my home IP in menu Active sessoins . Is it ok?

Error mtproto-proxy: command not found

Hi all
i try to run this proxy with command
mtproto-proxy -u VPN_And_Proxies -p 8888 -H 443 -S b587aa366b4a5b76bc2c5f42dc696900 --aes-pwd proxy-secret proxy-multi.conf -M 2
return
mtproto-proxy: command not found
What do I do now?
(i tru run with other port
mtproto-proxy -u VPN_And_Proxies -p 5878 -H 4578 -S b587aa366b4a5b76bc2c5f42dc696900 --aes-pwd proxy-secret proxy-multi.conf -M 2
but see again this error
)
i ty use mtproto-proxy help
but again return mtproto-proxy: command not found

On-the-fly config file reload

Would be very nice to add a feature to reload the config without restarting the proxy, for example, by SIGHUP and/or automatically (inotify)

verbosity does return help page

Hi all :)

Thanks for this program.

If i use -v the verbosity is set to 3
If i use --verbosity 1-3 the program run is aborted.

Does someone know the problem in the code?

Lack of MTPROTO proxy address provider channels

Some governments try to close MTPROTO proxy address provider channels. As a result one of them with 400K members was closed just today: t.me/ProxyMTProto
Moreover most of the people have difficulties obtaining the addresses of this type of proxy, also some of them don't trust proxy provider channels(you know because of security concerns).
Please establish a MTPROTO proxy address provider official channel(with blue tick) and provide proxy server addresses to users.
The mechanism would be simple: proxy server owners will send their proxy info to a robot and after being analyzed automatically (do they work correctly or not), these addresses will be introduced in the official channel.

+The address of the official channel and robot could be sent through the official account of Telegram (in Telegram) to all of the users.

How to setup on Microsoft azure?

I've configured and ran the agent under ubuntu server but cannot access through the proxy. Probably there should be some additional port rules or smth like that...

MTProxybot has a bug and does not show me my proxies

After I run the commands step by step from your git, when i create a proxy in the @MTProxybot it said everything is ok but when I want to get the list of my proxies I see this result from the bot. When i click in the blank it says invalid proxy. I think it is a bug

Docker container: Can't start by rlimit assertion

Terminated after start:

[5][2018-05-30 19:13:03.765738 local] Invoking engine mtproxy-0.01 compiled at May 26 2018 17:35:43 by gcc 4.7.2 64-bit after commit cb4c3402bc3744f4bd956f9538fc54acaafc2638
[5][2018-05-30 19:13:03.765906 local] config_filename = '/etc/telegram/backend.conf'
[5][2018-05-30 19:13:03.766378 local] creating 2 workers
[5][2018-05-30 19:13:03.766801 local] failed to set rlimit for open files. Try running as root or requesting smaller maxconns value.
[5][2018-05-30 19:13:03.766824 local] fatal: cannot raise open file limit to 65552
root@70dae078eec2:/# mtproto-proxy: mtproto/mtproto-proxy.c:2251: mtfront_pre_init: Assertion `parent_pid == real_parent_pid' failed.
[pid 41] [time 1527707583]
------- Stack Backtrace -------
/usr/local/bin/mtproto-proxy(print_backtrace+0x15)[0x448ac5]
/usr/local/bin/mtproto-proxy(extended_debug_handler+0x10)[0x448c10]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fd21f98d890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fd21f608067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fd21f609448]
/lib/x86_64-linux-gnu/libc.so.6(+0x2e266)[0x7fd21f601266]
/lib/x86_64-linux-gnu/libc.so.6(+0x2e312)[0x7fd21f601312]
/usr/local/bin/mtproto-proxy(mtfront_pre_init+0x1fd)[0x41911d]
/usr/local/bin/mtproto-proxy(default_main+0x11a)[0x44371a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd21f5f4b45]
/usr/local/bin/mtproto-proxy[0x412129]
[pid 41] [time 1527707583] -------------------------------
[pid 41] [time 1527707583] mtproxy-0.01 compiled at May 26 2018 17:35:43 by gcc 4.7.2 64-bit after commit cb4c3402bc3744f4bd956f9538fc54acaafc2638[pid 41] [time 1527707583]
mtproto-proxy: mtproto/mtproto-proxy.c:2251: mtfront_pre_init: Assertion `parent_pid == real_parent_pid' failed.
[pid 40] [time 1527707583]
------- Stack Backtrace -------
/usr/local/bin/mtproto-proxy(print_backtrace+0x15)[0x448ac5]
/usr/local/bin/mtproto-proxy(extended_debug_handler+0x10)[0x448c10]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fd21f98d890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fd21f608067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fd21f609448]
/lib/x86_64-linux-gnu/libc.so.6(+0x2e266)[0x7fd21f601266]
/lib/x86_64-linux-gnu/libc.so.6(+0x2e312)[0x7fd21f601312]
/usr/local/bin/mtproto-proxy(mtfront_pre_init+0x1fd)[0x41911d]
/usr/local/bin/mtproto-proxy(default_main+0x11a)[0x44371a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd21f5f4b45]
/usr/local/bin/mtproto-proxy[0x412129]
[pid 40] [time 1527707583] -------------------------------
[pid 40] [time 1527707583] mtproxy-0.01 compiled at May 26 2018 17:35:43 by gcc 4.7.2 64-bit after commit cb4c3402bc3744f4bd956f9538fc54acaafc2638[pid 40] [time 1527707583]

Info:

docker version:
Client:
 Version:      18.03.1-ce
 API version:  1.37
 Go version:   go1.9.4
 Git commit:   3dfb8343b139d6342acfd9975d7f1068b5b1c3d3
 Built:        Thu May 24 22:21:27 2018
 OS/Arch:      linux/amd64
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.03.1-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   7390fc6/18.03.1-ce
  Built:        Thu May 24 22:22:43 2018
  OS/Arch:      linux/amd64
  Experimental: false

assert (!(p & 0xffff0000)); /*where p is pid*/

Hello, frends!

On my hosting when the application starts, it ends up on
assert (! (p & 0xffff0000));
in
common/pid.c:32

if I comment on this line the application is launched, but all system connection calls are terminated with the EINPROGRESS return code and the process consumes ~ 70% of the CPU

Could you please clarify what this check makes p & 0xffff0000

Could you clarify what this check makes p & 0xffff0000 and what rights in the system need to be checked, because on another hosting, everything works without any noticing.

And by the way, yes, the process pid> 110000, if this is important, but apparently important.

===
iqdoctor @ raccoon4x: ~ / MTProxy $ grep connect st | grep 43
connect (43, {sa_family = AF_INET, sin_port = htons (8888), sin_addr = inet_addr ("91.108.4.135")}, 16) = -1 EINPROGRESS (Operation now in progress)
connect (43, {sa_family = AF_INET, sin_port = htons (80), sin_addr = inet_addr ("149.154.162.39")}, 16) = -1 EINPROGRESS (Operation now in progress)
connect (43, {sa_family = AF_INET, sin_port = htons (8888), sin_addr = inet_addr ("91.108.4.175")}, 16) = -1 EINPROGRESS (Operation now in progress)

Server is running but can't connect from client

cli# ./objs/bin/mtproto-proxy -u nobody -p 8888 -H 6968 -S ace63eff7aefb133be6e72f5f57d8382 --aes-pwd proxy-secret proxy-multi.conf -M 0

[8770][2018-05-31 16:01:59.314524 local] Invoking engine mtproxy-0.01 compiled at May 31 2018 15:07:13 by gcc 5.4.0 20160609 64-bit after commit 2fd27cb
[8770][2018-05-31 16:01:59.314907 local] config_filename = 'proxy-multi.conf'
[8770][2018-05-31 16:01:59.316577 local] Started as [85.143.175.202:8888:8770:1527771719]
[8770][2018-05-31 16:01:59.316968 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[8770][2018-05-31 16:01:59.317146 local] main loop

When I try to connect from client - nothing. But with all the same configuration on other 2 servers (OVH and Hetzner) it works fine. For this configuration I run VPN + mtproxy because server is located at Russia.
I also tried to use sockify to forward all connections through socks5 proxy - didn't help

Though, other mtproxy implementations actually work even without vpn, so that means that telegram servers are actually accessible

Error on make - field ‘rand_data’ has incomplete type

$ make
cc -m64 -O3 -std=gnu11 -Wall -mpclmul -march=core2 -mfpmath=sse -mssse3 -fno-strict-aliasing -fno-strict-overflow -fwrapv -DAES=1 -DCOMMIT="2fd27cb0753c62e5766c86db28f2acc1d755547f" -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -iquote common -iquote . -c -MP -MD -MF dep/mtproto/mtproto-proxy.d -MQ objs/mtproto/mtproto-proxy.o -o objs/mtproto/mtproto-proxy.o mtproto/mtproto-proxy.c
In file included from ./net/net-connections.h:34:0,
from ./net/net-tcp-connections.h:28,
from mtproto/mtproto-proxy.c:53:
./jobs/jobs.h:234:23: error: field ‘rand_data’ has incomplete type
struct drand48_data rand_data;
^~~~~~~~~
make: *** [Makefile:78: objs/mtproto/mtproto-proxy.o] Error 1

Does anyone have thoughts?

RAND_pseudo_bytes’ is deprecated

I get the following warning while compiling on Debian stretch:

net/net-crypto-dh.c: In function ‘create_g_a’:
net/net-crypto-dh.c:150:5: warning: ‘RAND_pseudo_bytes’ is deprecated [-Wdeprecated-declarations]
assert (RAND_pseudo_bytes (a, 256) >= 0); /* if you write '>0', the assert will fail. It's very sad */
^~~~~~
In file included from /usr/include/openssl/crypto.h:32:0,
from /usr/include/openssl/bn.h:33,
from net/net-crypto-dh.c:36:
/usr/include/openssl/rand.h:47:1: note: declared here
DEPRECATEDIN_1_1_0(int RAND_pseudo_bytes(unsigned char *buf, int num))
^

Not working at all, can't connect, and routing table overflow(

Hi guys! First of all sorry for my english) Becouse english isn't my native language)
(If someone have interested in this, my native language is russian)
I have really strange problem.
I compiled the proxy sucsessfully.
The server which will run proxy is behind my nat router(i have public static ip of course),
and have address 10.10.158.233(my local network is 10.10.158.0/24)
8443 port looks outside. ip of router is 10.10.158.254.
So, when i run proxy with command
mtproto-proxy -u nobody -H 8888 -p 8443 -S <here is the secret> -M 3 --aes-pwd proxy-secret proxy-multi.conf
it succesfully starts.
default

But in secods after it's started, routing table of my router is overflowed.
For example:
Before
default
After run:
default
Limit on router is net.netfilter.nf_conntrack_max=65536
When it's running, i can't connect to it using local ip, and public ip too, from my android client.
And after something about minute, router is going down)
System is Ubuntu 16.04 x64.
So, what i'm gonna do?
Which additional information i can provide, to fix it?

Error while using MAKE

Hi I get this error when I use 'make' :


cc -m64 -O3 -std=gnu11 -Wall -mpclmul -march=core2 -mfpmath=sse -mssse3 -fno-strict-aliasing -fno-strict-overflow -fwrapv -DAES=1 -DCOMMIT=\"e231d049362476be7f3c1cbe8fa0d22b76d698dd\" -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -iquote common -iquote . -c -MP -MD -MF dep/mtproto/mtproto-proxy.d -MQ objs/mtproto/mtproto-proxy.o -o objs/mtproto/mtproto-proxy.o mtproto/mtproto-proxy.c
cc1: error: unrecognized command line option "-std=gnu11"
make: *** [objs/mtproto/mtproto-proxy.o] Error 1

Cannot raise open file limit to 65552

Hello!

I run into issues with MTProxy running on Docker on CentOS cloud VM. When I'm trying to start docker container, it goes into the endless loop of restarts. Docker logs show next error.

failed to set rlimit for open files. Try running as root or requesting smaller maxconns value.
fatal: cannot raise open file limit to 65552

What is the right way to set MAX_CONNECTIONS value when running Docker container?

My setup:

Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-862.2.3.el7.x86_64
Architecture: x86-64
Docker version 18.03.1-ce, build 9ee9f40

error in kali

cc -m64 -O3 -std=gnu11 -Wall -mpclmul -march=core2 -mfpmath=sse -mssse3 -fno-strict-aliasing -fno-strict-overflow -fwrapv -DAES=1 -DCOMMIT="2fd27cb0753c62e5766c86db28f2acc1d755547f" -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -iquote common -iquote . -c -MP -MD -MF dep/mtproto/mtproto-proxy.d -MQ objs/mtproto/mtproto-proxy.o -o objs/mtproto/mtproto-proxy.o mtproto/mtproto-proxy.c
mtproto/mtproto-proxy.c:42:10: fatal error: openssl/rand.h: No such file or directory
#include <openssl/rand.h>
^~~~~~~~~~~~~~~~
compilation terminated.
Makefile:78: recipe for target 'objs/mtproto/mtproto-proxy.o' failed
make: *** [objs/mtproto/mtproto-proxy.o] Error 1

what is that problem please help

Error when i used " Make"

Hi ,
when i want to use " make " i faced with this error
make: *** No rule to make target objs/bin/mtproto-proxy. Stop.
and also openSSL 1.1.1 is installed on centos 7 kernel 4

without make is also
[root@cs09-prod ~]# mtproto-proxy -u nobody -p 8888 -H 443 -S 3d1404e83ff3457b2407b4eba6d2842e --aes-pwd proxy-secret proxy-multi.conf -M 7 -bash: mtproto-proxy: command not found

Is not building for 32bit

Trying to build for 32bit CPU, getting this errors:

$ make -j2
cc -O3 -std=gnu11 -Wall -mpclmul -march=native -mfpmath=sse -mssse3 -fno-strict-aliasing -fno-strict-overflow -fwrapv -DAES=1 -DCOMMIT=\"2fd27cb0753c62e5766c86db28f2acc1d755547f\" -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -fpic -iquote common -iquote . -c -MP -MD -MF dep/common/crc32c.d -MQ objs/common/crc32c.o -o objs/common/crc32c.o common/crc32c.c
cc -O3 -std=gnu11 -Wall -mpclmul -march=native -mfpmath=sse -mssse3 -fno-strict-aliasing -fno-strict-overflow -fwrapv -DAES=1 -DCOMMIT=\"2fd27cb0753c62e5766c86db28f2acc1d755547f\" -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -fpic -iquote common -iquote . -c -MP -MD -MF dep/common/crc32.d -MQ objs/common/crc32.o -o objs/common/crc32.o common/crc32.c
In file included from common/crc32c.c:28:0:
common/crc32c.c: In function ‘crc32c_combine_clmul’:
common/crc32c.c:624:47: error: ‘CRC32C_REFLECTED_X1023’ undeclared (first use in this function)
     assert (crc32c_powers[7 * 4 + 3] == (int) CRC32C_REFLECTED_X1023);
                                               ^
common/crc32c.c:624:47: note: each undeclared identifier is reported only once for each function it appears in
common/crc32c.c:625:47: error: ‘CRC32C_REFLECTED_X2047’ undeclared (first use in this function)
     assert (crc32c_powers[8 * 4 + 3] == (int) CRC32C_REFLECTED_X2047);
                                               ^
common/crc32c.c:626:47: error: ‘CRC32C_REFLECTED_X4095’ undeclared (first use in this function)
     assert (crc32c_powers[9 * 4 + 3] == (int) CRC32C_REFLECTED_X4095);
                                               ^
common/crc32c.c:627:48: error: ‘CRC32C_REFLECTED_X8191’ undeclared (first use in this function)
     assert (crc32c_powers[10 * 4 + 3] == (int) CRC32C_REFLECTED_X8191);
                                                ^
common/crc32c.c:628:48: error: ‘CRC32C_REFLECTED_X16383’ undeclared (first use in this function)
     assert (crc32c_powers[11 * 4 + 3] == (int) CRC32C_REFLECTED_X16383);
                                                ^
common/crc32c.c: At top level:
common/crc32c.c:617:17: warning: ‘crc32c_combine_clmul’ defined but not used [-Wunused-function]
 static unsigned crc32c_combine_clmul (unsigned crc1, unsigned crc2, int64_t len2) {
                 ^
Makefile:81: recipe for target 'objs/common/crc32c.o' failed
make: *** [objs/common/crc32c.o] Error 1
make: *** Waiting for unfinished jobs....
common/crc32.c: Assembler messages:
common/crc32.c:589: Error: unsupported instruction `movq'
common/crc32.c:575: Error: unsupported instruction `movq'
common/crc32.c:476: Error: unsupported instruction `movq'
common/crc32.c:725: Error: unsupported instruction `movq'
common/crc32.c:830: Error: unsupported instruction `movq'
common/crc32.c:575: Error: unsupported instruction `movq'
Makefile:81: recipe for target 'objs/common/crc32.o' failed
make: *** [objs/common/crc32.o] Error 1

main loop

in my installation when run mtproxy , hang up in main loop but it works but terminated after press ctrl+c

any soloution?

[2320][2018-05-31 16:57:03.421314 local] creating 1 workers
READ: Resource temporarily unavailable
[2320][2018-05-31 16:57:03.466619 local] Started as [0.0.0.0:8888:2320:1527769623]
[2320][2018-05-31 16:57:03.466753 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[2320][2018-05-31 16:57:03.467579 local] main loop
[2321][2018-05-31 16:57:03.467759 local] Started as [0.0.0.0:8888:2321:1527769623]
[2321][2018-05-31 16:57:03.467908 local] configuration file proxy-multi.conf re-read successfully (797 bytes parsed), new configuration active
[2321][2018-05-31 16:57:03.468713 local] main loop
^C[pid 2320] [time 1527769916] SIGINT handled.
[pid 2321] [time 1527769916] SIGINT handled.
[2321][2018-05-31 17:01:56.920137 local] Terminated by SIGINT.
[2320][2018-05-31 17:01:56.923692 local] Terminated by SIGINT.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.