logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

interfaces-bridge - Bridge extensions for the interfaces(5) file format

Authors

Maximilian Wilhelm <max@sdn.clinic> 2025-03-25 interfaces-bridge(5)

Description

Linux has support for Ethernet bridging interfaces which act like an Ethernet switch within the Linux Kernel. The following options allow to set up Ethernet bridges and adding configured interfaces to bridges. See ip-link(8) for more details about the options listed below.

Examples

A simple layer 2 only bridge: auto br0 iface br0 bridge-ports eth0 veth-vm1 tap0 bridge-fd 0 bridge-stp off A bridge with layer 3 configuration: auto br0 iface br0 bridge-ports eth0 veth-vm1 tap0 bridge-fd 0 bridge-stp off # address 192.0.2.42/24 address 2001:db8::42/64 A layer 2 only vlan-aware bridge: auto bond0 iface bond0 bond-members eth0 eth1 bridge-vids 23 42 84 1337 auto br0 iface br0 bridge-ports bond0 A vlan-aware bridge with a VLAN interface on top: auto eth0 iface eth0 bridge-vids 23 42 84 1337 auto br0 iface br0 bridge-ports eth0 bridge-vlan-aware yes bridge-vids 42 auto vlan42 iface vlan42 vlan-raw-device br0 # address 192.0.2.42/24 address 2001:db8::42/64

Name

interfaces-bridge - Bridge extensions for the interfaces(5) file format

Options For Vlan-Aware-Bridges

The following options only have an effect on vlan-aware bridges and their ports. All settings can be applied on the bridge interface itself and all member port iface stanzas. If applied on the bridge interface they take effect for the bridge interface itself and might be inherited to bridge-ports depending on the compatibility settings configured in ifupdown-ng.conf(5). Configuring VLAN options on the bridge interface might be required for setting up a VLAN interface to one of the VLANs carried within the bridge. See the EXAMPLES section for an example for this scenario. See ifupdown-ng.conf(5) for more information about compatiblity settings mentioned below. bridge-accessvlanID Configure the given vlanID for untagged ingress and egress on this interface. The common description for this kind of configuration is called "access port". bridge-pvidvlanID Denotes the vlanID to considered a PVID at ingress. Any untagged frames received on this interface will be assigned to this vlanID. The default PVID is 1. If compatibility to ifupdown2 bridge port inheritance is active a bridge-pvid set on the bridge will be inherited to any interface configured in bridge-ports without a bridge-pvid set. bridge-vidslistofvlanIDs Denotes the space separated list of VLANs to be allowed tagged ingress/egress on this interface. If compatibility to ifupdown2 bridge port inheritance is active a bridge-vids set on the bridge will be inherited to any interface configured in bridge-ports without bridge-vids set. bridge-allow-untaggedbool Denotes wether or not the bridge should allow untagged frames on ingress as well as egress. If set to no untagged frames will be droppped on ingress and none will be sent. bool can be given as yes/no or 0/1. The defaul is yes.

See Also

interfaces(5) ifupdown-ng.conf(5) ip-link(8) bridge(8)

See Also