V2ray-core: quic+caddy+v2ray的问题

Created on 30 Nov 2018 · 5Comments · Source: v2ray/v2ray-core

1) 你正在使用哪个版本的 V2Ray？
4.7.0
2) 你的使用场景是什么？
像h2一样，用caddy在443端口做一次代理到v2ray的quic端口
3) 你看到的不正常的现象是什么？
客户端直接填v2ray的quic端口可以使用，换成443不行
4) 你期待看到的正确表现是怎样的？
可以正常使用
5) 请附上你的配置。

服务器端配置:

    {
            "port": 445,
            "protocol": "vmess",
            "tag": "quicin",
            "settings": {
                "clients": [
                    ***
                ],
                "disableInsecureEncryption": false
            },
            "streamSettings": {
                "network": "quic",
                "quicSettings": {
                    "security": "none",
                    "key": "",
                    "header": {
                        "type": "none"
                    }
                },
                "security": "tls",
                "tlsSettings": {
                    "serverName": "quic.name",
                    "allowInsecureCiphers": false,
                    "certificates": [
                        {
                            "certificateFile": *,
                            "keyFile": *
                        }
                    ]
                }
            },
            "sniffing": {
                "enabled": false,
                "destOverride": [
                    "http",
                    "tls"
                ]
            }
        }
附上caddy
https://quic.name {
    tls *
    proxy / quic://127.0.0.1:445 {
        insecure_skip_verify
        header_upstream Host "quic.name"
    }
}

客户端配置:

    "outbound": {
    "protocol": "vmess",
    "tag": "direct",
    "settings": {
      "vnext": [
        {
          "address": "quic.name",
          "port": 445,
          "users": [
            *
          ]
        }
      ]
    },
    "streamSettings": {
      "network": "quic",
      "security": "tls",
      "quicSettings": {
        "security": "none",
        "key": "",
        "header": {
          "type": "none"
        }
      },
      "tlsSettings": {
        "serverName": "quic.name",
        "allowInsecure": false
      }
    },
    "mux": {
      "enabled": false
    }
  },

6) 日志
caddy加上QUIC_GO_LOG_LEVEL=DEBUG的环境变量之后，连接443一直输出 muxer error handling packet from host:port: error parsing header: InvalidPacketHeader: Received packet with invalid packet type: 65

端口改成445，wireshark抓了下包，发现浏览器直连访问我网站443端口的包能被识别为gquic，v2ray到445的包还是被识别为普通udp包

Source