Chapter 5: Simple private network
Build a simple private network, with two VMs who can talk to each other, but cannot talk to the Hyper-V host or the Internet.
Last tested: NEVER
On this page
- Defining multiple nodes in configuration data
- The lab network
- Lab exercises and files
Defining multiple nodes in configuration data
If you look at the configuration data for this chapter,
you will find three entries under
NodeName = '*'
NodeName = 'CLIENT1'
NodeName = 'CLIENT2'
The first entry,
NodeName = '*', is special -
rather than defining a node named
it actually sets default values for all nodes.
(Nodes can override these defaults.)
This is a useful way to avoid heavy repetition that might otherwise be unavoidable
when configuring multiple similar nodes.
The lab network
In the non-node data, we declare a private Hyper-V network, like so:
A private switch allows VMs to communicate only with each other - not the Internet or even with the host machine. In this chapter, we will not be connecting the VMs to the Internet, or even connecting to a host network. The only way to interact with VMs on a private network is to use the Hyper-V console.
Declaring switches that already exist
Previously, we have declared the use of a switch which we first created by hand on the Hyper-V host, such that when it is referenced, that switch already exists.
We can also declare use of switches which do not yet exist on the host.
If that switch is defined in
then the definition laid out in that section is used.
If it isn’t, then Lability creates a new internal Hyper-V switch.
More information on Hyper-V switch types
See Hyper-V switch types for more information about different switch types.
Lab exercises and files
Deploy the lab with Deploy-SIMPLENET.ps1
Log in to one of the servers using the Hyper-V management console.
- Ping the other server by its IP address
Enter-PSSessionto connect to the other server - this requires understanding Powershell Remoting, including setting
TrustedHostsand ensuring the firewall allows access.
Get-NetIpAddresson your lab host and try to understand each network device that it returns.
Observe that there is no network device on the private network, and therefore no way for you to RDP or
Enter-PSSessionto the VMs from your host.
Change the network from “private” to “internal” and redeploy.
Get-NetIpAddressagain and see a new IP address on the new internal Hyper-V switch.
Open Hyper-V Manager, click on Virtual Switch Manager, and delete any switches you don’t need.
(If you fail to delete internal or external switches that are no longer in use, useful information in output of
Get-NetIpAddresscan get drowned in noise from old networks.)