v2ray / v2ray-core

A platform for building proxies to bypass network restrictions.
https://www.v2ray.com/
MIT License
45.35k stars 8.94k forks source link

玩彩6或者开Origin时,断流严重 #1614

Closed Ricky-Hao closed 4 years ago

Ricky-Hao commented 5 years ago

1) 你正在使用哪个版本的 V2Ray?(如果服务器和客户端使用了不同版本,请注明)

服务器端配置:

{
    "log":
    {
        "loglevel": "debug"
    },
    "api":
    {
        "tag": "api",
        "services": [
            "StatsService"
        ]
    },
    "stats": {},
    "policy":
    {
        "levels":
        {
            "0":
            {
                "handshake": 4,
                "connIdle": 300,
                "uplinkOnly": 2,
                "downlinkOnly": 5,
                "statsUserUplink": true,
                "statsUserDownlink": true,
                "bufferSize": 512
            }
        },
        "system":
        {
            "statsInboundUplink": false,
            "statsInboundDownlink": false
        }
    },
    "inbound":
    {
        "port": 2334,
        "listen": "127.0.0.1",
        "protocol": "vmess",
        "tag": "proxy",
        "settings":
        {
            "clients": [
                {
                    "id": "***",
                    "level": 0,
                    "alterId": 100,
                    "email": "***"
                }
            ]
        },
        "streamSettings":
        {
            "network": "ws",
            "security": "tls",
            "tlsSettings":
            {
                "serverName": "***",
                "certificates": [
                    {
                        "certificateFile": "***",
                        "keyFile": "***"
                    }
                ]
            },
            "wsSettings":
            {
                "path": "/test_v",
                "headers":
                {
                    "Host": "***"
                }
            }
        }
    },
    "outbound":
    {
        "protocol": "freedom",
        "settings": {}
    },
    "inboundDetour": [
        {
            "port": 2335,
            "listen": "127.0.0.1",
            "tag": "api",
            "protocol": "dokodemo-door",
            "settings":
            {
                "address": "127.0.0.1"
            }
        }
    ],
    "outboundDetour": [
        {
            "protocol": "blackhole",
            "settings": {},
            "tag": "blocked"
        }
    ],
    "routing":
    {
        "strategy": "rules",
        "settings":
        {
            "rules": [
                {
                    "inboundTag": [
                        "api"
                    ],
                    "outboundTag": "api",
                    "type": "field"
                },
                {
                    "type": "field",
                    "ip": [
                        "0.0.0.0/8",
                        "10.0.0.0/8",
                        "100.64.0.0/10",
                        "127.0.0.0/8",
                        "169.254.0.0/16",
                        "172.16.0.0/12",
                        "192.0.0.0/24",
                        "192.0.2.0/24",
                        "192.168.0.0/16",
                        "198.18.0.0/15",
                        "198.51.100.0/24",
                        "203.0.113.0/24",
                        "::1/128",
                        "fc00::/7",
                        "fe80::/10"
                    ],
                    "outboundTag": "blocked"
                }
            ]
        }
    }
}

客户端配置:

{
  "log": {
    "access": "",
    "error": "",
    "loglevel": "warning"
  },
  "inbounds": [
    {
      "port": 10808,
      "listen": "127.0.0.1",
      "protocol": "socks",
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls"
        ]
      },
      "settings": {
        "auth": "noauth",
        "udp": true,
        "ip": null,
        "clients": null
      },
      "streamSettings": null
    }
  ],
  "outbounds": [
    {
      "tag": "proxy",
      "protocol": "vmess",
      "settings": {
        "vnext": [
          {
            "address": "***",
            "port": 443,
            "users": [
              {
                "id": "***",
                "alterId": 100,
                "email": "t@t.tt",
                "security": "auto"
              }
            ]
          }
        ],
        "servers": null,
        "response": null
      },
      "streamSettings": {
        "network": "ws",
        "security": "tls",
        "tlsSettings": {
          "allowInsecure": false,
          "serverName": null
        },
        "tcpSettings": null,
        "kcpSettings": null,
        "wsSettings": {
          "connectionReuse": true,
          "path": "/test_v",
          "headers": {
            "Host": "***"
          }
        },
        "httpSettings": null,
        "quicSettings": null
      },
      "mux": {
        "enabled": false
      }
    },
    {
      "tag": "direct",
      "protocol": "freedom",
      "settings": {
        "vnext": null,
        "servers": null,
        "response": null
      },
      "streamSettings": null,
      "mux": null
    },
    {
      "tag": "block",
      "protocol": "blackhole",
      "settings": {
        "vnext": null,
        "servers": null,
        "response": {
          "type": "http"
        }
      },
      "streamSettings": null,
      "mux": null
    }
  ],
  "dns": null,
  "routing": {
    "domainStrategy": "IPIfNonMatch",
    "rules": [
      {
        "type": "field",
        "port": null,
        "outboundTag": "direct",
        "ip": [
          "geoip:private"
        ],
        "domain": null
      },
      {
        "type": "field",
        "port": null,
        "outboundTag": "direct",
        "ip": [
          "geoip:cn"
        ],
        "domain": null
      },
      {
        "type": "field",
        "port": null,
        "outboundTag": "direct",
        "ip": null,
        "domain": [
          "geosite:cn"
        ]
      }
    ]
  }
}

6) 请附上出错时软件输出的错误日志。在 Linux 中,日志通常在 /var/log/v2ray/error.log 文件中。

服务器端错误日志:

2019/03/23 03:28:12 [Info] [3399946940] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: failed to transfer request > websocket: close 1000 (normal)
2019/03/23 03:28:12 [Info] [3399946940] v2ray.com/core/app/proxyman/inbound: failed to close connection > v2ray.com/core/transport/internet/websocket: failed to close connection > v2ray.com/core/transport/internet/websocket: websocket: close sentwrite tcp 127.0.0.1:2334->127.0.0.1:26496: write: broken pipe
2019/03/23 03:28:12 [Info] [3399946940] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/03/23 03:28:12 [Info] [3142491323] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: failed to transfer request > websocket: close 1000 (normal)
2019/03/23 03:28:12 [Info] [3142491323] v2ray.com/core/app/proxyman/inbound: failed to close connection > v2ray.com/core/transport/internet/websocket: failed to close connection > v2ray.com/core/transport/internet/websocket: websocket: close sentwrite tcp 127.0.0.1:2334->127.0.0.1:26498: write: broken pipe
2019/03/23 03:28:12 [Info] [3142491323] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/03/23 03:28:12 [Info] [2993494188] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: failed to transfer request > websocket: close 1000 (normal)
2019/03/23 03:28:12 [Info] [2993494188] v2ray.com/core/app/proxyman/inbound: failed to close connection > v2ray.com/core/transport/internet/websocket: failed to close connection > v2ray.com/core/transport/internet/websocket: websocket: close sentwrite tcp 127.0.0.1:2334->127.0.0.1:26508: write: broken pipe
2019/03/23 03:28:12 [Info] [2993494188] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/03/23 03:28:12 [Info] [3300021770] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: failed to transfer request > websocket: close 1000 (normal)
2019/03/23 03:28:12 [Info] [3300021770] v2ray.com/core/app/proxyman/inbound: failed to close connection > v2ray.com/core/transport/internet/websocket: failed to close connection > v2ray.com/core/transport/internet/websocket: websocket: close sentwrite tcp 127.0.0.1:2334->127.0.0.1:26510: write: broken pipe
2019/03/23 03:28:12 [Info] [3300021770] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/03/23 03:28:14 [Info] [4166674718] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: failed to transfer request > websocket: close 1000 (normal)
2019/03/23 03:28:14 [Info] [4166674718] v2ray.com/core/app/proxyman/inbound: failed to close connection > v2ray.com/core/transport/internet/websocket: failed to close connection > v2ray.com/core/transport/internet/websocket: websocket: close sentwrite tcp 127.0.0.1:2334->127.0.0.1:26524: write: broken pipe
2019/03/23 03:28:14 [Info] [4166674718] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/03/23 03:28:15 [Info] [3563336077] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: failed to transfer request > websocket: close 1000 (normal)
2019/03/23 03:28:15 [Info] [3563336077] v2ray.com/core/app/proxyman/inbound: failed to close connection > v2ray.com/core/transport/internet/websocket: failed to close connection > v2ray.com/core/transport/internet/websocket: websocket: close sentwrite tcp 127.0.0.1:2334->127.0.0.1:26576: write: broken pipe
2019/03/23 03:28:15 [Info] [3563336077] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled

客户端错误日志:

2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 479 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 463 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 607 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 655 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 639 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 495 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 607 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 559 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 623 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 479 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 607 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 607 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 543 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 607 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 511 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Info] [1951376141] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:12 [Info] [1951376141] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 623 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 575 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 511 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 511 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 559 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 463 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 607 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 639 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Info] [3760129143] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:12 [Info] [3760129143] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 543 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 559 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 591 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 591 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 623 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 607 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 511 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 559 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:12 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 575 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 639 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 543 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 527 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 591 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 799 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 543 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 559 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 607 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 511 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 591 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 527 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 495 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 559 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 495 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 575 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 767 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 479 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 511 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 143 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 143 bytes
2019/03/23 03:28:13 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:14 [Info] [4148587627] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:14 [Info] [4148587627] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/03/23 03:28:14 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 15 bytes
2019/03/23 03:28:14 [Debug] [2075365824] v2ray.com/core/proxy/socks: writing back UDP response with 111 bytes
2019/03/23 03:28:14 [Debug] [2075365824] v2ray.com/core/proxy/socks: send packet to udp:216.98.55.85:6085 with 15 bytes
2019/03/23 03:28:14 [Debug] [2075365824] v2ray.com/core/transport/internet/udp: dispatch request to: udp:216.98.55.85:6085
2019/03/23 03:28:14 [Info] [2073150449] v2ray.com/core/proxy/socks: client UDP connection from udp:127.0.0.1:58459
2019/03/23 03:28:14 [Debug] [2073150449] v2ray.com/core/proxy/socks: send packet to udp:31.49.182.222:44822 with 65 bytes
2019/03/23 03:28:14 [Debug] [2073150449] v2ray.com/core/transport/internet/udp: dispatch request to: udp:31.49.182.222:44822
2019/03/23 03:28:14 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:31.49.182.222:44822
2019/03/23 03:28:14 [Info] [2073150449] v2ray.com/core/app/dispatcher: default route for udp:31.49.182.222:44822
2019/03/23 03:28:14 [Info] [2073150449] v2ray.com/core/transport/internet/websocket: creating connection to tcp:***:443
2019/03/23 03:28:14 [Info] [2073150449] v2ray.com/core/proxy/vmess/outbound: tunneling request to udp:31.49.182.222:44822 via tcp:***:443
2019/03/23 03:28:14 [Info] [3114762234] v2ray.com/core/proxy/socks: TCP Connect request to tcp:216.98.56.230:443
2019/03/23 03:28:14 [Info] [3114762234] v2ray.com/core/app/dispatcher: sniffed domain: mercury.ubi.com
2019/03/23 03:28:14 [Info] [3114762234] v2ray.com/core/app/dispatcher: default route for tcp:mercury.ubi.com:443
2019/03/23 03:28:14 [Info] [3114762234] v2ray.com/core/transport/internet/websocket: creating connection to tcp:***:443
2019/03/23 03:28:15 [Info] [3114762234] v2ray.com/core/proxy/vmess/outbound: tunneling request to tcp:mercury.ubi.com:443 via tcp:***:443
2019/03/23 03:28:15 [Info] [630875575] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:15 [Info] [630875575] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/03/23 03:28:15 [Info] [1558977782] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:15 [Info] [1558977782] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/03/23 03:28:15 [Info] [3481053925] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:15 [Info] [3481053925] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/03/23 03:28:15 [Info] [3482308387] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:15 [Info] [3482308387] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/03/23 03:28:15 [Info] [1358573055] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:15 [Info] [1358573055] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/03/23 03:28:16 [Info] [91660882] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/03/23 03:28:16 [Info] [91660882] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe

7) 请附上访问日志。在 Linux 中,日志通常在 /var/log/v2ray/access.log 文件中。

Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26550 accepted udp:9.9.9.9:53
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26552 accepted udp:137.135.201.29:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26554 accepted udp:138.91.117.92:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26556 accepted udp:40.115.66.5:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26558 accepted udp:168.63.239.108:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26562 accepted udp:168.61.145.218:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26560 accepted udp:65.52.120.69:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26566 accepted udp:23.98.144.17:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26568 accepted udp:138.91.2.227:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26564 accepted udp:168.63.152.107:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26572 accepted udp:23.97.144.150:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26570 accepted udp:23.97.97.114:3075
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26574 accepted udp:121.133.38.107:40938
Mar 23 03:28:11 *** v2ray[10147]: 2019/03/23 03:28:11 127.0.0.1:26576 accepted udp:91.1.208.16:6881
Mar 23 03:28:16 *** v2ray[10147]: 2019/03/23 03:28:16 127.0.0.1:26578 accepted udp:31.49.182.222:44822

8) 其它相关的配置文件(如 Nginx)和相关日志。

server {
        listen 443 ssl default_server;
        listen [::]:443 ssl;

        include ssl.conf;

        send_timeout 600;

        root /usr/share/nginx/***;

        # Add index.php to the list if you are using PHP
        index index.php index.html index.htm index.nginx-debian.html;

        server_name ***.com www.***.com;

        # Add headers to serve security related headers
        # Before enabling Strict-Transport-Security headers please read into this topic first.
        add_header Strict-Transport-Security "max-age=15552000; includeSubDomains";
        add_header X-Content-Type-Options nosniff;
        add_header X-Frame-Options "SAMEORIGIN";
        add_header X-XSS-Protection "1; mode=block";
        add_header X-Robots-Tag all;
        add_header X-Download-Options noopen;
        add_header X-Permitted-Cross-Domain-Policies none;

        location = /test_v {
            proxy_redirect off;
            proxy_pass https://127.0.0.1:2334;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_set_header Host $http_host;
        }
}
Ricky-Hao commented 5 years ago
Ricky-Hao commented 5 years ago
{
    "port": 22222,
    "listen": "0.0.0.0",
    "tag": "game",
    "protocol": "shadowsocks",
    "settings":
    {
        "email": "***",
        "method": "chacha20-ietf-poly1305",
        "password": "***",
        "level": 0,
        "network": "tcp,udp"
    }
}
kslr commented 5 years ago

你能通过vmess来尝试一下吗?

Ricky-Hao commented 5 years ago

你能通过vmess来尝试一下吗?

一开始用的就是vmess,只不过套了ws+tls+nginx

kslr commented 5 years ago

我建议你从最小模型排查下这个问题,另外你的Shadowsocks 有处理UDP吗 彩6是彩虹六号吗

Ricky-Hao commented 5 years ago

是的,彩六就是彩虹六号。我用shadwosocks的时候用的是sstap,挂着全局的规则,是有走udp的。
而且我发现可能问题是出在udp部分上,会有很多的unexcepted EOF这样,导致像Origin这样也需要udp的软件就打不开。
今天还测试了用sstap直连shadowsocks和用sstap直连v2ray内置的shadowsocks的情况,两个ss的配置基本一样,但是使用原版的ss就能够正常游戏。所以我感觉可能问题出在v2ray这个平台上?(已经排除了v2rayN这个windows下客户端的干扰,直接都使用sstap进行连接,且都是同一台服务器。

kslr commented 5 years ago

建议尝试取消UDP或者单纯vmess,ws这一套我现在也不是太清楚 还是要研究一下

有收到过几次Iptables UDP 转发失败的报告,我自己也没有成功,参考倒数的几个issues

supersndqd commented 5 years ago

ws+tls 服务器客户端配置里面都用不到证书的,web反代,证书放web服务器里,第二个,就是想问一下,你配置那么多参数,你理解是什么意思吗,没别的意思,不理解就删除,就按白皮书上来的配,第三个udp的问题 不是服务器udp的设置,是sstap强行转udp的,不管你用什么协议,他都是把udp再次封装的,最后就是排除法,别的游戏能玩不。

supersndqd commented 5 years ago

我服务器配置 { "log": { "error": "/var/log/v2ray/error.log", "access": "/var/log/v2ray/access.log", "loglevel": "warning" }, "inbounds": [ { "port": 56788, "listen":"127.0.0.1", "protocol": "vmess", "settings": { "clients": [ { "id": "×××××××××××××××××××××××", "alterId": 8 } ] }, "streamSettings": { "network": "ws", "wsSettings": { "path": "/search" } } } ], "outbounds": [ { "protocol": "freedom", "settings": {} } ] } caddy代理 hk.**:443 { root /var/www/caddy timeouts none gzip tls /etc/ssl/caddy/hk.pem /etc/ssl/caddy/hk.key filebrowser / /var/www/caddy { database /var/www/filebrowser.db } proxy /search localhost:56788 { websocket header_upstream -Origin } } 客户端 { "log": { "error": "/data/v2ray/error.log", "access": "/data/v2ray/access.log", "loglevel": "warning" }, "inbounds": [ { "tag": "sockslocal", "port": 58081, "listen": "0.0.0.0", "protocol": "socks", "settings": { "auth": "noauth", "udp": true, "ip": "0.0.0.0" } } ], "outbounds": [ { "protocol": "freedom", "settings": {}, "tag": "freedomout" }, { "tag": "sockslocalout", "protocol": "vmess", "settings": { "vnext": [ { "address": "", "port": 443, "users": [ { "id": "***", "alterId": 8 } ] } ] }, "streamSettings": { "network": "ws", "security": "tls", "wsSettings": { "path": "/search" } } } ], "dns": { "servers": [ "223.5.5.5" ] }, "routing": { "strategy": "rules", "settings": { "domainStrategy": "IPIfNonMatch", "rules": [ { "type": "field", "ip": [ "10.0.0.0/8", "100.64.0.0/10", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.168.0.0/16", "198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "::1/128", "fc00::/7", "fe80::/10", "0.0.0.0/8", "192.0.2.0/24" ], "outboundTag": "freedomout" }, { "type": "field", "inboundTag": [ "sockslocal" ], "outboundTag": "sockslocalout" } ] } } }

我这个可以玩lol测试服,吃机,和魔兽美服,别的没试过

Ricky-Hao commented 5 years ago

尝试过以下几种组合:

关于不转发udp只代理tcp的话,tcp链接倒是很稳,但是游戏主要流量都在udp上。
感觉可能V2RayUDP的转发有问题,而不是协议上的问题。
在思考会不会是freedom的问题?

supersndqd commented 5 years ago

vps 直接开socks5,sstap直接连,看能玩,能玩,socks5后面再接vmess,还有配置文件去掉所有不需要的参数,问你明白了参数的意思就是这个意思,你都不明白意思,直接抄错了也不知道,不是增加找错的困难吗,我贴我配置的意思,不是让你抄我的配置,而是给你看看,这么简单就可以了

Ricky-Hao commented 5 years ago

vps 直接开socks5,sstap直接连,看能玩,能玩,socks5后面再接vmess,还有配置文件去掉所有不需要的参数,问你明白了参数的意思就是这个意思,你都不明白意思,直接抄错了也不知道,不是增加找错的困难吗

不好意思,至少我写的配置里的参数我都懂。

{
    "log":
    {
        "error": "/var/log/v2ray/error.log",
        "loglevel": "debug"
    },
    "inbound":
    {
        "port": 22222,
        "listen": "0.0.0.0",
        "tag": "game",
        "protocol": "socks",
        "settings":
        {
            "auth": "password",
            "accounts": [
                {
                    "user": "***",
                    "pass": "***"
                }
            ],
            "udp": true,
            "ip": "***",
            "userLevel": 0
        }
    },
    "outbound":
    {
        "protocol": "freedom",
        "settings": {}
    }
}

参数最小化我也试过,然而还是不行,所以只能思考是不是平台或者freedom的问题。

supersndqd commented 5 years ago

直接这样socks5都不行啊,你用的aliyun的香港服务器,你打过客服电话吗,游戏vpn呢,其他youtobe再代理呢,你直接跟客服说,我vpn要玩国外游戏。真金白银的,你怕什么

Ricky-Hao commented 5 years ago

不是服务器问题啊大哥,我用goproxysocks就能玩,连加密都不用上。

supersndqd commented 5 years ago

就使用者来说,我们用代理,各种加密,目的是为了不被墙,简单说不加密能玩,加密出现问题是正常。 v2ray对我来说就是个软件,我说参数的意思,就是我也不懂,我的要求就是能用,这路不通换条路。你真金白银买的香港阿里的服务器,比较的贵了,简单的游戏也被墙,你可以直接找他的。我结束了,不再回复

kslr commented 5 years ago

你的网络是NAT吗? https://github.com/v2ray/v2ray-core/issues/1384

Ricky-Hao commented 5 years ago

我这里是北京联通,有公网ip:

光猫 -桥接-> 路由器(拨号)(公网IP)->主机
kslr commented 5 years ago

https://github.com/v2ray/v2ray-core/issues/1429 这个问题暂时先保持打开

supersndqd commented 5 years ago

换个bsd系列的服务器系统看看呢,或者windows

xiaokangwang commented 5 years ago

首先V2Ray在设计的时候主要是为了TCP(尤其是网页浏览)设计的,所以对于UDP类型的流量的支持程度很差。(也就将就能用来进行DNS请求)

使用UDP进行通信的程序常常因为以下原因无法使用或性能不佳:

  1. V2Ray会将全部通信数据转化为流式格式(即SEQPACKET模型),不保留UDP的高速,低延迟特性。导致游戏在实际运行中出现延迟高,失去和其他客户端的同步的问题。

  2. V2Ray不支持任何形式的NAT穿透。这对于DNS等客户端-服务器模型的程序来说并不是什么大问题。但是对于类似游戏这样的使用P2P模式进行通信的程序来说是灾难性的。

xiaokangwang commented 5 years ago

我2年之前有建议过Raymond单独实现一个保留UDP特性的传输方式结果被拒绝了。 https://github.com/v2ray/v2ray-core/issues/578

xiaokangwang commented 5 years ago

我感觉如果想实现这个的话,比较简单的方式是利用类似Mux的机制,将一个新的微型协议整合入V2Ray\VMess.

使用基于AES-SIV之类的无overhead的加密模式在保留全部UDP特性并避免拆包的情况下传输UDP数据。

使用原有的VMess协议传输元数据,保证对于NAT穿透的支持。

xiaokangwang commented 5 years ago

你的网络是NAT吗?

1384

V2Ray客户端设备相对于通过其连接的其他网络设备而言,一定处于一个无法穿透的NAT环境中。

现在就是需要知道到底游戏是不是需要NAT穿透

1265578519 commented 5 years ago

你这问题,我早在2017年的时候,两年前就反映过,我出现是在吃鸡上面, 相同的服务器,部署ss,直接sstap直连没有问题,s5转到小飞机,也没有问题。 但是用v2ray,s5到v2rayn上,就出问题了,包括tcp,kcp,各种模式都试过,无限断流,或者是查看到日志无限刷UDP请求,导致进程占用率吃满CPU卡顿等等,很多种现象问题。数不过来,太多问题了,当时我全都有反应过,一个人都没有回。 然后以后我打游戏只用ss了,v2ray只能适合网页浏览,做BT下载,也是这种情况,可能只能用于TCP协议的页面浏览。

embeddedsecurity commented 5 years ago

你这问题,我早在2017年的时候,两年前就反映过,我出现是在吃鸡上面, 相同的服务器,部署ss,直接sstap直连没有问题,s5转到小飞机,也没有问题。 但是用v2ray,s5到v2rayn上,就出问题了,包括tcp,kcp,各种模式都试过,无限断流,或者是查看到日志无限刷UDP请求,导致进程占用率吃满CPU卡顿等等,很多种现象问题。数不过来,太多问题了,当时我全都有反应过,一个人都没有回。 然后以后我打游戏只用ss了,v2ray只能适合网页浏览,做BT下载,也是这种情况,可能只能用于TCP协议的页面浏览。

你说的S5是指socks5?

1265578519 commented 5 years ago

@embeddedsecurity 对,127.0.0.1到v2ray的socks5

0bo commented 5 years ago

你这问题,我早在2017年的时候,两年前就反映过,我出现是在吃鸡上面, 相同的服务器,部署ss,直接sstap直连没有问题,s5转到小飞机,也没有问题。 但是用v2ray,s5到v2rayn上,就出问题了,包括tcp,kcp,各种模式都试过,无限断流,或者是查看到日志无限刷UDP请求,导致进程占用率吃满CPU卡顿等等,很多种现象问题。数不过来,太多问题了,当时我全都有反应过,一个人都没有回。 然后以后我打游戏只用ss了,v2ray只能适合网页浏览,做BT下载,也是这种情况,可能只能用于TCP协议的页面浏览。

@1265578519 这几天也发现了这个问题,用路由器的游戏模式,switch 的nat type为D.

@xiaokangwang 即使使用v2ray搭建的shadowsocks,也是D。感觉是v2ray核心程序的问题,不是协议的问题。

xiaokangwang commented 5 years ago

你这问题,我早在2017年的时候,两年前就反映过,我出现是在吃鸡上面, 相同的服务器,部署ss,直接sstap直连没有问题,s5转到小飞机,也没有问题。 但是用v2ray,s5到v2rayn上,就出问题了,包括tcp,kcp,各种模式都试过,无限断流,或者是查看到日志无限刷UDP请求,导致进程占用率吃满CPU卡顿等等,很多种现象问题。数不过来,太多问题了,当时我全都有反应过,一个人都没有回。 然后以后我打游戏只用ss了,v2ray只能适合网页浏览,做BT下载,也是这种情况,可能只能用于TCP协议的页面浏览。

@1265578519 这几天也发现了这个问题,用路由器的游戏模式,switch 的nat type为D.

@xiaokangwang 即使使用v2ray搭建的shadowsocks,也是D。感觉是v2ray核心程序的问题,不是协议的问题。

嗯,估计还是要具体定位一下问题。看看能不能用简单的工具复现这个问题,然后找到问题的原因。

yuchting commented 5 years ago

你这问题,我早在2017年的时候,两年前就反映过,我出现是在吃鸡上面, 相同的服务器,部署ss,直接sstap直连没有问题,s5转到小飞机,也没有问题。 但是用v2ray,s5到v2rayn上,就出问题了,包括tcp,kcp,各种模式都试过,无限断流,或者是查看到日志无限刷UDP请求,导致进程占用率吃满CPU卡顿等等,很多种现象问题。数不过来,太多问题了,当时我全都有反应过,一个人都没有回。 然后以后我打游戏只用ss了,v2ray只能适合网页浏览,做BT下载,也是这种情况,可能只能用于TCP协议的页面浏览。

@1265578519 这几天也发现了这个问题,用路由器的游戏模式,switch 的nat type为D. @xiaokangwang 即使使用v2ray搭建的shadowsocks,也是D。感觉是v2ray核心程序的问题,不是协议的问题。

嗯,估计还是要具体定位一下问题。看看能不能用简单的工具复现这个问题,然后找到问题的原因。

简单工具复现:

你用一个很简单的透明代理,使用nc工具测试udp包,先用直接连接,再用ss-redir,再用v2ray。

简单使用如下:

在一台服务器上面:

nc -l -u -p 3333 -n -v 使用 udp协议监听本地223端口

然后在客户端(3333端口使用iptable判断转发到服务器上去):

nc 127.0.0.1 3333 -u -v -n 就可以连接,并且键盘输入回车发送了!两边可以相互发送。

关闭iptable直接连接测试 nc <服务器IP> 3333 -u -v -n

你能看到,使用ss-redir和直接连接的时候,行云流水。只要用v2ray,前几个字符还可以相互发送,后面就断了,得重新再连接。也就是说,v2ray 的udp本身就是供给DNS使用的,刷一下,就断了,根本不能维持一个稳定的连接。

但是,手机上的v2ray代理却没有这个问题,使用同一个服务器。

其实当年我看到之后,一开始想看懂源码进行修改的,后来花了一个月的通勤时间学了Go,然后花了一定时间研究了一下udp协议,优化了几周学习了iptable,然后项目压力一来,没时间了,就不搞了……

udp协议问题使用的场景非常多,不光游戏,我Google安卓手机没有udp几乎没法用,因为google几乎所有手机上面的app都是用一个叫QUIC,所以没有udp,透明代理在手机上就废了。

PS、不过v2ray的代码模块依赖性真高啊,而且搞得貌似有些太复杂,不像ss-libev,比较简单,可能是我对Go还不够熟悉的缘故吧。

@xiaokangwang

eycorsican commented 5 years ago

关于 NAT 的问题,如果会自己编译的话,可以尝试下这个 fork:https://github.com/eycorsican/v2ray-core

配置方面请使用最简单的 socks inbound + shadowsocks outbound,其它配置组合的代码没改所以应该是不行的,整体配置上,在 windows 下可以使用:SSTAP -> socks inbound -> shadowsocks outbound -> shadowsocks-libev(服务端):

{
    "inbounds": [
        {
            "port": 1086,
            "listen": "127.0.0.1",
            "protocol": "socks",
            "settings": {
                "auth": "noauth",
                "udp": true,
                "ip": "127.0.0.1"
            }
        }
    ],
    "outbounds": [
        {
            "protocol": "shadowsocks",
            "settings": {
                "servers": [
                    {
                        "email": "xxx@v2ray.com",
                        "address": "1.2.3.4",
                        "port": 10086,
                        "method": "aes-256-cfb",
                        "password": "123457",
                        "ota": false,
                        "level": 0
                    }
                ]
            },
            "tag": "proxy"
        }
    ]
}

仅测试用。

a8l1vy commented 5 years ago

UDP很有需求的。 放弃ss后发现游戏都戒了。现在只用v2ray了。 去VPN gate网站上随便下载一个udp的openvpn配置文件,修改配置,前置socks5代理加进去,配置里添加 route serverip netmask 让服务器走直连 (具体咋写的忘记了,都是复制粘贴的)。让openvpn通过v2ray的socks5 inbound。连接成功不了的。 只能使用tcp的openvpn配置。tcp配置用多了很难受。记得老早以前UDP的还可以来着。中间哪个版本更新之后就不能了。

udp主要还是打游戏。 次要就是注册东西,VPS的IP都注册不了,就下个openvpn的配置,通过v2ray的socks5 inbound连接。注册完成再一关。 比如注册苹果美区账号,苹果的idsm.apple.com把好多VPS地址禁止了。 只能电脑共享出来WiFi,openvpn共享网络连接给电脑共享的WiFi,openvpn通过v2ray的socks5 inbound。手机连接WiFi,商店登录账号,付款方式才可以选择none,才能完成注册。

LeXwDeX commented 5 years ago

v2ray别想了,彩6等需要NAT开放的。 老老实实用SS吧。

aryMBLec commented 4 years ago

最近udp的nat问题终于开始解决了吗?期待20年能解决这个老大难问题。

ragnaroks commented 4 years ago

服务器开放 udp 20000:65535 服务端 v2ray 使用 socks5 监听 0.0.0.0:$port 客户端 v2ray 使用 socks5 链接 $IP:$port,并转发至本地 127.0.0.1:1080

吃屎狗/叛乱沙暴/彩虹六号/战地4/救世之树/命运2.... 使用 sstap 全局代理并排除本地IP,暂未发现断流等现象,且Nattypetest显示fullcone

吃屎狗=>直接邀请好友游玩社区地图,游戏流畅,语音正常 叛乱沙暴=>未测试p2p 彩虹六号=>未测试p2p 战地4=>未测试p2p 救世之树=>未测试p2p 命运2=>语音正常,未提示"因NAT原因无法语音"

有一说一,再好的加速端也救不了掉线2

aryMBLec commented 4 years ago

服务器开放 udp 20000:65535 服务端 v2ray 使用 socks5 监听 0.0.0.0:$port 客户端 v2ray 使用 socks5 链接 $IP:$port,并转发至本地 127.0.0.1:1080

吃屎狗/叛乱沙暴/彩虹六号/战地4/救世之树/命运2.... 使用 sstap 全局代理并排除本地IP,暂未发现断流等现象,且Nattypetest显示fullcone

吃屎狗=>直接邀请好友游玩社区地图,游戏流畅,语音正常 叛乱沙暴=>未测试p2p 彩虹六号=>未测试p2p 战地4=>未测试p2p 救世之树=>未测试p2p 命运2=>语音正常,未提示"因NAT原因无法语音"

有一说一,再好的加速端也救不了掉线2

大家再说vmess协议,socks5的UDP穿透功能本来就十分完善了啊,肯定没问题。

embeddedsecurity commented 4 years ago

你这问题,我早在2017年的时候,两年前就反映过,我出现是在吃鸡上面, 相同的服务器,部署ss,直接sstap直连没有问题,s5转到小飞机,也没有问题。 但是用v2ray,s5到v2rayn上,就出问题了,包括tcp,kcp,各种模式都试过,无限断流,或者是查看到日志无限刷UDP请求,导致进程占用率吃满CPU卡顿等等,很多种现象问题。数不过来,太多问题了,当时我全都有反应过,一个人都没有回。 然后以后我打游戏只用ss了,v2ray只能适合网页浏览,做BT下载,也是这种情况,可能只能用于TCP协议的页面浏览。

请问你是用sstap 1.9.0.7版本嘛?你是不是把原版SS链接导入到SSTAP,不在SSTAP里选择战地1 GAME规则、不选择吃鸡GAME规则,不选择网游规则,SSTAP开全局代理进game? @Ricky-Hao

jiangcuo commented 4 years ago

最近在尝试使用阿里云试用小鸡搭建加速器,使用的是v2ray_tls_ws_nginx。sstap转发udp至v2ray用的socks5。一切正常,未感受到卡顿,但是有时候吃鸡存在断流,就是你看得到他们在动,而自己卡在延迟检测。因此想找一个基于UDP的富强方式,使用udpspeeder加速,但是在非常险峻的这段时间,貌似只有ws+tls最稳,试过mkcp。第二天端口阻断,第三天被封。google到这里,留言一下

fbion commented 4 years ago

最近在尝试使用阿里云试用小鸡搭建加速器,使用的是v2ray_tls_ws_nginx。sstap转发udp至v2ray用的socks5。一切正常,未感受到卡顿,但是有时候吃鸡存在断流,就是你看得到他们在动,而自己卡在延迟检测。因此想找一个基于UDP的富强方式,使用udpspeeder加速,但是在非常险峻的这段时间,貌似只有ws+tls最稳,试过mkcp。第二天端口阻断,第三天被封。google到这里,留言一下 套 https://github.com/wangyu-/udp2raw-tunnel

HaoweiCh commented 4 years ago

ss xchacha20 挺好的。

ohperhaps commented 4 years ago

Upd转发方面有没有什么更新

jinbasex commented 4 years ago

ss xchacha20 挺好的。

现在ss/ssr不封ip了吗?我就是被封好几个机子 没ip换 转来v2

1265578519 commented 4 years ago

@micnp ss出现封IP你肯定用的是垃圾脚本 你用这里的就没事了https://github.com/shadowsocks/shadowsocks-libev

jinbasex commented 4 years ago

@micnp ss出现封IP你肯定用的是垃圾脚本 你用这里的就没事了https://github.com/shadowsocks/shadowsocks-libev

????你确定你不是隧道吗?直接ss ssr现在不是很会被封吗?

1265578519 commented 4 years ago

@micnp ss出现封IP你肯定用的是垃圾脚本 你用这里的就没事了https://github.com/shadowsocks/shadowsocks-libev

????你确定你不是隧道吗?直接ss ssr现在不是很会被封吗?

@micnp 你要用支持aead加密的脚本,老掉牙的加密已经不安全了,有特征头,参考v2ray最近更新的内容,也是加入了aead加密才去掉了特征。

jinbasex commented 4 years ago

@micnp ss出现封IP你肯定用的是垃圾脚本 你用这里的就没事了https://github.com/shadowsocks/shadowsocks-libev

????你确定你不是隧道吗?直接ss ssr现在不是很会被封吗?

@micnp 你要用支持aead加密的脚本,老掉牙的加密已经不安全了,有特征头,参考v2ray最近更新的内容,也是加入了aead加密才去掉了特征。 emmmm 那有ssr脚本吗? 还是说现在ss脚本反而是比较新的?

HaoweiCh commented 4 years ago

ss,还是比较稳的

jinbasex commented 4 years ago

ss,还是比较稳的

会不会你们流量不大呀 现在不是说ss ssr 经常被封 我v2 一直跑4k 几个小时 都没事

HaoweiCh commented 4 years ago

玩游戏全部 ss 的代理。。自己用的 浏览网站的 ws + tls + vmess

不建议搬瓦工,这个是重点关注对象

三年了,挺稳的

加密方式要注意用 chacha20 等非对称加密的

kslr commented 4 years ago

@Ricky-Hao

bvmy commented 4 years ago

v2ray的shadowsocks协议就可以呀,一点问题都没有!当然也可以使用socks协议。Netch检测通通 FullCone. Apex玩起来一点问题都没有。 有没有人windows下搞 shadowsocks + udp2raw,把v2ray配置文件内的shadowsocks服务器还有端口改到udp2raw监听的127.0.0.1:3333 不可用,不知道这是为什么?