In T915#73587, @Cheeze_It wrote:

One thing I did notice that did not work (and I think this would more or less be due to other options that can be enabled that FRR currently doesn't have yet) was that LSP pings from the Junipers directly connected to the Vyos VM failed but that's due to a specific corner case. FRR currently doesn't support explicit null in LDP, and Vyos doesn't have it implemented. However that shouldn't cause a problem in the current role that Vyos has. As an MPLS P Vyos works absolutely how it needs to. This seems to have a fix in FRR 7.4 as well per note "Ingress packets coming through broken LSP are no longer dropped." 

I would say that for what it's worth....I think we're good here. I think that the new additions are working as expected. So I am unsure if the ordered label allocation will be added later when things are moved to FRR 7.4, or if you'll put in that now @Viacheslav. But for what it is, MPLS support with LDP is verifiably working as it should be per the implementation in FRR 7.3.1. Thank you sir :)

Reopen to investigate, as unresolved ... cf. T5515, T3821

This does still need to be addressed in 1.4. Without a version string, the 2-to-3 migrator is adding the conntrack helpers to the default config.

https://github.com/vyos/vyatta-nat/commit/01b9a8598dabd391cc42da4c66d7a8067846b12b

This happened because the rule numbers only got increased in the XML implementation but not in the old Perl backend. This has been fixed.

In 1.3.0 the limitation remains

PR https://github.com/vyos/vyatta-op-vpn/pull/30

PR for "crux": https://github.com/vyos/vyos-1x/pull/1029

@Viacheslav we need to port this to 1.2 too

The real bug is it shouldn't allow port-range values as it is not implemented.
Or just add this feature T2798

Can we close it @Viacheslav?