Test v6LC.2.1.23 - Fragment Header in Neighbor Solicitation and Neighbor Advertisement
Part A: Neighbor Soliciation with Fragment Header
Verify that the NUT doesn't process Neighbor Soliciation and Neighbor Advertisement messages with fragments.
* [RFC-6980] - Section 5
* Packet generator
* Monitor to capture packets
No Common Test Setup is performed. If the NUT is a router, configure a default route
with TR1 as next hop. The Common Test Cleanup is performed after each part.
Neighbor Soliciation
IPv6 Header
Next Header: 44
Source Address: TN1's Link-local Address
Destination Address: NUT's Link-Local Address
|
Fragment Header
Next Header: 58
Fragment Offset: 0
More Fragments flag: 1
|
| ICMPv6 Neighbor Soliciation
|
| Source Link-Layer Option |
|
NS Fragment
IPv6 Header
Next Header: 44
Source Address: TN1's Link-local Address
Destination Address: NUT's Link-Local Address
|
Fragment Header
Next Header: 58
Fragment Offset: 2
More Fragments flag: 0
|
|
Part A: Neighbor Soliciation with Fragment Header
1. TN1 transmits Neighbor Soliciation and NS fragment.
2. TN1 transmits an Echo Request to the NUT.
Part A
Step 2:
Observe the NUT transmitting a Neighbor Soliciation indicating that it didn't process the Neighbor Soliticaiton.
The NUT must not transmit an Echo Reply.
* None.