[Bug]: v2rayN (incorrectly) does not allow mux for vless+realty with "flow=none" #3657
Closed
2 tasks done
Labels
bug
Something isn't working
预期情况
(security=reality) + (flow=none) + MUX => Should be allowed by
v2rayN
(it is allowed byxray
)实际情况
It is correct that with
flow=xlts-rprx-vision
set for reality, v2rayN does not connection multiplexing (mux).But with
flow=none
set for reality, there is no longer any reason to disallow multiplexing.xray
allows this and I have tested a custom config withmux enabled=true concurrency=8
explicitly set for reality (withflow=none
) and it worked.In summary, the expected behavior should be:
(security=reality) + (flow=none) + MUX
=> Should be allowed(security=reality) + (flow=xlts-rprx-vision) + MUX
=> NOT allowed复现方法
Add any
security=reality
based v2ray server(with flow=vision or flow=none)
and v2rayN will setmux enabled=false, concurrency=-1
in the config passed to xray.exe (disables mux feature)This is the default behavior even in the latest build (v6.21) of v2rayN. But this is an unnecessary restriction.
日志信息
Not required, as the described behavior is the default and intentional (but incorrect) behavior of the current version of the software.
额外信息
No response
我确认已更新至最新版本
我确认已查询历史issues
The text was updated successfully, but these errors were encountered: