NAME

routerRecvRs - Verifying that NUT responds valid RSs


TARGET

  Router Only


SYNOPSIS

  routerRecvRs.seq [-tooloption ...] -p routerRecvRs.def


INITIALIZATION

  Clear NC state for TN.


TEST PROCEDURE

routerRecvRs verifies that NUT responds valid RSs and ignores invalid RSs.

  TN               NUT
  ----------------------
  State: NONCE (for TN)

==== valid/invalid RS ===>
<=== RA ====
Wait for MIN_DELAY_BETWEEN_RAS sec.


JUDGMENT

  1. NUT must send a valid RA when received a valid RS.

========================================+================= RS | Expected RA ========================================+================= RS w/o SLL, src=unspecific | sending RA ----------------------------------------+----------------- RS w/o SLL, src=link-local | sending RA ----------------------------------------+----------------- RS w/ SLL, src=link-local | sending RA ----------------------------------------+----------------- RS w/o SLL, hop *limit!=255 (INVALID) | NOT sending RA ----------------------------------------+----------------- RS w/o SLL, *invalid checksum (INVALID) | NOT sending RA ----------------------------------------+----------------- RS w/o SLL, *icmp code!=0( INVALID) | NOT sending RA ----------------------------------------+----------------- RS *w/ SLL, *src=unspecified (INVALID) | NOT sending RA ========================================+=================
2. NUT sends the following RA that was configured by the previous test.
3. The received RA may have - Source link-layer address option - MUT option - Prefix option


TERMINATION

  N/A


NOTE

  N/A


REFERENCE

RFC2461

4.3. Neighbor Solicitation Message Format IP Fields:
Source Address Either an address assigned to the interface from which this message is sent or (if Duplicate Address Detection is in progress [ADDRCONF]) the unspecified address.
Destination Address Either the solicited-node multicast address corresponding to the target address, or the target address.
Hop Limit 255
Authentication Header If a Security Association for the IP Authentication Header exists between the sender and the destination address, then the sender SHOULD include this header.
ICMP Fields:
Type 135
Code 0
Checksum The ICMP checksum. See [ICMPv6].
Reserved This field is unused. It MUST be initialized to zero by the sender and MUST be ignored by the receiver.
Target Address The IP address of the target of the solicitation. It MUST NOT be a multicast address.
Possible options:
Source link-layer address The link-layer address for the sender. MUST NOT be included when the source IP address is the unspecified address. Otherwise, on link layers that have addresses this option MUST be included in multicast solicitations and SHOULD be included in unicast solicitations.

6.2.6. Processing Router Solicitations
In addition to sending periodic, unsolicited advertisements, a router sends advertisements in response to valid solicitations received on an advertising interface. A router MAY choose to unicast the response directly to the soliciting host's address (if the solicitation's source address is not the unspecified address), but the usual case is to multicast the response to the all-nodes group. In the latter case, the interface's interval timer is reset to a new random value, as if an unsolicited advertisement had just been sent (see Section 6.2.4).


SEE ALSO

  perldoc V6evalTool
  perldoc V6evalRemote