S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgWithReconfigureOP.seq - Server's Reply message with Reconfigure Accept Option
Server
S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgWithReconfigureOP.seq [-tooloption ...]
-pkt S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgWithReconfigureOP.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)
Server Identifier option
Any
Client Identifier option
Same as the Solicit Message
Reconfigure Accept option
Any
- 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(w/ Reconfigure Accept option)
| <---- | Request
| ----> | Reply (w/ Reconfigure Accept option)(*1)
| |
(*1) PASS: The format of Advertise,Solicit & Request message is correct.
The Reply message with Reconfigure Accept option is received by TN(not check).
N/A
see also RFC3315
17.2.3. Creation and Transmission of Reply Messages
22.20 Reconfigure Accept option
perldoc V6evalTool