Project

General

Profile

Actions
Copy link

Feature #11130

closed

FRR RIP support

Added by Viktor Gurov about 2 years ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
FRR
Target version:
-
Start date:
12/04/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:

Description

since the routing daemon is not available in version 2.5, it would be useful to add RIP (+ RIPng?) support to the FRR package
see http://docs.frrouting.org/en/latest/ripd.html

Related issues

Related to Regression #12653: RIP related startup errorResolvedViktor Gurov

Actions
Actions
Copy link
 #1

Updated by Viktor Gurov about 2 years ago

RIP can also be used as a workaround for #9204

Actions
Copy link
 #3

Updated by Jim Pingle over 1 year ago

  • Status changed from New to Pull Request Review
Actions
Copy link
 #4

Updated by Viktor Gurov about 1 year ago

  • Status changed from Pull Request Review to Feedback

Merged

Actions
Copy link
 #5

Updated by Viktor Gurov about 1 year ago

Actions
Copy link
 #6

Updated by Max Leighton about 1 year ago

After performing the workaround in https://redmine.pfsense.org/issues/12653, I am able to successfully exchange routes with RIP using FRR 1.1.1_2. I don't see any errors except for the one that is already documented on the related issue.

Actions
Copy link
 #7

Updated by Azamat Khakimyanov 2 months ago

Tested on 22.05 and on latest 23.01-DEV (built on Thu Nov 24 06:04:19 UTC 2022)

I used RIP between 2 nodes, with advertising internal subnets (passive interfaces) and Routed IPsec tunnels as active RIP interfaces. Everything was working correctly.

The only issues I saw were lack of RIP logging and absence of RIPng for IPv6.

I marked this Feature request as resolved.

Actions
Copy link
 #8

Updated by Azamat Khakimyanov 2 months ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF