Reading: Finish me!
In this lab, you will reuse the topology from Lab #3 except that you will use IPv6 instead of IPv4. As with Lab #3, you will configure static routes that enable a router to send packets to networks that are not directly connected to it.
NOTE! Recall that in addition to submitting your Packet Tracer file for this lab, you should also submit a document that includes all the commands you used to configure your device(s), along with any comments or observations you made, and the answers to any questions asked. This is true for all future labs unless otherwise noted. This is the last reminder.
Using Packet Tracer, construct the following network:
| Device | Interface | IP Address | Default Gateway |
|---|---|---|---|
| R1 | Gig0/0 | FD25:F376:7B60:8001::1/64 | N/A |
| Gig0/1 | FD25:F376:7B60:8000::1/64 | N/A | |
| R2 | Gig0/0 | FD25:F376:7B60:8002::1/64 | N/A |
| Gig0/1 | FD25:F376:7B60:8000::2/64 | N/A | |
| PC-A | FA0 | FD25:F376:7B60:8001::2/64 | FD25:F376:7B60:8001::1 |
| PC-B | FA0 | FD25:F376:7B60:8002::2/64 | FD25:F376:7B60:8002::1 |
Use 1941 routers and 2960-24TT switches (might be shown as just "2960" in Packet Tracer's menu of switches). As before, use one of the uplink ports to connect to the routers.
Important! Before using any IPv6 features of the routers, execute the following command on them:
Router(config)# ipv6 unicast-routing
This command activates IPv6 support on these devices.
Configure the router basic settings as you did in Lab #1 (Global Settings and Console Access; you do not need to configure remote access for this lab). Configure the network interfaces using the addresses in the addressing table above. Be sure to provide a description for the network interfaces as was done in the previous lab.
None of the switches supported by Packet Tracer allow an IPv6 address to be assigned to a switch virtual interface. This means, for those devices, remote access over IPv6 is not possible. In practice, this isn't a serious issue since many networks support both IPv4 and IPv6. In that case, switch management could be done over IPv4. For IPv6-only networks, the administrators would want to use newer devices than those Packet Tracer simulates.
Keep in mind that the older switches can pass IPv6 traffic without an issue since they operate at level 2 in the protocol stack. They have no knowledge of the layer 3 protocols in use in the frames. The issue here only arises when one wants to communicate with the switch itself.
For this lab, you should instead configure two PCs (PC-A and PC-B) to use IPv6.
Check your work trying to ping both interfaces on R1 from PC-A. Similarly, try to ping both interfaces on R2 from PC-B. Use IPv6 addresses. There are no IPv4 addresses being used in this lab. Finally, try to ping R2 from R1. Use the show ipv6 route command on each of the routers to view their IPv6 routing tables.
You should notice that you can ping both interfaces on the router connected to a particular PC, including the interface on the "remote" side of the directly connected router. Yet the PCs cannot ping the "far" routers at all. Why is that?
Configure a static route in R1 for the remote (relative to R1) network of FD25:F376:7B60:8002::/64 by specifying the next-hop address toward that network.
Configure a static route in R2 for the remote (relative to R2) network of FD25:F376:7B60:8001::/64 by specifying the next-hop address toward that network. If you try to use the exit interface in the static route, it won't work. This may be a Packet Tracer limitation in its simulation of IPv6 support on the devices, since the command specifying an exit interface is accepted despite it not working.
Verify that the two PCs can ping each other.
For this lab, submit your final Packet Tracer model, along with a document containing the commands you used to configure your devices, and your answers to the questions. The preferred document format is PDF, but Word, ODT, or plain text is also acceptable.
Last Revised: 2023-09-08
© Copyright 2023 by Peter Chapin <peter.chapin@vermontstate.edu>