vyos-1x.git/interface-definitions/interfaces_ethernet.xml.in, 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-tls2026-01-22T07:52:44+00:00ethtool: T7730: Add configuration coalesce for interface2026-01-22T07:52:44+00:00Oleksandr Kuchmystyio.kuchmystyi@vyos.io2025-12-25T13:48:03+00:00urn:sha1:f01ff15b7530053e18bb79cd529a84e3f15b294a
This change introduces CLI support for configuring network interface
interrupt coalescing parameters via `netlink`.
Note: Not all NIC drivers support interrupt coalescing. On unsupported interfaces,
`netlink` returns an error and the VyOS commit will fail.
interface: T4627: not every interface type supports IPv6 interface-identifiers2025-04-23T18:17:06+00:00Christian Breunigchristian@breunig.cc2025-04-23T18:14:56+00:00urn:sha1:d0a20884614e773b074c39cd496717440faa89c1
Turns out commit b124f0b3b ("interface: T4627: support IPv6 Interface
Identifier (token) for SLAAC") uncovered a wrong assumption in VyOS that every
interface type in use always supports SLAAC and IPv6-ND (neighbor discovery).
This is not true for WireGuard, Tunnel and VTI interfaces, thus do not provide
that CLI option. In addition SLAAC support should be removed for those interface
types in a future PR.
T6944: adds option to enable switchdev mode on ethernet interface2024-12-24T12:44:20+00:00Nicolas Vollmarnvollmar@gmail.com2024-12-12T18:34:20+00:00urn:sha1:3d5cc842ea651de68cfac299d6a8bd2849c9a1f8ethernet: 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
T5474: establish common file name pattern for XML conf mode commands2023-12-31T22:49:48+00:00Christian Breunigchristian@breunig.cc2023-12-30T22:25:20+00:00urn:sha1:4ef110fd2c501b718344c72d495ad7e16d2bd465
We will use _ as CLI level divider. The XML definition filename and also
the Python helper should match the CLI node.
Example:
set interfaces ethernet -> interfaces_ethernet.xml.in
set interfaces bond -> interfaces_bond.xml.in
set service dhcp-server -> service_dhcp-server-xml.in