Add Lneto as a stack - #143
Closed
soypat wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Patricio Whittingslow <graded.sp@gmail.com>
Member
|
Why closed? Looked interesting |
Author
|
I'll be adding it in netbird's repo first since that's what I'll be testing on- as soon as we get it working there I'll be more than happy to send one your way! |
Member
|
Disappointing. Forks are annoying. Send this upstream. |
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
2 participants
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.
Hey! I wanted to add an alternative networking stack for use with wireguard as part of a project to add it in netbird. Gvisor currently does not compile with TinyGo and using something like lneto would allow for much smaller binaries besides providing support for use of wireguard on microcontrollers.
This PR is still a WIP. The Net2 type provided is just a working title (and also a working abstraction at that). Ideally wireguard go should go the go-net abstraction way where the networking stack is an interface provided during configuration (my opinion :) )
https://github.com/soypat/lneto