R_RFC3315_20_RelayMsgFromRelayAgent.seq - Relay Relay-reply message
Relay agent
R_RFC3315_20_RelayReplyMsg.seq [-tooloption ...]
-pkt R_RFC3315_20_RelayReplyMsg.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link1 ----------+----------+--------------- 3ffe:501:ffff:101::/64
|
NUT(Relay1)
|
Link0 ---------------------+----------+---- 3ffe:501:ffff:100::/64
|
TN(Server1)
- Verification Points
NUT's Message Format
- NUT will relay the Relay-reply message and only relay
the DHCP-relay message(Advertise) part of relay message option.
TN(Server1)'s Relay-reply Message
msg-type
RELAY-REPL(13)
hop-count
Any
link-address
A global or site-scoped address with a prefix assigned to the link
peer-address
Any
options
Relay Message option
DHCP-relay-message = Advertise
| Device Name |
Device Type |
I/F |
Assigned Prefix |
Link Local Addr |
MAC Addr |
| Relay1(Link0) |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address(Link0) |
NUT's MAC address(Link0) |
| Relay1(Link1) |
NUT |
Link1 |
3ffe:501:ffff:101::/64 |
NUT's Linklocal address(Link1) |
NUT's MAC address(Link1) |
| Server1 |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a1a1 |
00:00:00:00:a1:a1 |
| Client1 |
TN |
Link1 |
3ffe:501:ffff:101::/64 |
fe80::200:ff:fe00:a2a2 |
00:00:00:00:a2:a2 |
TN(Client1) NUT(Relay1)TN(Server1)
| | |
| ----> | |Solicit
| | -----> |Relay-forward(Solicit)
| | <---- |Relay-reply(Advertise) (*1)
|<---- | |Advertise
| | |
(*1)PASS: NUT will receive the Relay-reply message and relay it to the client.
N/A
see also RFC3315
20.2. Relaying a Relay-reply Message
perldoc V6evalTool