Virtualbox VLANs in Ubuntu

Wanted to add quick note about VLANs, VirtualBox, and Ubuntu.

Virtualbox does VLANs a little differently on Ubuntu than other hypervisors. In order to get a VLANs working for a Virtualbox VM, you have to create a subinterface that is for a specific VLAN (of course, assuming your NIC supports 802.1q tagging). To create a subinterface in Ubuntu, follow the instructions here:

https://wiki.ubuntu.com/vlan

Then in Virtualbox, you set the network interface to ‘bridged mode’, then select the subinterface. Assuming your new subinterface is permanent, the VM will use that subinterface and be within that VLAN.

I’m not entirely sure how to accomplish this for Virtualbox on Windows. It would seem like you would need a separate physical interface, especially for Windows 10 and probably others.

Unrelated note: Virtualbox on Windows 10 is horrible, and so is the native Hyper-V, but that’s for another post, maybe.

Edit (20180705): A few years later, and I can honestly say VirtualBox on Windows 10 is stable now, and has been for awhile. Felt the need to update this. :-p

What I Learned This Week

Here’s my first installment of “What I learned This Week”. It’s just a collection of topics that I’m hoping to solidify into solid memories versus fluid, potentially lost ones.

  • Sysprep doesn’t work on upgrades. Sysprep is a tool used for imaging, and according to the error log generated after I attempted a sysprep on a Windows 8.1 machines that was upgraded from Windows 8, you cannot sysprep machines that were upgraded.
  • In Ubuntu 12.04, the DHCP server isn’t named DHCP3 but isc-dhcp-server. The settings also different; dhcpd server settings are located in /etc/dhcp/dhcpd.conf. More info here.
  • The MCSA is a pain in the a–, especially the 70-412. That was the hardest MS test I’ve taken.

That’s all folks.

That's all folks!