Repository navigation
Conversation
- 新增 openclash-target-via-proxy-when-direct-degrades.md:tproxy 的 TCP connect 是假握手不能当判据;用 ICMP 丢包 + 应用层握手(RDP X.224)+ 三方对照定界;订阅节点不放行 3389;自定义规则引用 overwrite 脚本动态创建的组会被合并阶段丢弃,须在脚本里幂等注入;保留 DIRECT 兜底;目标规则不挂 url-test - 级联登记 best-practices index/log、solutions 根 log 与平表 - us_openai_api_proxy 的 handoff / log / office-lan-access 补指针,与 per-target-direct 那篇双向互链 - AGENTS.md 经验库篇数同步(best-practices 9→10、总 131→133) 已同步更新根目录索引。无客户数据/凭证;无隐私外泄。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
做了什么
docs/solutions/best-practices/openclash-target-via-proxy-when-direct-degrades.md(直连「能用但严重丢包」时把单个目标改走代理的排查方法论)index.md/log.md、docs/solutions/log.md与根平表us_openai_api_proxy的AGENT_HANDOFF.md/docs/log.md/docs/office-lan-access.md补指针,并与openclash-per-target-direct-rule.md双向互链AGENTS.md经验库篇数同步(best-practices 9→10、总 131→133)为什么
某境外 Windows Server 的 RDP 在办公室「能用但严重丢包」(直连 40 包丢 45%),换光猫/WiFi 无改善、服务器重启也无效。排查确认:
openclash_custom_overwrite.sh动态创建的策略组会被合并阶段丢弃,只能在该脚本里幂等注入。这些判据与坑对以后同类问题可复用,值得沉淀。
怎么测
uv run python scripts/check_solutions_health.py --strict→ 通过(预存的 3 条 frontmatter 日期键 WARN 与 5 条豁免为历史遗留,非本次引入)uv run python scripts/check_secrets.py→ OK(649 个文件无明文凭证)文档只写占位符与相对路径,实际目标 IP / 中转地址仍只保留在受控配置。
无客户数据/凭证;无隐私外泄。