I didn’t care about the latter– I just needed internet access from the VM. Normally, in this setup, the VM would attempt to use the development laptop as a NAT gateway for external access, but since our laptop isn’t setup that way, the VM can’t see the internet nor is it accessible from the internet. eth0: Host-only interface connecting to laptop’s vboxnet0.I disabled DHCP to reproduce production setup. vboxnet0: VirtualBox’s host-only interface (creating these is well-documented).This is actually pretty easy, especially after reading Ubuntu’s Connection Sharing wiki page. Since I’m trying to reproduce a production system in VirtualBox for testing purposes (which is how I typically use it), it stands to reason that I want the VM setup as close to the real thing as possible. However, I’m trying to test out some new networking ideas for my OpenStack Network node, and it doesn’t have a NIC configured with NAT. Of course, you’re saying “There’s a better way to do that!” And of course, I agree: with no other considerations, the best way to do this is to simply add another NIC to the VM configured as NAT instead of host-only. I ran into the need to access the internet from a VirtualBox VM via host-only networking.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |