Description of the Tests
You will all go through these steps sooner or later, but I thought I’d share my first tries with you.
I started out with two hosts. One host is a Windows 2000 machine running the Microsoft Research stack. I called this host Marvin. The second host is a SuSE Linux host, also running an IPv6 stack. That host’s name is Ford. Communication between the two hosts has not been an issue. In the absence of a router, they both autoconfigured for a link-local IPv6 address, using the 48-bit MAC identifier to build the address.
The Windows 2000 host Marvin has the following configuration:
|
MAC address |
00-02-B3-1E-83-29
|
|
IPv4 address |
|
|
IPv6 address |
fe80::202:b3ff:fe1e:8329
|
The Linux host Ford has the following configuration:
|
MAC address |
00-A0-24-C5-32-56
|
|
IPv4 address |
|
|
IPv6 address |
fe80::2a0:24ff:fec5:3256
|
Pinging with IPv6
The first success was the verification of IPv6 communication by pinging each host as follows.
Open a command window on Marvin and issue the following command:
ping6 fe80::2a0:24ff:fec5:3256
Do you want to know what a ping with IPv6 looks like? Have a look at Figure 11-6.
Figure 11-6. Trace file with an IPv6 ping
Frame 1 is the Echo Request from Ford; Frame 2 is the Echo Reply from Marvin. The screenshot shows the two MAC addresses configured for a link-local ...
Get IPv6 Essentials now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
