Fix for VBox NAT interface address #1041
Merged
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
mpapis
added a commit
that referenced
this pull request
Mar 6, 2015
Fix for VBox NAT interface address
|
thank you! |
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.
Hi,
I wanted to be able to build a virtualbox vm and have 4 NICs attached to it. It turned out you can not by default do that because of the way VBox assigns IPs to NAT. If the NIC to get NAT is eth0 all is well and it works, but if it's eth3 it doesn't work anymore because veewee serves the kickstart on the wrong IP.
I only tested on my box by using 4 network card and changing the NAT one, from eth0 to eth3.