Set the MTU on tap interfaces #308
Open
Conversation
This file contains 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.
The MTU of tap interfaces must match the bridge they're added to. This PR makes the tap interface MTU match the bridge interface.
I ran into this when switching over to a larger MTU to get better throughput for services I'm testing. I found that I needed to manually set the MTU of the tap interfaces and add them to the bridge after starting guests. During startup, there'd be errors like
ifconfig: BRDGADD tap0: Invalid argument.I've tested this in a couple of cases, but it's certainly not exhaustively vetted.
Thanks! Hopefully it's worth the merge.