vyos-1x.git/interface-definitions/interfaces_bridge.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-04-21T08:41:33+00:00bridge: T8411: Allow disabling MAC learning on bridge member interfaces2026-04-21T08:41:33+00:00Nataliia Solomkonatalirs1985@gmail.com2026-04-20T11:19:44+00:00urn:sha1:b5b5c421baae71b586c84aedb8f119daf18964eebridge: T6775: The isolation option disappears after reboot2025-11-12T07:54:48+00:00Oleksandr Kuchmystyio.kuchmystyi@vyos.io2025-11-12T07:54:02+00:00urn:sha1:d3b2215ff16044fe9125196015644caf3b443c3e
Previously, the bridge definition had priority 310 while ethernet interfaces
used 318. This caused bridges to be built before their member interfaces were
ready, resulting in missing or incomplete bridge configuration at boot.
Increase bridge priority from 310 to 319 to ensure bridges are processed
after base ethernet/VLAN interfaces and before higher‑level subsystems.
Bridge: T7430: Add BPDU Guard and Root Guard support2025-05-05T19:35:32+00:00l0crian1ryan.claridge13@gmail.com2025-05-05T16:04:02+00:00urn:sha1:7e035196049ff0525b01020ac12689612bdda2cb
This will add support for BPDU Guard and Root Guard to the bridge interface.
Verification will come from:
show log spanning-tree
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.
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.
bridge: 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
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