plugins: net/frr7 - completely broken in 20.7
Important notices Before you add a new report, we ask you kindly to acknowledge the following: [X] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md [X] I have searched the existing issues and I’m convinced that mine is new. [X] The title contains the plugin to which this issue belongs
Describe the bug FRR communication between Zebra (route export/import) and all daemons is broken in 20.7, which means that routing does not work correctly, period. This can be reproduced by any configuration and protocol because it is a failure to communicate with Zebra.
Indicator:
zebra/zebra_ptm.c:1362 failed to find process pid registration
BGP: [EC 33554499] sendmsg_nexthop: zclient_send_message() failed
If that appears in the logs, routes are not going to be updated correctly. It will appear in the logs every time. See https://github.com/FRRouting/frr/issues/3136 for a better explanation and details. This matches exactly.
To Reproduce
- Set up any sort of FRR configuration (OSPF, OSPFv3, BGP)
- Enable FRR
- Observe
zebra/zebra_ptm.c:1362 failed to find process pid registration
in logs
Expected behavior See https://github.com/FRRouting/frr/issues/3136
Relevant log files
2020/08/01 12:28:52 ZEBRA: zebra/zebra_ptm.c:1351 failed to find process pid registration
2020/08/01 12:28:52 ZEBRA: client 20 disconnected 0 bgp routes removed from the rib
2020/08/01 12:28:53 ZEBRA: Terminating on signal
2020/08/01 12:28:53 BGP: [EC 33554499] sendmsg_nexthop: zclient_send_message() failed
Additional context Add any other context about the problem here.
Environment OPNsense 20.7 frr7 7.4_1
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 5
- Comments: 46 (19 by maintainers)
Via CLI:
fetch -o /usr/local/opnsense/scripts/quagga/quagga.rb https://raw.githubusercontent.com/opnsense/plugins/5d1b241c831ffdbfacaa577f0852e62127905a64/net/frr/src/opnsense/scripts/quagga/quagga.rb
Can you login via CLI, type
vtysh
and check if it’s just a display error?I already have a PR open which disables the requirement for ebgp policies. Maybe we will just revert to 7.3 but with 7.4 and policy disables I was seeing routes in zebra