systemd.netdev - Virtual Network Device configuration
Network setup is performed by systemd-networkd(8).
The main Virtual Network Device file must have the extension
.netdev; other extensions are ignored. Virtual network devices are created
as soon as networkd is started. If a netdev with the specified name already
exists, networkd will use that as-is rather than create its own. Note that
the settings of the pre-existing netdev will not be changed by networkd.
The .netdev files are read from the files located in the system
network directory /lib/systemd/network, the volatile runtime network
directory /run/systemd/network and the local administration network
directory /etc/systemd/network. All configuration files are collectively
sorted and processed in lexical order, regardless of the directories in
which they live. However, files with identical filenames replace each other.
Files in /etc have the highest priority, files in /run take precedence over
files with the same name in /lib. This can be used to override a
system-supplied configuration file with a local file if needed. As a special
case, an empty file (file size 0) or symlink with the same name pointing to
/dev/null disables the configuration file entirely (it is
Along with the netdev file foo.netdev, a "drop-in"
directory foo.netdev.d/ may exist. All files with the suffix
".conf" from this directory will be parsed after the file itself
is parsed. This is useful to alter or add configuration settings, without
having to modify the main configuration file. Each drop-in file must have
appropriate section headers.
In addition to /etc/systemd/network, drop-in ".d"
directories can be placed in /lib/systemd/network or /run/systemd/network
directories. Drop-in files in /etc take precedence over those in /run which
in turn take precedence over those in /lib. Drop-in files under any of these
directories take precedence over the main netdev file wherever located. (Of
course, since /run is temporary and /usr/lib is for vendors, it is unlikely
drop-ins should be used in either of those places.)
SUPPORTED NETDEV KINDS¶
The following kinds of virtual network devices may be configured in .netdev
Table 1. Supported kinds of virtual network
||A bond device is an aggregation of all its slave devices. See Linux
Ethernet Bonding Driver HOWTO for details.Local configuration
||A bridge device is a software switch, and each of its slave devices and
the bridge itself are ports of the switch.
||A dummy device drops all packets sent to it.
||A Level 3 GRE tunnel over IPv4. See RFC 2784 for details.
||A Level 2 GRE tunnel over IPv4.
||ERSPAN mirrors traffic on one or more source ports and delivers the
mirrored traffic to one or more destination ports on another switch. The
traffic is encapsulated in generic routing encapsulation (GRE) and is
therefore routable across a layer 3 network between the source switch and
the destination switch.
||A Level 3 GRE tunnel over IPv6.
||An IPv4 or IPv6 tunnel over IPv6
||A Level 2 GRE tunnel over IPv6.
||An IPv4 over IPv4 tunnel.
||An ipvlan device is a stacked device which receives packets from its
underlying device based on IP address filtering.
||A macvlan device is a stacked device which receives packets from its
underlying device based on MAC address filtering.
||A macvtap device is a stacked device which receives packets from its
underlying device based on MAC address filtering.
||An IPv6 over IPv4 tunnel.
||A persistent Level 2 tunnel between a network device and a device
||A persistent Level 3 tunnel between a network device and a device
||An Ethernet tunnel between a pair of network devices.
||A VLAN is a stacked device which receives packets from its underlying
device based on VLAN tagging. See IEEE 802.1Q for details.
||An IPv4 over IPSec tunnel.
||An IPv6 over IPSec tunnel.
||A virtual extensible LAN (vxlan), for connecting Cloud computing
||A GEneric NEtwork Virtualization Encapsulation (GENEVE) netdev
||A Virtual Routing and Forwarding (VRF) interface to create
separate routing and forwarding domains.
||The virtual CAN driver (vcan). Similar to the network loopback devices,
vcan offers a virtual local CAN interface.
||The virtual CAN tunnel driver (vxcan). Similar to the virtual ethernet
driver veth, vxcan implements a local CAN traffic tunnel between two
virtual CAN network devices. When creating a vxcan, two vxcan devices are
created as pair. When one end receives the packet it appears on its pair
and vice versa. The vxcan can be used for cross namespace
||WireGuard Secure Network Tunnel.
||A simulator. This simulated networking device is used for testing
various networking APIs and at this time is particularly focused on
testing hardware offloading related interfaces.
[MATCH] SECTION OPTIONS¶
A virtual network device is only created if the
"[Match]" section matches the current environment, or if the section
is empty. The following keys are accepted:
Matches against the hostname or machine ID of the host.
See "ConditionHost=" in systemd.unit(5)
Checks whether the system is executed in a virtualized
environment and optionally test whether it is a specific implementation. See
"ConditionVirtualization=" in systemd.unit(5)
Checks whether a specific kernel command line option is
set (or if prefixed with the exclamation mark unset). See
"ConditionKernelCommandLine=" in systemd.unit(5)
Checks whether the kernel version (as reported by
) matches a certain expression (or if prefixed with the
exclamation mark does not match it). See "ConditionKernelVersion="
Checks whether the system is running on a specific
architecture. See "ConditionArchitecture=" in systemd.unit(5)
[NETDEV] SECTION OPTIONS¶
The "[NetDev]" section accepts the following keys:
A free-form description of the netdev.
The interface name used when creating the netdev. This
option is compulsory.
The netdev kind. This option is compulsory. See the
"Supported netdev kinds" section for the valid keys.
The maximum transmission unit in bytes to set for the
device. The usual suffixes K, M, G, are supported and are understood to the
base of 1024. For "tun" or "tap" devices, MTUBytes=
setting is not currently supported in "[NetDev]" section. Please
specify it in "[Link]" section of corresponding
The MAC address to use for the device. For
"tun" or "tap" devices, setting MACAddress=
"[NetDev]" section is not supported. Please specify it in
"[Link]" section of the corresponding systemd.network(5)
file. If this option is not set, "vlan" devices inherit the MAC
address of the physical interface. For other kind of netdevs, if this option
is not set, then MAC address is generated based on the interface name and the
[BRIDGE] SECTION OPTIONS¶
The "[Bridge]" section only applies for netdevs of kind
"bridge", and accepts the following keys:
HelloTimeSec specifies the number of seconds between two
hello packets sent out by the root bridge and the designated bridges. Hello
packets are used to communicate information about the topology throughout the
entire bridged local area network.
MaxAgeSec specifies the number of seconds of maximum
message age. If the last seen (received) hello packet is more than this number
of seconds old, the bridge in question will start the takeover procedure in
attempt to become the Root Bridge itself.
ForwardDelaySec specifies the number of seconds spent in
each of the Listening and Learning states before the Forwarding state is
This specifies the number of seconds a MAC Address will
be kept in the forwarding database after having a packet received from this
The priority of the bridge. An integer between 0 and
65535. A lower value means higher priority. The bridge having the lowest
priority will be elected as root bridge.
A 16-bit bitmask represented as an integer which allows
forwarding of link local frames with 802.1D reserved addresses
(01:80:C2:00:00:0X). A logical AND is performed between the specified bitmask
and the exponentiation of 2^X, the lower nibble of the last octet of the MAC
address. For example, a value of 8 would allow forwarding of frames addressed
to 01:80:C2:00:00:03 (802.1X PAE).
This specifies the default port VLAN ID of a newly
attached bridge port. Set this to an integer in the range 1–4094 or
"none" to disable the PVID.
Takes a boolean. This setting controls the
IFLA_BR_MCAST_QUERIER option in the kernel. If enabled, the kernel will send
general ICMP queries from a zero source address. This feature should allow
faster convergence on startup, but it causes some multicast-aware switches to
misbehave and disrupt forwarding of multicast packets. When unset, the
kernel's default will be used.
Takes a boolean. This setting controls the
IFLA_BR_MCAST_SNOOPING option in the kernel. If enabled, IGMP snooping
monitors the Internet Group Management Protocol (IGMP) traffic between hosts
and multicast routers. When unset, the kernel's default will be used.
Takes a boolean. This setting controls the
IFLA_BR_VLAN_FILTERING option in the kernel. If enabled, the bridge will be
started in VLAN-filtering mode. When unset, the kernel's default will be
Takes a boolean. This enables the bridge's Spanning Tree
Protocol (STP). When unset, the kernel's default will be used.
[VLAN] SECTION OPTIONS¶
The "[VLAN]" section only applies for netdevs of kind
"vlan", and accepts the following key:
The VLAN ID to use. An integer in the range
0–4094. This option is compulsory.
Takes a boolean. The Generic VLAN Registration Protocol
(GVRP) is a protocol that allows automatic learning of VLANs on a network.
When unset, the kernel's default will be used.
Takes a boolean. Multiple VLAN Registration Protocol
(MVRP) formerly known as GARP VLAN Registration Protocol (GVRP) is a
standards-based Layer 2 network protocol, for automatic configuration of VLAN
information on switches. It was defined in the 802.1ak amendment to
802.1Q-2005. When unset, the kernel's default will be used.
Takes a boolean. The VLAN loose binding mode, in which
only the operational state is passed from the parent to the associated VLANs,
but the VLAN device state is not changed. When unset, the kernel's default
will be used.
Takes a boolean. The VLAN reorder header is set VLAN
interfaces behave like physical interfaces. When unset, the kernel's default
will be used.
[MACVLAN] SECTION OPTIONS¶
The "[MACVLAN]" section only applies for netdevs of kind
"macvlan", and accepts the following key:
The MACVLAN mode to use. The supported options are
"private", "vepa", "bridge", and
[MACVTAP] SECTION OPTIONS¶
The "[MACVTAP]" section applies for netdevs of kind
"macvtap" and accepts the same key as "[MACVLAN]".
[IPVLAN] SECTION OPTIONS¶
The "[IPVLAN]" section only applies for netdevs of kind
"ipvlan", and accepts the following key:
The IPVLAN mode to use. The supported options are
"L2","L3" and "L3S".
The IPVLAN flags to use. The supported options are
"bridge","private" and "vepa".
[VXLAN] SECTION OPTIONS¶
The "[VXLAN]" section only applies for netdevs of kind
"vxlan", and accepts the following keys:
The VXLAN ID to use.
Configures destination IP address.
Configures local IP address.
The Type Of Service byte value for a vxlan
A fixed Time To Live N on Virtual eXtensible Local Area
Network packets. N is a number in the range 1–255. 0 is a special value
meaning that packets inherit the TTL value.
Takes a boolean. When true, enables dynamic MAC learning
to discover remote MAC addresses.
The lifetime of Forwarding Database entry learnt by the
kernel, in seconds.
Configures maximum number of FDB entries.
Takes a boolean. When true, bridge-connected VXLAN tunnel
endpoint answers ARP requests from the local bridge on behalf of remote
Distributed Overlay Virtual Ethernet (DVOE) clients. Defaults to
Takes a boolean. When true, enables netlink LLADDR miss
Takes a boolean. When true, enables netlink IP address
Takes a boolean. When true, route short circuiting is
Takes a boolean. When true, transmitting UDP checksums
when doing VXLAN/IPv4 is turned on.
Takes a boolean. When true, sending zero checksums in
VXLAN/IPv6 is turned on.
Takes a boolean. When true, receiving zero checksums in
VXLAN/IPv6 is turned on.
Takes a boolean. When true, remote transmit checksum
offload of VXLAN is turned on.
Takes a boolean. When true, remote receive checksum
offload in VXLAN is turned on.
Takes a boolean. When true, it enables Group Policy VXLAN
extension security label mechanism across network peers based on VXLAN. For
details about the Group Policy VXLAN, see the VXLAN Group Policy
document. Defaults to false.
Configures the default destination UDP port on a
per-device basis. If destination port is not specified then Linux kernel
default will be used. Set destination port 4789 to get the IANA assigned
value. If not set or if the destination port is assigned the empty string the
default port of 4789 is used.
Configures VXLAN port range. VXLAN bases source UDP port
based on flow to help the receiver to be able to load balance based on outer
header flow. It restricts the port range to the normal UDP local ports, and
allows overriding via configuration.
Specifies the flow label to use in outgoing packets. The
valid range is 0-1048575.
[GENEVE] SECTION OPTIONS¶
The "[GENEVE]" section only applies for netdevs of kind
"geneve", and accepts the following keys:
Specifies the Virtual Network Identifier (VNI) to use.
Specifies the unicast destination IP address to use in
Specifies the TOS value to use in outgoing packets.
Specifies the TTL value to use in outgoing packets.
Takes a boolean. When true, specifies if UDP checksum is
calculated for transmitted packets over IPv4.
Takes a boolean. When true, skip UDP checksum calculation
for transmitted packets over IPv6.
Takes a boolean. When true, allows incoming UDP packets
over IPv6 with zero checksum field.
Specifies destination port. Defaults to 6081. If not set
or assigned the empty string, the default port of 6081 is used.
Specifies the flow label to use in outgoing
[TUNNEL] SECTION OPTIONS¶
The "[Tunnel]" section only applies for netdevs of kind
"ipip", "sit", "gre", "gretap",
"ip6gre", "ip6gretap", "vti", "vti6",
and "ip6tnl" and accepts the following keys:
A static local address for tunneled packets. It must be
an address on another interface of this host.
The remote endpoint of the tunnel.
The Type Of Service byte value for a tunnel interface.
For details about the TOS, see the Type of Service in the Internet Protocol
A fixed Time To Live N on tunneled packets. N is a number
in the range 1–255. 0 is a special value meaning that packets inherit
the TTL value. The default value for IPv4 tunnels is: inherit. The default
value for IPv6 tunnels is 64.
Takes a boolean. When true, enables Path MTU Discovery on
Configures the 20-bit flow label (see RFC 6437)
field in the IPv6 header (see RFC 2460), which is used by a node to
label packets of a flow. It is only used for IPv6 tunnels. A flow label of
zero is used to indicate packets that have not been labeled. It can be
configured to a value in the range 0–0xFFFFF, or be set to
"inherit", in which case the original flowlabel is used.
Takes a boolean. When true, the Differentiated Service
Code Point (DSCP) field will be copied to the inner header from outer header
during the decapsulation of an IPv6 tunnel packet. DSCP is a field in an IP
packet that enables different levels of service to be assigned to network
traffic. Defaults to "no".
The Tunnel Encapsulation Limit option specifies how many
additional levels of encapsulation are permitted to be prepended to the
packet. For example, a Tunnel Encapsulation Limit option containing a limit
value of zero means that a packet carrying that option may not enter another
tunnel before exiting the current tunnel. (see RFC 2473). The valid
range is 0–255 and "none". Defaults to 4.
The Key= parameter specifies the same key to use
in both directions (InputKey= and OutputKey=). The Key=
is either a number or an IPv4 address-like dotted quad. It is used as
mark-configured SAD/SPD entry as part of the lookup key (both in data and
control path) in ip xfrm (framework used to implement IPsec protocol). See
ip-xfrm — transform configuration for details. It is only
used for VTI/VTI6 tunnels.
The InputKey= parameter specifies the key to use
for input. The format is same as Key=. It is only used for VTI/VTI6
The OutputKey= parameter specifies the key to use
for output. The format is same as Key=. It is only used for VTI/VTI6
An "ip6tnl" tunnel can be in one of three modes
"ip6ip6" for IPv6 over IPv6, "ipip6" for IPv4 over IPv6 or
"any" for either.
Takes a boolean. When true tunnel does not require
.network file. Created as "tunnel@NONE". Defaults to
Takes a boolean. When true allows tunnel traffic on
ip6tnl devices where the remote endpoint is a local host address. When
unset, the kernel's default will be used.
Takes a boolean. Specifies whether FooOverUDP=
tunnel is to be configured. Defaults to false. For more detail information see
Foo over UDP
This setting specifies the UDP destination port for
encapsulation. This field is mandatory and is not set by default.
This setting specifies the UDP source port for
encapsulation. Defaults to 0 — that is, the source port for
packets is left to the network stack to decide.
Accepts the same key as "[FooOverUDP]"
Reconfigure the tunnel for IPv6 Rapid
Deployment, also known as 6rd. The value is an ISP-specific IPv6
prefix with a non-zero length. Only applicable to SIT tunnels.
Takes a boolean. If set, configures the tunnel as
Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunnel. Only
applicable to SIT tunnels. When unset, the kernel's default will be
Takes a boolean. If set to yes, then packets are
serialized. Only applies for ERSPAN tunnel. When unset, the kernel's default
will be used.
Specifies the ERSPAN index field for the interface, an
integer in the range 1-1048575 associated with the ERSPAN traffic's source
port and direction. This field is mandatory.
[FOOOVERUDP] SECTION OPTIONS¶
The "[FooOverUDP]" section only applies for netdevs of kind
"fou" and accepts the following keys:
The Protocol= specifies the protocol number of the
packets arriving at the UDP port. This field is mandatory and is not set by
default. Valid range is 1-255.
Specifies the encapsulation mechanism used to store
networking packets of various protocols inside the UDP packets. Supports the
following values: "FooOverUDP" provides the simplest no frills model
of UDP encapsulation, it simply encapsulates packets directly in the UDP
payload. "GenericUDPEncapsulation" is a generic and extensible
encapsulation, it allows encapsulation of packets for any IP protocol and
optional data as part of the encapsulation. For more detailed information see
Generic UDP Encapsulation. Defaults to
Specifies the port number, where the IP encapsulation
packets will arrive. Please take note that the packets will arrive with the
encapsulation will be removed. Then they will be manually fed back into the
network stack, and sent ahead for delivery to the real destination. This
option is mandatory.
[PEER] SECTION OPTIONS¶
The "[Peer]" section only applies for netdevs of kind "veth"
and accepts the following keys:
The interface name used when creating the netdev. This
option is compulsory.
The peer MACAddress, if not set, it is generated in the
same way as the MAC address of the main interface.
[VXCAN] SECTION OPTIONS¶
The "[VXCAN]" section only applies for netdevs of kind
"vxcan" and accepts the following key:
The peer interface name used when creating the netdev.
This option is compulsory.
[TUN] SECTION OPTIONS¶
The "[Tun]" section only applies for netdevs of kind "tun",
and accepts the following keys:
Takes a boolean. Configures whether all packets are
queued at the device (enabled), or a fixed number of packets are queued at the
device and the rest at the "qdisc". Defaults to
Takes a boolean. Configures whether to use multiple file
descriptors (queues) to parallelize packets sending and receiving. Defaults to
Takes a boolean. Configures whether packets should be
prepended with four extra bytes (two flag bytes and two protocol bytes). If
disabled, it indicates that the packets will be pure IP packets. Defaults to
Takes a boolean. Configures IFF_VNET_HDR flag for a tap
device. It allows sending and receiving larger Generic Segmentation Offload
(GSO) packets. This may increase throughput significantly. Defaults to
User to grant access to the /dev/net/tun device.
Group to grant access to the /dev/net/tun device.
[TAP] SECTION OPTIONS¶
The "[Tap]" section only applies for netdevs of kind "tap",
and accepts the same keys as the "[Tun]" section.
[WIREGUARD] SECTION OPTIONS¶
The "[WireGuard]" section accepts the following keys:
The Base64 encoded private key for the interface. It can
be generated using the wg genkey command (see wg(8)). This
option is mandatory to use WireGuard. Note that because this information is
secret, you may want to set the permissions of the .netdev file to be owned by
"root:systemd-network" with a "0640" file mode.
Sets UDP port for listening. Takes either value between 1
and 65535 or "auto". If "auto" is specified, the port is
automatically generated based on interface name. Defaults to
Sets a firewall mark on outgoing WireGuard packets from
[WIREGUARDPEER] SECTION OPTIONS¶
The "[WireGuardPeer]" section accepts the following keys:
Sets a Base64 encoded public key calculated by wg
pubkey (see wg(8)) from a private key, and usually transmitted out
of band to the author of the configuration file. This option is mandatory for
Optional preshared key for the interface. It can be
generated by the wg genpsk command. This option adds an additional
layer of symmetric-key cryptography to be mixed into the already existing
public-key cryptography, for post-quantum resistance. Note that because this
information is secret, you may want to set the permissions of the .netdev file
to be owned by "root:systemd-networkd" with a "0640" file
Sets a comma-separated list of IP (v4 or v6) addresses
with CIDR masks from which this peer is allowed to send incoming traffic and
to which outgoing traffic for this peer is directed. The catch-all 0.0.0.0/0
may be specified for matching all IPv4 addresses, and ::/0 may be specified
for matching all IPv6 addresses.
Sets an endpoint IP address or hostname, followed by a
colon, and then a port number. This endpoint will be updated automatically
once to the most recent source IP address and port of correctly authenticated
packets from the peer at configuration time.
Sets a seconds interval, between 1 and 65535 inclusive,
of how often to send an authenticated empty packet to the peer for the purpose
of keeping a stateful firewall or NAT mapping valid persistently. For example,
if the interface very rarely sends traffic, but it might at anytime receive
traffic from a peer, and it is behind NAT, the interface might benefit from
having a persistent keepalive interval of 25 seconds. If set to 0 or
"off", this option is disabled. By default or when unspecified, this
option is off. Most users will not need this.
[BOND] SECTION OPTIONS¶
The "[Bond]" section accepts the following key:
Specifies one of the bonding policies. The default is
"balance-rr" (round robin). Possible values are
"balance-rr", "active-backup", "balance-xor",
"broadcast", "802.3ad", "balance-tlb", and
Selects the transmit hash policy to use for slave
selection in balance-xor, 802.3ad, and tlb modes. Possible values are
"layer2", "layer3+4", "layer2+3",
"encap2+3", and "encap3+4".
Specifies the rate with which link partner transmits Link
Aggregation Control Protocol Data Unit packets in 802.3ad mode. Possible
values are "slow", which requests partner to transmit LACPDUs every
30 seconds, and "fast", which requests partner to transmit LACPDUs
every second. The default value is "slow".
Specifies the frequency that Media Independent Interface
link monitoring will occur. A value of zero disables MII link monitoring. This
value is rounded down to the nearest millisecond. The default value is
Specifies the delay before a link is enabled after a link
up status has been detected. This value is rounded down to a multiple of
MIIMonitorSec. The default value is 0.
Specifies the delay before a link is disabled after a
link down status has been detected. This value is rounded down to a multiple
of MIIMonitorSec. The default value is 0.
Specifies the number of seconds between instances where
the bonding driver sends learning packets to each slave peer switch. The valid
range is 1–0x7fffffff; the default value is 1. This option has an
effect only for the balance-tlb and balance-alb modes.
Specifies the 802.3ad aggregation selection logic to use.
Possible values are "stable", "bandwidth" and
Specifies the 802.3ad actor system priority. Ranges
Specifies the 802.3ad user defined portion of the port
key. Ranges [0-1023].
Specifies the 802.3ad system mac address. This can not be
either NULL or Multicast.
Specifies whether the active-backup mode should set all
slaves to the same MAC address at the time of enslavement or, when enabled, to
perform special handling of the bond's MAC address in accordance with the
selected policy. The default policy is none. Possible values are
"none", "active" and "follow".
Specifies whether or not ARP probes and replies should be
validated in any mode that supports ARP monitoring, or whether non-ARP traffic
should be filtered (disregarded) for link monitoring purposes. Possible values
are "none", "active", "backup" and
Specifies the ARP link monitoring frequency in
milliseconds. A value of 0 disables ARP monitoring. The default value is
Specifies the IP addresses to use as ARP monitoring peers
when ARPIntervalSec is greater than 0. These are the targets of the ARP
request sent to determine the health of the link to the targets. Specify these
values in IPv4 dotted decimal format. At least one IP address must be given
for ARP monitoring to function. The maximum number of targets that can be
specified is 16. The default value is no IP addresses.
Specifies the quantity of ARPIPTargets that must be
reachable in order for the ARP monitor to consider a slave as being up. This
option affects only active-backup mode for slaves with ARPValidate enabled.
Possible values are "any" and "all".
Specifies the reselection policy for the primary slave.
This affects how the primary slave is chosen to become the active slave when
failure of the active slave or recovery of the primary slave occurs. This
option is designed to prevent flip-flopping between the primary slave and
other slaves. Possible values are "always", "better" and
Specifies the number of IGMP membership reports to be
issued after a failover event. One membership report is issued immediately
after the failover, subsequent packets are sent in each 200ms interval. The
valid range is 0–255. Defaults to 1. A value of 0 prevents the IGMP
membership report from being issued in response to the failover event.
Specify the number of packets to transmit through a slave
before moving to the next one. When set to 0, then a slave is chosen at
random. The valid range is 0–65535. Defaults to 1. This option only has
effect when in balance-rr mode.
Specify the number of peer notifications (gratuitous ARPs
and unsolicited IPv6 Neighbor Advertisements) to be issued after a failover
event. As soon as the link is up on the new slave, a peer notification is sent
on the bonding device and each VLAN sub-device. This is repeated at each link
monitor interval (ARPIntervalSec or MIIMonitorSec, whichever is active) if the
number is greater than 1. The valid range is 0–255. The default value
is 1. These options affect only the active-backup mode.
Takes a boolean. Specifies that duplicate frames
(received on inactive ports) should be dropped when false, or delivered when
true. Normally, bonding will drop duplicate frames (received on inactive
ports), which is desirable for most users. But there are some times it is nice
to allow duplicate frames to be delivered. The default value is false (drop
duplicate frames received on inactive ports).
Takes a boolean. Specifies if dynamic shuffling of flows
is enabled. Applies only for balance-tlb mode. Defaults to unset.
Specifies the minimum number of links that must be active
before asserting carrier. The default value is 0.
For more detail information see Linux Ethernet Bonding Driver
Example 1. /etc/systemd/network/25-bridge.netdev
Example 2. /etc/systemd/network/25-vlan1.netdev
Example 3. /etc/systemd/network/25-ipip.netdev
Example 4. /etc/systemd/network/1-fou-tunnel.netdev
Example 5. /etc/systemd/network/25-fou-ipip.netdev
Example 6. /etc/systemd/network/25-tap.netdev
Example 7. /etc/systemd/network/25-sit.netdev
Example 8. /etc/systemd/network/25-6rd.netdev
Example 9. /etc/systemd/network/25-gre.netdev
Example 10. /etc/systemd/network/25-vti.netdev
Example 11. /etc/systemd/network/25-veth.netdev
Example 12. /etc/systemd/network/25-bond.netdev
Example 13. /etc/systemd/network/25-dummy.netdev
Example 14. /etc/systemd/network/25-vrf.netdev
Create a VRF interface with table 42.
Example 15. /etc/systemd/network/25-macvtap.netdev
Create a MacVTap device.
Example 16. /etc/systemd/network/25-wireguard.netdev
- Linux Ethernet Bonding Driver HOWTO
- RFC 2784
- IEEE 802.1Q
- VXLAN Group Policy
- Type of Service in the Internet Protocol Suite
- RFC 6437
- RFC 2460
- RFC 2473
- ip-xfrm — transform configuration
- Foo over UDP
- IPv6 Rapid Deployment
- Generic UDP Encapsulation