Hello all, With Fedora 43's bird 3.2.0-1 rpm installed on an x86_64 system, I'm seeing that several routes are being dropped from a full feed with the log messages below. Using Fedora's bird 3.1.4-1 does not seem to have any issues with the same BGP config and peer. Is this a known bug? What additional information can I provide to aid in the debugging? This is a backup transit connection that is not yet in full production use (but will be soon), so I can help with debugging and testing for now. Cheers, -ben Feb 4 14:42:49 router bird[24317]: upstream: Malformed AS_PATH attribute - AS_SET segment (1) at 14 Feb 4 14:42:49 router bird[24317]: upstream: Invalid route 76.165.0.0/16 withdrawn Feb 4 14:42:49 router bird[24317]: upstream: Malformed AS_PATH attribute - AS_SET segment (1) at 18 Feb 4 14:42:49 router bird[24317]: upstream: Invalid route 204.10.20.0/22 withdrawn Feb 4 14:42:49 router bird[24317]: upstream: Malformed AS_PATH attribute - AS_SET segment (1) at 14 Feb 4 14:42:49 router bird[24317]: upstream: Invalid route 213.186.96.0/19 withdrawn Feb 4 14:42:49 router bird[24317]: upstream: Invalid route 94.178.0.0/15 withdrawn Feb 4 14:42:49 router bird[24317]: upstream: Invalid route 37.52.0.0/14 withdrawn Feb 4 14:42:50 router bird[24317]: upstream: Malformed AS_PATH attribute - AS_SET segment (1) at 26 Feb 4 14:42:50 router bird[24317]: upstream: Invalid route 208.68.112.0/21 withdrawn Feb 4 14:42:50 router bird[24317]: upstream: Malformed AS_PATH attribute - AS_SET segment (1) at 18 Feb 4 14:42:50 router bird[24317]: upstream: Invalid route 147.92.87.0/24 withdrawn Feb 4 14:42:50 router bird[24317]: upstream: Invalid route 52.129.48.0/24 withdrawn Feb 4 14:42:50 router bird[24317]: upstream: Malformed AS_PATH attribute - AS_SET segment (1) at 18 Feb 4 14:42:50 router bird[24317]: upstream: Invalid route 15.20.64.0/18 withdrawn -- "Thought is the essence of where you are now."