Repository navigation
Support for ICMPv6 Neighbor Solicitation - #502
Merged
Merged
Conversation
anjan-keysight
requested review from
abhijit-dhar,
alakendu and
apratimmukherjee
November 12, 2026 12:45
Contributor
Author
|
Review comments can be found below: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feature Overview
Related Issues: (#501, #507)
Redocly view of proposed model
Current we only support message type "Echo" in ICMPv6 traffic header. This proposal is for adding support for new message type "Neighbor Solicitation" in ICMPv6 header. Neighbor Solicitation is used to resolve IPv6 address, detect duplicate addresses or detect neighbor unreachability.
In addition, in IPv6 extension header segment routing, the segments list property is also updated to allow empty list, that may be required for negative testing. It is left to the implementation to add a default segment in the list.
Dev-Snappi branch reference
go get github.com/open-traffic-generator/snappi/gosnappi@dev-icmpv6
Case 1 - address resolution (multicast NS, Source Link-Layer Address included)
Case 2 - neighbor reachability check (unicast NS, Source Link-Layer Address included)
Case 3 - duplicate address detection (unspecified source, no options)
Optional case 4 - conformance / negative test (options RFC 4861 does not define for NS)