You can't/don't need to set local-as for neighbor [ if neighbor local as == your global asn ]
Can you send a code error?

I wonder if this used to work in the past?

@maznu @Merijn Can you test the latest rolling 1.4 release?
It should be fixed.
You can kill ripd/ripng/ospfd/bgpd/isisd daemons or allow it for watchfrr.

Turns out this is not a VyOS limitation but is a Linux Kernel/iproute2 limitation.

Fixed via https://github.com/vyos/vyatta-cfg-firewall/pull/21

This bug also persists in VyOS 1.2.7

The same with "policy" /usr/libexec/vyos/tests/config/dialup-router-medium-vpn

To reproduce it add firewall and attach it to interface

Usually on delete, the firewall should be detached from the interface first as the logic should go from the highest priority to the lowest one.

It is a priority for configurations
When the system load, the firewall should have configuration, and after configuration is applied to the interface.
So I think we can't delete it in one commit, it tried to delete the firewall before detaching the firewall from the interface.

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

We can do some workaround for that level,

It seems that "call" doesn't react to env.

'VYATTA_EDIT_LEVEL': '/system/login'

https://github.com/vyos/vyos-1x/blob/810f4700acc9816178dc9a7f5f555bbde71a141d/src/conf_mode/system-login.py#L161

PR https://github.com/vyos/vyatta-cfg/pull/34
PR https://github.com/vyos/vyos-1x/pull/798

This can be reproduced with the following config on 1.4

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

Chown for saved configuration file should be frr:frr

Hmm, where should the documentation for "gretap" be now? I checked the following and it's still missing:

Parent task: https://phabricator.vyos.net/T3356

Expect

vyos@r5-roll# set protocols ospf redistribute isis 
Possible completions:
   metric       OSPF default metric
   metric-type  OSPF metric type for default routes (default: 2)
   route-map    Route map reference

Update: It turns out the md5sum.txt files are put there by Debian's Live Build. Checksums are added on lb binary_checksums step of the build, which defaults to MD5 if no variable is provided to tell it otherwise. As Daniil suggested, we can put a second checksum step with SHA256 variable to produce both checksums, then check for sha256sum.txt files on new images. This way, old update scripts can still find an md5sum.txt in images.

The workaround for save command does not seem to work, have you tried for commit-archive option ?

Turns out vyatta-remote-copy.pl has been broken for a while. It fails to exchange encryption keys when it tries to establish an SSH connection (for SFTP or SCP), possibly because of the old libssh it relies on.

I tried using ssh-keyscan and it's still didn't work for me and it still having the same curl error 60

Looks good on 1.3-rolling-202103280642:

Looks good on 1.3-rolling-202103280642:

Looks good on 1.3-rolling-202103280642: