Fix WireGuard route-rule chains by binding generated route endpoints to TUN - #1714
Open
x15rte wants to merge 1 commit into
Open
Fix WireGuard route-rule chains by binding generated route endpoints to TUN#1714x15rte wants to merge 1 commit into
x15rte wants to merge 1 commit into
Conversation
Contributor
Author
|
Most of my traffic goes through a proxy chain, specifically by forwarding Singbox Shadowsocks via XRay Reality. |
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
1 participant
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.
Throne treated generated WireGuard endpoint tags as valid route-rule targets in the same way as normal outbounds. On sing-box 1.13.x, route rules targeting WireGuard endpoints do not reliably carry TCP/UDP route-profile traffic. This broke route-profile chains whose first generated hop was WireGuard/AmneziaWG. Applying
bind_interface = throne-tunto those generated WireGuard route endpoints to restores connectivity.This should be treated as a sing-box 1.13.x compatibility shim.
When Throne upgrades to sing-box 1.14+, re-check this path. sing-box 1.14 documents broader TCP/UDP L3 forwarding support to WireGuard/Tailscale endpoints, so this auto-bind may become unnecessary or should be gated by core version.