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

@fernando, this was something I was looking into adding but it'll be in 1.4 One day.....I hope soonish....maybe in a few months.

I can confirm that beheivor , settings on FRR :

Before that configuration , we should add the mpls settings in our cli-vyos , it is an example:

Link to repo there
https://github.com/vyos/vyos-build/blob/06dc2469cc4c42a579a44e985d8099fc399f9c7b/data/defaults.json#L12

I had a go at implementing this myself. First time ever for vyos development, using git or even python. Please be gentle!
https://github.com/vyos/vyos-1x/pull/851

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

Function get_interface_config itself not added. Needs to add it for 1.3.

vyos@r4-1.3:~$ show int
Traceback (most recent call last):
  File "/usr/libexec/vyos/op_mode/show_interfaces.py", line 26, in <module>
    from vyos.ifconfig import Section
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/__init__.py", line 18, in <module>
    from vyos.ifconfig.interface import Interface
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/interface.py", line 39, in <module>
    from vyos.util import get_interface_config
ImportError: cannot import name 'get_interface_config' from 'vyos.util' (/usr/lib/python3/dist-packages/vyos/util.py)
vyos@r4-1.3:~$

Fixed VyOS 1.4-rolling-202105192127

set protocols ospfv3 area 23 area-type stub
set protocols ospfv3 area 25 area-type stub no-summary

It seems other commands like save, copy which depend on scp and tftp are also broken.

@olofl Can you re-check it? Or can we close it?

ddclient does currently not release anymore, see https://github.com/ddclient/ddclient/issues/302 , some of the integrations are already outdated in the current release like cloudflare which does not support API tokens - only the unprotected global key which grants access to everything.

I just want to add that my ISP is dropping dual stack in next few months and at the end of 2021 all users will only have IPV6 networking capabilities.
For thoose who still require IPV4 traffic it will be "tunneled" via MAP-T.

As I understand it a part of zebra, not specified to any protocol.
Maybe I'm wrong and we don't need it.

PR https://github.com/vyos/vyatta-cfg-system/pull/148

Why move the protocol specific route map to a new CLI node? This makes no sense to me.

A similar problem, only for ipv4 https://phabricator.vyos.net/T1053
As we can see ipv6 address before normalization without prefix
DEBUG: 2001:db8::191 before normalize
https://github.com/vyos/vyatta-cfg-system/blob/165e56e88763c40f13e6ef77f5df1c888fdfb899/scripts/vyatta-address#L38

@c-po Nope,

vyos@r6-roll:~$ sudo ip -d link show | grep vtun -A 5
5: vtun1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
    link/none  promiscuity 0 minmtu 68 maxmtu 65535 
    tun type tun pi off vnet_hdr off persist off addrgenmode none numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535

@c-po
I propose to add "set routing-options x.x.x.x"
And also migrate protocols xxx route-map

set protocols bgp 65001 route-map RMAP
set protocols bgp|ospf|isis route-map RMAP

Does not reproducing on eve-ng.

Confirmed on VyOS 1.3-rolling-202105011026

This is still reproducible in the FRR master branch, so I've filed an issue: https://github.com/FRRouting/frr/issues/8695

Is the IP address probably listed in

you have an idea how the VyOS CLI commands should look like?