|
NAMEvxlan —
Virtual eXtensible LAN interface
SYNOPSISTo compile this driver into the kernel, place the following line in your kernel configuration file:device vxlan Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_vxlan_load="YES" DESCRIPTIONThevxlan driver creates a virtual tunnel endpoint in a
vxlan segment. A vxlan segment
is a virtual Layer 2 (Ethernet) network that is overlaid in a Layer 3 (IP/UDP)
network. vxlan is analogous to
vlan(4) but
is designed to be better suited for large, multiple tenant data center
environments.
Each The The When the When configured with the
ifconfig(8)
MTUSince thevxlan 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.
By default, the Alternatively, the
ifconfig(8)
HARDWAREThevxlan driver supports hardware checksum offload
(receive and transmit) and TSO on the encapsulated traffic over physical
interfaces that support these features. The vxlan
interface examines the vxlandev interface, if one is
specified, or the interface hosting the vxlanlocal
address, and configures its capabilities based on the hardware offload
capabilities of that physical interface. If multiple physical interfaces will
transmit or receive traffic for the vxlan then they
all must have the same hardware capabilities. The transmit routine of a
vxlan interface may fail with
ENXIO if an outbound physical interface does not
support an offload that the vxlan interface is
requesting. This can happen if there are multiple physical interfaces
involved, with different hardware capabilities, or an interface capability was
disabled after the vxlan interface had already
started.
At present, these devices are capable of generating checksums and performing TSO on the inner frames in hardware: cxgbe(4). EXAMPLESCreate avxlan 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 Create a ifconfig vxlan create vxlanid 42 vxlanlocal 192.168.10.95 vxlangroup 224.0.2.6 vxlandev em0 Once created, the The following when placed in the file
/etc/rc.conf will cause a vxlan interface called
“ cloned_interfaces="vxlan0" create_args_vxlan0="vxlanid 108 vxlanlocal 192.168.100.1 vxlanremote 192.168.100.2" SEE ALSOinet(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. AUTHORSThevxlan driver was written by Bryan
Venteicher ⟨bryanv@freebsd.org⟩. Support for stateless
hardware offloads was added by Navdeep Parhar
⟨np@freebsd.org⟩ in FreeBSD 13.0.
Visit the GSP FreeBSD Man Page Interface. |