Project

General

Profile

Actions

Bug #10935

open

FRR 0.6.7-6 - BGPD service recycled IPv6 without Route Map

Added by Jeremy Peterson about 1 year ago. Updated 11 months ago.

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

0%

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

Description

https://forum.netgate.com/topic/157120/frr-0-6-7_6-bgp-won-t-start-without-route-map-ipv6-unicast?_=1601149473142

Above is my forum post.

As explained above. BGPd will not start unless all Networks to Distribute have valid Route Map defined.

But I am sharing IPv6 with BGPd and it seems that if I define a Route Map to the v6 networks BGPd will not redistribute the route.

https://forum.netgate.com/topic/157104/frr-0-6-7_6-bgp-ipv6-advertised-routes

I don't mind not defining a Route Map for IPv6 sharing but if the service will not start cleanly on a reboot that is a big problem.

To resolve the service not starting I navigate to pkg_edit.php?xml=frr/frr_bgp.xml and define a Route Map for the IPv6 networks to distribute and click save.

I then see the BGPd service is running and I have a valid IPv6 peer to my router but there will bo no advertised-routes showed when I issue this command to see the status of my peering via vtysh.

show bgp ipv6 neighbors 2606:0000:a120:5::13 advertised-routes

Now that the service is running if I go back to pkg_edit.php?xml=frr/frr_bgp.xml and remote the Route-Map defined for the IPv6 networks to distribute and click save the service will stay running and I will now see the advertised routes in vtysh.

I have recreated this on a second pfsense.
2.4.5-RELEASE-p1 (amd64)
frr 0.6.7_6

To recreate it yourself create and ipv6 peer in BGP and share a network from pfSense to your peer.

Actions #1

Updated by Jim Pingle about 1 year ago

  • Category set to FRR
Actions #3

Updated by Ben Hughes 11 months ago

0.6.8 has a lot of changes in it, so it's probably not directly relevant.

That config should work though so you'll need to do some more debug to find out why FRR doesn't start with it, try to get some logs as there isn't a lot to go off at this point. One thought might be RFC8212 but that shouldn't stop FRR starting and isn't forced until FRR 7.5.

Actions

Also available in: Atom PDF