Skip to content

Conversation

@tiborschneider
Copy link
Contributor

The policy_tests.go file is updated to ignore that next-hop field when comparing attributes, so that previous test cases don't need to be rewritten.

The test case does not yet modify the attribute itself, as this feature is not yet supported.

The policy_tests.go file is updated to ignore that next-hop field when
comparing attributes, so that previous test cases don't need to be
rewritten.

The test case does not yet modify the attribute itself, as this feature
is not yet supported.
Devices like the OTG send the next-hop within MP_REACH_NLRI, while
others (like gobgp itself) uses the NEXT_HOP. We must read both when
converting back to OpenConfig.

Note, that gobgp allows multiple next-hops to be represented in
MP_REACH_NLRI (even though rfc-4760 only specifies a single next-hop).
Since OpenConfig only represents single next-hops, we error if we see
multiple next-hops. See https://datatracker.ietf.org/doc/html/rfc4760.
IPv6 unicast allows adding multiple next-hop addresses in the
MP_REACH_NLRI attribute. In that case, the second one is a link-local
address. Since OC does not support multiple next-hops, we just export
the first one. I added a comment explaining this.
@tiborschneider tiborschneider merged commit 503e57f into openconfig:main Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants