Leadaxe：LxBox 启动自动探测曾额外重测负载均衡组

Leadaxe 在 LxBox 问题清单中说明，round_robin 配合 pool_tolerance=0 时，内核先将最前面的 pool 个节点入池而不测试，之后只检查池内节点，出现空位才接触其余节点。启动后全节点探测来自默认启用的“Auto ping on start”：连接 5 秒后先测活动组每个节点以显示延迟，再强制对 urltest 组测试，导致内核重测全部成员并重建池。他表示已从自动探测尾部去掉 round_robin 与“Hold until failure”的强制组测试，后者原先会在节点未失败时重选；线程将该修复标为 develop 中完成、随下版发布。手动“Run URLTest”和自动化仍保留强制测试。对当前构建，他建议关闭“Auto ping on start”以获得所述池行为。他还解释，方向自动组仅测试该方向节点，直连与其他方向只供手动选择；链节点由内核逐跳作端到端测试。

作者原文@Leadaxe
Went through the list. Below: what works as designed and what is rejected. Items 8, 17, 18 are confirmed on our side. The rest (1, 2, 5, 6, 9, 12, 15, 19, 21) stays open as feature requests or pending data.
3, 14 — by design. <direction>-auto is a urltest over the direction's nodes only. direct-out and other directions are selector entries, not race participants. A direct outbound inside a urltest wins every test, and the auto group degrades to "always direct". Nested directions are picked manually for the same reason.
4 — already covered. A chain is one type: chain node. The kernel tests it end to end through every hop, so a hop that passes alone but cannot reach the endpoint fails the chain's test. Hops are not auto-picked by independent urltests here. If a chain passed its test and then failed on traffic, that is a separate report with the config attached.
7 — by design. A chain is a node in a direction's pool, not a direction. It shows up in the node list under the direction that includes it.
11, 13 — by design. "Replace groups" in a direction has something to replace only when the folder is folded into a group in its own settings. The node filter matches kernel outbounds; an unfolded folder is not an outbound, so there is nothing to match. The preview-without-tunnel part (12) is a real gap and stays open.
16 — the core does not; the app does. (task 677) A round_robin group with pool_tolerance: 0 seats the first pool nodes without testing, then health-checks only the pool and touches the rest only when a slot dies, as documented. What tests every node is "Auto ping on start" (App Settings, on by default): 5 s after connecting it pings every node of the active group to show delays in the list, and then forced a group URL test on every urltest group, which made the core re-test all members and rebuild the pool. That forced test only makes sense for Fastest (least_test): for round_robin it buys nothing, and for "Hold until failure" it resets the held node for no failure at all. It is removed from the auto-ping tail for both; the manual "Run URLTest" and automation keep theirs. Switching "Auto ping on start" off gives the documented behaviour on current builds. Docs: core balancer semantics — https://github.com/Leadaxe/sing-box-lx/blob/lx/docs/configuration/outbound/urltest.md#balancer ; app auto-select and balancing, pool mechanics — https://github.com/Leadaxe/LxBox/blob/develop/docs/spec/features/006-DETOUR_AND_BALANCE/FUNCTIONS/balancing.md (RU: balancing.ru.md) ; user guide — https://github.com/Leadaxe/LxBox/blob/develop/docs/USER_GUIDE.md
20 — rejected. sing-box has never accepted # comments. // and /* */ are accepted by the editor and stripped on Format, which is what sing-box's own parser does with them.
9, 17 — need data. For 9: composition mode (All / Rule / Explicit), member types, whether "Replace with a group" is on for that folder, and what exactly fails — the node is missing on the home screen, tap does nothing, or traffic does not flow. For 17: was the VPN up or down when it froze? If down, that is "Test servers" in a folder or subscription, and the cause is already located. App version for both.

返回动态列表查看原文