S_RFC3736_Creation-Transmission_RelayReply.seq - Relay-Reply message transmission
Server
S_RFC3736_Creation-Transmission_RelayReply.seq [-tooloption ...]
-pkt S_RFC3736_Creation-Transmission_RelayReply.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link0 ---------------------+-------------- 3ffe:501:ffff:100::/64
|
TN(Relay1)
|
Link1 ---------------------+---------+--- 3ffe:501:ffff:101::/64
|
NUT(Server1)
Destination address set to TN's unicast address same as the Information-request message's source adderess
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
- option-code
OPTION_RELAY_MSG (9)
- option-len
Length of DHCP-relay-message
- DHCP-relay-message
Reply Message
- msg-type
REPLY(7)
- transaction-id
Same as the Relay-forward message
- Server Identifier option
Any
- Client Identifier option
Same as the Relay-forward message
- DNS Recursive Name Server option
- Configuration
| Device Name |
Device Type |
I/F |
Assigned Prefix |
Link Local Addr |
MAC Addr |
| Server1 |
NUT |
Link1 |
3ffe:501:ffff:101::/64 |
NUT's Linklocal address |
NUT's MAC address |
| Relay1(Link1) |
TN |
Link1 |
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:a3a3 |
00:00:00:00:a3:a3 |
| Client1 |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a4a4 |
00:00:00:00:a4:a4 |
NUT TN(Relay1) TN(Client1)
| | |
| | | initialize NUT (as a stateless DHCPv6 Server)
| | <---- | Information-request
| <---- | | Relay-forward (Information-request)
| ----> | | Relay-reply (Reply) (*1)
| | |
(*1)PASS: The server returns the relay-reply message that is same as the description of verification points.
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