C_RFC3315_17_1_4_SubReplyWRapidCommit.seq - Test when receiving Reply with Rapid commit option
Client
C_RFC3315_17_1_4_SubReplyWRapidCommit.seq [-tooloption...]
-pkt C_RFC3315_17_1_4_SubReplyWRapidCommit.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
The client sends Solicit with Rapid commit option, and the Server
sends Advertise message to respond to the client, the client does
receive the configuration information in the Advertise message.
If the client subsequently receives a valid Reply message that
includes a Rapid Commit option, it either:
processes the Reply message, and discards any Reply messages
received in response to the Request message, or
processes any Reply messages received in response to the Request
message and discards the Reply message that includes the Rapid
Commit option.
- 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 |
NUT TN
| |
| |Initialize NUT(as a DHCPv6 client)
| |
| ----> |Solicit w/Rapid commit option
| |
| <---- |Advetise as a DHCPv6 Server1
| |
| ----> |Request
| |
| <---- |Reply w/Rapid commit opiton as a DHCPv6 Server2
| |
| <---- |Reply
| |
| <---- |Echo Request to address assgined by Server1
| |
| ----> |Echo Reply (7*)
| |
(7*)PASS: TN receives Echo Reply message from NUT.
N/A
Also see RFC3315
17.1.4. Receipt of Reply Message
perldoc V6evalTool