Project

General

Profile

Actions

Bug #11686

closed

FRR generated ACCEPTFILTER permit statement broken

Added by Robert Sailer about 1 year ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
FRR
Target version:
-
Start date:
03/16/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.5.0
Affected Plus Version:
Affected Architecture:
All

Description

When the ACCEPTFILTER is generated all goes well except the last line which is ip prefix-list ACCEPTFILTER seq 10 permit any.
When it starts ospf works fine and the routes are in the ospf database but zebra refuses to add them to the FIB.
After removing "seq 10" manually and restarting frr it just works as expected.

Solution proposed: Just remove "seq 10" when generating the last rule for the ACCESSFILTER from the generator code


Files

acceptfilter.txt (1.61 KB) acceptfilter.txt Marcos Mendoza, 02/08/2022 04:00 PM

Related issues

Related to Bug #11836: FRR ACCEPTFILTER unstableAssignedViktor Gurov04/22/2021

Actions
Actions #1

Updated by Jim Pingle about 1 year ago

  • Project changed from pfSense to pfSense Packages
  • Category changed from Routing to FRR
  • Target version deleted (2.5.1)
  • Release Notes deleted (Default)
Actions #3

Updated by Jim Pingle 3 months ago

  • Status changed from New to Pull Request Review
Actions #4

Updated by Marcos Mendoza 3 months ago

This can be applied using the System Patches package.

Actions #5

Updated by Viktor Gurov 3 months ago

  • Related to Bug #11836: FRR ACCEPTFILTER unstable added
Actions #6

Updated by Azamat Khakimyanov 3 months ago

  • Status changed from Pull Request Review to Resolved

Tested on 22.01-RELEASE (built on Mon Feb 07 16:37:59 UTC 2022) with patch applied.

I see correct ACL sequence now. For example for my setup
ip prefix-list ACCEPTFILTER seq 10 deny 192.168.25.0/24
ip prefix-list ACCEPTFILTER seq 20 deny 192.168.25.1/32
ip prefix-list ACCEPTFILTER seq 30 deny 172.31.25.0/24
ip prefix-list ACCEPTFILTER seq 40 deny 172.31.25.1/32
ip prefix-list ACCEPTFILTER seq 50 deny 10.10.87.0/30
ip prefix-list ACCEPTFILTER seq 60 deny 10.10.87.2/32
ip prefix-list ACCEPTFILTER seq 70 permit any

so I saw that Permit Any rule had correct sequence number (last in order)

I marked this Bug as resolved.

Actions

Also available in: Atom PDF