Module 12: IPv6 Addressing

Hello teacher and everyone. We are Group [group number/name]. In this video, our group will present Module 12: IPv6 Addressing from the CCNA Introduction to Networks course.

This module focuses on why IPv6 is needed, how IPv6 addresses are represented, the main types of IPv6 addresses, how IPv6 addresses are configured and verified, and how IPv6 subnetting works.

Xin chào thầy và các bạn. Tụi em là nhóm [số/tên nhóm]. Trong video này, nhóm em sẽ trình bày Module 12: IPv6 Addressing trong khóa CCNA Introduction to Networks.

Module này tập trung vào lý do cần IPv6, cách biểu diễn địa chỉ IPv6, các loại địa chỉ IPv6, cách cấu hình và kiểm tra IPv6, và cách chia subnet trong IPv6.

Our group has four members. [Name 1] is responsible for the introduction, IPv4 issues, IPv4 and IPv6 coexistence, and IPv6 address representation from section 12.0.1 to 12.2.4.

[Name 2] is responsible for IPv6 address types, prefix length, Global Unicast Addresses, Link-Local Addresses, and static IPv6 configuration from section 12.3.1 to 12.4.5.

[Name 3] is responsible for dynamic IPv6 addressing, RS and RA messages, SLAAC, Stateless DHCPv6, Stateful DHCPv6, interface IDs, dynamic LLAs, and verification commands from section 12.5.1 to 12.6.6.

[Name 4] is responsible for IPv6 multicast addresses, solicited-node multicast, IPv6 subnetting, module practice activities, and the module summary from section 12.7.1 to 12.9.3.

Nhóm em gồm 4 thành viên. [Tên 1] phụ trách phần giới thiệu, vấn đề của IPv4, sự cùng tồn tại IPv4 và IPv6, và cách biểu diễn địa chỉ IPv6 từ mục 12.0.1 đến 12.2.4.

[Tên 2] phụ trách các loại địa chỉ IPv6, prefix length, Global Unicast Address, Link-Local Address, và cấu hình IPv6 tĩnh từ mục 12.3.1 đến 12.4.5.

[Tên 3] phụ trách cấu hình IPv6 động, RS và RA messages, SLAAC, Stateless DHCPv6, Stateful DHCPv6, interface ID, dynamic LLA, và các lệnh kiểm tra từ mục 12.5.1 đến 12.6.6.

[Tên 4] phụ trách IPv6 multicast, solicited-node multicast, chia subnet IPv6, các bài practice, và tổng kết module từ mục 12.7.1 đến 12.9.3.

This video is the theory presentation. We will go through the NetAcad sections in order and explain the important concepts. After the theory video, our group will also provide separate demo videos for each Packet Tracer activity and lab in Module 12.

Now, we will start with section 12.0.1 and explain why IPv6 addressing is important.

Video này là phần trình bày lý thuyết. Nhóm em sẽ đi theo thứ tự các mục trên NetAcad và giải thích các ý quan trọng. Sau video lý thuyết, nhóm em sẽ có các video demo riêng cho từng bài Packet Tracer và Lab trong Module 12.

Bây giờ nhóm em sẽ bắt đầu từ mục 12.0.1 để giải thích vì sao IPv6 Addressing là nội dung quan trọng.

First, we start with Module 12: IPv6 Addressing. This module is important because modern networks cannot depend on IPv4 only. In real networks, IPv4 and IPv6 often exist together, so a network administrator must understand how IPv6 addressing works.

The goal is not just to memorize an IPv6 address format. By the end of the module, we should be able to understand IPv6 address structure, identify different IPv6 address types, configure IPv6 addresses on network devices, verify the configuration, and apply an IPv6 subnetting scheme.

So in this theory video, we will move from the reason why IPv6 is needed, to how IPv6 addresses are written, and then to configuration, multicast, and subnetting.

This overview also tells the audience what to expect from our group: we will explain the theory first, and later the lab videos will show the same ideas in Packet Tracer and Windows command output.

In section 12.0.2, NetAcad shows the module objective: implement an IPv6 addressing scheme. That means this module connects theory with practice. We do not stop at definitions; we also use Packet Tracer and lab activities to apply the concepts.

The order of topics is also important. First, the course explains IPv4 issues and why IPv6 is necessary. Second, it explains the IPv6 address format and abbreviation rules. Third, it compares address types such as unicast, multicast, anycast, global unicast, and link-local addresses.

After that, the module moves into static and dynamic IPv6 configuration, verification commands, multicast behavior, and IPv6 subnetting. This order is the same order we will follow in our presentation.

Section 12.1.1 explains why IPv6 is needed. The main problem is IPv4 address exhaustion. IPv4 uses 32-bit addresses, so the total address space is about 4.3 billion addresses. That was enough in the early stage of the internet, but it is not enough for the number of devices connected today.

When the course mentions address depletion, we should understand that public IPv4 addresses are limited resources. The growth of personal computers, smartphones, servers, cloud platforms, cameras, sensors, and IoT devices increases the need for globally reachable addresses.

NAT helped slow down IPv4 exhaustion because many private IPv4 devices can share one public IPv4 address. However, NAT is not a perfect solution. It can make troubleshooting harder, add complexity to applications, and reduce true end-to-end connectivity between devices.

IPv6 was created as the successor to IPv4. It uses 128-bit addresses, which provides a much larger address space. IPv6 also supports features that help modern networks, such as automatic address configuration and ICMPv6-based neighbor discovery. So the key idea of this page is that IPv6 is necessary because the internet needs scalable addressing, not just temporary workarounds.

Section 12.1.2 explains that IPv4 and IPv6 will coexist for a long time. There is no single day when all networks turn off IPv4 and move completely to IPv6. Organizations migrate gradually because they have different devices, applications, providers, and budgets.

The first coexistence method is dual stack. A dual-stack device runs IPv4 and IPv6 at the same time. This is usually the most straightforward transition method because the same device can communicate with IPv4 destinations and IPv6 destinations.

The second method is tunneling. Tunneling carries IPv6 packets across an IPv4 network. This is useful when part of the path does not support native IPv6 yet, but the source and destination still need IPv6 communication.

The third method is translation. Translation converts traffic between IPv6 and IPv4. It is useful when an IPv6-only device must communicate with an IPv4-only device. However, translation adds complexity, so the long-term goal is still native IPv6 communication when possible.

This check-your-understanding page is used to review the previous ideas. We should be able to explain why IPv4 addresses are not enough, why NAT is only a workaround, and how dual stack, tunneling, and translation help during the transition period.

Now we move to IPv6 address representation. An IPv6 address is 128 bits long. It is written as eight groups of hexadecimal values, and each group is called a hextet. Each hextet represents 16 bits.

For example, an address can look like 2001:0db8:0000:1111:0000:0000:0000:0200. Compared with IPv4, this is much longer. Because of that, IPv6 has abbreviation rules to make addresses shorter and easier to read.

The first IPv6 abbreviation rule is to omit leading zeros. A leading zero is a zero at the beginning of a hextet. For example, 0db8 can be written as db8, and 0200 can be written as 200.

If a hextet is 0000, after removing leading zeros, we keep one zero. So 0000 becomes 0. We do not delete zeros in a way that changes the hexadecimal value. For example, 200 cannot become 2, because that is no longer the same value.

This rule is used very often because many IPv6 addresses contain leading zeros. It makes the address shorter while keeping the same meaning.

When presenting this part, point directly at the changed hextets so the audience can see that the address is shorter but the value is unchanged.

The second abbreviation rule is the double colon rule. A double colon, ::, can replace one continuous sequence of all-zero hextets. This can make an IPv6 address much shorter.

When this heading is on screen, emphasize that this rule is different from Rule 1. Rule 1 works inside one hextet, while Rule 2 replaces several full zero hextets at once.

For example, if an address contains 0000:0000:0000 in one continuous block, that block can be replaced with ::. However, the double colon can only be used once in one IPv6 address.

The reason is ambiguity. If we use :: two times, we cannot know how many zero hextets belong to the first double colon and how many belong to the second one. So the rule is clear: use the double colon only once, for the longest or most useful continuous zero block.

This check reviews the two abbreviation rules. At this point, we should be able to read a full IPv6 address, remove leading zeros, and use the double colon correctly. This skill is necessary before we classify IPv6 addresses and configure them in the next sections.

Section 12.3 starts with the three main IPv6 address categories: unicast, multicast, and anycast. A unicast address identifies one specific interface. If a packet is sent to a unicast address, it is delivered to one destination interface.

A multicast address identifies a group of interfaces. A packet sent to a multicast address is delivered to all members of that group. This is important in IPv6 because IPv6 does not use broadcast like IPv4.

An anycast address can be assigned to multiple devices, but the packet is delivered to the nearest device based on routing. Anycast is useful for services where the client should reach the closest available server or router.

IPv6 uses prefix length instead of an IPv4 dotted-decimal subnet mask. The prefix length is written with slash notation, for example /64. This means the first 64 bits identify the network portion, and the remaining 64 bits are used for the interface ID.

In most IPv6 LANs, /64 is the standard prefix length. This is important because features such as SLAAC expect a 64-bit interface ID. So when we see an IPv6 address like 2001:db8:acad:1::10/64, the /64 tells us where the network part ends.

This page focuses on IPv6 unicast address types. In practice, the two most important types for this module are the Global Unicast Address and the Link-Local Address. A global unicast address is used for routable communication beyond the local link. A link-local address is used only on the local network segment.

Other special unicast addresses also exist, such as the loopback address and the unspecified address. The main idea is that not every IPv6 unicast address has the same scope or purpose, so we must identify the type before configuring or troubleshooting it.

A unique local address is used for local communication inside an organization. It is similar in purpose to private IPv4 addressing because it is not intended to be globally routed on the public internet.

However, unique local addresses are still IPv6 addresses and follow IPv6 format rules. In this module, unique local addresses are mainly important for identification. For most configuration examples, we focus more on global unicast and link-local addresses.

A GUA, or Global Unicast Address, is an IPv6 address that is globally routable. This means it can be used to communicate across IPv6 networks, including the internet, if routing and policy allow it.

GUAs are the IPv6 addresses we commonly configure on router interfaces and hosts when we want them to communicate beyond the local link. When we see addresses such as 2001:db8:acad:1::1/64 in the labs, those are examples used for global unicast addressing practice.

A Global Unicast Address normally has three main parts. The first part is the global routing prefix. This prefix is assigned to an organization by an ISP or address provider, and it identifies the larger network block.

The second part is the subnet ID. The organization uses the subnet ID to create internal subnets. This is the part we use later when we learn IPv6 subnetting.

This is the field we change when we need more internal networks. In the later subnetting section, this same subnet ID becomes the main part we use to build multiple /64 subnets.

The third part is the interface ID. The interface ID identifies the individual interface inside that subnet. In a typical /64 LAN, the first 64 bits are the network prefix and subnet information, and the last 64 bits are the interface ID.

An LLA, or Link-Local Address, is used only on the local link. Link-local addresses usually begin with fe80. They are not routed to other networks, so they cannot be used as global destination addresses across the internet.

Even though LLAs are local, they are very important. IPv6 devices use link-local addresses for neighbor discovery and local communication. A host can also use the router link-local address as its default gateway. This is why router LLAs are often configured manually with simple addresses such as fe80::1.

This check confirms that we can recognize IPv6 address types. Before configuring IPv6, we must know whether an address is global, local to a link, multicast, or another special type. This helps us avoid using the wrong address in routing, gateway, or ping tests.

Section 12.4 moves from theory to configuration. To configure a static IPv6 global unicast address on a Cisco router interface, we enter interface configuration mode and use the command ipv6 address address/prefix-length.

For example, the command may look like ipv6 address 2001:db8:acad:1::1/64. The address identifies the interface, and the /64 identifies the prefix length. After assigning the address, the interface must be enabled with no shutdown if it is administratively down.

This is the same idea as IPv4 interface configuration, but the address format and prefix notation are IPv6-based.

When recording, keep the CLI example visible long enough for viewers to see that configuration is not complete until the interface is enabled and verified.

This page shows that IPv6 addresses can also be configured statically on a Windows host. A host needs an IPv6 address, prefix length, default gateway, and usually DNS information.

When presenting this heading, explain that a host configuration needs to match the router subnet. If the host address, prefix length, or default gateway is wrong, IPv6 communication will fail.

Static host configuration is useful in labs and for some fixed devices, but it does not scale well for many users. That is why later sections introduce dynamic methods such as SLAAC and DHCPv6.

A link-local address can be generated automatically, but on routers it is common to configure it manually. The command format is ipv6 address fe80::1 link-local under the interface.

The keyword link-local is important because it tells the router that this address is not a global unicast address. A simple link-local address such as fe80::1 makes troubleshooting easier, especially when that router is used as the default gateway for hosts on the link.

The syntax checker is used to practice the commands from the previous pages. The key commands are entering the interface, assigning a global unicast address with prefix length, assigning a link-local address with the link-local keyword, and enabling the interface if needed.

The Packet Tracer activity 12.4.5 gives practical work for this topic. In the theory video, we only introduce it. In the separate demo video, we will open the Packet Tracer file, read the addressing table, configure the required devices, and verify that the basic configuration is correct.

Dynamic IPv6 addressing starts with ICMPv6 Router Solicitation and Router Advertisement messages. A host can send an RS message to ask for IPv6 network information. A router sends an RA message to provide information such as the network prefix, default gateway information, and flags that tell the host which addressing method to use.

This is different from IPv4, where hosts usually depend on DHCP for automatic addressing. In IPv6, router advertisements are a central part of automatic address configuration.

Use this point to connect the diagram to the next three methods. The RA message is what tells the host whether it should use SLAAC only, SLAAC with DHCPv6, or Stateful DHCPv6.

Method 1 is SLAAC, which means Stateless Address Autoconfiguration. With SLAAC, the router advertises the network prefix in an RA message, and the host creates its own IPv6 address.

The host combines the advertised prefix with an interface ID. In this method, a DHCPv6 server is not needed for assigning the main IPv6 address. SLAAC is simple and efficient, especially for networks where hosts can generate their own addresses automatically.

Method 2 combines SLAAC with Stateless DHCPv6. The host still uses SLAAC to create its own IPv6 address, so the DHCPv6 server does not assign the main address.

The important distinction is that the host owns the address creation process, but DHCPv6 still helps by providing supporting information such as DNS.

However, the host contacts a DHCPv6 server for additional information, such as DNS server addresses or domain information. This is why it is called stateless DHCPv6: the server provides extra configuration information but does not keep address leases in the same way as stateful DHCPv6.

Method 3 is Stateful DHCPv6. In this method, the DHCPv6 server assigns IPv6 address information to the host, similar to DHCP in IPv4.

When this heading is on screen, compare it directly with IPv4 DHCP. The server is now responsible for assigning address information, so administration is more centralized.

This method gives administrators more centralized control because the server manages address assignment. The key difference from Stateless DHCPv6 is that Stateful DHCPv6 provides the IPv6 address itself, not only additional information.

After a host receives the prefix, it still needs an interface ID. This page compares two ways to create the interface ID: the EUI-64 process and a randomly generated interface ID.

This section explains where the host part of an IPv6 address comes from. The network prefix may come from the router, but the interface ID still has to be created by the host.

EUI-64 is based on the MAC address, so it creates a predictable interface ID. Randomly generated interface IDs are more privacy-friendly because they do not directly expose information related to the device MAC address.

The EUI-64 process creates a 64-bit interface ID from a 48-bit MAC address. The process inserts additional hexadecimal values in the middle and changes a specific bit to produce the final interface ID.

For this presentation, the important idea is not to memorize every bit operation. The important idea is that EUI-64 creates an interface ID based on the MAC address, which makes it predictable but less private than a random interface ID.

Modern operating systems often use randomly generated interface IDs. This improves privacy because the IPv6 address does not reveal a stable interface ID based on the MAC address.

This is mainly a privacy topic. A random interface ID makes it harder to identify or track the same device only by looking at the host portion of the IPv6 address.

The network prefix still identifies the subnet, but the host portion can change or be generated in a way that is harder to track. This is why random interface IDs are common on end-user devices.

This check reviews the three dynamic addressing methods for IPv6 global unicast addresses. We should be able to explain which method lets the host create its own address, which method uses DHCPv6 only for extra information, and which method uses DHCPv6 to assign addresses.

Section 12.6 moves to dynamic link-local addresses. Every IPv6-enabled interface must have a link-local address. This address is used for communication on the local link, including neighbor discovery and communication with the default gateway.

A device can generate a link-local address automatically. However, for routers, administrators often configure a simple static LLA to make the gateway address easier to recognize.

This explains why link-local addresses appear even when no global IPv6 address is configured. They are required for basic local IPv6 functions.

On Windows, the link-local IPv6 address is generated automatically. We can view it with the ipconfig command. In the output, the link-local address usually starts with fe80.

When showing this section, connect the NetAcad output to the real lab. In the lab video, we can run ipconfig /all and find the same kind of fe80 link-local address.

This is useful in troubleshooting because it shows that IPv6 is enabled on the interface even if the device does not have a global IPv6 address.

This output is useful because it gives a real example, not only theory. It proves that Windows automatically creates IPv6 information on the network adapter.

On Cisco routers, a link-local address is also generated automatically when IPv6 is enabled on an interface. The automatically generated address works, but it can be long and difficult to remember.

That is why many labs manually configure link-local addresses on router interfaces. For example, using fe80::1 on a router interface makes it easier to identify the default gateway during verification.

After configuring IPv6, we must verify the result. The command show ipv6 interface brief displays interfaces and assigned IPv6 addresses. It helps us confirm that the correct addresses are configured and that interfaces are up.

The command show ipv6 route displays the IPv6 routing table. This helps us confirm that connected routes and other IPv6 routes are present. Finally, ping tests end-to-end reachability between devices.

Verification is important because configuration commands alone do not prove that the network works. We need show commands and connectivity tests to confirm the final result.

End this subsection by saying that a good network engineer does not stop after typing commands. The final step is always to prove that the configuration works.

The syntax checker gives practice with IPv6 verification commands. The important habit is to verify interface status, assigned addresses, routing information, and connectivity after every configuration task.

The Packet Tracer activity 12.6.6 applies the IPv6 addressing and verification concepts. In the separate demo video, we will configure IPv6 addressing on the required devices and verify the result with show commands and ping tests.

Section 12.7 starts with IPv6 multicast addresses. IPv6 does not use broadcast. Instead, it uses multicast to send traffic to a selected group of devices.

Make clear that multicast replaces many places where IPv4 would use broadcast. This reduces unnecessary traffic because only interested multicast groups receive the packet.

IPv6 multicast addresses begin with ff00::/8. When we see an address that starts with ff, we should recognize it as multicast. This is important because multicast is used by many IPv6 control functions, including neighbor discovery.

Two important well-known IPv6 multicast addresses are ff02::1 and ff02::2. The address ff02::1 is the all-nodes multicast address. It reaches all IPv6-enabled devices on the local link.

The address ff02::2 is the all-routers multicast address. It reaches all IPv6 routers on the local link. These addresses are link-local multicast addresses, so they are used only within the local network segment.

A solicited-node multicast address is a special multicast address used by Neighbor Discovery. It allows a device to reach a more specific group instead of sending a message to every node on the link.

This improves efficiency compared with broadcast behavior. In IPv4, ARP uses broadcast to find a MAC address. In IPv6, Neighbor Discovery uses ICMPv6 and solicited-node multicast to perform a similar function with less unnecessary traffic.

The lab 12.7.4 focuses on identifying IPv6 addresses. It connects to the theory because we must recognize different IPv6 address types, practice abbreviation rules, and inspect IPv6 information on a Windows host.

In the separate lab video, we will open the PDF file, classify the sample addresses, and use Windows commands such as ipconfig /all to observe IPv6 information on the computer.

This also tells the audience why the lab is separate from the theory video: the theory explains address categories, while the lab proves that we can recognize those categories in examples and real command output.

Section 12.8 explains IPv6 subnetting. In IPv6, subnetting usually uses the subnet ID field inside the global unicast address. The goal is not mainly to save addresses, because IPv6 has a very large address space.

The goal is to create a logical addressing plan. Each LAN, point-to-point link, or network segment should have its own IPv6 subnet. This makes routing, documentation, and troubleshooting easier.

The subnetting example shows how to create multiple IPv6 subnets from one assigned prefix. In many examples, each LAN receives a /64 prefix. The subnet ID changes from one subnet to another.

For example, if the organization has a prefix such as 2001:db8:acad::/48, the subnet ID can be used to create subnets like 2001:db8:acad:1::/64, 2001:db8:acad:2::/64, and so on. The main skill is to assign a unique subnet prefix to each network segment.

Subnet allocation means deciding which subnet will be used for each part of the topology. Each router interface connected to a different network should belong to a different IPv6 subnet.

This is similar to IPv4 design, but IPv6 gives us much more address space. So we can use clean and consistent /64 subnets without trying to conserve every address. The important point is that the addressing plan must match the topology.

This page shows a router configured with IPv6 subnets. Each router interface receives an IPv6 address from the subnet assigned to that link or LAN. This is how the subnetting plan becomes a real device configuration.

After configuring the addresses, we still need to verify the interface status and routes. This connects back to the verification commands from section 12.6, such as show ipv6 interface brief, show ipv6 route, and ping.

This check reviews IPv6 subnetting. We should be able to identify the subnet ID, create multiple /64 subnets, and match each subnet to the correct part of the topology.

Use this check as a checkpoint before the Packet Tracer activity. If we cannot identify the subnet ID here, we will not be able to complete the subnetting lab correctly.

The Packet Tracer activity 12.9.1 is the practical activity for IPv6 subnetting. In the demo video, we will calculate the required /64 subnets, assign IPv6 addresses according to the addressing plan, and verify connectivity between devices.

The lab 12.9.2 is a complete IPv6 configuration lab. It includes router interfaces, switch management addressing, host IPv6 settings, and connectivity verification.

This lab is longer than the other activities, so the demo should be recorded slowly. Show the PDF requirements first, then configure devices, then verify with commands and ping.

In the demo video, we will use the PDF instructions to understand the requirements and the Packet Tracer Physical Mode file to perform the configuration. The key steps are enabling IPv6 routing, assigning IPv6 addresses, configuring link-local addresses where required, setting host addresses and gateways, and testing connectivity.

To summarize Module 12, we learned why IPv6 is needed, how IPv4 and IPv6 coexist, how IPv6 addresses are represented, and how to shorten IPv6 addresses correctly.

This is the closing section of the theory video. Use it to connect all parts of the module into one story: IPv6 is needed, addresses must be understood, and configuration must be verified.

We also learned the main IPv6 address types, including global unicast, link-local, multicast, and anycast. Then we studied static and dynamic IPv6 addressing, including SLAAC, Stateless DHCPv6, Stateful DHCPv6, and verification commands.

Finally, we learned how IPv6 multicast replaces broadcast behavior and how IPv6 subnetting uses the subnet ID to create a scalable addressing plan. After this theory video, our group will upload separate demo videos for each Packet Tracer activity and lab in Module 12.