Currently enabling the option will add Mux option to outbound regardless of the outbound is able to use Mux or would break if used.
Currently we cannot use Mux in these configurations:
Vless + vision + * : breaks the connection
xhttp :(only xudp is usable)
My recommendation:
In VLESS + Vision outbounds : Do not add Mux option or have it set to false as this will break the entire connection.
In XHTTP outbounds : according to the description provided by rprx it has XMux enabled by default so there is harm in enabling mux.cool. In this case set concurrency to -1 and only set xudpConcurrency if the user did set it in config.
Let me know your thoughts.
Regards,
Currently enabling the option will add Mux option to outbound regardless of the outbound is able to use Mux or would break if used.
Currently we cannot use Mux in these configurations:
Vless + vision + * : breaks the connection
xhttp :(only xudp is usable)
My recommendation:
In
VLESS + Visionoutbounds : Do not add Mux option or have it set tofalseas this will break the entire connection.In
XHTTPoutbounds : according to the description provided by rprx it has XMux enabled by default so there is harm in enabling mux.cool. In this case setconcurrencyto -1 and only setxudpConcurrencyif the user did set it in config.Let me know your thoughts.
Regards,