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 instrucation vxlan-bgp-vpn

We don't can do it as default behavior.
Frr documentation, frr has profiles

@jestabro Create it please.

@jestabro I fixed commit to

Add show commands for multicast/igmp/pim

Template VyOS for Zabbix 4.x version with SNMPv2 checks.
No need to install any additional programs.

Can we add checks?

@dmbaturin Can you put it back on the rolling? We periodically have many appeals on this issue.

Max positive value for Integer32 = 2147483647
Max negative value = -2147483648

Template for zabbix-server on base zabbix-agent checks (without SNMP).
Dynamically creates items and some graphs for:

• CPU
• Memory
• Cpu Cores
• Interfaces rate bps/pps
• Interfaces drops/errors
• State some services (OpenVPN/VRRP)
• Conntrack entries (used for nat)

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

We have this feature but with wrong logic.
https://github.com/vyos/vyatta-cfg-quagga/blob/current/scripts/bgp/vyatta-bgp.pl#L723

@syncer One thing to consider. If dynamic interfaces are used and there are several thousand of them (ipoe/ppp), this will kill the server, if we try to pull this data.

I can confirm this bug also with VyOS 1.2.4

PR # 219

Thanks @runar . It worked for me.
Libvirtd +6 interfaces.

Ability to use Local PBR ref T439

To install the zabbix-agent (for rolling) you need:

VyOS on 'Buster' don't have flag "-I" for select specific interface for command ping.

root@vyos:/home/vyos#  dpkg-query -l | grep ping
ii  inetutils-ping                    2:1.9.4-7                                    amd64        ICMP echo tool
ii  iputils-arping                    3:20180629-2                                 amd64        Tool to send ICMP echo requests to an ARP address

I’ll mark it here for the future. "ldpd 100% CPU utilization"
ref_cpu_utilization

SNMP with VRRP work

# snmpwalk -v2c -c public 10.0.0.1  VRRP-MIB:vrrpOperations
VRRP-MIB::vrrpNodeVersion.0 = INTEGER: 2
VRRP-MIB::vrrpNotificationCntl.0 = INTEGER: disabled(2)
VRRP-MIB::vrrpOperVrId.3.10 = INTEGER: 10
VRRP-MIB::vrrpOperVirtualMacAddr.3.10 = STRING: 52:54:0:1d:4:4e
VRRP-MIB::vrrpOperState.3.10 = INTEGER: backup(2)
VRRP-MIB::vrrpOperAdminState.3.10 = INTEGER: up(1)
VRRP-MIB::vrrpOperPriority.3.10 = INTEGER: 50
VRRP-MIB::vrrpOperIpAddrCount.3.10 = INTEGER: 1
VRRP-MIB::vrrpOperMasterIpAddr.3.10 = IpAddress: 10.0.0.2
VRRP-MIB::vrrpOperPrimaryIpAddr.3.10 = IpAddress: 10.0.0.1
VRRP-MIB::vrrpOperAuthType.3.10 = INTEGER: noAuthentication(1)
VRRP-MIB::vrrpOperAdvertisementInterval.3.10 = INTEGER: 1 seconds
VRRP-MIB::vrrpOperPreemptMode.3.10 = INTEGER: true(1)
VRRP-MIB::vrrpOperVirtualRouterUpTime.3.10 = Timeticks: (2) 0:00:00.02
VRRP-MIB::vrrpOperProtocol.3.10 = INTEGER: ip(1)
VRRP-MIB::vrrpOperRowStatus.3.10 = INTEGER: active(1)
VRRP-MIB::vrrpAssoIpAddr.3.10.10.0.0.254 = IpAddress: 10.0.0.254
VRRP-MIB::vrrpAssoIpAddrRowStatus.3.10.10.0.0.254 = INTEGER: active(1)

@bbs2web you can try use sysctl params from set

Xml for interface-definitions for commands set protocol mpls
https://github.com/sever-sever/vyos-1x/blob/current/interface-definitions/protocols-mpls.xml.in

I think we can close this task.
Nothing like that has happened in the last few months.

@elbuit

vyos@mpls# sudo nft list table nat
table ip nat {
	chain PREROUTING {
		type nat hook prerouting priority -100; policy accept;
		counter packets 0 bytes 0 jump VYATTA_PRE_DNAT_HOOK
	}

@elbuit
Rolling is support nft now.

vyos@mpls:~$ sudo nft -v
nftables v0.9.0 (Fearless Fosdick)

PR https://github.com/vyos/vyos-1x/pull/203
Adding commands for show mpls

Service custom don't support 2 ddns entries now.
It overwrite login/pass to (login02) for each custom service

First tests for MPLS.
Latest rolling releases is supported it.

Update
The problem was resolved by manually removing the interfaces from the file /config/config.boot (section flow-accounting)

@bbabich If router A and router B connected via iBGP you need use nexthop-self

Hi @bbabich
How we can reproduce this bug?
I tested with 55 bgp-sessions. Each with its own unique filter. All filters applied as needed.
Without filters I announced 111 routes.
With filters per session I export 1 route to each peer.

@wcktklwn Can you provide vyos config for dynamic service and config ddclient.conf
Which lines do you add manually?

It fixed in 1.3 version. With "next-hop-interface "

In the latest VyOS 1.3-rolling-201912261106 all work fine.

MPLS requires Linux Kernel 4.5 or higher (LDPcan be built, but may have limited use without MPLS).
Ref https://readthedocs.org/projects/frrouting-developers-guide/downloads/pdf/latest/

PR https://github.com/vyos/vyatta-op/pull/32
Fix "show monitoring" command.

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

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

PR https://github.com/vyos/vyatta-op-quagga/pull/4/commits/7659873869d92c9ec6b363db7e06d2ba5b41e5f6
New syntax for commands "monitor protocol bgp enable", "monitor protocol bgp disable"

It looks like the VyOS has the old command syntax.

Similar bug with FRR ref https://github.com/FRRouting/frr/pull/5450

Hi @MrXermon
Can you describe how we can reproduce this bug?
Can you show share your configuration?

@c-po
I get other result.
After set from your example I see correct area
FRR

I check it in latest rolling releases and it work fine (ipv4 and ipv6).

In the VyOS 1.2-rolling-201912090217 and VyOS 1.3-rolling-201912090242 all work fine

Over the past 3 months of rolling releases, I haven't seen this problem in KVM with virtio.

@hagbard An inactive route in this case can be resolved using the command "ebgp-multihop 10".

In the latest rolling VyOS 1.3-rolling-201912090242 it work fine.
R1 advertise ipv6 routes with community 65001:666
R2 receives these routes.

Similar task https://phabricator.vyos.net/T1838

/opt/vyatta/sbin/vyatta-firewall.pl contains lines

Hi @systo
Can you describe step by step what you did not succeed?
The example below is just an example.

Confirm the problem on edit level.

I don't see this bug in the latest versions of the VyOS (VyOS 1.2-rolling-201912090217 and VyOS 1.3-rolling-201912090242).