Network+ lab 4 of 27
IPv6: SLAAC and dual stack with a 6in4 tunnel
Add IPv6 to a working IPv4 network. Hosts configure themselves with SLAAC, a server gets a static address, and two sites are joined across an IPv4-only provider with a 6in4 tunnel. You read link-local, global and EUI-64 addresses and see how NDP replaces ARP.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 4,096 MB in total. That fits the free demo too.
In your workspace: Shared, then CompTIA Network Plus N10-009 guided labs, then 04 - IPv6 - SLAAC and dual stack with a 6in4 tunnel
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 6 vCPU, 4,096 MB
- Smallest plan
- Lite
The scenario
Harbour Logistics' provider has assigned it the IPv6 prefix 2001:db8:4c00::/48. You'll roll IPv6 out alongside IPv4 at head office (R1) and the depot (R3) without breaking anything. The catch: the provider core between them (R2) only carries IPv4 today, so the two IPv6 islands must be joined with a tunnel.
IPv4 already works end to end. H1 gets its IPv4 address by DHCP; the PCs are static.
| Device | Interface | IPv4 | IPv6 |
|---|---|---|---|
| R1 | Gi0/0 (HQ LAN) | 10.10.10.1/24 | 2001:db8:4c00:10::1/64, link-local fe80::1 |
| R1 | Gi0/1 | 10.0.12.1/30 | none (provider is IPv4-only) |
| R1 | Tunnel0 | - | 2001:db8:4c00:ffff::1/64 |
| R3 | Gi0/0 (depot LAN) | 10.20.20.1/24 | 2001:db8:4c00:20::1/64, link-local fe80::3 |
| R3 | Gi0/1 | 10.0.23.1/30 | none |
| R3 | Tunnel0 | - | 2001:db8:4c00:ffff::2/64 |
| H1 | eth0 | DHCP | SLAAC, plus static 2001:db8:4c00:10::100/64 |
| PC1 | eth0 | 10.10.10.10/24 | SLAAC |
| PC2 | eth0 | 10.20.20.10/24 | SLAAC |
What you’ll practise
- Recognise IPv6 address types and write addresses in their shortest valid form
- Enable IPv6 routing and configure global and link-local addresses on a router
- Let hosts autoconfigure with SLAAC and work out an EUI-64 interface ID
- Run IPv4 and IPv6 side by side (dual stack)
- Carry IPv6 across an IPv4-only network with a 6in4 tunnel and static routes
The tasks
- Turn on IPv6 at head office
- Watch hosts configure themselves with SLAAC
- Give the server a static address and test dual stack
- Enable IPv6 at the depot
- Tunnel IPv6 across the IPv4-only provider
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- R1
Gi0/0to HQ-LAN (network) - H1
eth0to HQ-LAN (network) - PC1
eth0to HQ-LAN (network) - R1
Gi0/1to R2Gi0/0 - R2
Gi0/1to R3Gi0/1 - R3
Gi0/0to PC2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| R3 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CompTIA Network Plus N10-009 guided labs.Open
04 - IPv6 - SLAAC and dual stack with a 6in4 tunneland start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Network+ labs
Related labs in other courses
CloudLabBox is independent of CompTIA, Cisco and Netgate. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.