Conversation
17 tasks
troglobit
requested changes
Sep 14, 2026
troglobit
left a comment
troglobit
left a comment
Contributor
There was a problem hiding this comment.
Not sure if these ospfv3.adoc files are just remnants of the old copy-paste regime, because I couldn't find their corresponding Python docstring in code, so I assume they are generated then. In which case I suggest lifting out the IP address details from figures and placing them in tables¹ after the ASCII art image. This would make the ASCII art cleaner as well and candidate for draw.io replacements in the style of other tests.
Other than that, this looks great, awesome work on this! 👍
¹)
| Router | IPv4 | IPv6 |
|---|---|---|
| R1 | ... | ... |
| R2 | ... | ... |
| R3 | ... | ... |
saba8814
force-pushed
the
dynamic-routing-on-ipv6
branch
3 times, most recently
from
September 14, 2026 14:14
a85f4bf to
0396722
Compare
mattiaswal
reviewed
Sep 14, 2026
saba8814
force-pushed
the
dynamic-routing-on-ipv6
branch
from
September 15, 2026 09:40
0396722 to
71c8189
Compare
saba8814
force-pushed
the
dynamic-routing-on-ipv6
branch
from
September 17, 2026 06:44
71c8189 to
7383abb
Compare
Add support for dynamic IPv6 routing with OSPFv3 and RIPng: - RIPng: mirror of the RIPv2 feature set on IPv6 (basic, passive interfaces, multi-hop, redistribution), driven through netd. - OSPFv3: address-family ipv6 with areas, NSSA/stub, interface types (broadcast, point-to-point, hybrid), cost/priority/timers, BFD, default-route advertisement and redistribution (incl. RIPng <-> OSPFv3). - Operational state via statd (show ipv6 ospf [neighbor|interface|route]) - Full test coverage for both protocols. Limitations - OSPFv3 requires an explicit-router-id (no IPv4 to derive one from). - ospf6d has no totally-NSSA, no default-cost, and no non-broadcast / static-neighbor interfaces; these are rejected/omitted accordingly. - OSPFv3 next-hops are IPv6 link-local, so paths are verified by traceroute rather than by RIB next-hop matching. Signed-off-by: Ejub Sabic <ejub1946@outlook.com>
saba8814
force-pushed
the
dynamic-routing-on-ipv6
branch
from
September 17, 2026 11:01
7383abb to
80fca82
Compare
mattiaswal
requested changes
Sep 17, 2026
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
3 participants
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.
Add support for dynamic IPv6 routing with OSPFv3 and RIPng:
interfaces, multi-hop, redistribution), driven through netd.
(broadcast, point-to-point, hybrid), cost/priority/timers, BFD,
default-route advertisement and redistribution (incl. RIPng <-> OSPFv3).
Limitations
static-neighbor interfaces; these are rejected/omitted accordingly.
traceroute rather than by RIB next-hop matching.
Original PR: #1577
Description
Checklist
Tick relevant boxes, this PR is-a or has-a: