Bug #11290

FRR Service not following CARP Status IP

Added by Christian McDonald 3 months ago. Updated 3 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


FRR 1.0.0 is not properly starting/stopping in regards to the configured CARP status IP.


#1 Updated by Christian McDonald 3 months ago

Update: I'm not seeing this in the latest snapshots now. So I'm not entirely sure what's going on. There might be an edge case when upgrading from 2.4.x branch and porting the configuration over, not sure. But this might be closeable unless someone else can replicate this.

#2 Updated by Alhusein Zawi 3 months ago

please provide the Steps to reproduce the issue.

#3 Updated by Christian McDonald 3 months ago

I experienced this with a very simple OSPF configuration that I had on the 2.4 stable branch. This was an in-place upgrade to the 2.5 development branch (eager to begin testing WireGuard). Initially I was seeing FRR 1) not starting on system boot-up and 2) not following CARP VIP status. So, I uninstalled FRR 1.0.0, neutered my config.xml file by hand (removing any and all references to FRR configuration), reinstalled FRR 1.0.0 and reconfigured the packaged from scratch. I thought I was still observing the issue, but it seems to be working correctly I'm not entirely sure what happened.

Either way, it would be worth at least keeping an eye out for this potential edge case.

#4 Updated by Jim Pingle 3 months ago

  • Status changed from New to Closed
  • Target version deleted (2.5.0)

I'll close this out for now, but if someone can reproduce it, we can open it back up with more details about exactly what it takes to replicate.

Also available in: Atom PDF