tools/testing/selftests/net/forwarding/dual_vxlan_bridge.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/net/forwarding/dual_vxlan_bridge.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/net/forwarding/dual_vxlan_bridge.sh- Extension
.sh- Size
- 11477 bytes
- Lines
- 368
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: tools
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#!/bin/bash
# SPDX-License-Identifier: GPL-2.0
# +--------------------+ +----------------------+
# | H1 (vrf) | | H2 (vrf) |
# | + h1.10 | | + h2.20 |
# | | 192.0.2.1/28 | | | 192.0.2.2/28 |
# | | | | | |
# | + $h1 | | + $h2 |
# | | | | | |
# +----|---------------+ +--|-------------------+
# | |
# +----|--------------------------------------------------|--------------------+
# | SW | | |
# | +--|-------------------------------+ +----------------|------------------+ |
# | | + $swp1 BR1 (802.1ad) | | BR2 (802.1d) + $swp2 | |
# | | vid 100 pvid untagged | | | | |
# | | | | + $swp2.20 | |
# | | | | | |
# | | + vx100 (vxlan) | | + vx200 (vxlan) | |
# | | local 192.0.2.17 | | local 192.0.2.17 | |
# | | remote 192.0.2.34 | | remote 192.0.2.50 | |
# | | id 1000 dstport $VXPORT | | id 2000 dstport $VXPORT | |
# | | vid 100 pvid untagged | | | |
# | +--------------------------------- + +-----------------------------------+ |
# | |
# | 192.0.2.32/28 via 192.0.2.18 |
# | 192.0.2.48/28 via 192.0.2.18 |
# | |
# | + $rp1 |
# | | 192.0.2.17/28 |
# +----|-----------------------------------------------------------------------+
# |
# +----|--------------------------------------------------------+
# | | VRP2 (vrf) |
# | + $rp2 |
# | 192.0.2.18/28 |
# | | (maybe) HW
# =============================================================================
# | | (likely) SW
# | + v1 (veth) + v3 (veth) |
# | | 192.0.2.33/28 | 192.0.2.49/28 |
# +----|---------------------------------------|----------------+
# | |
# +----|------------------------------+ +----|------------------------------+
# | + v2 (veth) NS1 (netns) | | + v4 (veth) NS2 (netns) |
# | 192.0.2.34/28 | | 192.0.2.50/28 |
# | | | |
# | 192.0.2.16/28 via 192.0.2.33 | | 192.0.2.16/28 via 192.0.2.49 |
# | 192.0.2.50/32 via 192.0.2.33 | | 192.0.2.34/32 via 192.0.2.49 |
# | | | |
# | +-------------------------------+ | | +-------------------------------+ |
# | | BR3 (802.1ad) | | | | BR3 (802.1d) | |
# | | + vx100 (vxlan) | | | | + vx200 (vxlan) | |
# | | local 192.0.2.34 | | | | local 192.0.2.50 | |
# | | remote 192.0.2.17 | | | | remote 192.0.2.17 | |
# | | remote 192.0.2.50 | | | | remote 192.0.2.34 | |
# | | id 1000 dstport $VXPORT | | | | id 2000 dstport $VXPORT | |
# | | vid 100 pvid untagged | | | | | |
# | | | | | | + w1.20 | |
# | | | | | | | | |
# | | + w1 (veth) | | | | + w1 (veth) | |
# | | | vid 100 pvid untagged | | | | | | |
# | +--|----------------------------+ | | +--|----------------------------+ |
# | | | | | |
# | +--|----------------------------+ | | +--|----------------------------+ |
# | | | VW2 (vrf) | | | | | VW2 (vrf) | |
# | | + w2 (veth) | | | | + w2 (veth) | |
# | | | | | | | | | |
# | | | | | | | | | |Annotation
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.