Bug #11325
BGP MD5 Keys Dropping Unintentionally
0%
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
History
Updated by #2
Updated by Christian McDonald about 1 month ago
Updated by Great thanks!
#3
Updated by Renato Botelho about 1 month ago
Updated by - Status changed from New to Feedback
PR has been merged. Thanks!
#4
Updated by Alhusein Zawi about 1 month ago
Updated by pressing "save" interrupts the adjacency.
2.5.0.a.20210127.2350
#5
Updated by Viktor Gurov about 1 month 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
#6
Updated by Jim Pingle about 1 month ago
Updated by - Status changed from Feedback to Pull Request Review
#7
Updated by Renato Botelho about 1 month ago
- Status changed from Pull Request Review to Feedback
PR has been merged. Thanks!
#8
Updated by Jim Pingle about 1 month ago
- Target version deleted (
2.5.0)
#9
Updated by Alhusein Zawi about 1 month ago
pressing "save" is not interrupting the adjacency. (fixed).
2.5.0.a.20210129.1122
#10
Updated by Viktor Gurov about 1 month ago
- Status changed from Feedback to Resolved