[FROG] Filter connected routes from being learned ?

[Brandon Applegate]

Hello,

I am trying to prevent FRR from picking up a route - let’s call it “mgmt”.  These are Ubuntu 16.04 hosts, so I’m using /etc/network/interfaces.  I’m using some manual post-up commands to take one of my NICs and put it into the “mgmt” table (already added to /etc/iproute2/rt_tables).  This is working as intended.

The issue is that FRR is still picking this up as a connected route.  I don’t know enough about the innards of FRR, but I’m guessing it’s picking it up from the interface structure in the kernel - as my route table commands have expunged it from the global/default table.

So on with my real question - is there a way I can filter this ?  I had thought/hoped it would be this:

http://docs.frrouting.org/en/latest/zebra.html#zebra-route-filtering

Either that doesn’t do what I had hoped - or I’m configuring it wrong.  My thought process was to make a PL with a permit matching my mgmt route (10.255.0.0/16) - and a route-map with a deny matching on the PL.  Then I would ‘ip protocol connected route-map DENY-MGMT’.  I’ve tried this, and restarted FRR, but no matter what - this route keeps finding it’s way back in as “connected”.

Any pointers would be greatly appreciated.  Thanks.

--
Brandon Applegate - CCIE 10273
PGP Key fingerprint:
0641 D285 A36F 533A 73E5  2541 4920 533C C616 703A
"For thousands of years men dreamed of pacts with demons.
Only now are such things possible."

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20180629/08de7f5a/attachment.sig>