RA_BOTH_sRAmPXsRT - check the process when NUT receives RA which contains both of Global and Site-local prefixes.(Assigning both of Glboal and Site-local addresses)
All Node
Reboot NUT or Initialize interface of NUT or Initialize IPv6 stack of NUT.
The following tests are prepared in this test package. See INDEX file.
Test for all node
When NUT receives RA which contains Global and Site-local Prefixes, NUT assignes autoconfigured addresses. NUT MAY perform DAD for its Global and Site-local address prior to assigning them.
Test sequence
TN NUT --------------------------------- Initialize NUT
Configure address of NUT (reboot or interface initialization etc...)
TN wait the DAD NS sent from NUT
<=== Judgement #1: DAD NS =======
name: DADNS_from_NUT
<=== Judgement #2: RS ===========
name: RS_from_NUT, RS_from_NUT_wSLL
==== Action #1: RA =============>
name: RA_GA0SLA0
<=== Judgement #3: DAD NS =======
name: DADNS_from_NUT_GA0Tgt
<=== Judgement #4: DAD NS =======
name: DADNS_from_NUT_SLA0Tgt
Wait for 5+DupAddrDetectTransmits*(RetransTimer/1000)[sec]
Check if NUT's address is configured
==== Action #2: SOL NS =========>
name: SOLNS_from_TN_GA0Tgt
<=== Judgement #5: SOL NA =======
name:
NA_from_NUT_GA0Tgt,
NA_from_NUT_GA0Tgt_woTLL,
NA_from_GA0NUT_GA0Tgt,
NA_from_GA0NUT_GA0Tgt_woTLL,
NA_from_SLA0NUT_GA0Tgt,
NA_from_SLA0NUT_GA0Tgt_woTLL
==== Action #3: SOL NS =========>
name: SOLNS_from_TN_SLA0Tgt
<=== Judgement #6: SOL NA =======
name:
NA_from_GA0NUT_SLA0Tgt,
NA_from_GA0NUT_SLA0Tgt_woTLL,
NA_from_NUT_SLA0Tgt,
NA_from_NUT_SLA0Tgt_woTLL,
NA_from_SLA0NUT_SLA0Tgt,
NA_from_SLA0NUT_SLA0Tgt_woTLL
Test for all NODE
NUT performs Stateless Address Autoconfiguration(Global and Site-local) on its interface
Judgement #1. NUT MUST transmit DAD NS for its autoconfigured Link-local address.
name: DADNS_from_NUT
src: ::0
dst: solnode[NUT's tentative Link-local]
TargetAddress: NUT's tentative Link-local
Judgement #2. NUT SHOULD transmit RS.
name: RS_from_NUT
src: NUT's Link-local
dst: allrouter
Action #1. TN transmits RA which contains both of Global and Site-local Prefixes.
name: RA_GA0SLA0
src: TN's Link-local
dst: allnode
PXOPT: GA0
PXOPT: SLA0
Judgement #3. NUT MUST transmit DAD NS for its autoconfigured Global address.
(* If the address is consisits of EUI64, as same as Link-local
address, This DAD MAY be omitted.)
name: DADNS_from_NUT_GA0Tgt
src: ::0
dst: solnode[NUT's tentative Global0]
TargetAddress: NUT's tentative Global0
Judgement #4. NUT MUST transmit DAD NS for its autoconfigured Site-local address.
(* If the address is consisits of EUI64, as same as Link-local
address, This DAD MAY be omitted.)
name: DADNS_from_NUT_SLA0Tgt
src: ::0
dst: solnode[NUT's tentative Site-local0]
TargetAddress: NUT's tentative Site-local0
Action #2. TN transmits SOL NS to check if NUT's address is configured.
name: DADNS_from_TN_GA0Tgt
src: TN's Link-local
dst: solnode[NUT's Global0]
TargetAddress: NUT's Global0
Judgement #5. NUT MUST transmit SOL NA for its autoconfigured Global address.
name:
NA_from_NUT_GA0Tgt,
NA_from_NUT_GA0Tgt_woTLL,
NA_from_GA0NUT_GA0Tgt,
NA_from_GA0NUT_GA0Tgt_woTLL,
NA_from_SLA0NUT_GA0Tgt,
NA_from_SLA0NUT_GA0Tgt_woTLL
src: NUT's any Unicast Address
dst: TN's Link-local
TargetAddress: NUT's Global0
RFlag: 0
SFlag: 1
OFlag: 1
TLLOPT: NUT's MAC address
(* TLLOPT may be omitted)
Action #3. TN transmits SOL NS to check if NUT's address is configured.
name: DADNS_from_TN_SLA0Tgt
src: TN's Link-local
dst: solnode[NUT's Site-local0]
TargetAddress: NUT's Site-local0
Judgement #6. NUT MUST transmit SOL NA for its autoconfigured Site-local address.
name:
NA_from_GA0NUT_SLA0Tgt,
NA_from_GA0NUT_SLA0Tgt_woTLL,
NA_from_NUT_SLA0Tgt,
NA_from_NUT_SLA0Tgt_woTLL,
NA_from_SLA0NUT_SLA0Tgt,
NA_from_SLA0NUT_SLA0Tgt_woTLL
src: NUT's any Unicast Address
dst: TN's Link-local
TargetAddress: NUT's Site-local0
RFlag: 0
SFlag: 1
OFlag: 1
TLLOPT: NUT's MAC address
(* TLLOPT may be omitted)
RFC2462
(omit)
5.5.3. Router Advertisement Processing
(omit)
For each Prefix-Information option in the Router Advertisement:
a) If the Autonomous flag is not set, silently ignore the Prefix Information option.
b) If the prefix is the link-local prefix, silently ignore the Prefix Information option.
c) If the preferred lifetime is greater than the valid lifetime, silently ignore the Prefix Information option. A node MAY wish to log a system management error in this case.
d) If the prefix advertised does not match the prefix of an address already in the list, and the Valid Lifetime is not 0, form an address (and add it to the list) by combining the advertised prefix with the link's interface identifier as follows:
| 128 - N bits | N bits | +---------------------------------------+------------------------+ | link prefix | interface identifier | +----------------------------------------------------------------+
If the sum of the prefix length and interface identifier length does not equal 128 bits, the Prefix Information option MUST be ignored. An implementation MAY wish to log a system management error in this case. It is the responsibility of the system administrator to insure that the lengths of prefixes contained in Router Advertisements are consistent with the length of interface identifiers for that link type. Note that interface identifiers will typically be 64-bits long and based on EUI-64 identifiers as described in [ADDR-ARCH].
If an address is formed successfully, the host adds it to the list of addresses assigned to the interface, initializing its preferred and valid lifetime values from the Prefix Information option.
(omit)
RFC2461
(omit)
4.2. Router Advertisement Message Format
(omit)
Possible options:
Source link-layer address The link-layer address of the interface from which the Router Advertisement is sent. Only used on link layers that have addresses. A router MAY omit this option in order to enable inbound load sharing across multiple link-layer addresses.
MTU SHOULD be sent on links that have a variable MTU (as specified in the document that describes how to run IP over the particular link type). MAY be sent on other links.
Prefix Information These options specify the prefixes that are on-link and/or are used for address autoconfiguration. A router SHOULD include all its on-link prefixes (except the link-local prefix) so that multihomed hosts have complete prefix information about on- link destinations for the links to which they attach. If complete information is lacking, a multihomed host may not be able to choose the correct outgoing interface when sending traffic to its neighbors.
(omit)
detail of v6eval tool option: see perldoc V6evalTool.pm, perldoc V6evalRemote.pm