Open maskedeken opened 3 years ago
两天前的提交已经修复 https://github.com/XTLS/Xray-core/commit/13ad3fddf6f7ff01fe9541b6c9f2dca6f7f87e4b
(不过最新的 commit 有问题,等下会 force
怎么解决循环引用的问题?
如果发现存在其它问题,也请直接反馈
比如目前发现任意门 TPROXY 那里不能缓存 conns,只能发一个包就 close,否则行为会异常,等下打算看看把 dial 改为 listen 的表现
问题修复了吗,我用最新版碰到了相同的问题 我想大概是使用TPROXY转发UDP流量导致,使用tun2socks转发不会出现这类问题。
I encountered this issue just now on xray 1.8.10
unfortunately i have nothing useful to reproduce it with. the server config has been running fine for a very long time before then, so i suspect it is somehow triggered by traffic and not the config itself. but i also don't know which protocol.
It occurs with 1.8.13 as well. Stacktrace is the same.
Is it reasonable to think the broken address comes from a specific inbound? I can try to remove inbounds from production (or rather, move them to a secondary xray container) until the problem stops occurring, but would like to know if it's worth the effort.
currently the issue only happens 2-3 times per day, so it's kind of fine with autorestart.
Also had this a few times on one server. Can you by any chance have any outbound with ForceIP?
I didn't checked the code but I didn't see this error anymore when I removed plain ForceIP from outbound (ForceIPv4v6 & ForceIPv6v4 is ok for me)
i posted my full config above, no I don't use any variant of ForceIP.
i posted my full config above, no I don't use any variant of ForceIP.
Oh, sorry, didn't pay enough attention. Now I see. That's strange than.
If I encounter that once more I'll get back with additional info.
在往buf.Buffer的UDP属性赋值的时候,创建 &net.UDPAddr{ IP: addr.IP(), Port: int(port.Value()), }
但这里的addr是从addrParser.ReadAddressPort()而来,这里的addr有可能是域名,如果直接调用addr.IP(),会直接panic
func (domainAddress) IP() net.IP { panic("Calling IP() on a DomainAddress.") }