Skip to content

Conversation

yuhan6665
Copy link
Member

  • Always apply NoTerminationSignal

@yuhan6665
Copy link
Member Author

这个很奇怪
vmess 改了 Link 之后 一般用法没问题 就是 Mux(TCP) 和 reverse proxy 会出现 头几个连接正常 后面死掉的情况
但是 VLESS 却没事

@yuhan6665
Copy link
Member Author

yuhan6665 commented Sep 14, 2025

好像是因为 vmess 的 mux 只会 DispatchLink 一次 而 VLESS 会多次

@yuhan6665
Copy link
Member Author

这样可以修复 4eadb8f
也就是说在 Mux 环境下省掉 pipe 是可能的 但是由于多个子链接会同时写 势必导致代码逻辑较复杂的各个地方需要加锁
所以我觉得在 Mux 环境下用 pipe 的设计可能更好一点? @RPRX

@RPRX
Copy link
Member

RPRX commented Sep 15, 2025

我还想让 VLESS 出站也能返回个 reader / writer,这样可以把客户端 outbound reverse 那个 pipe 给省掉

- Always apply NoTerminationSignal
For Mux, we need to use pipe to guard against multiple sub-connections writing back responses at the same time
@yuhan6665
Copy link
Member Author

在 Vmess 加锁我觉得不对 因为是全局锁 而 pipe 是锁单个连接
把 pipe 转移到 Mux 那边应该可以
还需要修 reverse。。
另外加了 vlessenc (Mux Tcp) 测试

@yuhan6665 yuhan6665 marked this pull request as ready for review September 22, 2025 00:11
@yuhan6665
Copy link
Member Author

修好了 你们看一下 mux server 和 reverse portal 这样改行不行
@RPRX @Fangliding

@RPRX
Copy link
Member

RPRX commented Oct 14, 2025

我觉得 VMess inbound 倒是无所谓,只是往 Mux/Reverse 再加 pipe 这种事情尽量避免吧

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants