S_RFC3315_18.2.2_ReceiptConfirmMsg.seq - Receipt of Confirm Message and return Reply
Server
S_RFC3315_18.2.2_ReceiptConfirmMsg.seq [-tooloption ...]
-pkt S_RFC3315_18.2.2_ReceiptConfirmMsg.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
Reply Message
msg-type
REPLY(7)
transaction ID
Same as the Confirm message
Server ID option
Include Server's DUID
Client ID option
Same as the Confirm message
Status Code option
value=Success(0)
Configuration
| Device Name |
Device Type |
I/F |
Assigned Prefix |
Link Local Addr |
MAC Addr |
| Server1 |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
| Client1 |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a2a2 |
00:00:00:00:a2:a2 |
NUT TN
| |
| | initialize NUT (as a DHCPv6 Server)
| |
| <---- | Solicit
| ----> | Advertise
| <---- | Request
| ----> | Reply
| |
| |
| |
| <---- | Confirm
| ----> | Reply (*1 )
| |
(*1) PASS: If all the address in the Confirm message passed test, the NUT
will return a Reply message.
N/A
see also RFC3315
18 DHCP Client-Initiated Configuration Exchange
18.2.2. Receipt of Confirm Messages
perldoc V6evalTool