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.

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.

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

@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

Is the IP address probably listed in

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

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

Tested on 1.4-rolling-202105170417 works correct. Propose to backport this to 1.3

There are two separate issues in this task: quoting of hw-id values (resolved in Sagitta/Equuleus); re-ordering of interfaces with respect to hw-id (Open).

@wsapplegate I create a PR for it https://github.com/vyos/vyos-1x/pull/847
Can you describe how to test/check it? I'm not familiar with that dns format. I tried zone with dot and without. Not sure how to check/test it.

My expectation is that you can configure MTU 1500 at a GRETAP device to ensure same mtu at bridge. This solves a lot of problems caused by mixing host with different MTU size.
Larger frames that exceed pmtu and have df = 1 are fragmented and send to the gretap endpoint. Thus, underlay MTU has no impact of the communitcation between two hosts that are bridged via GRETAP and communicate with MTU 1500.

@ernstjo what you mean by "too old"? I think it's fairly new (5.10):

I don't fully understand your scheme
What interrelation between arp and tcp policy?

I just tried that and it fails. We get

did you try
set protocols static table 1 route 0.0.0.0/0 interface 'eth1'

Iproute2 is too old and needs a newer version. So, we have to upgrade that package.

Even I also faced this error while upgrading the server from 1.2.7 to the latest rolling release.

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

PR for current https://github.com/vyos/vyos-1x/pull/844
PR for Equuleus https://github.com/vyos/vyatta-cfg-quagga/pull/78

Fix should be easy implement in create function with following add in:

Hi @ernstjo got an idea how we should do it?

Thanks for the hint.