NAME
C_RFC3736_DUID_ENPersit.seq - Validate DUID consistency using Basic message exchange
TARGET
Client
SYNOPSIS
C_RFC3736_DUID_ENPersit.seq [-tooloption...]
-pkt C_RFC3736_DUID_ENPersit.def
-tooloption : v6eval tool option
See Also DHCPv6.def
INITIALIZATION
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
The client using DUID-EN should store it in the non-volatile storage. So if client
reboots, the DUID-EN will not change.
- Configurations
Device Name |
Device Type |
Interface |
Assigned Prefix |
Link Local Addr |
MAC Addr |
Client |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
Server |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a1a1 |
00:00:00:00:a1:a1 |
TEST PROCEDURE
NUT TN
| |
| |Initialize NUT(as a DHCPv6 Client)
| |
| ----> |information-request (1*)
| |
| |Reboot NUT
| |
| ----> |information-request (2*)
| |
JUDGEMENT
(2*)PASS: DUID-EN should be the same with that of (1*).
TERMINATION
N/A
REFERENCE
Also See RFC3315
9. DHCP Unique Identifier (DUID)
9.1. DUID Contents
9.3. DUID Assigned by Vendor Based on Enterprise Number [DUID-EN]
22.2. Client Identifier Option
SEE ALSO
perldoc V6evalTool