NAME

routerRecvRsInvalid - Verifying invalid RS does not influence NCE.


TARGET

Router Only


INITIALIZATION

  Clear a neighbor cache entry for TN.


TEST PROCEDURE

routerRecvRsInvalid verifies that NUT does not create NCE even if receive an invalid RS.

  TN                 NUT
  ----------------------

State: No neighbor cache entry (for TN)
==== invalid RS ===>
Judgment: Examining NUT's neighbor state


JUDGMENT

  ==================+=====================================
  RS                | NCE state
                    +------------------+------------------
                    | Before           | After
                    | receiving the RS | receiving the RS
  ==================+==================+==================
  RS w/ SLL         | none             | none 
  hop *limit!=255   |
  ------------------+------------------+------------------
  RS w/ SLL         | none             | none 
  *invalid checksum |
  ------------------+------------------+------------------
  RS w/ SLL         | none             | none 
  *icmp code!=0     |
  ------------------+------------------+------------------
  RS w/ SLL         | none             | none 
  *src=unspecified  |
  ==================+==================+==================


TERMINATION

  N/A


NOTE

  N/A


REFERENCE

RFC2461

6.1.1. Validation of Router Solicitation Messages
A router MUST silently discard any received Router Solicitation messages that do not satisfy all of the following validity checks:
- The IP Hop Limit field has a value of 255, i.e., the packet could not possibly have been forwarded by a router.
- If the message includes an IP Authentication Header, the message authenticates correctly.
- ICMP Checksum is valid.
- ICMP Code is 0.
- ICMP length (derived from the IP length) is 8 or more octets.
- All included options have a length that is greater than zero.
- If the IP source address is the unspecified address, there is no source link-layer address option in the message.


SEE ALSO

  perldoc V6evalTool
  perldoc V6evalRemote