C_RFC3315_18_1_1_RetransReq.seq - Check MRC of Request
Client
C_RFC3315_18_1_1_RetransReq.seq [-tooloption...]
-pkt C_RFC3315_18_1_1_RetransReq.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 REQ_TIMEOUT
MRT REQ_MAX_RT
MRC REQ_MAX_RC
MRD 0
The client retransmits Request for MRC times.
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 | | | |Initialize NUT(as a DHCPv6 client) | | | ----> |Solicit | <---- |Advertise | ----> |Request | | . .Retransmit REQ_MAX_RC times. | | | ----> |Request (4*) | |
(4*)PASS: NUT does not retransmit Request message.
N/A
Also see RFC3315
18.1.1. Creation and Transmission of Request Messages
perldoc V6evalTool