- User Since
- Aug 3 2017, 1:55 PM (196 w, 1 d)
19: l2tpeth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master foo state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 7e:0a:f4:5c:ef:8c brd ff:ff:ff:ff:ff:ff alias L2 VPN Tunnel
master foo <- foo is the VRF name
@Viacheslav it must be added in the proper order and contexts need to be entered - exited appropriately
It is implemented in VyOS 1.4
Wed, May 5
frr-reload output: 116 Error description: Interface tun0 has MTU 1473, minimum MTU for the area is 1497
Tue, May 4
I have boiled down your commands to the following:
Can't reproduce on VyOS 1.3.0-rc4, even after a reboot I get a single ipv6 route ::/0 2a01:9820:5::10 table 100 line
Sun, May 2
Sat, May 1
I see no connected network in your FIB for 2001:19f0:ffff::1 I guess that's the reason.
Fri, Apr 30
This requires a fix to https://github.com/FRRouting/frr/issues/8403 first
Tue, Apr 27
Mon, Apr 26
Sun, Apr 25
Retested this with VyOS 1.3.0-rc3 and the bahavior is the same.
Turns out the example config has a typo. Issue is reproducible by:
Analysing the provided configuration file has shown that this is unrelated to the change. The supplied configuration used a non existing route-map/prefix list on the CLI. As this is now properly validated for existence the error was triggered.
How were you be able to set this on the CLI?
Sat, Apr 24
Thu, Apr 22
This is a bug which is introduced by the rewrite of policy from old node.def files to XML and Python.
Tue, Apr 20
Sun, Apr 18
Sat, Apr 17
Latest rolling runs 5.10.30 - patch is in there, please verify
That should be rewritten in the same style as the interface stuff rendering the appropriate commands (https://github.com/vyos/vyos-documentation/blob/master/docs/_include/interface-disable.txt)
Can you please re-test this with VyOS 1.4?