A bit of background.. I have an OPNsense instance that has a full BGP feed from an ISP. The routing actually does seem to work fine, but I can't see debug info in OPNsense -
When I try to view "Routing: Diagnostics: BGPv4" in OPNsense, it doesn't display the routing table, it just sits there saying "loading..." forever.
Meanwhile, in the configd logs I see:
configd.py: unable to sendback response [{"bgp_overview":{"table_version":"6317840","local_router_id":"XXX.XXX.XXX.XXX","output":[{"status":[{"dn":"valid","abb":"*"},{"dn":"best","abb":">"}],"Network":"XXX.XXX.XXX.XXX/24","Next Hop":"209.51.161.249","Metric":"","LocPrf":"","Weight":"0","Path":[{"dn":null,"abb":"6"},{"dn":null,"abb":"9"},{"dn":null,"abb":"3"},{"dn":null,"abb":"9"},{"dn":null,"abb":" "},{"dn":null,"abb":"1"},{"dn":null,"abb":"3"},{"dn":null,"abb":"3"},{"dn":null,"abb":"3"},{"dn":null,"abb":"5"},{"dn":null,"abb":" "},{"dn":null,"abb":"1"},{"dn":null,"abb":"3"},{"dn":null,"abb":"3"},{"dn":null,"abb":"3"},{"dn":null,"abb":"5"},{"dn":null,"abb":" "},{"dn":"IGP","abb":"i"}]},{"status":[{"dn":"valid","abb":"*"},{"dn":"best","abb":">"}],"Network":"XXX.XXX.XXX.XXX/22","Next Hop":"209.51.161.249","Metric":"","LocPrf":"","Weight":"0","Path":[{"dn":null,"abb":"6"},{"dn":null,"abb":"9"},{"dn":null,"abb":"3"},{"dn":null,"abb":"9"},{"dn":null,"abb":" "},{"dn":null,"abb":"4"},{"dn":null,"abb":"8"},{"dn":nu
And in the General log file I see:
configd[54631]: Timeout (120) executing : quagga diag-bgp2
I guess it's a matter of how long it takes to pull the routing table out, as it's quite large ..
If I move to the "Summary" tab it does eventually give output which gives a sense of how large the routing table is:
IPv4 Unicast Summary:
BGP router identifier XXX.XXX.XXX.XXX, local AS number XXXX vrf-id 0
BGP table version 6980978
RIB entries 1297961, using 168 MiB of memory
Peers 1, using 14 KiB of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
XXX.XX.XX.XX 4 XXXX 1170526 1078483 0 0 0 1d02h15m 714537
Total number of neighbors 1
Thanks for all the work you do !
This seems to be not a problem specific to FRR but a frontend / backend problem in general as the gui seem to have run in a timeout when the result arrives. Anyway you probably don't want to view such a big routing table in the browser. Which does not solve the issue as the API requests by other clients will have the timeout issue as well.