sendMcastNS - Verify that NUT sends multicast NSs with RetransTimer = 1sec
Host and Router
Clear a neighbor cache entry for TN.
sendMcastNS verifies NUT send multicast NSs with following paramters
- MAX_MULTICAST_SOLICIT = 3 - RETRANS_TIMER = 1sec
TN NUT --------------------------------
State: No neighbor cache entry (for TN)
==== echo-request ===> src=TN's link-local dst=NUT's link-local
State: INCOMPLETE
Wait (RETRANS_TIMER * MAX_MULTICAST_SOLICIT)
<=== Judgment #1: multicast NS === src=NUT's link-local or global dst=solicited-node[TN's link-local] w/ SLLA
<=== Judgment #1: multicast NS === src=NUT's link-local or global dst=solicited-node[TN's link-local] w/ SLLA
<=== Judgment #1: multicast NS === src=NUT's link-local or global dst=solicited-node[TN's link-local] w/ SLLA
1. NUT sends the following multicast NSs:
src=NUT's link-local or global, dst=solicited-node[TN's link-local], w/ SLLA
1.1. A Number of the multicast NSs <= MAX_MULTICAST_SOLICIT(3)
1.2. Intervals between the multicast NSs >= RETRANS_TIMER(1 sec.)
N/A
The test does not invoke any remote command.
RFC2461
7.2.2 Sending Neighbor Solicitations
When a node has a unicast packet to send to a neighbor, but does not know the neighbor's link-layer address, it performs address resolution. For multicast-capable interfaces this entails creating a Neighbor Cache entry in the INCOMPLETE state and transmitting a Neighbor Solicitation message targeted at the neighbor. The solicitation is sent to the solicited-node multicast address corresponding to the target address.
If the source address of the packet prompting the solicitation is the same as one of the addresses assigned to the outgoing interface, that address SHOULD be placed in the IP Source Address of the outgoing solicitation. Otherwise, any one of the addresses assigned to the interface should be used. Using the prompting packet's source address when possible insures that the recipient of the Neighbor Solicitation installs in its Neighbor Cache the IP address that is highly likely to be used in subsequent return traffic belonging to the prompting packet's "connection".
If the solicitation is being sent to a solicited-node multicast address, the sender MUST include its link-layer address (if it has one) as a Source Link-Layer Address option. Otherwise, the sender SHOULD include its link-layer address (if it has one) as a Source Link-Layer Address option. Including the source link-layer address in a multicast solicitation is required to give the target an address to which it can send the Neighbor Advertisement. On unicast solicitations, an implementation MAY omit the Source Link-Layer Address option. The assumption here is that if the sender has a peer's link-layer address in its cache, there is a high probability that the peer will also have an entry in its cache for the sender. Consequently, it need not be sent.
While waiting for address resolution to complete, the sender MUST, for each neighbor, retain a small queue of packets waiting for address resolution to complete. The queue MUST hold at least one packet, and MAY contain more. However, the number of queued packets per neighbor SHOULD be limited to some small value. When a queue overflows, the new arrival SHOULD replace the oldest entry. Once address resolution completes, the node transmits any queued packets.
While awaiting a response, the sender SHOULD retransmit Neighbor Solicitation messages approximately every RetransTimer milliseconds, even in the absence of additional traffic to the neighbor. Retransmissions MUST be rate-limited to at most one solicitation per neighbor every RetransTimer milliseconds.
10. PROTOCOL CONSTANTS
Node constants:
MAX_MULTICAST_SOLICIT 3 transmissions
MAX_UNICAST_SOLICIT 3 transmissions
MAX_ANYCAST_DELAY_TIME 1 second
MAX_NEIGHBOR_ADVERTISEMENT 3 transmissions
REACHABLE_TIME 30,000 milliseconds
RETRANS_TIMER 1,000 milliseconds
DELAY_FIRST_PROBE_TIME 5 seconds
MIN_RANDOM_FACTOR .5
MAX_RANDOM_FACTOR 1.5
perldoc V6evalTool perldoc V6evalRemote