Test v6LC.2.3.15 - Invalid Redirect does not Update Neighbor Cache (Hosts Only)
Part A: Redirect Source Address is Global
Verify that a host properly processes invalid Redirect messages when redirected on-link.
* [ND] Sections 8.1
* Packet generator
* Monitor to capture packets
Common Setup 1.1 is performed at the beginning of each test part. Wait at least 3
seconds (MAX_MULTICAST_SOLICIT * RETRANS_TIMER) after any previous cleanup to make sure
all previous NCE's are in state No NCE. The Common Test Cleanup Procedure is performed after each
part.
Part A: Redirect Source Address is Global
1. TR1 forwards an Echo Request to the HUT. The Source Address is the off-link global address o
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. The Redirect message
contains an incorrect IPv6 Source Address (the off-link global address of TN2).
4. Wait (RETRANS_TIMER * MAX_*CAST_SOLICIT). (3 seconds)
5. TR2 transmits a link-local Echo Request to the HUT.
6. Wait 2 seconds.
7. Observe the packets transmitted by the HUT.
Parts A through I
Step 2:
The HUT should respond to the Echo Request using TR1 as a first hop.
Step 7:
The HUT should transmit a multicast Neighbor Solicitation for TR2, indicating the
HUT did not create a NCE for TR2 upon reception of an invalid Redirect message.
* None.