[Bug]: v2rayN (incorrectly) does not allow mux for vless+realty with "flow=none"

[OnceUponATimeInAmerica]

预期情况

(security=reality) + (flow=none) + MUX => Should be allowed by v2rayN(it is allowed by xray)

实际情况

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 with mux enabled=true concurrency=8 explicitly set for reality (with flow=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 set mux 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

我确认已更新至最新版本

• [X] 是

我确认已查询历史issues

• [X] 是

[2dust]

when security=reality msut flow=xlts-rprx-vision

[OnceUponATimeInAmerica]

when security=reality msut flow=xlts-rprx-vision

But it says here in the official repo's comments that it is optional.

And I have it (security=reality) working perfectly with flow=none and mux enabled=true too (I also checked that local tcp connections are being multiplexed into the same remote tcp connection with TcpView or SystemInformer).

Also I have seen other configs (e.g. this popular x-ui-fork's latest version) which also allows both flow=none and flow=xlts-rprx-vision.

[2dust]

https://github.com/2dust/v2rayN/releases/tag/6.22

[OnceUponATimeInAmerica]

thanks.