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

Update WireGuard's conn.Bind to use message vectors #137

Open
stv0g opened this issue Mar 5, 2023 · 0 comments
Open

Update WireGuard's conn.Bind to use message vectors #137

stv0g opened this issue Mar 5, 2023 · 0 comments
Labels
enhancement New feature or request performance Improves performance

Comments

@stv0g
Copy link
Collaborator

stv0g commented Mar 5, 2023

The recent improvements by Tailscale in wireguard-go have changed wireguard-go's conn.Bind interface to use message vectors.

We are currently using this new interface. However, we are limited to vectors with just a single message in it.

We should refactor the code, to allow processing larger batches of messages where possible.
Unfortunately, pion/ice does not support this. So this is only applicable to the places where we bypass the ice.Conn.

@stv0g stv0g added enhancement New feature or request performance Improves performance labels Mar 5, 2023
@stv0g stv0g added this to the First Stable (v1.0) milestone Jun 7, 2023
@stv0g stv0g changed the title Update wireguard-go and Bind to use message vectors Update WireGuard's conn.Bind to use message vectors Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request performance Improves performance
Projects
None yet
Development

No branches or pull requests

1 participant