Virtualbox - Revision history

M: /* LAN and DHCP */

2018-04-20T15:10:24Z

LAN and DHCP

← Older revision		Revision as of 15:10, 20 April 2018
Line 19:		Line 19:

	* For each VM > Settings > Network > Adapter1 > Attached to: Bridged Adapter		* For each VM > Settings > Network > Adapter1 > Attached to: Bridged Adapter
			* Do NOT "create a network" for the host

	That spoofs VM packets so they travel to host LAN as if VM was also on the LAN. From what I've read, wifi connections in linux do NOT work with bridged due to anti-spoofing protections. But wired works fine. You'll get an IP from the host's LAN. You can go host <-> VM since they are both on the LAN.		That spoofs VM packets so they travel to host LAN as if VM was also on the LAN. From what I've read, wifi connections in linux do NOT work with bridged due to anti-spoofing protections. But wired works fine. You'll get an IP from the host's LAN. You can go host <-> VM since they are both on the LAN.

2018-04-20T15:09:50Z

LAN and DHCP

← Older revision		Revision as of 15:09, 20 April 2018
Line 15:		Line 15:

	=== LAN and DHCP ===		=== LAN and DHCP ===

			ALWAYS use bridged mode, so the boxes can see each other, and the host, and the internet, ffs:

			* For each VM > Settings > Network > Adapter1 > Attached to: Bridged Adapter

			That spoofs VM packets so they travel to host LAN as if VM was also on the LAN. From what I've read, wifi connections in linux do NOT work with bridged due to anti-spoofing protections. But wired works fine. You'll get an IP from the host's LAN. You can go host <-> VM since they are both on the LAN.

			OLD NOTES

	I think these are the defaults, they seem sane:		I think these are the defaults, they seem sane:

2018-04-11T17:08:51Z

← Older revision		Revision as of 17:08, 11 April 2018
Line 13:		Line 13:
	cd /mnt/guestiness/		cd /mnt/guestiness/
	./VBoxLinuxAdditions.run		./VBoxLinuxAdditions.run

			=== LAN and DHCP ===

			I think these are the defaults, they seem sane:
			Host app > File > Host Network Manager > Properties > Adapter > [x] Configure automatically
			> DHCP Server > Server Address > 192.168.56.100
			> Lower/Upper bounds .101 - .254
			So we can just set a static one in a VM to:
			192.168.56. [2 through .99]
			And set up the host in the VM hosts file to:
			192.168.56.100

2018-04-11T15:43:43Z

← Older revision		Revision as of 15:43, 11 April 2018
Line 1:		Line 1:
	~~VirtualBox works great if you don't mess with it too much - do NOT install any virtualbox* apt packages.~~		=== Guest Additions ===
			Guest additions seem to be a necessary evil to get the clock syncing. Which version to install? Seems that the apt way is working best.
	=== ~~Time sync~~ ===		* In Ubuntu you can use apt:
	~~I'm not getting time sync, trying this~~:		sudo apt-get install dkms
	sudo apt-get install virtualbox-guest-~~dkms~~		sudo apt-get install virtualbox-guest-additions-iso
	sudo apt install ~~ntp~~		# check the status:
	~~We will see~~..		sudo service virtualbox-guest-utils status
			# DO NOT INSTALL ntp!
			sudo apt remove ntp
			* You can mount /dev/cdrom to get the version that came with the Windows host install.
			su -
			mount /mnt/cdrom /mnt/guestiness
			cd /mnt/guestiness/
			./VBoxLinuxAdditions.run

2018-04-09T14:56:01Z

← Older revision		Revision as of 14:56, 9 April 2018
Line 1:		Line 1:
	VirtualBox works great if you don't mess with it too much - do NOT install any virtualbox* apt packages.		VirtualBox works great if you don't mess with it too much - do NOT install any virtualbox* apt packages.

			=== Time sync ===
			I'm not getting time sync, trying this:
			sudo apt-get install virtualbox-guest-dkms
			sudo apt install ntp
			We will see..

2017-12-20T18:21:04Z

Created page with "VirtualBox works great if you don't mess with it too much - do NOT install any virtualbox* apt packages."

New page

VirtualBox works great if you don't mess with it too much - do NOT install any virtualbox* apt packages.