vyos-1x.git/src/validators/vrf-name, branch vyos/1.4dev0 VyOS command definitions, scripts, and utilities (mirror of https://github.com/marekm72/vyos-1x.git) https://git.amelek.net/marekm72/vyos-1x.git/atom?h=vyos%2F1.4dev0 2020-05-30T09:21:15+00:00 vrf: T2530: instance name must be 15 characters or less 2020-05-30T09:21:15+00:00 Christian Poessinger christian@poessinger.com 2020-05-30T09:21:15+00:00 urn:sha1:8f1f0e9da6967319c044d410cc10f144659cc0ef validator: T2417: try to make the code clearer 2020-05-06T15:45:44+00:00 Thomas Mangin thomas.mangin@exa.net.uk 2020-05-06T15:45:44+00:00 urn:sha1:3639a5610b590a64d6d56bee81dddd252994cfe5 vrf: T31: Allow vrf name to look more like interface name 2020-04-03T12:53:38+00:00 Runar Borge runar@borge.nu 2020-04-03T12:53:38+00:00 urn:sha1:68b4090f3ee1e313ae6beb590608f257687e03f2 Fix the regex to allow vrf instances like "eth0vrf" but not to allow "eth0" vrf: T31: name of isntance is not allowed to mimic an interface name 2020-04-03T12:23:02+00:00 Christian Poessinger christian@poessinger.com 2020-04-03T12:23:00+00:00 urn:sha1:a509d5ee53f42912d9722c9aae890e2ca6967680 Every VRF that's created is not allowed to be named like any interface that can be active on the system. This includes eth, lan, br, dum, lo .... In theoriy this would work but as soon as such a regular interface is created things will go sideways rather quick thus we limit the namespace which can be used to create a VRF. Appending an interface name is still possible like coolvrf-eth0.