Project

General

Profile

Actions

Bug #11847

open

Filters not applied to PEER Groups

Added by Grant Gordon 5 months ago. Updated about 2 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
FRR
Target version:
-
Start date:
04/23/2021
Due date:
% Done:

0%

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

Description

When creating a Peer group and adding an AS/Prefix filter or route map to the peer group, the generated configuration does not apply the filters to the peer group. Applying them directly to a peer does.

Expected Output

neighbor DEFAULT_PEERS peer-group
neighbor DEFAULT_PEERS description Default Peer Group
neighbor DEFAULT_PEERS prefix-list default-routes out
neighbor DEFAULT_PEERS filter-list default-as-filter out
neighbor DEFAULT_PEERS route-map set-local-pref in

Actual Output

neighbor DEFAULT_PEERS peer-group
neighbor DEFAULT_PEERS description Default Peer Group

Actions #2

Updated by Jim Pingle 5 months ago

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

Updated by Renato Botelho 2 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Viktor Gurov

PR has been merged. Thanks!

Actions #4

Updated by Alhusein Zawi about 2 months ago

Prefix filter is not showing up in configuration file if there is no added neighbor

router bgp 61000
no bgp network import-check
neighbor peergrouptest peer-group
neighbor peergrouptest remote-as 61000

after adding neighbor:

router bgp 61000
no bgp network import-check
neighbor peergrouptest peer-group
neighbor peergrouptest remote-as 61000
neighbor 172.17.99.211 remote-as 61000
!
address-family ipv4 unicast
neighbor 172.17.99.211 activate
no neighbor peergrouptest send-community
neighbor peergrouptest prefix-list prefixtest in
neighbor peergrouptest prefix-list prefixtest out
no neighbor 172.17.99.211 send-community
exit-address-family

Actions

Also available in: Atom PDF