tools/testing/selftests/net/test_vxlan_under_vrf.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/net/test_vxlan_under_vrf.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/net/test_vxlan_under_vrf.sh- Extension
.sh- Size
- 5676 bytes
- Lines
- 134
- 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
# This test is for checking VXLAN underlay in a non-default VRF.
#
# It simulates two hypervisors running a VM each using four network namespaces:
# two for the HVs, two for the VMs.
# A small VXLAN tunnel is made between the two hypervisors to have the two vms
# in the same virtual L2:
#
# +-------------------+ +-------------------+
# | | | |
# | vm-1 netns | | vm-2 netns |
# | | | |
# | +-------------+ | | +-------------+ |
# | | veth-hv | | | | veth-hv | |
# | | 10.0.0.1/24 | | | | 10.0.0.2/24 | |
# | +-------------+ | | +-------------+ |
# | . | | . |
# +-------------------+ +-------------------+
# . .
# . .
# . .
# +-----------------------------------+ +------------------------------------+
# | . | | . |
# | +----------+ | | +----------+ |
# | | veth-tap | | | | veth-tap | |
# | +----+-----+ | | +----+-----+ |
# | | | | | |
# | +--+--+ +--------------+ | | +--------------+ +--+--+ |
# | | br0 | | vrf-underlay | | | | vrf-underlay | | br0 | |
# | +--+--+ +-------+------+ | | +------+-------+ +--+--+ |
# | | | | | | | |
# | +---+----+ +-------+-------+ | | +-------+-------+ +---+----+ |
# | | vxlan0 |....| veth0 |.|...|.| veth0 |....| vxlan0 | |
# | +--------+ | 172.16.0.1/24 | | | | 172.16.0.2/24 | +--------+ |
# | +---------------+ | | +---------------+ |
# | | | |
# | hv-1 netns | | hv-2 netns |
# | | | |
# +-----------------------------------+ +------------------------------------+
#
# This tests both the connectivity between vm-1 and vm-2, and that the underlay
# can be moved in and out of the vrf by unsetting and setting veth0's master.
source lib.sh
set -e
cleanup() {
ip link del veth-hv-1 2>/dev/null || true
ip link del veth-tap 2>/dev/null || true
cleanup_ns $hv_1 $hv_2 $vm_1 $vm_2
}
# Clean start
cleanup &> /dev/null
[[ $1 == "clean" ]] && exit 0
trap cleanup EXIT
setup_ns hv_1 hv_2 vm_1 vm_2
hv[1]=$hv_1
hv[2]=$hv_2
vm[1]=$vm_1
vm[2]=$vm_2
# Setup "Hypervisors" simulated with netns
ip link add veth-hv-1 type veth peer name veth-hv-2
setup-hv-networking() {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.