In order to minimize technical difficulties and discrepancies across all systems, in today's workshop you will be working from a pair of Linux VMs running on your own computer under VirtualBox.
The .OVA appliance file is available on my Raspberry Pi which is
connected to the OpenWestOpenSSH network. This network's WPA key is
TatuYlonen, the name of the creator of SSH. Once
connected to this network, navigate to
...you may download the latest installer for your OS from the internet via the conference's WiFi, or from my Raspberry Pi on my network.
I will name my Virtual Machines alpine0 and alpine1. To prevent confusion, I expect you to do the same.
alpine0.ovafile from your filesystem
At this point in time both VMs are configured identically.
Both machines share the same hostname, are connected to a virtual
network containing your laptop, and are assigned the static IP address
rootaccount on each machine is
noobuser with a password of
...giving a warning about a missing network interface.
Since both machines come from the same template, alpine1 needs to be given its own IP address and hostname
Initially both VMs are assigned the static IP
setup-interfaces to assign alpine1
a static address
192.168.56.101. Do this when
setup-interfaces asks you to enter an Ip address
or to select "dhcp" or "none". Hit ENTER to use the default
values for the remaining questions.
Restart the eth0 network interface to bind the
eth0 interface to the new address by running the
Under a host-only virtual network configuration your laptop may reach both virtual machines, and both virtual machines are reachable from each other. Do a ping test and an SSH connection test to make sure that this is the case before proceeding.
We aren't using DHCP in our little virtual network, so you'll have to refer to each machine by its IP address for now.