I hereby claim:
- I am lbogdan on github.
- I am lbogdan (https://keybase.io/lbogdan) on keybase.
- I have a public key ASAgdD06ulF9Q3S3sOgaWoFSS6rZ6jgp_Fc1COXa4WUWyQo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
| #!/bin/bash | |
| set -euo pipefail | |
| IMAGE_QCOW2="AlmaLinux-8-GenericCloud-8.5-20211119.x86_64.qcow2" | |
| IMAGE_URL="https://repo.almalinux.org/almalinux/8/cloud/x86_64/images/$IMAGE_QCOW2" | |
| IMAGE_VMDK="AlmaLinux-8-GenericCloud-8.5-20211119.x86_64.vmdk" | |
| VMS_PATH="/Users/lbogdan/Virtual Machines.localized" | |
| VM_NAME="control" | |
| USERNAME="lbogdan" |
So, I've been taking a better look at VirtualBox's networking model. Turns out that the Vagrant's networking model was a direct consequence of VirtualBox's: if you take a look at VirtualBox's Networking Modes documentation, you'll see the only mode that provides full Host <-> VM, VM1 <-> VM2 and VM <-> Internet connectivity by using a single network interface is "Bridged".
That's probably the reason why Vagrant chose to use "NAT" mode for the default network interface, which provides VM <-> Internet connectivity, and only limited Host <-> VM connectivity, by using port forwarding to be able to SSH from the Host to the VM. So if you need additional full Host <-> VM and VM1 <-> VM2 connectivity, you'll need to add another network interface in "Host-only" mode.
So it looks like for fluff we're only left with being able to use "Bridged" mode, which comes with a few drawbacks: