Skip to content

🛠 Project 13 β€” IPv6 Dual-Stack Migration

Network Systems

View the live site β€” ijk37.com

Project 13: IPv6 Dual-Stack Migration

Home All Projects Notes Quiz

Type: Design + Packet Tracer or lab verification
Modules: 03 (IPv6 Addressing), 08 (Subnetting), 12 (Routing)
Difficulty: Ò­Ò­Ò­Ò­

🎯 Objective

Plan and test a small dual-stack network where IPv4 continues to work while IPv6 is introduced with clean addressing, router advertisements, DNS records, and routing.

🧭 Scenario

Summit Health Clinic runs an IPv4 network today but wants to prepare for IPv6. The clinic will not remove IPv4 yet. Instead, it will deploy dual stack on the staff, voice, server, and guest networks.

You are given the IPv6 prefix:

2001:db8:5040::/48

Use one /64 per VLAN.

🧱 Existing IPv4 VLANs

VLAN Name IPv4 subnet IPv6 subnet to assign
10 Staff 192.168.10.0/24
20 Voice 192.168.20.0/24
30 Guest 192.168.30.0/24
40 Servers 192.168.40.0/24
99 Management 192.168.99.0/24

Suggested IPv6 pattern:

2001:db8:5040:10::/64
2001:db8:5040:20::/64
2001:db8:5040:30::/64
2001:db8:5040:40::/64
2001:db8:5040:99::/64

🧩 Tasks

🔹 Part A β€” Addressing Plan

  1. Assign one /64 to each VLAN.
  2. Reserve ::1 in each subnet for the default gateway.
  3. Assign static IPv6 addresses to server and management devices.
  4. Decide whether clients use SLAAC, DHCPv6, or static addressing.
  5. Document the plan in a table.

🔹 Part B β€” Router and Client Behavior

Configure or describe:

  • Router IPv6 unicast routing.
  • IPv6 gateway addresses on VLAN interfaces.
  • Router advertisements for client networks.
  • DHCPv6 if you choose managed addressing.
  • IPv6 DNS resolver settings.

🌐 Part C β€” DNS and Application Testing

Create or document:

Record Purpose
A Existing IPv4 host record
AAAA IPv6 host record
PTR Reverse lookup if supported

Test that a client can reach the server by:

  1. IPv4 address.
  2. IPv6 address.
  3. DNS name.

🔐 Part D β€” Routing and Security

  1. Add a default IPv6 route toward the ISP edge or upstream router.
  2. Verify inter-VLAN IPv6 connectivity.
  3. Apply firewall/ACL rules so guest IPv6 traffic cannot reach internal VLANs.
  4. Confirm IPv4 security rules were not accidentally bypassed by IPv6.

✅ Verification Checklist

  • Each VLAN has a unique /64.
  • Clients receive or configure an IPv6 address.
  • Clients have a valid IPv6 default gateway.
  • ping works between approved IPv6 endpoints.
  • DNS has both A and AAAA records where appropriate.
  • Guest IPv6 traffic is blocked from internal networks.
  • IPv4 still works after IPv6 is enabled.

📦 Deliverables

  • IPv6 addressing table.
  • Dual-stack topology diagram.
  • Screenshots or command output proving IPv4 and IPv6 connectivity.
  • Short migration memo explaining risks, rollback plan, and security controls.

🚀 Stretch Goals

  • Add OSPFv3 between routers.
  • Compare SLAAC vs DHCPv6 behavior.
  • Add an IPv6-only test host and document what still breaks.
  • Write a short "IPv6 readiness checklist" for the clinic.

See also notes: [[03-03-ipv6-addressing]], [[08-11-ipv6-subnetting]], [[12-03-routing]]