vyos-1x.git/src/conf_mode/interfaces-bridge.py, branch 1.4.0-rc2VyOS command definitions, scripts, and utilities (mirror of https://github.com/marekm72/vyos-1x.git)
https://git.amelek.net/marekm72/vyos-1x.git/atom?h=1.4.0-rc22024-01-01T08:25:32+00:00T5474: establish common file name pattern for XML conf mode commands2024-01-01T08:25:32+00:00Christian Breunigchristian@breunig.cc2023-12-30T22:25:20+00:00urn:sha1:c9eaafd9f808aba8d29be73054e11d37577e539a
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
(cherry picked from commit 4ef110fd2c501b718344c72d495ad7e16d2bd465)
T5837: cleanup use of calls to vyos.configdict.node_changed()2023-12-24T16:40:10+00:00Christian Breunigchristian@breunig.cc2023-12-24T09:17:20+00:00urn:sha1:cddd596a0e03a0ecbbe63bba4f64e9932d02d01f
node_changed() will return a list of changed keys under "path". We are not
always interested what changed, sometimes we are only interested if something
changed at all, that what vyos.configdict.is_node_changed() is for.
(cherry picked from commit 5e7a8288d06a6d6beee5e1abd2e06698ab778650)
vxlan: T3700: add bridge dependency call when altering member interfaces2023-11-06T19:19:23+00:00Christian Breunigchristian@breunig.cc2023-11-05T21:10:29+00:00urn:sha1:583d007b09e653b335d933014803b4cdb4a91060
Commit 7f6624f5a6f8bd ("vxlan: T3700: support VLAN tunnel mapping of VLAN aware
bridges") added support for Single VXLAN Device (SVD) containers supported by
the Linux Kernel.
When working with bridge VIFs it turned out that when deleting a VIF all the
VXLAN tunnel mappings got deleted, too. In order to avoid this, if the bridge
has a VXLAN member interface which vlan-to-vni mapping enabled, we add a
dependency that we call VXLAN conf-mode script after messing arround with the
bridge VIFs and re-create tunnel mappings.
(cherry picked from commit fdf7f3a05edbaaf8aeca7e24a9980d5af67dca18)
T5319: remove workarounds for defaults in interfaces-bridge.py2023-08-07T05:48:31+00:00John Estabrookjestabro@vyos.io2023-08-06T03:28:24+00:00urn:sha1:2df376f44e6e5b412c9ddf13ed395bb583216f45T5195: move helpers from vyos.validate to vyos.utils package2023-08-06T18:25:01+00:00Christian Breunigchristian@breunig.cc2023-08-06T17:29:50+00:00urn:sha1:d1c4294534dd04f075f89f1bb60736d56fc6c22aT5195: vyos.util -> vyos.utils package refactoring (#2093)2023-07-14T20:18:36+00:00Christian Breunigchristian@breunig.cc2023-07-14T20:18:36+00:00urn:sha1:d1ca536da448749dff557f13ecae97b124026e96
* T5195: move run, cmd, call, rc_cmd helper to vyos.utils.process
* T5195: use read_file and write_file implementation from vyos.utils.file
Changed code automatically using:
find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import read_file$/from vyos.utils.file import read_file/g' {} +
find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import write_file$/from vyos.utils.file import write_file/g' {} +
* T5195: move chmod* helpers to vyos.utils.permission
* T5195: use colon_separated_to_dict from vyos.utils.dict
* T5195: move is_systemd_service_* to vyos.utils.process
* T5195: fix boot issues with missing imports
* T5195: move dict_search_* helpers to vyos.utils.dict
* T5195: move network helpers to vyos.utils.network
* T5195: move commit_* helpers to vyos.utils.commit
* T5195: move user I/O helpers to vyos.utils.iobridge: T4579: fix error message for bridge and bond membership2023-05-26T20:10:05+00:00Christian Breunigchristian@breunig.cc2023-05-26T20:10:05+00:00urn:sha1:105224d67c36ef43ee83635b8108faa9a142745cbridge: T4579: cleanup interface dict (remove empty keys)2022-07-30T17:52:20+00:00Christian Poessingerchristian@poessinger.com2022-07-30T17:52:03+00:00urn:sha1:54227591a0eb3c7aa8c896c6ec8b1826ce070ddfbond: bridge: T4534: error out if member interface is assigned to a VRF instance2022-07-15T05:10:29+00:00Christian Poessingerchristian@poessinger.com2022-07-14T18:13:53+00:00urn:sha1:87d2dff241d9ab4de9f3a2c7fbf9852934557aef
It makes no sense to enslave an interface to a bond or a bridge device if it is
bound to a given VRF. If VRFs should be used - the encapuslating/master
interface should be part of the VRF.
Error out if the member interface is part of a VRF.
vyos.configdict(): T4228: is_member() must use the "real" hardware interface2022-07-10T20:44:03+00:00Christian Poessingerchristian@poessinger.com2022-07-10T20:44:03+00:00urn:sha1:3915791216998a18bf6831450df68ee199e2e4f8
When is_member() is inspecting the bridge/Bond member interfaces it must work
with the real interface (e.g. eth1) under the "ethernet" node and not work on
the "member interface eth1" CLI tree, that makes no sense at all.