Project

General

Profile

Actions
Copy link

Bug #13441

open

FRR fails to start with route map on "sequence 0" in configuration

Added by Paighton Bisconer over 2 years ago. Updated 4 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
FRR
Target version:
-
Start date:
Due date:
% Done:

0%

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

Description

Creating a route map in FRR global configuration and assigning a network to sequence 0 prevents FRR/BGP from loading

Fails to load

route-map IPv4_Export permit 0
 match ip address prefix-list EXPORT_IPv4
route-map IPv4_Import permit 0
 match ip address prefix-list IMPORT_IPv4

Loads Successfully

route-map IPv4_Export permit 1
 match ip address prefix-list EXPORT_IPv4
route-map IPv4_Import permit 1
 match ip address prefix-list IMPORT_IPv4

Input validation or a valid integer range on the input is recommended

Actions
Copy link
 #1

Updated by Marcos M over 2 years ago

  • Project changed from pfSense Plus to pfSense Packages
  • Category changed from Routing to FRR
  • Release Notes deleted (Default)
Actions
Copy link
 #2

Updated by Danilo Zrenjanin over 2 years ago

  • Status changed from New to Confirmed

Tested on the:

FRR 1.1.1_7

Yes, I can confirm this issue. I couldn't find the valid sequence number range in the FRR docs. Upon my testing, it will work if the route map sequence number is between 1 - 65535.

ospfd is impacted too.

Actions
Copy link
 #3

Updated by Lev Prokofev almost 2 years ago

The same behavior on frr 1.2_3

frr fail to start

Jan 28 11:02:02 watchfrr 97266 [EC 268435457] bgpd state -> down : read returned EOF
Jan 28 11:02:02 watchfrr 97266 [EC 268435457] staticd state -> down : read returned EOF
Jan 28 11:02:02 watchfrr 97266 [EC 268435457] zebra state -> down : read returned EOF
Jan 28 11:02:02 watchfrr 97266 Terminating on signal
Jan 28 11:02:03 watchfrr 72106 watchfrr 7.5.1 starting: vty@0
Jan 28 11:02:03 watchfrr 72106 zebra state -> down : initial connection attempt failed
Jan 28 11:02:03 watchfrr 72106 staticd state -> down : initial connection attempt failed
Jan 28 11:02:03 watchfrr 72106 bgpd state -> down : initial connection attempt failed
Jan 28 11:02:03 watchfrr 72106 Forked background command [pid 72282]: /usr/local/etc/rc.d/frr restart all
Jan 28 11:02:03 watchfrr 72106 restart all process 72282 exited with non-zero status 2

Actions
Copy link
 #4

Updated by Danilo Zrenjanin 4 months ago

Tested against frr 2.0.2_4

pfSense 24.03

The behavior is the same. Sequence 0 in route map prevents FRR/BGP service from starting.

Actions
Copy link

Also available in: Atom PDF