vyos-1x.git/interface-definitions/include/constraint/interface-name.xml.i, branch fix/T8955-http-api-verify-tlsVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=fix%2FT8955-http-api-verify-tls2025-03-17T10:38:15+00:00T7252: 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:9db6b57e1516acfceec9a40a3e63c501f67d578dconfigverify: T5880: raise exception if interfaces sourced form dynamic interfaces2024-01-01T00:01:25+00:00Christian Breunigchristian@breunig.cc2023-12-31T10:21:14+00:00urn:sha1:5062f5d313548d6ebb9c07fee6b6d6be25b8f8f0
Interfaces matching the following regex (ppp|pppoe|sstpc|l2tp|ipoe)[0-9]+ can
not be used as source-interface for e.g. a tunnel.
The main reason is that these are dynamic interfaces which come and go from a
kernel point of view, thus it's not possible to bind an interface to them.
T5226: Fix typo in XML include headers2023-05-17T04:18:25+00:00Indrajit Raychaudhuriirc@indrajit.com2023-05-17T01:56:24+00:00urn:sha1:b6e780e05893c92e6bc36bdc452c31cf94673719xml: include building block file name should end with .i and not .in2023-04-01T11:14:30+00:00Christian Breunigchristian@breunig.cc2023-04-01T11:14:30+00:00urn:sha1:2265bb4dc27965da3dce7e3f476366b7d1e911f3