S_RFC3315_18.2.8_TransmissionReplyMsg.seq - Checking Reply message transmission(Unicast)
Server
S_RFC3315_18.2.8_TransmissionReplyMsg.seq [-tooloption ...]
-pkt S_RFC3315_18.2.8_TransmissionReplyMsg.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
- Verification Points
- Reply Message
Unicast transmission
Through the same interface in which the original message is received
- 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 (Unicast from Client)
| ----> | Reply (Unicast to Client) (*1)
| |
(*1)PASS: The Reply message is unicast to Client through the interface which received the Request Message.
N/A
see also RFC3315
18 DHCP Client-Initiated Configuration Exchange
18.2.8. Transmission of Reply Messages
perldoc V6evalTool