@tuxis-ie
FRR doesn't allow you to set that value. It's not a bug of VyOS.
In commands description allowed values (0-4294967295)

r12-1.2.6(config)# route-map FOO permit 100
r12-1.2.6(config-route-map)# set local-preference 
  (0-4294967295)  Preference value
r12-1.2.6(config-route-map)# set local-preference 
  (0-4294967295)  Preference value
r12-1.2.6(config-route-map)# set local-preference -10
% Unknown command: set local-preference -10

@c-po Sorry for the late notice on this -- One of the 2020 releases sort-of fixed the issue in my environment. I'm not seeing crashes on the OSPF daemon but I have seen it on occasion with OSPF6 like @maznu mentioned.

VyOS packages are currently beeing regenerated with a fix for this.

PR https://github.com/vyos/vyos-1x/pull/670

As far as i know all our other "disable" commands starts wirh "disable-"

Some additional information: Here's what happens after upgrading (the version I was running predated ip6gre support, so that was my bad)...
I try to configure the tunnel interface and get the following:

I'd personally recommend "pmtu-discovery-disable", but either would be fine.

PR https://github.com/vyos/vyos-1x/pull/669

Proposed CLI

set interfaces tunnel tun0 parameters ip disable-pmtu-discovery

@Dmitry Thank you for correcting. I may have got it wrong

@victorhooi try to build a stable version for yourself, on the stable version is defined by udev rules https://github.com/vyos/vyos-build/blob/crux/tools/vendors_udev/64-vyos-SAF51015I-net.rules
Or you can use way with binding hw-id as noticed @jack9603301 (but not mac)

PR https://github.com/vyos/vyatta-cfg-quagga/pull/61

@c-po https://github.com/vyos/vyos-1x/pull/668

@c-po has also tested an iso from the above branches, notably testing a vyatta-wanloadbalance configuration. It had been presumed that the listed dependency of vyatta-wanloadbalance on vyatta-config-migrate was a legacy error, as there were no explicit dependencies, but it required a sanity check. I will merge via PR's, in order to better track the changes over the 3 required packages.

Put PR for segment routing addition:

Thanks for that. However, encapsulation ip6gre is nowhere to be found in a documentation search on readthedocs.
As to why it got tased VyOS Manager, the tag was automatically inserted when I created the issue and no alternatives were offered by the UI at my userlevel.
Apologies for my ignorance, I am relatively new to VyOS though quite experienced with IPv6 and with routing in general.
Respectfully, I suggest reopening this ticket and recategorizing it to documentation appropriately so as to get the documents brought up to speed with the implementation.

@maznu I've also been looking at switch to Mellanox cards after my experience with Intel. It's not as if this is a mass consumer product with end-users that don't really know what they're doing. It's a product that's most likely supported by IT/network staff that get to influence purchasing decisions for equipment like this.

@drac, while yes that is an option I am unsure which VyOS should as a software package should use.

Or you could implement import and export policies for BGP, which is what I did.
We already had export policies but it is good practice to have both.

So, this option can be disabled here per the FRR manual:

Just tried this with 7.4 yeah, issue persists. Using 7.3 which is also in the LTS version for so long...

This is due to RFC 8212, which was added on FRR 7.4. Please see here...

Reverting back to 7.4 series until those are resolved.

This infact hit me, too which is super annoying and could kill your entire AS.

Here are my conclusions about the last week's shenanigans.