Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Add WireGuard inbound #2236

Open
bsdayo opened this issue Nov 1, 2024 · 2 comments
Open

[Feature Request] Add WireGuard inbound #2236

bsdayo opened this issue Nov 1, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@bsdayo
Copy link

bsdayo commented Nov 1, 2024

Currently, sing-box only supports WireGuard as a outbound. Works great when it is used only for access to the server, but the server cannot access back, while the official WireGuard client can achieve this.

For example, Server A which is running sing-box (with WireGuard outbound), connect to Server B, which is running WireGuard server, A can nc to B, but B cannot nc to A.

It will be handy if sing-box also supports WireGuard as a inbound, as this will only require sing-box (1 tool) to setup the network, without the need of a dedicated WireGuard client.

@nekohasekai nekohasekai added the enhancement New feature or request label Nov 17, 2024
@devopg
Copy link

devopg commented Nov 18, 2024

I support the proposal.

@finch71
Copy link

finch71 commented Nov 25, 2024

Just tried the new endpoint and it's super cool!!

The only problem is that wireguard does not support QUIC/bbr and therefore performs bad in bad internet environment.

It would be nice to extend TUIC/Hysteria1 protocol to support bi-directional communication. (since they are anyways abandoned)

Mirror: apernet/hysteria#1256

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants