Upgraded to 2.5 from 2.4.5 forced upgrade of FRR and it broke

[SBTech]

My config is pretty basic, but Its not working frr won't start.

sounds like some people had luck with deleting config.cache and rebooting that did not work for me.
I also added the route-map Allow-All with no success. I'm sure I'm missing something simple.

##################### DO NOT EDIT THIS FILE! ######################
###################################################################
# This file was created by an automatic configuration generator.  #
# The contents of this file will be overwritten without warning!  #
###################################################################
!
frr defaults traditional
hostname hostname.domain.com
password ChangeME
log syslog
service integrated-vtysh-config
!
ip router-id xx.xx.44.1
!
router bgp xxx55
 bgp router-id xxx.xxx.189.138
 no bgp network import-check
 neighbor xx.xx.68.5 remote-as 209
 neighbor xx.xx.68.5 update-source xx.xx.189.138
 neighbor xx.xx.68.5 ebgp-multihop 2
 neighbor xx.xx.68.5 enforce-multihop
 neighbor xx.xx.68.5 local-as xx55
 !
 address-family ipv4 unicast
  network xx.xx.44.0/24
  neighbor xx.xx.68.5 activate
  no neighbor xx.xx.68.5 send-community
  neighbor xx.xx.68.5 route-map Allow-All in
  neighbor xx.xx.68.5 route-map Allow-All out
 exit-address-family
 !
!
route-map Allow-All permit 100
!
line vty
!
end

[SBTech]

This post is deleted!

[SBTech]

Got FRR and BGP running but looks like nothing is passing.

BGP neighbor is XX.XX.68.5, remote AS XX09, local AS XXX55, external link
  BGP version 4, remote router ID 0.0.0.0, local router ID XX.XX.189.138
  BGP state = Active
  Last read 00:07:09, Last write never
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  0          0
    Notifications:          0          0
    Updates:                0          0
    Keepalives:             0          0
    Route Refresh:          0          0
    Capability:             0          0
    Total:                  0          0
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(large)
  Inbound path policy configured
  Outbound path policy configured
  Route map for incoming advertisements is *Allow-All
  Route map for outgoing advertisements is *Allow-All
  Route map for selective unsuppress is *Allow-All
  0 accepted prefixes

  Connections established 0; dropped 0
  Last reset 00:07:09,  Waiting for NHT
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 52 seconds
Read thread: off  Write thread: off  FD used: -1

[SBTech]

@sbtech

What I think happened was that during the upgrade something nuked the FRR BGP config.

I ended up rolling back to 2.4.5 and restoring from a backup config. After that was working again I review the BGP and settings where missing in the config after it had upgraded.

I installed 2.4.5 on a test router and restored the config from my core BGP router and after upgrading it, the settings for BGP came across.

I have not tested the upgrade test router since I will need to getup at 4am to try it :)

[Gcon]

@sbtech Perhaps "route-map Allow-All permit 100" should call a prefix-list which matches everything:

---

route-map Allow-All permit 100
match ip address prefix-list ALLOW-ALL

ip prefix-list ALLOW-ALL sq 5 permit any

---

I have found that in pfSense 2.5.x - the FRR has some differences compared to older rules when it comes to implicit permits and denys, so things have to spelled out explicitly now.