S_RFC3315_7_Relay-replyMsgFormat.seq - Check Server's Relay-reply Message Format
Server
S_RFC3315_7_Relay-replyMsgFormat.seq [-tooloption ...]
-pkt S_RFC3315_7_Relay-replyMsgFormat.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client)
|
Link1 -------+-------------+---------------- 3ffe:501:ffff:101::/64
|
TN(Relay1)
|
Link0 ---------------------+----------+----- 3ffe:501:ffff:100::/64
|
NUT(Server1)
Relay-reply Message Format
msg-type
RELAY-REPL(13)
hop-count
Copied from the Relay-forward message
link-address
Copied from the Relay-forward message
peer-address
Copied from the Relay-forward message
options
Relay Message option
| 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 |
| Relay1(Link0) |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a4a4 |
00:00:00:00:a4:a4 |
| Relay1(Link1) |
TN |
Link1 |
3ffe:501:ffff:101::/64 |
fe80::200:ff:fe00:a5a5 |
00:00:00:00:a5:a5 |
NUT TN
| |
| | initialize NUT (as a DHCPv6 Server)
| |
| <---- | Relay Forward(Solicit)
| ----> | Relay Reply(Advertise) (*1)
The server's Relay-reply message(*1 )'s Format must be base on description
of RFC(see above Verification Points).
N/A
see also RFC3315
7. Relay Agent/Server Message Formats
20.3. Construction of Relay-reply Messages
perldoc V6evalTool