Adds support for bridged networking.#1
Open
brenns10 wants to merge 1 commit intog2p:masterfrom
Open
Conversation
The user may create bridges and connect them to host interfaces. Then, they can specify a bridge with the --bridge option, and qemu will create a tap device and connect it to that bridge. You can pass the same bridge multiple times to create several guest interfaces on the same bridge. The startup script requests a DHCP lease on all interfaces.
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
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.
This PR adds the ability to create multiple guest interfaces using a bridge interface on the host. Basically, on the host, you do something like this:
Then, you can launch the kernel vm with vido:
In the stub script, a dhcp client server will be launched for each interface created.
This also supports creating multiple guest interfaces that either share the same bridge or use different bridges:
The resulting VM has eth0 and eth1 which behave as completely independent NICs.
This is implemented using Qemu's bridge helper, which will create the required TAP device and add it to your bridge. You may need to edit
/etc/qemu/bridge.confto include the bridge device you created, as described in the link.I figured you might want to at least see this functionality, even if you don't end up merging it. It's very important for my use case, but I can always keep using my fork!