veeos-1x.git/interface-definitions/include/interface, branch circinusVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos-contrib/veeos-1x.git)
https://git.amelek.net/vyos-contrib/veeos-1x.git/atom?h=circinus2024-05-11T12:12:31+00:00ethernet: T6306: add support for EVPN MH uplink/core tracking2024-05-11T12:12:31+00:00Christian Breunigchristian@breunig.cc2024-05-11T12:12:31+00:00urn:sha1:5565f27d15c5e7378e94aae8db8a894a12e25d7b
When all the underlay links go down the PE no longer has access to the VxLAN
+overlay.
To prevent blackholing of traffic the server/ES links are protodowned on the PE.
A link can be setup for uplink tracking via the following configuration:
set interfaces ethernet eth0 evpn uplink
T6258: Add sysctl base-reachable-time for IPv62024-04-25T08:23:14+00:00Viacheslav Hletenkov.gletenko@vyos.io2024-04-25T08:23:14+00:00urn:sha1:0bf4b570fe2d239b9fbabd3ae801ad3f04a06bde
Add abiilty to change `base_reachable_time_ms` option
/proc/sys/net/ipv6/neigh/{ifname}/base_reachable_time_ms
xml: T5862: drop defaultValue from mtu-68-16000.xml.i - use individual values2024-04-06T10:10:57+00:00Christian Breunigchristian@breunig.cc2024-04-06T10:10:57+00:00urn:sha1:e86761fa1307596c721c3ddf3a61d263e8f5177b
In order to lower the Ethernet default MTU we need to drop the common
defaultValue from the XML mtu-68-16000.xml.i building block. Per interface
default MTU is later overloaded by XML.
xml: T5738: extend VRF building blocks with common constraint definition2024-04-01T18:27:24+00:00Christian Breunigchristian@breunig.cc2024-04-01T18:27:24+00:00urn:sha1:32d6a693de99021d2cd44fb4235e929caf7b4a6dbridge: T6125: support 802.1ad (ethertype 0x88a8) VLAN filtering2024-03-20T20:25:43+00:00Christian Breunigchristian@breunig.cc2024-03-20T20:25:43+00:00urn:sha1:9c9b1febff6863ccd3632a04d9e307909b3efe7a
Linux bridge uses EtherType 0x8100 by default. In some scenarios, an EtherType
value of 0x88A8 is required.
Reusing CLI command from VIF-S (QinQ) interfaces:
set interfaces bridge br0 protocol 802.1ad
dhcp: T5846: Ensure DUID regex range is bound2023-12-21T09:26:26+00:00Indrajit Raychaudhuriirc@indrajit.com2023-12-21T09:18:45+00:00urn:sha1:551f06218755076cde588c848c01ce5ca1bf5e6b
The DUID regex was missing a lower bound, which could cause it not to
match when it should.
We have to specify the lower bound explicitly as 0 to keep the regex
behavior similar to that in Python (in Python, omitting the lower bound
is equivalent to specifying 0).
dhcp: T5846: Fix include path2023-12-21T07:59:20+00:00Indrajit Raychaudhuriirc@indrajit.com2023-12-21T07:59:20+00:00urn:sha1:5768bc2d56cc8aabd8d276a2afc30608c1bc9838dhcp: T5846: Refactor and simplify DUID definition2023-12-21T07:49:58+00:00Indrajit Raychaudhuriirc@indrajit.com2023-12-20T21:34:22+00:00urn:sha1:51e7832fc5c88f9956b26157a80947bad4495a4e
Refactor DUID XML definition in conf-mode to be reusable. Additionally, remove
explicit call to a separate validator `ipv6-duid` and inline the regex into the
XML definition.
dhcp-client: T5760: add CLI option to pass user-class parameter2023-11-19T20:47:31+00:00Christian Breunigchristian@breunig.cc2023-11-19T20:47:31+00:00urn:sha1:260645d0c6ff078cc89601f3a586195902f9c18e
Example:
set interfaces ethernet eth0 dhcp-options user-class VyOS
or
set interfaces ethernet eth0 dhcp-options user-class 56:79:4f:53
dhcp-client: T5760: add constraints for dhclient string options2023-11-19T20:43:15+00:00Christian Breunigchristian@breunig.cc2023-11-19T20:43:15+00:00urn:sha1:bed1cd01904ef89b5d31bd47de0f230214900f16
The string data type specifies either an NVT ASCII string enclosed in double
quotes, or a series of octets specified in hexadecimal, separated by colons.
For example:
set interfaces ethernet eth0 dhcp-options client-id CLIENT-FOO
or
set interfaces ethernet eth0 dhcp-options client-id 43:4c:49:45:54:2d:46:4f:4f
As of now there was no input validation performed.