Project

General

Profile

Bug #11158

FRR Prefix Lists

Added by Alhusein Zawi 5 months ago. Updated 4 months ago.

Status:
New
Priority:
High
Assignee:
-
Category:
FRR
Target version:
-
Start date:
12/12/2020
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:

Description

Adding any value to Minimum Prefix box on Prefix Lists will stop receiving/sending the routes from/to the neighbor when applied.

it should filter the prefix depending on the value .

with 32 ip prefix-list test33 seq 10 permit 33.3.3.3/24 ge 32
and 1 ip prefix-list test33 seq 10 permit 33.3.3.3/24 ge 1

it is not working as expected even if the value was 1 or 32

tested on 2.4.5-RELEASE-p1 and 2.5 (2.5.0.a.20201212.0250)

History

#1 Updated by Jim Pingle 5 months ago

  • Project changed from pfSense to pfSense Packages
  • Category changed from Routing to FRR

#2 Updated by Ben Hughes 4 months ago

As long as the configuration is getting generated correctly this is probably an FRR bug, I've run into various 'strange' things with route-maps and prefix-lists with FRR. But I'll check it out and see if I can reproduce anything that needs to be fixed in the package.

Can you try removing and re-applying the route-map to the relevant redistribution in the mean time? I've found it normally gets FRR back on the level after changing things.

Also available in: Atom PDF