summaryrefslogtreecommitdiff
path: root/src/validators/ipv4-range-exclude
diff options
context:
space:
mode:
authorChristian Breunig <christian@breunig.cc>2023-11-05 22:10:29 +0100
committerChristian Breunig <christian@breunig.cc>2023-11-06 20:19:23 +0100
commit583d007b09e653b335d933014803b4cdb4a91060 (patch)
tree06f482f2257f21425d9981d2fe2b8e3548ff35fc /src/validators/ipv4-range-exclude
parent148ab6c4382be62c1021ec49e3262de66d38ab0a (diff)
downloadvyos-1x-583d007b09e653b335d933014803b4cdb4a91060.tar.gz
vyos-1x-583d007b09e653b335d933014803b4cdb4a91060.zip
vxlan: T3700: add bridge dependency call when altering member interfaces
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)
Diffstat (limited to 'src/validators/ipv4-range-exclude')
0 files changed, 0 insertions, 0 deletions