S_RFC3315_22.7_OptionRequestOP.seq - Checking Relay Message Option in the Relay-reply message
Server
S_RFC3315_22.7_OptionRequestOP.seq [-tooloption ...]
-pkt S_RFC3315_22.7_OptionRequestOP.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Relay agent1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
Relay-reply Message Format
msg-type
RELAY-REPL(13)
transaction-id
Any
Server ID option
Any
Client ID option
Any
Relay Message option
- option-code
OPTION_RELAY_MSG (9)
- option-len
Length of DHCP-relay-message
| 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 |
| Relay agent1 |
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)
| |
| <---- | Relay-forward (w/ Relay Message option Solicit)
| ----> | Relay-reply (w/ Relay Message option Advertise) (*1)
| |
| |
(*1)PASS: The NUT received the Relay-forward message and return the Relay-reply message
including the Relay Message option.
N/A
see also RFC3315
22.10. Relay Message Option
perldoc V6evalTool