vyos-1x.git/interface-definitions/include/interface, 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-03-24T17:02:56+00:00T8410: Fix typos and mistakes for operational and configuration commands2026-03-24T17:02:56+00:00Viacheslav Hletenkov.gletenko@vyos.io2026-03-20T16:41:24+00:00urn:sha1:bb2aee1e58c1cd30087b935798060e6bf3c698c8
Fix typos and mistakes in the commands and comments
No functional changes
dhcpv6: T8414: missing prefix-delegation interface constraint2026-03-20T20:28:51+00:00Christian Breunigchristian@breunig.cc2026-03-20T20:28:51+00:00urn:sha1:f6f341cffc98af15ff53588240da14f2d0fb0082interfaces: T8054: use --is-valid-intf-address for validating interface addresses2025-12-01T20:16:47+00:00Daniil Baturindaniil@baturin.org2025-12-01T20:07:22+00:00urn:sha1:a87836ebbffa76134bd95cd10039b3d893e2ec03pppoe: T7485: add DHCPv6 options to disable DNS2025-10-09T15:12:10+00:00Nicolas Vandammen.vandamme@firis-system.lu2025-10-09T15:12:10+00:00urn:sha1:0c5809588980a198a02ebfb70a459d519af0001e
Co-Authored-By: Christian Breunig <christian@breunig.cc>
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.
interface: T4627: support IPv6 Interface Identifier (token) for SLAAC2025-04-18T18:45:46+00:00Yoshiaki Suyamayoshiaki.suyama@suyama.ne.jp2025-03-15T16:16:55+00:00urn:sha1:b124f0b3b05bced1f916e9519d986d03f2b95c51
Add common IPv6 CLI option (use ethernet as example):
set interfaces ethernet eth0 ipv6 address interface-identifier
Co-authored-by: Christian Breunig <christian@breunig.cc>
T6863: Fix default distance for PPPoE (#4229)2024-12-12T19:14:17+00:00Roman KhramshinHollyGurza@users.noreply.github.com2024-12-12T19:14:17+00:00urn:sha1:678c6cd00412cad5d788da210c6dfeae6e77907c
set `default-route-distance` to 1ethernet: 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.