NST and Virtual Machines - Revision history

Paul Blankenbaker: Added section on creating VMDK meta file

2020-01-22T19:25:28Z

Added section on creating VMDK meta file

@@ Line 123: / Line 123: @@
 * You'd like to monitor the network traffic to and from a particular Windows machine, and you don't have the necessary hardware to tap into what's going across the Ethernet cable. By booting the Network Security Toolkit within a virtual machine on the Windows machine, you will be able to monitor the Ethernet traffic with tools such as wireshark, snort, ntop, etc.
 * You are doing development on a Windows machine and would like to use some of the features from the Network Security Toolkit without using an additional machine (the Network Security Toolkit makes it pretty easy to setup a web server or SQL database in these situations).
 == How Much Does It Cost? ==

Rwh: /* USB Access: VirtualBox 6.x or Greater */

2020-01-03T00:26:06Z

USB Access: VirtualBox 6.x or Greater

← Older revision		Revision as of 20:26, 2 January 2020
Line 111:		Line 111:
	VMs running on VirtualBox 6.x or greater requires the user running the VirtualBox hypervisor to be added to the "'''vboxusers'''" group. In this example we will add the "'''nst'''" user to the "'''vboxusers'''" group.		VMs running on VirtualBox 6.x or greater requires the user running the VirtualBox hypervisor to be added to the "'''vboxusers'''" group. In this example we will add the "'''nst'''" user to the "'''vboxusers'''" group.

	usermod -G vboxusers -a nst		usermod -G vboxusers -a nst;

	= VMware Frequently Asked Questions =		= VMware Frequently Asked Questions =

Rwh: /* USB Access: VirtualBox 6.x or Greater */

2020-01-03T00:25:52Z

USB Access: VirtualBox 6.x or Greater

← Older revision		Revision as of 20:25, 2 January 2020
Line 110:		Line 110:
	== USB Access: VirtualBox 6.x or Greater ==		== USB Access: VirtualBox 6.x or Greater ==
	VMs running on VirtualBox 6.x or greater requires the user running the VirtualBox hypervisor to be added to the "'''vboxusers'''" group. In this example we will add the "'''nst'''" user to the "'''vboxusers'''" group.		VMs running on VirtualBox 6.x or greater requires the user running the VirtualBox hypervisor to be added to the "'''vboxusers'''" group. In this example we will add the "'''nst'''" user to the "'''vboxusers'''" group.

			usermod -G vboxusers -a nst

	= VMware Frequently Asked Questions =		= VMware Frequently Asked Questions =

Rwh: /* VirtualBox 6.x or Greater USB Access */

2020-01-03T00:21:52Z

VirtualBox 6.x or Greater USB Access

← Older revision		Revision as of 20:21, 2 January 2020
Line 108:		Line 108:
	NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.		NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.

	== VirtualBox 6.x or Greater ~~USB Access~~ ==		== USB Access: VirtualBox 6.x or Greater ==
	VirtualBox 6.x or greater requires the user running VirtualBox to be added to the "'''vboxusers'''" group. In this example we will add the "'''nst'''" user to the "'''vboxusers'''" group.		VMs running on VirtualBox 6.x or greater requires the user running the VirtualBox hypervisor to be added to the "'''vboxusers'''" group. In this example we will add the "'''nst'''" user to the "'''vboxusers'''" group.

	= VMware Frequently Asked Questions =		= VMware Frequently Asked Questions =

Rwh: /* VirtualBox Frequently Asked Questions */

2020-01-03T00:20:29Z

VirtualBox Frequently Asked Questions

← Older revision		Revision as of 20:20, 2 January 2020
Line 107:		Line 107:

	NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.		NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.

			== VirtualBox 6.x or Greater USB Access ==
			VirtualBox 6.x or greater requires the user running VirtualBox to be added to the "'''vboxusers'''" group. In this example we will add the "'''nst'''" user to the "'''vboxusers'''" group.

	= VMware Frequently Asked Questions =		= VMware Frequently Asked Questions =

Rwh: /* How do I update the VirtualBox Server Modules on Hypervisor (v5.0.x)? */

2016-07-02T12:39:11Z

How do I update the VirtualBox Server Modules on Hypervisor (v5.0.x)?

← Older revision		Revision as of 08:39, 2 July 2016
Line 100:		Line 100:
	NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.		NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.

	== How do I update the VirtualBox Server Modules on Hypervisor (v5.0.x)? ==		== How do I update the VirtualBox Server Modules on the Host Hypervisor (v5.0.x)? ==

	Anytime you update the kernel on a Linux based system running VirtualBox v5.0.x, you will need to tell VirtualBox to rebuild its kernel modules. This can be done using the following command:		Anytime you update the kernel on a Linux based system running VirtualBox v5.0.x, you will need to tell VirtualBox to rebuild its kernel modules. This can be done using the following command:

Rwh: /* How do I update the VirtualBox Server Modules on Hypervisor (v3.1.x)? */

2016-07-02T12:38:49Z

How do I update the VirtualBox Server Modules on Hypervisor (v3.1.x)?

← Older revision		Revision as of 08:38, 2 July 2016
Line 92:		Line 92:
	See the [[HowTo Install VirtualBox]] page for details.		See the [[HowTo Install VirtualBox]] page for details.

	== How do I update the VirtualBox Server Modules on Hypervisor (v3.1.x)? ==		== How do I update the VirtualBox Server Modules on the Host Hypervisor (v3.1.x)? ==

	Anytime you update the kernel on a Linux based system running VirtualBox v3.1.x, you will need to tell VirtualBox to rebuild its kernel modules. This can be done using the following command:		Anytime you update the kernel on a Linux based system running VirtualBox v3.1.x, you will need to tell VirtualBox to rebuild its kernel modules. This can be done using the following command:

Rwh: /* How do I update the VirtualBox Server Modules? */

2016-07-02T12:37:40Z

How do I update the VirtualBox Server Modules?

← Older revision		Revision as of 08:37, 2 July 2016
Line 92:		Line 92:
	See the [[HowTo Install VirtualBox]] page for details.		See the [[HowTo Install VirtualBox]] page for details.

	== How do I update the VirtualBox Server Modules? ==		== How do I update the VirtualBox Server Modules on Hypervisor (v3.1.x)? ==

	Anytime you update the kernel on a Linux based system running VirtualBox v3.1.x, you will need to tell VirtualBox to rebuild its kernel modules. This can be done using the following command:		Anytime you update the kernel on a Linux based system running VirtualBox v3.1.x, you will need to tell VirtualBox to rebuild its kernel modules. This can be done using the following command:

	service vboxdrv setup		service vboxdrv setup;

			NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.

			== How do I update the VirtualBox Server Modules on Hypervisor (v5.0.x)? ==

			Anytime you update the kernel on a Linux based system running VirtualBox v5.0.x, you will need to tell VirtualBox to rebuild its kernel modules. This can be done using the following command:

			/sbin/rcvboxdrv setup;

	NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.		NOTE: This this is different than the "VirtualBox Guest Additions" as this refers to the native OS under which the VirtualBox environment is running under.

Rwh: /* How Do I Add More Than One Network Ethernet Adapter? (VMware Player: Windows) */

2012-10-27T14:45:01Z

How Do I Add More Than One Network Ethernet Adapter? (VMware Player: Windows)

← Older revision		Revision as of 10:45, 27 October 2012
Line 220:		Line 220:
	ethernet3.vnet = "vmnet4"		ethernet3.vnet = "vmnet4"

	'''***Note:''' One can also use the new '''vmxnet3''' virtual network driver. According to VMware: The VMXNET 3 adapter is the next generation of a paravirtualized NIC designed for performance, and is not related to VMXNET or VMXNET 2. It offers all the features available in VMXNET 2, and adds several new features like multiqueue support (also known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.		'''***Note:''' One can also use the new '''vmxnet3''' virtual network driver. Example for "'''eth0'''":

			ethernet0.present = "TRUE"
			ethernet0.virtualDev = "vmxnet3"
			ethernet0.startConnected = "TRUE"
			ethernet0.connectionType = "custom"
			ethernet0.vnet = "vmnet0"

			According to VMware: The VMXNET 3 adapter is the next generation of a paravirtualized NIC designed for performance, and is not related to VMXNET or VMXNET 2. It offers all the features available in VMXNET 2, and adds several new features like multiqueue support (also known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.

Rwh: /* How Do I Add More Than One Network Ethernet Adapter? (VMware Player: Windows) */

2012-10-27T14:43:38Z

How Do I Add More Than One Network Ethernet Adapter? (VMware Player: Windows)

← Older revision		Revision as of 10:43, 27 October 2012
Line 219:		Line 219:
	ethernet3.connectionType = "custom"		ethernet3.connectionType = "custom"
	ethernet3.vnet = "vmnet4"		ethernet3.vnet = "vmnet4"

			'''***Note:''' One can also use the new '''vmxnet3''' virtual network driver. According to VMware: The VMXNET 3 adapter is the next generation of a paravirtualized NIC designed for performance, and is not related to VMXNET or VMXNET 2. It offers all the features available in VMXNET 2, and adds several new features like multiqueue support (also known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.


	Each defined network adapter will assume a globally unique "MAC" address when the NST Virtual Machine is first booted up. This allows for multiple NST Virtual Machine instances to exist on the same physical network subnet without duplicate "ARP" entries being discovered.		Each defined network adapter will assume a globally unique "MAC" address when the NST Virtual Machine is first booted up. This allows for multiple NST Virtual Machine instances to exist on the same physical network subnet without duplicate "ARP" entries being discovered.