Add dropweb Mihomo RU Cascade template (auto-failover) - #85
Open
enkinvsh wants to merge 1 commit into
Open
Conversation
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.
What
New MIHOMO subscription template
by-dropweb/subscription-templates/mihomo-ru-cascade.yaml+ registry entry insubscription-templates-list.json.Why another RU template
Unlike the existing select-based templates, routing here is fully automatic — users never pick a server manually:
[🌀 Cascade → ⚡ Fastest]: cascade nodes (RU-entry → EU-exit) preferred; automatic failover to the fastest direct node when the cascade dies; automatic return when it recovers[⚡ Fastest → 📶 First Available]— emergency net when the whole main pool is downHealth-check parameters verified against mihomo core sources
Documented in the template header:
expected-status: 204across all groups sharing one health-check url — per-url alive state is stored keyed by url (adapter.go), mixed criteria cause alive flapping between groupslazy: trueare safe because failover is event-driven (groupbase.goonDialFailed: real-traffic failures trigger an immediate health check) — battery-friendly on mobile without losing switching speedtimeout: 8000on the cascade path — a 2-hop probe under load doesn't fit the default 5s, causing false DEAD → flappingRU specifics
no-resolvelogic rule, voice on UDP/443 keeps working)exclude-packagelist, rules ordered so RU domains match without forced DNS resolutionCascade node-name filters are clearly marked for operators to adjust (
>>> ПОМЕНЯЙТЕ ПОД СЕБЯ <<<); comments are in Russian, consistent with the other RU templates.Running in production on our fleet (dropweb.org).