[FROG] Route-map lets through unwanted routes

Quentin Young qlyoung at nvidia.com
Thu Mar 4 18:23:36 UTC 2021


> I completely missed traces of that relation when trying to understand the code for the Quagga parser.

I don't have much to add here except that you shouldn't need to read parser source to understand where commands are. VTYSH has the "find" command that will search for commands and tell you what node they are in, and if our docs[0] are lacking, we'd like to know so we can fix them.

[0] http://docs.frrouting.org/en/latest/
FRRouting User Guide — FRR latest documentation<http://docs.frrouting.org/en/latest/>
Copyright notice¶. Copyright (c) 1996-2018 Kunihiro Ishiguro, et al. Permission is granted to make and distribute verbatim copies of this manual provided the ...
docs.frrouting.org

________________________________
From: frog <frog-bounces at lists.frrouting.org> on behalf of Chriztoffer Hansen <ch at ntrv.dk>
Sent: Thursday, March 4, 2021 7:43 AM
To: jimc <jimc at jfcarter.net>
Cc: FRRouting Operator Group - Users List <frog at lists.frrouting.org>
Subject: Re: [FROG] Route-map lets through unwanted routes

External email: Use caution opening links or attachments


On Thu, 4 Mar 2021 at 01:40, jimc <jimc at jfcarter.net> wrote:
> redistribute kernel
> redistribute static
> redistribute connected

https://docs.frrouting.org/en/latest/ripd.html

What about applying a route-map directly to the redistribute command?

Thereby controlling which routes RIP(ng) imports from
kernel/connected/static protocols...

--
Chriztoffer


_______________________________________________
frog mailing list
frog at lists.frrouting.org
https://lists.frrouting.org/listinfo/frog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20210304/4565387d/attachment.htm>


More information about the frog mailing list