Skip to content

Add ipv6 support for paloalto panos show routing route#2298

Open
lundgrenolof wants to merge 6 commits intonetworktocode:masterfrom
lundgrenolof:master
Open

Add ipv6 support for paloalto panos show routing route#2298
lundgrenolof wants to merge 6 commits intonetworktocode:masterfrom
lundgrenolof:master

Conversation

@lundgrenolof
Copy link
Copy Markdown

Adding ipv6 support in the show routing route parser

@lundgrenolof
Copy link
Copy Markdown
Author

Sorry about the commit mess.
Here are two fixes to show routing route.
The first commit adds ipv6 support
The second and third commit adds support for a few variations of which fields are displayed on each line.

mjbear added 2 commits March 30, 2026 20:39
Use pattern repetition to consolidate the flags regex further.

From the test data there can be up to three flag characters.
The white space regex is made non-greedy so it does not capture
a bunch of trailing white space.
@lundgrenolof lundgrenolof requested a review from mjbear April 2, 2026 07:35
The regex is a bit odd that it ends in a pipe symbol with no
other characters on the other side of the pipe (boolean or).

Change regex for:

- metric
- age
- nexthop_if
- next_as
@mjbear
Copy link
Copy Markdown
Collaborator

mjbear commented Apr 9, 2026

After further review, I found the existing template regex that end in a pipe symbol to be peculiar. It predated this PR.

  • METRIC
  • AGE
  • NEXTHOP_IF
  • NEXT_AS

For example:

Value METRIC (\d*|)

I've updated the line patterns accordingly to the changes I made to those regex.


Also it's possible to collapse most of the pattern lines into a single line with optional patterns. I was tempted to do that ... worked up that regex ... but have held off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants