Test v6LC.2.3.7 - Redirected Twice (Hosts Only)
Verify that a host properly processes valid Redirect messages twice for the same destination.
* [ND] Sections 8.3
* Packet generator
* Monitor to capture packets
The following setup procedure is performed before each Part:
a) Perform Common Setup 1.1.
b) TR2 transmits an Echo Request to the HUT's link-local address. TR2 responds to any
Neighbor Solicitations from the HUT with a Neighbor Advertisement with the solicited bit set to
1 causing the HUT to update it's NCE for TR2 to sate REACHABLE.
The Common Test Cleanup Procedure is performed after each part.
1. TR1 forwards an Echo Request from TN1 to the HUT. The Source Address is the off-link global
address of TN1. The Destination Address is the global address of the HUT.
2. Observe the packets transmitted by the HUT.
3. TR1 transmits a Redirect message to the HUT. The ICMPv6 Destination Address is the global
address of TN1. The Target Address is the link-local address of TR2.
4. TR1 forwards an Echo Request from TN1 to the HUT. The Source Address is the off-link global
address of TN1. The Destination Address is the global address of the HUT.
5. Observe the packets transmitted by the HUT.
6. TR2 transmits a Redirect message to the HUT. The ICMPv6 Destination Address is the global
address of TN1. The Target Address is the link-local address of TR3.
7. TR1 forwards an Echo Request from TN1 to the HUT. The Source Address is the off-link global
address of TN1. The Destination Address is the global address of the HUT.
8. Observe the packets transmitted by the HUT.
Step 2:
The HUT should respond to the Echo Request using TR1 as a first hop, as it is the only router
in the HUT's Default Router List.
Step 5:
The HUT should respond to the Echo Request using TR2 as a first hop, indicating the HUT
processed the Redirect message.
Step 8:
The HUT should respond to the Echo Request using TR3 as a first hop, indicating the HUT
processed the Redirect message.
* None.