Skip to content

Add Static routing to RouterOS7 #3665

Merged
ipspace merged 8 commits into
ipspace:devfrom
snuffy22:routeros7-static
Jul 20, 2026
Merged

Add Static routing to RouterOS7 #3665
ipspace merged 8 commits into
ipspace:devfrom
snuffy22:routeros7-static

Conversation

@snuffy22

Copy link
Copy Markdown
Contributor

Create the needed templates for RouterOS 7 to do static routing.

Does all types

  • Static Global
  • Static VRF
  • Static Inter-VRF
  • Discard Routes

Passes all the static tests except the OSPFv3 because we do not yet support it.

(py-net) netlab@LAPTOP-8380MASB:~/snuffy-netlab/tests/integration$ ./device-module-test -p clab -d routeros7 -l '2[0-5]-static' routing
Pre-test cleanup:
12:59:03 routing/20-static.yml: create(ok) up(ok) config(ok) validate(ok) cleanup(ok) OK
13:00:29 routing/21-static-vrf.yml: create(ok) up(ok) config(ok) validate(ok) cleanup(ok) OK
13:01:55 routing/22-static-inter-vrf.yml: create(ok) up(ok) config(ok) validate(ok) cleanup(ok) OK
13:03:18 routing/23-static-indirect.yml: create(ok) up(ok) config(ok) validate(ok) cleanup(ok) OK
13:04:43 routing/24-static-indirect-inter-vrf.yml: create(FAIL)
13:04:43 routing/25-static-discard.yml: create(ok) up(ok) config(ok) validate(ok) cleanup(ok) OK

@snuffy22

Copy link
Copy Markdown
Contributor Author

Reviewed why OSPFv3 was not working for VRF, just a small copy/paste n value tweak to get working.

Advise if we want to break that out into another change.

Also migrated the target-scope to 41 to ensure any static indirect happens after at all other protocols.

@ipspace

ipspace commented Jul 20, 2026

Copy link
Copy Markdown
Owner

Reviewed why OSPFv3 was not working for VRF, just a small copy/paste n value tweak to get working.

Nice job. However, now you configure OSPFv3 for IPv4-only networks (like vrf/11-multi-vrf-ospf). Please look at the bigger picture, not just whether the tests pass. We cannot possibly check all ways in which things can be misconfigured. For example, we do not configure OSPFv3 on probes in OSPFv2-only scenarios just to detect whether someone configured OSPFv3 when it's not needed. OK, maybe we should...

Advise if we want to break that out into another change.

Please do.

Also migrated the target-scope to 41 to ensure any static indirect happens after at all other protocols.

That's an interesting concept. I've never seen anything like that before.

@snuffy22

Copy link
Copy Markdown
Contributor Author

Will create the new change with just vrf ospfv3 (with af check) in new PR as requested

ipspace added a commit that referenced this pull request Jul 20, 2026

@ipspace ipspace left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything works ;) Thank you!

@ipspace
ipspace marked this pull request as ready for review July 20, 2026 17:27
@ipspace
ipspace merged commit 0bcbad2 into ipspace:dev Jul 20, 2026
5 checks passed
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