Page MenuHomeVyOS Platform

restart bgp daemon throws route-map error
Closed, InvalidPublicBUG

Description

When you restart the bgp routing protocol via "restart bgp" it throws an error that the route-maps do not exist.
I was able to reproduce this in any configuration where a route-map is used in a BGP neighbour configuration.

The BGP session then will be established WITHOUT any filters and produces route leaks.

[email protected]:~$ restart bgp
WARNING: This is a potentially unsafe function!
You may lose the connection to the router or active configuration after
running this command. Use it at your own risk!

Continue? [y/N] y
The route-map 'INT-RS-IN' does not exist.
The route-map 'INT-RS-OUT' does not exist.

Details

Difficulty level
Normal (likely a few hours)
Version
1.4-rolling-202304130846
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Event Timeline

Hi

Could you share configuration ? where attached RM and BGP settings:

show configuration commands

As I said, this happens with any config that includes route maps

set protocols bgp neighbor 192.168.10.1 address-family ipv4-unicast route-map import 'INT-RS-IN'
set protocols bgp neighbor 192.168.10.1 address-family ipv4-unicast soft-reconfiguration inbound
set protocols bgp neighbor 192.168.10.1 remote-as '65000'
set protocols bgp neighbor 192.168.10.1 update-source '192.168.10.0'

set policy route-map INT-RS-IN rule 10 action 'permit'
set policy route-map INT-RS-IN rule 1000 action 'deny'

If I need to guess, it is just an issue that the BGP session gets configured before the route-maps

Looking at the FRR configuration vtysh -c "show run" I see the route-map - maybe it's just a display error? Or you actually leak routes?

It was actually leaking routes.

But it was a while ago, I will try to confirm it on a current build when I'm at the office tomorrow :)

Viacheslav changed the task status from Open to Needs reporter action.Jan 20 2024, 12:26 PM
Viacheslav triaged this task as Normal priority.
Viacheslav added a subscriber: Viacheslav.

@Arc771 Can you update the task?

Seems like its either fixed or was a quirk in that specific version.

I can't reproduce it on any recent version.