Hi Quagga Users,
I have a crash bug to report with bgpd in quagga-1.0.20160315.
Until recently I had been running quagga-0.99.-something via its
FreeBSD port. In my bgpd.conf I define this route-map:
!
route-map BRICKWALL deny 1
!
I apply that route-map outbound on all bgp sessions -- my quagga box
serves just as a bgp collector, writing MRT table and update files, so
it should never send out any updates.
On many bgp peering sessions I also apply that same route-map inbound.
Under quagga-0.99 the resulting behavior was that the updates from
those peers would still be written in the updates files, but no routes
from this neighbor would be recorded in the table dump files.
But now upon upgrading to quagga-1.0.20160315, having any session
configured with that "neighbor ww.xx.yy.zz route-map BRICKWALL in"
causes bgpd to crash with:
BGP: Received signal 11 at 1462800687 (si_addr 0x0); aborting...
in thread bgp_read scheduled from bgp_packet.c:2472
I am also now getting many of the following messages logged:
2016/05/09 15:00:05 BGP: unknown afi/safi (0/0)
2016/05/09 15:00:05 BGP: ww.xx.yy.zz [Info] UPDATE with unsupported AFI/SAFI 0/0
Thank you.
Jay B.
PS: Does quagga-1.0.20160315-specific documentation exist online yet?
My searches all seem to take me to sites with docs for older
versions.
_______________________________________________
Quagga-users mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-users
