C_RFC3315_18_1_5_InfRetransRT.seq - Check RT of Information-request
Client
C_RFC3315_18_1_5_InfRetransRT.seq [-tooloption...]
-pkt C_RFC3315_18_1_5_InfRetransRT.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
The client transmits the message using the following parameters:
IRT INF_TIMEOUT
MRT INF_MAX_RT
MRC 0
MRD 0
RT for the first message transmission is based on IRT:
RT = IRT + RAND*IRT
- Configurations
| Device Name |
Device Type |
Interface |
Assigned Prefix |
Link Local Addr |
MAC Addr |
| Client |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
| Server |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a1a1 |
00:00:00:00:a1:a1 |
NUT TN
| |
| |NUT only request configuration information
| |Initiate NUT (As a DHCPv6 Client)
| |
| ----> |Information-request
| |
| |Wait until the retransmission
| |
| ----> |Information-request (2*)
| |
| |
(2*)PASS: NUT retransmits Information-request.
And first RT conforms to Verification Points.
N/A
Also see RFC3315
18.1.5. Creation and Transmission of Information-request Messages
perldoc V6evalTool