-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for frr ? #96
Comments
Can you articulate the differences and perhaps provide a patch via a pull-request? |
Not the OP, but I use Vyos (which is Frr under the hood). The one major thing that I've found bgpq4 can't do that would be a big help for both FRR and Vyos is a way to sequence prefix lists. FRR prefix list syntax is this:
Vyos syntax is for one prefix item is:
I currently use the following to generate a custom format in bgpq4 and then go and manually change the ### into rule numbers.
Even if not a fully supported format, I would love to see a way to sequence rules with numbers added into the custom format options. |
Hi, I have added support for FRRouting prefix lists in #126. I would appreciate if you have the time to review the changes. |
Thanks, it looks very good, but newer versions of frr have numbered prefix lists, like this:
Any chance to add those seq numbers ? |
I'm playing with the code and might have some quick-and-dirty answer. |
The patches to main.c and printer.c modified to add sequence numbers see: https://people.freebsd.org/~pi/bgpq4/patch-main.c |
And: bgpq4_print_frr_prefixlist() in printer.c is probably not needed, as bgpq4_print_cisco_prefixlist() works for frr. |
The links above are extended to also support sequence numbers in frr as-path. |
example: bgpq4 -W 2 -Zsf 12502 AS-NEPUSTIL |
Thank you for the patches, I will take a look. |
I have added support for sequenced prefix lists. I'm not familiar with the as-path list, therefor I will not include it in my PR. |
Is there a plan to support frr syntax ?
https://frrouting.org/
The syntax is very similar to cisco, but some differences exist.
The text was updated successfully, but these errors were encountered: