@syncer I assume this can be closed as fixed by upstream.

Seems like its either fixed or was a quirk in that specific version.

It was actually leaking routes.

Well, in an example like yours, using the network address as an IP is not really best practice even tho its works.
So, the validator forces the users to do it the right way, which is probably a good thing.

If I need to guess, it is just an issue that the BGP session gets configured before the route-maps

As I said, this happens with any config that includes route maps

Just as a minor update
FFR seems now to support SNMP for IPv6 BGP sessions

This works,
but if this is the new syntax the cli needs some cleanup.

@Viacheslav Works!

First of all, sorry for my late reply. I was on vacation and stayed away from IT for a bit ;)

Seems to be not fully functional

Ah, yea that is true.
They are enabled by default.

What do you mean by "enable by default"?
The issue is that, right now, we are unable to add these kind of ssh keys because the cli won't let you define the type.

My fault. Sorry.