S_RFC3315_20.3_Relay-replyConstruction.seq - Relay-reply message between multiple relay agents
Server
S_RFC3315_20.3_Relay-replyConstruction.seq [-tooloption ...]
-pkt S_RFC3315_20.3_Relay-replyConstruction.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link2 -------------+----------+---------------------3ffe:501:ffff:102::/64
|
|
TN(Relay2)
|
|
Link1 -------------+-----------------------+-------- 3ffe:501:ffff:101::/64
|
|
TN(Relay1)
|
|
Link0 ------------------------+------------+-------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
- Verification Points
Relay-reply Message
- msg-type
RELAY-REPLY
- hop-count
1
- link-address
0
- peer-address
3ffe:501:ffff:101::xxxx
- Relay Message option
- msg-type
RELAY-REPLY
- hop-count
0
- link-address
3ffe:501:ffff:102::xxxx
- peer-address
fe80::200:ff:fe00:a2a2
- Relay Message option
Advertise 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 |
| 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 |
| Relay2(Link1) |
TN |
Link1 |
3ffe:501:ffff:101::/64 |
fe80::200:ff:fe00:a5a5 |
00:00:00:00:a5:a5 |
| Relay2(Link2) |
TN |
Link2 |
3ffe:501:ffff:102::/64 |
fe80::200:ff:fe00:a6a6 |
00:00:00:00:a6:a6 |
TN(Client1)TN(Relay2) TN(Relay1) NUT(Server1)
| | | |
| ----> | | |Solicit
| | -----> | |Relay-forward(Solicit)
| | | -------> |Relay-forward(Solicit)
| | | <------ |Relay-reply(Advertise) (*1)
| | | |
(*1)PASS: NUT will send the correctly Relay-reply message.
N/A
see also RFC3315
20.3. Construction of Relay-reply Messages
perldoc V6evalTool