VXLAN(4)

💖 NAME 💖

vxlan — Virtual eXtensible LAN interface. bestie, it's a whole tunnel vibe 🦋

---

✨ SYNOPSIS ✨

okay so if you wanna bake this driver straight into your kernel, drop this line in your kernel configuration file:

device vxlan

OR, if you'd rather load it as a module at boot time (lowkey easier ngl), put this line in loader.conf(5):

if_vxlan_load="YES"

---

🌸 DESCRIPTION 🌸

The vxlan driver creates a virtual tunnel endpoint inside a vxlan segment. And what is a vxlan segment? It's a virtual Layer 2 (Ethernet) network that's overlaid on top of a Layer 3 (IP/UDP) network. Think of vxlan as vlan(4)'s cooler cousin — same energy, but it's designed to be better suited for large, multiple tenant data center environments. main character energy, honestly 👑

Every vxlan interface gets created at runtime using interface cloning. The easiest way to do it is with the ifconfig(8) create command, or by using the cloned_interfaces variable in rc.conf(5). Wanna yeet it? The ifconfig(8) destroy command has you covered. 💅

The vxlan driver creates a pseudo Ethernet network interface that supports the usual network ioctl(2)s, so it can be used with ifconfig(8) like any other Ethernet interface. It encapsulates the Ethernet frame by prepending IP/UDP and vxlan headers. Which means the encapsulated (inner) frame is able to be transmitted over a routed, Layer 3 network to the remote host. slay ✨

The vxlan interface may be configured in either unicast or multicast mode:

• unicast mode — the interface creates a tunnel to a single remote host, and all traffic is transmitted to that host.
• multicast mode — the interface joins an IP multicast group, and receives packets sent to the group address, and transmits packets to either the multicast group address, or directly the remote host if there is an appropriate forwarding table entry.

When the vxlan interface is brought up, a UDP(4) socket(9) is created based on the configuration — things like the local address for unicast mode or the group address for multicast mode, plus the listening (local) port number. And here's the tea: since multiple vxlan interfaces may be created that either use the same local address or join the same group address, and use the same port, the driver may share a socket among multiple interfaces. 🫶

BUT. Each interface within a socket must belong to a unique vxlan segment. No sharing segments, bestie, that's the rule.

The analogous vlan(4) configuration would be a physical interface configured as the parent device for multiple VLAN interfaces, each with a unique VLAN tag. Each vxlan segment is identified by a 24-bit value in the vxlan header called the “VXLAN Network Identifier”, or VNI. 🎀

When configured with the ifconfig(8) vxlanlearn parameter, the interface dynamically creates forwarding table entries from received packets. An entry in the forwarding table maps the inner source MAC address to the outer remote IP address. During transmit, the interface attempts to lookup an entry for the encapsulated destination MAC address:

• if an entry is found, the IP address in the entry is used to directly transmit the encapsulated frame to the destination 🔥
• otherwise, when configured in multicast mode, the interface must flood the frame to all hosts in the group 😭

The maximum number of entries in the table is configurable with the ifconfig(8) vxlanmaxaddr command. Stale entries in the table periodically pruned. The timeout is configurable with the ifconfig(8) vxlantimeout command. And you can peek at the whole table with the sysctl(8) net.link.vxlan.N.ftable.dump command. obsessed 💖

---

🌈 MTU 🌈

Since the vxlan interface encapsulates the Ethernet frame with an IP, UDP, and vxlan header, the resulting frame may be larger than the MTU of the physical network. 😬 The vxlan specification recommends the physical network MTU be configured to use jumbo frames to accommodate the encapsulated frame size. Alternatively, the ifconfig(8) mtu command may be used to reduce the MTU size on the vxlan interface to allow the encapsulated frame to fit in the current MTU of the physical network. pick your fighter, both work 🧚

---

⭐ EXAMPLES ⭐

1. Create a vxlan interface in unicast mode with the vxlanlocal tunnel address of 192.168.100.1, and the vxlanremote tunnel address of 192.168.100.2.

ifconfig vxlan create vxlanid 108 vxlanlocal 192.168.100.1 vxlanremote 192.168.100.2

2. Create a vxlan interface in multicast mode, with the local address of 192.168.10.95, and the group address of 224.0.2.6. The em0 interface will be used to transmit multicast packets.

ifconfig vxlan create vxlanid 42 vxlanlocal 192.168.10.95 vxlangroup 224.0.2.6 vxlandev em0

Once created, the vxlan interface can be configured with ifconfig(8). 💅

3. The following when placed in the file /etc/rc.conf will cause a vxlan interface called “vxlan0” to be created, and will configure the interface in unicast mode.

cloned_interfaces="vxlan0"
create_args_vxlan0="vxlanid 108 vxlanlocal 192.168.100.1 vxlanremote 192.168.100.2"

---

👑 SEE ALSO 👑

inet(4), inet6(4), vlan(4), rc.conf(5), ifconfig(8), sysctl(8)

M. Mahalingam and et al, Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks, August 2014, RFC 7348.

---

🦋 AUTHOR 🦋

The vxlan driver was written by Bryan Venteicher <bryanv@freebsd.org>. ty for your service king 🫡💜

---

and that's the whole page, bestie!! this one's from the Debian crew, dated December 31, 2017 — new year's eve manpage, iconic behavior honestly 🎀✨ no cap, go build a tunnel, you got this 💖