V2ray MTProto through Shadowsocks

README.MD

V2ray MTProto through Shadowsocks

Why use it

The MTProto is easy to block; shadowsocks is hard to identify but cannot work without a client.

You can deylop this docker image to run a relay inside the firewall (China/Russia etc.), it provide a MTProto and all the packets will be sent through shadowsocks protocol.

How to run

Modify the v2ray.conf, change the port, secret, and the other 4 settings in servers for shadowsocks configure.

Then put these 2 files in a folder and run docker-compose up -d.

Other info

It is based on V2ray. Also, I wrote some similar programs: inner-shadowsocks, shadowsocks-with-socks-auth to provide a Socks5 through shadowsocks. But for telegram, they are not recommended, because the Socks5 credential is transported in plain.

UPDATE: I add a pre-connection pool to the original v2ray in a ugly way, but it works. It can reduce a lot of "Connecting" time.

docker-compose.yml

version: "3"
services:
  v2ray:
    image: ihciah/v2ray
    container_name: v2ray
    restart: always
    command: v2ray -config=/etc/v2ray/config.json
    network_mode: "host"
    volumes:
      - ./v2ray.conf:/etc/v2ray/config.json

v2ray.conf

{
    "inbounds": [
        {
            "port": 12345,
            "protocol": "mtproto",
            "settings": {
                "users": [
                    {
                        "secret": "YOURTGMTPROTOSECRET"
                    }
                ]
            },
            "tag": "tg-in"
        }
    ],
    "outbounds": [
        {
            "protocol": "shadowsocks",
            "settings": {
                "servers": [
                    {
                        "address": "SSSERVER",
                        "method": "SSMETHOD",
                        "password": "SSPASSWORD",
                        "port": SSPORT
                    }
                ]
            },
            "tag": "OUTSIDE"
        },
        {
            "protocol": "mtproto",
            "proxySettings": {
                "tag": "OUTSIDE"
            },
            "settings": {},
            "tag": "tg-out"
        }
    ],
    "routing": {
        "rules": [
            {
                "inboundTag": [
                    "tg-in"
                ],
                "outboundTag": "tg-out",
                "type": "field"
            }
        ]
    }
}