It seems fixed for rolling release 1.4 because soft has been moved to FRR7.5.1
Of course it is not fixed for rolling release 1.3 (and as I understand won't be) due to FRR7.3.1

@Viacheslav, tested on VyOS 1.3-beta-202102270443. It works

ok, I'll do it

As I see in VyOS 1.4-rolling-202102040221 the OSPF interface configuration is already under protocol section. Looks good.
So next up are ospfv3 and rip.

Tested on VyOS 1.4-rolling-202101261956. Works fine

Looks good. But maybe it is reasonable to change argument start-suppress-time to start-suppress because it is not a time, but penalty points

Quoted Text

If I use

In T3207#84000, @Viacheslav wrote:

@craterman It the same? https://github.com/FRRouting/frr/issues/739

I have just re-checked. It works fine for everyone LSAs type.
summary and asbr-summary also works fine

It works fine for show ip ospf database router x.x.x.x and show ip ospf database network x.x.x.x
It does not work for show ip ospf database <summary|asbr-summary|external> x.x.x.x
The output of these commands is empty.

Ok. I'll do it

FRR value for the same command

Can you add this commands

In T915#73396, @Viacheslav wrote:

@craterman Can you share an example of a configuration or how it looks in the frr? So that I can reproduce this in a test lab.
And share additional show the output and what you expect to see.

@Viacheslav what about abnormal label allocation behavior which I wrote earlier? Was it fixed?

I found abnormal behavior during label allocation. As I wrote above VyOS generate label for all prefixes presented in routing table. But when we have for example 5 connected routes (four /24 and one /32) on Egress LSR and we start mpls VyOS allocates labels for all routes and neighbor (downstream LSR) receives label=3 (implicit null). But if we have 2 connected routes (one /24 and one /32) then we start mpls, Egress LSR allocates labels for all routes (two in this case), but if we add on Egress LSR one, two or more new connected routes VyOS does not allocate label=3 for this routes and does not send Label Mapping Message to its neighbors for FECs related to new added routes. The software version is 1.3-rolling-202005160117

Hi, everyone.
As I understood from my lab VyOS generate label in cisco fashion (for all presented prefixes in routing table). And it is good as for me. But I think it is necessary to be able to filter the FEC for which labels will be generated (for example only for /32 routes, or only for particular routes).