S_RFC3736_Relay-replyThSameRelayAgent.seq - Relay-Reply message transmission
Server
S_RFC3736_Relay-replyThSameRelayAgent.seq [-tooloption ...]
-pkt S_RFC3736_Relay-replyThSameRelayAgent.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link1 -------------+----------+------------+--------3ffe:501:ffff:101::/64
| |
| |
| |
TN(Relay1) TN(Relay2)
| |
| |
Link0 -------------+----------+------------+-------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
NUT's Message
The Relay-reply message will be relayed through the same relay agent(TN)
that received the message from the client.
- 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:101::/64 |
fe80::200:ff:fe00:a2a2 |
00:00:00:00:a2:a2 |
| Relay1(Link0) |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a4a4 |
00:00:00:00:a4:a4 |
| Relay2(Link0) |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a7a7 |
00:00:00:00:a7:a7 |
TN(Client1) TN(Relay1) NUT(Server1)
| | |
| ----> | |Information-request
| | -----> |Relay-forward(Information-request)
| | <---- |Relay-reply(Reply) (*1)
| <---- | |Reply
| | |
wait for 5s
TN(Client1) TN(Relay2)NUT(Server1)
| | |
| ----> | |Information-request
| | -----> |Relay-forward(Information-request)
| | <---- |Relay-reply(Reply) (*2)
| <---- | |Reply
| | |
(*1)(*2)PASS: NUT should send the Relay-reply message to the Relay agent
has sent the Relay-forward message.
N/A
See also RFC3315
20.3 See also RFC3646
3 and 4 see also RFC3736
5.1. 5.2 adn 5.3
perldoc V6evalTool