Project

General

Profile

Actions
Copy link

Bug #14668

open

FRR BGP route is not making into kernel route table after WireGuard's peer change is applied

Added by Oleksii Tucha 9 months ago. Updated 5 months ago.

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

0%

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

Description

I was able to reproduce this behavior in clear PfSense 2.7 setup with frr 1.3_1 and WireGuard 0.2.0_2, not sure which package is guilty.

Steps to reproduce:
1. Create a WireGuard tunnel between two PfSense and configure BGP to use WireGuard's interface addresses as neighbors
2. Make sure there are correct routes from BGP in kernel routes
3. Make any change in WireGuard tunnel (or peer) and apply change - the route disappears from kernel route table
4. The route is never making it into kernel unless there is an advertisement update from neighbor or service restart

Actions
Copy link

Also available in: Atom PDF