S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsg.seq - Creation & Transmission of Advertise Message
Server
S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsg.seq [-tooloption ...]
-pkt S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsg.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
NUT must reply with Advertise message.
Advertise Message
msg-type
ADVERTISE(2)
transaction-id
Same as the Solicit Message
Server Identifier option
Any
Client Identifier option
Same as the Solicit Message
- 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 (*1)
| |
(*1) PASS: NUT reply with Advertise message.
N/A
see also RFC3315
17.2.2. Creation and Transmission of Advertise Messages [Page 36 Line 2005]
perldoc V6evalTool