[Feature Request] Wireguard outbound
- Dominant language
- Go
- Stars
- 6.2k
- Forks
- 403
- Avg merge
- 57m
- Merged PRs (30d)
- 2
Description
### Greetings
_No response_
### Feature Request
I want wireguard outbound support with reserved bits for WARP.
I found #397 as not planned but I don't need to bypass GFW.
### Use Cases
Fast and secure connection for people outside of the Chinese Mainland
### Potential Benefits
People subscribed [Mullvad](https://mullvad.net/en/servers), [WindScribe](https://windscribe.com/getconfig/wireguard), or any other VPNs that provide WireGuard profiles can configure them easily without [complex config](https://github.com/daeuniverse/dae/blob/main/docs/en/configuration/gaming-oriented-routing.md).
With reserved bits support, some IP ban targeted data-center IPs may be bypassed with WARP proxy chaining too.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing issue #397 and docs/en/configuration/gaming-oriented-routing.md to understand the existing outbound configuration and why complex config is currently required. Define the integration needed for WireGuard profiles and reserved bits for WARP, then establish tests or acceptance criteria showing profiles can be configured and WARP proxy chaining works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100