0:00–0:30
Lecture
0:30–1:50
Lab 1A
1:50–2:00
Debrief
0:00 – 0:30
Lecture · 30 min
Course overview and the lab network topology — what we're building and why
Students arrive from NETW-0001 with Linux fundamentals: filesystem navigation, user management, package management, basic networking, and SSH. This course picks up where that one stopped. The focus shifts from the operating system itself to the services that make Linux a server platform. Day 1 is about understanding what we're building before we build it.
Part 1 — Where NETW-0014 fits (10 min)
- Open with a question: "In NETW-0001, your VMs existed in isolation — they were Linux machines you could log into. What would you need to add before you'd call them servers?" Take answers. Build toward: a server is a machine that provides a service to other machines. This course is about building and securing those services — DHCP, DNS, web, VPN, containers.
- Walk through the course arc: Week 1 builds the foundation (VMs + SSH). Weeks 2–3 add visibility (packet analysis, logging). Weeks 4–5 add services (DHCP, DNS, web). Week 6 adds security infrastructure (VPN). Week 7 adds modern deployment (Docker). Every week's work depends on what came before — the VMs built today are the exam environment in Week 8.
- Contrast with NETW-0001: that course used two desktop VMs. This course uses Ubuntu Server — no GUI, no graphical package manager, no file manager. Everything is done from the command line over SSH. Students who relied on the GUI in NETW-0001 will need to adjust. Reassure: the shell skills from that course are exactly what's needed here.
Part 2 — The lab network topology (15 min)
- Draw the full topology on the board before showing the slide. Start from scratch: one Windows host PC, three virtual machines, three virtual network segments. Let students suggest connections as you draw.
- S1 — the gateway server: Three network interfaces. eth0 connects to the External vSwitch (classroom network, DHCP from classroom router). eth1 connects to LAN1 (internal-only, no physical NIC). eth2 connects to LAN2 (internal-only, no physical NIC). S1 is the only VM with internet access directly — S2 and S3 get internet through S1 via NAT. Ask: "What does a device with multiple network interfaces and routing between them remind you of?" — a router. S1 behaves like a router for the lab network. This is intentional.
- S2 — primary internal server: One interface on LAN1. No direct internet access — routes through S1. S2 is where most services run: DHCP, DNS, web server, VPN endpoint, Docker. Students will spend most of their time here in weeks 3–7.
- S3 — secondary internal server: One interface on LAN2 (different subnet from S2). Deliberately isolated from S2 at the network layer until routing or VPN connects them. S3 is used for DNS secondary, VPN testing, and multi-server scenarios. Ask: "Why would we want S2 and S3 on different subnets?" — isolation, testing routing, simulating a remote site.
- IP addressing scheme: Write the scheme on the board. External NIC: DHCP (172.17.X.X from classroom). LAN1: 192.168.50.0/24 — S1 gets .1, S2 gets .2. LAN2: 192.168.51.0/24 — S1 gets .1, S3 gets .2. Students adjust the third octet to match their desk number to avoid conflicts between students sharing the same lab network. Example: desk 12 uses 192.168.12.0/24 for LAN1, 192.168.13.0/24 for LAN2.
- Ask: "Why three vSwitches instead of just one?" — segmentation. LAN1 and LAN2 are internal-only; VMs on those networks cannot directly reach the classroom network or each other unless S1 routes the traffic. This enforces a real network boundary that makes the VPN lab in Week 6 meaningful.
Part 3 — Ubuntu Server vs. Ubuntu Desktop (5 min)
- Ubuntu Server has no graphical interface by default. The installer is text-based. Once installed, there is no desktop — only a login prompt and a shell. This is intentional: servers don't need a GUI, and a GUI consumes RAM and CPU that should go to services.
- All configuration is done by editing text files in
/etc/ and managing services with systemctl. Students already know both from NETW-0001. The commands are the same — the context is different.
- Previewing today's lab: students will configure Hyper-V, create three vSwitches, create and configure three VMs, and begin installing Ubuntu Server on S1. The VM settings differ slightly from NETW-0001: 14 virtual processors (services benefit from more cores), 8192 MB RAM, and three distinct NIC configurations per VM.
Instructor note: The topology diagram is the single most important thing to communicate clearly on Day 1. A student who misunderstands it — even slightly — will build the wrong thing and have compounding problems for weeks. Take the full 15 minutes on Part 2. Draw it by hand on the board, not just on slides. Students who draw it along with you retain it better than students watching a slide.
0:30 – 1:50
Lab 1A · 80 min
Lab 1A — Hyper-V configuration, three vSwitches, and VM creation
Students configure their Windows host, create the three required vSwitches, and build all three VMs with the correct settings. S1 Ubuntu Server installation begins. S2 and S3 are created but not yet installed.
Pre-lab orientation (5 min)
- Each workstation has a pre-imaged SSD. Credentials: username Student, password Room225. Hyper-V is already installed. Ubuntu Server 24.04 LTS ISO is pre-downloaded — confirm its location before starting (typically
C:\ISOs\). If it's missing, raise your hand immediately.
- Each student has a workstation number on a sticker on the case. This number appears in your VM names, IP addressing, and MAC range throughout the entire course. Write it in the Student Info box on your lab sheet now.
Step 1 — Host configuration and MAC range (15 min)
- Set computer name to
PC-[YourName]. Configure the primary Ethernet NIC: IP from the classroom scheme, subnet 255.255.0.0, gateway and DNS as per board. Disable Ethernet 2 if present.
- Open Hyper-V Manager → Hyper-V Settings → MAC Address Range. Change the 4th and 5th octets to your desk number. Example: desk 12 → Minimum
00-15-5D-12-12-00, Maximum 00-15-5D-12-12-FF. Ask your instructor why this step matters before continuing.
Step 2 — Create three virtual switches (15 min)
- Hyper-V Manager → Virtual Switch Manager. Create three switches in this order:
· External — type External, connect to physical Ethernet NIC. This gives VMs access to the classroom network.
· LAN1 — type Internal. This is the private network for S1 and S2.
· LAN2 — type Internal. This is the private network for S1 and S3.
- Verify all three switches appear in the Virtual Switch Manager list before proceeding. The types (External vs Internal) cannot be easily changed after VMs are connected — get this right now.
Step 3 — Create S1, S2, and S3 (25 min)
- S1: New VM → Name:
S1, store in C:\VM\S1\, Generation 2, 8192 MB RAM (Dynamic), 3 network adapters: External, LAN1, LAN2 (add additional NICs after wizard via Settings), 50 GB disk in C:\VM\S1\, Ubuntu Server ISO attached. Settings: Secure Boot OFF, 14 virtual processors.
- S2: New VM → Name:
S2, store in C:\VM\S2\, Generation 2, 8192 MB RAM, 1 network adapter: LAN1, 50 GB disk. Settings: Secure Boot OFF, 14 virtual processors. ISO attached.
- S3: Same as S2 but name
S3, stored in C:\VM\S3\, network adapter: LAN2.
- Call the instructor to verify all three VMs before starting any installation. Wrong NIC assignments now mean broken routing later.
Step 4 — Install Ubuntu Server on S1 (25 min)
- Start S1 and connect via Hyper-V console. Ubuntu Server installer is text-based. Walk through: language → keyboard → network (leave DHCP for now) → mirror (default) → storage (use entire disk, default layout is fine for S1) → user account: username
student, password Room225, hostname S1. Enable OpenSSH server when prompted. No additional snaps.
- Installation takes 10–15 minutes. While S1 installs, students can read ahead in the lab sheet to the static IP configuration steps that come tomorrow.
- Early finishers: While S1 finishes installing, begin S2's installation with the same settings — hostname
S2, same student/Room225 credentials. Getting S2 started today saves time tomorrow.
Lab 1A — network topology summary
Windows Host
PC-[Name]
172.17.X.X
→
S1
eth0: External
eth1: LAN1 .50.1
eth2: LAN2 .51.1
→
S2
eth0: LAN1
192.168.50.2
+
S3
eth0: LAN2
192.168.51.2
Lab 1A complete when: Three vSwitches exist (External, LAN1, LAN2). Three VMs exist (S1, S2, S3) with correct NIC assignments and settings verified by instructor. S1 Ubuntu Server installation is in progress or complete.
1:50 – 2:00
Debrief · 10 min
Topology check and preview of Day 2
- Show of hands: who has all three VMs created and verified? Who has S1 installation complete? Anyone whose S1 is still installing — it will finish shortly. VMs do not need to be running overnight.
- Ask: "S2 and S3 have no internet connection yet. Tomorrow we configure S1 as a NAT gateway to fix that. What two things need to happen on S1 to make NAT work?" — take guesses. The answer: IP forwarding must be enabled in the kernel, and an iptables rule must masquerade outbound traffic. Preview Tuesday's lab.
- Remind students: the three VMs created today are used for every lab from Week 1 through Week 8. Treat them carefully. If something goes wrong, take a snapshot before experimenting. Ask the instructor before deleting anything.
Learning outcomes — by end of Day 1, students can…
Describe the course network topologyDraw the S1/S2/S3 layout with correct vSwitch types and explain why each segment is isolated
Create correctly-typed vSwitchesDistinguish External, Internal, and Private switch types and explain the consequences of choosing the wrong type
Build multi-NIC VMs in Hyper-VCreate a VM with three network adapters attached to different vSwitches with correct Secure Boot and processor settings
Install Ubuntu Server 24.04Complete the text-based installer with correct hostname, user account, and OpenSSH server enabled
What you need ready before class
Ubuntu Server 24.04 LTS ISO on every workstation
Hyper-V pre-installed and enabled on host
Lab 1A handout printed
Workstation numbers labelled on cases
Topology diagram ready for projector
IP addressing scheme on board before class starts
Common issues and fixes
| Issue | Likely cause | Fix |
|---|
| S1 has only one NIC visible in Settings | Additional NICs not added after the wizard | Right-click S1 → Settings → Add Hardware → Network Adapter. Add LAN1 and LAN2 adapters separately after wizard completes |
| LAN1/LAN2 switches show as "External" type accidentally | Wrong type selected during creation | Delete the switch and recreate — cannot change type after creation. Disconnect any VMs first |
| Ubuntu Server installer stuck at "Waiting for network" | DHCP not available on External vSwitch, or switch misconfigured | Skip network config during install (can be set later). Ensure External vSwitch is connected to physical NIC |
| Cannot find Ubuntu Server ISO | ISO was downloaded as Desktop variant, not Server | Confirm filename contains "server" — Desktop and Server ISOs are different downloads. Server ISO is ~2GB, Desktop is ~5GB |
| Secure Boot option greyed out after first start | VM was started before disabling Secure Boot | Delete and recreate the VM, or boot into UEFI firmware via Actions → Start → immediately select "Firmware" from boot menu |