support bridge tap to reduce hop between tap & nic#19
Merged
Conversation
New network/bridge package: creates TAP devices and adds them directly to an existing Linux bridge as ports. An external DHCP server on the bridge serves VM IPs. Data path: VM → TAP → bridge → eth0 (3 hops, vs CNI's 5 hops). No veth, no TC redirect, no netns. TAP is a direct bridge port. Designed to work with cocoon-net's cni0 bridge or any pre-existing bridge with DHCP + routing already configured. Usage: cocoon vm run --bridge cni0 --name vm1 IMAGE The --bridge flag is mutually exclusive with --network (CNI). CH and FC launchProcess skip EnterNetns when NetnsPath is empty.
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.
No description provided.