Fixed in the latest rolling

sever@r11:~$ show vrrp 
VRRP is not running
sever@r11:~$ show vrrp detail 
VRRP is not running
sever@r11:~$ show vrrp statistics 
VRRP is not running
sever@r11:~$

Fixed in latest rolling

sever@r11-ansible# set interfaces ethernet eth3 description test
[edit]
sever@r11-ansible# commit
[ interfaces ethernet eth3 ]
Interface ethernet eth3 does not exist

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

@Dmitry Looks good.

These 2 PR are needed for new xml format

@dmbaturin to enable it by default we need rewrite BGP to new python/XML format and use template, where this feature will be by default because FRR by default doesn't check routes in the RIB.

@c-po Shure, config attached to task https://phabricator.vyos.net/T1315 (left-r1, left-r2, right-r1, right-r2)
Section "Autostart commands"

If you comment out this line, arp after reboot doesn't lose.

Latest rolling.

sever@vyos-1.3:~$ poweroff in 5
Poweroff is scheduled 2020-04-06 12:02:52
sever@vyos-1.3:~$

I think we can close this task

@dongjunbo Can you send an example?

Commands were rewritten to:

$ reset ip igmp interfaces
$ reset ip multicast route

@c-po the second part of task.
An example, we can't execute analog of this command in the VyOS syntax:

sudo ip link add vxlan11 type vxlan id 11 dstport 8472 local 22.22.22.1 nolearning

We need to add commands for vxlan:

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

To track similar https://github.com/FRRouting/frr/issues/4471

For the ECMP it's necessary that as-path length, weight, localpref, med, etc were the same.
Only, in that case, more than one eq route will be installed in the routing table.

@Merijn If you don't use ECMP, only one best route will be installed in routing table.
In your case, the best path via 20562 6830 198611 with localpref 140.
In the bgp table, all prefixes will be present.
It's a general BGP Best Path Selection Algorithm.
The same is true for ipv4.

How about parallel loops?
https://metacpan.org/pod/Parallel::Loops

Why we can't enable this feature by default.
A lot of customers don't use it, and announce their BGP prefix with "network x.x.x.x"
Imagine if you don't have configuration "redistribute connected" or "redistribute static".
If this feature enabled by default in the new release - you update the VyOS, reboot it and lose access to the router.
Because there are no routes /24 as directly connected. Also, you can use more-spec prefixes (/28 /29 /25), not /24.
Prefixes will disappear from the announcements ISPs.
It's impossible to figure out quickly what happened.

set nat destination rule 102 destination port '80'
set nat destination rule 102 inbound-interface 'eth2'
set nat destination rule 102 protocol 'tcp'
set nat destination rule 102 translation address '192.168.68.101'
set nat destination rule 102 translation port '80'

How will internal clients gain access to external sites if we forward all packets with dst port 80?
This is just one example.

This check interferes with the commit.
https://github.com/vyos/vyos-1x/blob/current/src/conf_mode/interfaces-vxlan.py#L163

I created a network diagram for "l2vpn evpn" implementation.
I used this instruction vxlan-bgp-vpn