vyos-1x.git/interface-definitions/include/constraint, branch rollingVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling2026-08-17T16:54:14+00:00xml: T9179: reject VRF names in interface-name constraint2026-08-17T16:54:14+00:00Christian Breunigchristian@breunig.cc2026-08-11T18:32:52+00:00urn:sha1:a57dd68ed40ec77ba0a0fc5a2c641fe344fc0570
Tab completion for source-interface and other interface leafNodes already
excludes VRF names, but the shared interface-name constraint accepted them
anyway: an existing VRF is a real net device, so it passed the file-path
existence check even though it failed the interface-name regex.
Replace the file-path validator with a new interface-exists validator that
requires the value to both exist under /sys/class/net and not be a VRF.
The regex-match fallback is unchanged, so dynamic interfaces (e.g. pppoe)
referenced before they exist still validate correctly.
T8923: normalize "can not" to "cannot"2026-06-16T18:24:44+00:00Christian Breunigchristian@breunig.cc2026-06-16T18:24:44+00:00urn:sha1:fa853ed8f25b5b9bf396d6e819b2c6259e7f5f42
Replace two-word "can not" / "Can not" with "cannot" across comments,
ConfigError messages, CLI help text, and op-mode output.
Standard SNMP MIB files under mibs/ are left unchanged.
vrf: T8320: improve constraint error message for given name2026-02-26T21:05:24+00:00Christian Breunigchristian@breunig.cc2026-02-26T20:57:12+00:00urn:sha1:08e5d166c4afca2476f88f483be28a65d64d9e92T7849: Extend regex for constraint wildcard interfaces2025-10-31T13:33:13+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-10-31T13:33:13+00:00urn:sha1:7f6be577b88949f3d568ad6761c6572d40bac421
Allow ipoe*, vpp and pod interfaceds
Merge pull request #4402 from c-po/wireguard-key-T72462025-03-20T21:05:04+00:00Christian Breunigchristian@breunig.cc2025-03-20T21:05:04+00:00urn:sha1:f2d427bd6b2a2a39d6eb086dd0abdfa099b78cdd
wireguard: T7246: verify Base64 encoded 32byte boundary on keyswireguard: T7246: verify Base64 encoded 32byte boundary on keys2025-03-20T21:00:10+00:00Christian Breunigchristian@breunig.cc2025-03-20T21:00:10+00:00urn:sha1:8021bdd62e4142caf4a5e82000c8ca3da99fcae4
Not 31 bytes or 33 bytes, but exactly 32. This matters, because 32 does not
divide evenly by .75, so there's a padding character and the penultimate
character does not include the whole base64 alphabet.
Extend the base64 validator with an optional argument to define the length
to match of the decrypted Base64 encoded string.
Source: https://lists.zx2c4.com/pipermail/wireguard/2020-December/006222.html
T7252: Allow vpptun and vpptap for constraint validator2025-03-17T10:38:15+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-03-17T10:38:15+00:00urn:sha1:f8bc27991374c7fa013dac56fef2ff8c1379d69a
It fixes cases whey we want to use VPP kernel interfaces for OSPF
But VPP kernel interface is not exists on this step
set vpp interfaces loopback lo0 kernel-interface 'vpptun0'
set protocols ospf interface vpptun0 area '0'
Incorrect path /sys/class/net/vpptun0: no such file or directory
firewall: T7177: update interface-name.xml.i constraint and smoketest to support pod interfaces from containers2025-02-19T16:30:14+00:00Markmark.hayes0338@gmail.com2025-02-19T16:30:14+00:00urn:sha1:9db6b57e1516acfceec9a40a3e63c501f67d578dxml: T7161: provide re-usable building block for alternative routing tables2025-02-13T16:00:01+00:00Christian Breunigchristian@breunig.cc2025-02-13T16:00:01+00:00urn:sha1:8f6246da654704c6bff3dbdb366b57f11253ba9eT6214: T6213: change constraint <alpha-numeric-hyphen-underscore-dot.xml.i> in order to not allow string starting with dot character; use such constraint in firewall group definitions.2024-04-09T16:50:36+00:00Nicolas Fortnicolasfort1988@gmail.com2024-04-09T11:02:58+00:00urn:sha1:c455a1f71674300b8a74863ddfe6e551fe8fd252