I agree it would be nice to have the Cisco Auth functionality, however, the original author of opennhrp themselves recommend using FRR nhrpd instead where possible. It appears that most effort going forward will be put into FRR's nhrpd, and not the original opennhrp.

I have added a test which does not let you delete the default BGP instance when VRF bound instances exist.

This is causing a configtest failure on 1.4-rolling-202107301807 stemming from not cleaning up after bgp-evpn-l3vpn-pe-router ("Cannot delete default BGP instance. Dependent VRF instances exist"):

I already backported it, but forgot to push. Will be part of the next 1.3 ISO/RC

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

@Viacheslav Hi, I saw it was fixed in current branch. Is there a plan to backport the fix to 1.3?

@kroy Can you re-check it with your environment? I can't reproduce it in 1.3.0-rc5.

@ciprian.craciun

On VyOS 1.2-rolling-201910180117, setting ip source-validation loose seems to have the same outcome as setting it to disable, i.e. results in rp_filter = 0.

What do you expect to see here?

Fixed in T2745

PR for 1.3 https://github.com/vyos/vyos-1x/pull/950

Using timeouts is a pretty bad idea as they vary on the host CPU or utilisation of a hypervisor.

it should be timeout ~1.8 sec between adding ipv6 address and create l2tp interface

Closing as invalid as the error was towards aarch64 which is yet not supported by VyOS.

I think NHRP Cisco Auth is still missing: https://github.com/FRRouting/frr/blob/master/nhrpd/nhrp_peer.c#L1212

@c-po @Viacheslav
Further news on this topic - FRR 8.0 released yesterday (7/29) which includes the aforementioned nhrpd multicast improvements, among a lot of other nice things:

By default, FRR uses all neighbors in afi ipv4.
This behavior can be disabled with:

Drivers for RTL8111 and RTL8168 are build into the kernel.

Large community format:

"1:2:3"
"1:2:3 5:6:7"
"4123456789:4123456780:4123456788"
"^5:.*:7$"

As I see it's already fixed:

vyos@r4-1.3# set protocols bgp 64512 neighbor 192.168.5.5 local-as 64513
[edit]
vyos@r4-1.3# set protocols bgp 64512 neighbor 192.168.5.5 remote-as 64513
[edit]
vyos@r4-1.3# commit
[ protocols bgp 64512 neighbor 192.168.5.5 local-as 64513 ]
local-as: 64513 and remote-as: 64513 can't be the same

The original issue with the name ( type "u32") was solved.
I'll create a separate task for comm-list bug that can't be used without the "delete" option. (T3712)

Config to reproduce in 1.4

set interfaces ethernet eth1 address 2001:db8::2/64
set interfaces l2tpv3 l2tpeth1010 address '192.168.37.2/27'
set interfaces l2tpv3 l2tpeth1010 encapsulation 'ip'
set interfaces l2tpv3 l2tpeth1010 source-address 2001:db8::2
set interfaces l2tpv3 l2tpeth1010 peer-session-id '100'
set interfaces l2tpv3 l2tpeth1010 peer-tunnel-id '200'
set interfaces l2tpv3 l2tpeth1010 remote 2001:db8::1
set interfaces l2tpv3 l2tpeth1010 session-id '100'
set interfaces l2tpv3 l2tpeth1010 tunnel-id '200'

commit

Traceback (most recent call last):
  File "/usr/libexec/vyos/conf_mode/interfaces-l2tpv3.py", line 105, in <module>
    apply(c)
  File "/usr/libexec/vyos/conf_mode/interfaces-l2tpv3.py", line 94, in apply
    l = L2TPv3If(**l2tpv3)
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/interface.py", line 264, in __init__
    self._create()
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/l2tpv3.py", line 46, in _create
    self._cmd(cmd.format(**self.config))
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/control.py", line 51, in _cmd
    return cmd(command, self.debug)
  File "/usr/lib/python3/dist-packages/vyos/util.py", line 161, in cmd
    raise OSError(code, feedback)
FileNotFoundError: [Errno 2] failed to run command: ip l2tp add tunnel tunnel_id 200 peer_tunnel_id 200 udp_sport 5000 udp_dport 5000 encap ip local 2001:db8::2 remote 2001:db8::1
returned: 
exit code: 2

PR for current https://github.com/vyos/vyos-1x/pull/949

They should be disabled by default, but there must be the ability to re-enable OIDs back from CLI.

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

As requested, checked in 1.3.0-rc and it shows the destination translations with basic configuration.

Since you can set the pool and gateway address by hand now, it's not impossible to use that subnet anymore.

PR for 1.3 https://github.com/vyos/vyatta-cfg-quagga/pull/86
add option "solo" for neighbor.