Nullroutes not valid in FRR BGP on 23.7

[zandrr]

Hi Team,

Just wondering if anyone else on 23.7 has static nullroutes and whether they're able to propagate those in BGP?

For reference, have tried static redistribution as well as no distribution.
BGP network statements are there of course; also working in 23.1 with no redist defined.

Under System > Routes > Configuration, 10.x.0.0/16 set with next-hop Null4 - 127.0.0.1
Under System > Routes > Status, the static null is present with next-hop 127.0.0.1 and flags USB (UGSB in 23.1)

Notably, per the flags table on below page, the flag G for Gateway is missing.
https://docs.opnsense.org/manual/routes.html#flags

Under Routing > Diagnostics > BGP > IPv4 Routing Table, the above static null is present but shown as invalid.
Under Routing > Diagnostics > General, no route is present for the static null.

The subnet is to act as an aggregate for more specific subnets within the same domain, such as interfaces.
Those propagate properly as /24's

Edit: Sorry, I read the table wrong, originally I said 23.7 flags were UGS, but it's actually USB; missing G for Gateway. Modified above. 23.1 was correct as UGSB
Also added IPv6 nullroutes to my 23.7 instance and the behaviour/flags are identical as IPv4. 23.1 has correct behaviour with both families.

[mimugmail]

There was a change from frr7 to frr8 which is not found yet. You still can advertise routes via route maps

[zandrr]

Thank you for the quick reply. However that doesn't appear to be the case; the nullroute(s) are still shown as invalid and thus aren't candidates for advertisement. I attempted that just now with no change in outcome, with a reboot for good measure.

I'm theorising, but could it be due to whatever the difference is with the flags in the system table; ie. the missing gateway flag?

I am also aware of redist kernel routes and network import check disablement, but would like to refrain for now - though the former may not even matter if the route is seen as invalid.