• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Problem getting FRR to filter routes as expected

FRR
1
1
1.0k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    joshuaitguy
    last edited by Oct 14, 2017, 12:53 AM

    So I've been banging my head against the wall the last few days trying to figure out how to get incoming BGP routes to be filtered out by FRR.

    I've configured a prefix list & route map and linked it to the neighbor, with the route map in place and matching against the prefix list I don't get any routes from the peer even though the one route I expect to see falls in one of the ranges specified in the prefix list.

    Below is the relevant sections of the config file showing what I've done.  Any suggestions or pointers would be much appreciated.  The documentation on frrouting.org hasn't been any help unfortunately and neither has any of the searches I've done on the Internet.

    Snippit from Zebra.conf

    
    ip prefix-list RFC1918 seq 5 permit 10.0.0.0/8 ge 21 le 24 
    ip prefix-list RFC1918 seq 10 permit 172.16.0.0/12 ge 21 le 24 
    ip prefix-list RFC1918 seq 15 permit 192.168.0.0/16 ge 21 le 24 
    ip prefix-list RFC1918 description Permite Addresses defined by RFC1918
    ! Route Maps
    route-map DefaultInBound permit 5
      match ip address prefix-list RFC1918
      on-match next
    route-map DefaultInBound permit 10
      set origin egp
    
    

    Snippit from bgpd.conf

    
      ! BGP Neighbors
      neighbor 10.255.0.2
      neighbor 10.255.0.2 remote-as XXXXX
      neighbor 10.255.0.2 update-source XXX.XXX.XXX.XXX
      no neighbor 10.255.0.2 send-community
      neighbor 10.255.0.2 soft-reconfiguration inbound
      neighbor 10.255.0.2 route-map DefaultInBound in
      neighbor 10.255.0.2 advertisement-interval 5
      neighbor 10.255.0.2 capability dynamic
      neighbor 10.255.0.2 maximum-prefix 10 80
    
    

    Note: This config is being managed through the "Raw Config" section of FRR settings.

    1 Reply Last reply Reply Quote 0
    1 out of 1
    • First post
      1/1
      Last post
    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.