Project

General

Profile

Actions

Bug #11325

closed

BGP MD5 Keys Dropping Unintentionally

Added by Christian McDonald about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
FRR
Target version:
-
Start date:
01/27/2021
Due date:
% Done:

0%

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

Description

FRR 1.0.0 on latest v2.5 snapshots.

I'm peering with an upstream that requires a neighbor password.

If I run 'setkey -D', I can see the SAD entries. However, if I go back to the BGP neighbor and just open the neighbor configuration and press save, the SAD entry is removed and setkey -D returns No SAD entries. The only way to get the adjacency back is to manually restart bgpd

Actions #2

Updated by Christian McDonald about 3 years ago

Great thanks!

Actions #3

Updated by Renato Botelho about 3 years ago

  • Status changed from New to Feedback

PR has been merged. Thanks!

Actions #4

Updated by Alhusein Zawi about 3 years ago

pressing "save" interrupts the adjacency.

2.5.0.a.20210127.2350

Actions #5

Updated by Viktor Gurov about 3 years ago

- restart setkey only if parameters are changed;
- start setkey on service startup (frr.sh rc file fix);

https://gitlab.netgate.com/pfSense/FreeBSD-ports/-/merge_requests/36

Actions #6

Updated by Jim Pingle about 3 years ago

  • Status changed from Feedback to Pull Request Review
Actions #7

Updated by Renato Botelho about 3 years ago

  • Status changed from Pull Request Review to Feedback

PR has been merged. Thanks!

Actions #8

Updated by Jim Pingle about 3 years ago

  • Target version deleted (2.5.0)
Actions #9

Updated by Alhusein Zawi about 3 years ago

pressing "save" is not interrupting the adjacency. (fixed).

2.5.0.a.20210129.1122

Actions #10

Updated by Viktor Gurov about 3 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF