NAME

  Test v6LC.2.1.7 - Invalid Neighbor Solicitation Handling
  Part E: Invalid Checksum

Purpose

  Verify that a node takes the proper actions upon receipt of an invalid Neighbor Solicitation.

References

  * [ND]  Sections 7.1.1 and 7.2.3

Resource Requirements

  * Packet generator
  * Monitor to capture packets

Test Setup

  No Common Test Setup is performed. The Common Test Cleanup procedure is
  performed after each part.

Neighbor Sol. A IPv6 Header Next Header: 58 Source Address: TN1's Link-local Address Destination Address: NUT's Link-local Address Hop Limit: 255 Neighbor Sol. Target Address: NUT's Link-local Address Souce Link-layer: Address: TN1's Link-layer address

Neighbor Sol. B IPv6 Header Next Header: 58 Source Address: Unspecified Address Destination Address: NUT's Link-local Address Hop Limit: 255 Neighbor Sol. Target Address: NUT's Link-local Address

Neighbor Sol. C IPv6 Header Next Header: 58 Source Address: Unspecified Address Destination Address: NUT's Solicited-node Multicast Address Hop Limit: 255 Neighbor Sol. Target Address: NUT's Link-local Address Source Link-layer Address: TN1's Link-layer address

Procedure

  Part E: Invalid Checksum
   9. TN1 transmits Neighbor Solicitation A with the ICMP checksum set to be invalid.
  10. Observe the packets transmitted by the NUT.

Observable Results

  Part E
   Step 10: The NUT must not transmit any packets corresponding to Neighbor Solicitation A.

Possible Problems

  * None.