.\" Generated by scdoc 1.11.2 .\" Complete documentation for this program is not available as a GNU info page .ie \n(.g .ds Aq \(aq .el .ds Aq ' .nh .ad l .\" Begin generated content: .TH "interfaces-bridge" "5" "2024-03-13" .P .SH NAME .P \fBinterfaces-bridge\fR - Bridge extensions for the interfaces(5) file format .P .SH DESCRIPTION .P 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.\& .P See \fBip-link\fR(8) for more details about the options listed below.\& .P .SH BRIDGE-RELATED OPTIONS .P \fBbridge-ports\fR \fIlist of interfaces\fR .RS 4 A space separated list of interfaces which should be configured as member interfaces of this bridge.\& This option must be set for the bridge to be configured.\& .P .RE \fBbridge-hw\fR \fIMAC address\fR .RS 4 Denotes the \fIMAC address\fR the bridge should use.\& .P .RE \fBbridge-ageing\fR \fIseconds\fR .RS 4 Denotes the time in seconds after which a MAC address will be removed from the Forwarding DataBase (FDB) after not having seen a frame with this source address.\& .P .RE \fBbridge-vlan-aware\fR \fIbool\fR .RS 4 Denotes wether or not the bridge should be aware of 802.\&1q VLANs.\& \fIbool\fR can be given as \fIyes\fR/\fIno\fR or \fI0\fR/\fI1\fR.\& The defaul is \fIno\fR.\& See related options for configuring vlan-aware bridges, below.\& .P .RE .SH SPANNING TREE RELATED BRIDGE OPTIONS .P \fBbridge-stp\fR \fIstate\fR .RS 4 Activates or deactivates IEEE 802.\&1d Spanning Tree Protocol (STP) support of the bridge.\& Valid values are \fIon\fR/\fIoff\fR.\& .P .RE \fBbridge-bridgeprio\fR \fIpriority\fR .RS 4 Sets the bridge'\&s priority to \fIpriority\fR.\& The priority value is a number between 0 and 65535.\& Lower priority values are better.\& The bridge with the lowest priority will be elected \fIroot bridge\fR.\& .P .RE \fBbridge-fd\fR \fIseconds\fR .RS 4 Denotes the bridge forward delay in seconds.\& Valid values are between 2 and 30.\& .P .RE \fBbridge-hello\fR \fIseconds\fR .RS 4 Denotes the bridge hello time in seconds.\& Valid values are between 1 and 10.\& .P .RE \fBbridge-maxage\fR \fIseconds\fR .RS 4 Denotes the seconds until another bridge is considerd dead after reception of its last STP hello message.\& Valid values are between 6 and 40.\& .P .RE .SH OPTIONS FOR VLAN-AWARE-BRIDGES .P The following options only have an effect on vlan-aware bridges and their ports.\& .P 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 \fIbridge-ports\fR depending on the compatibility settings configured in \fBifupdown-ng.\&conf\fR(5).\& .P 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.\& .P See \fBifupdown-ng.\&conf\fR(5) for more information about compatiblity settings mentioned below.\& .P \fBbridge-access\fR \fIvlan ID\fR .RS 4 Configure the given \fIvlan ID\fR for untagged ingress and egress on this interface.\& The common description for this kind of configuration is called "access port".\& .P .RE \fBbridge-pvid\fR \fIvlan ID\fR .RS 4 Denotes the \fIvlan ID\fR to considered a PVID at ingress.\& Any untagged frames received on this interface will be assigned to this \fIvlan ID\fR.\& The default PVID is \fI1\fR.\& .P If compatibility to ifupdown2 bridge port inheritance is active a \fIbridge-pvid\fR set on the bridge will be inherited to any interface configured in \fIbridge-ports\fR without a \fIbridge-pvid\fR set.\& .P .RE \fBbridge-vids\fR \fIlist of vlan IDs\fR .RS 4 Denotes the space separated list of VLANs to be allowed tagged ingress/egress on this interface.\& .P If compatibility to ifupdown2 bridge port inheritance is active a \fIbridge-vids\fR set on the bridge will be inherited to any interface configured in \fIbridge-ports\fR without \fIbridge-vids\fR set.\& .P .RE \fBbridge-allow-untagged\fR \fIbool\fR .RS 4 Denotes wether or not the bridge should allow untagged frames on ingress as well as egress.\& If set to \fIno\fR untagged frames will be droppped on ingress and none will be sent.\& \fIbool\fR can be given as \fIyes\fR/\fIno\fR or \fI0\fR/\fI1\fR.\& The defaul is \fIyes\fR.\& .P .RE .SH EXAMPLES .P A simple layer 2 only bridge: .P .nf .RS 4 auto br0 iface br0 bridge-ports eth0 veth-vm1 tap0 bridge-fd 0 bridge-stp off .fi .RE .P A bridge with layer 3 configuration: .P .nf .RS 4 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 .fi .RE .P A layer 2 only vlan-aware bridge: .P .nf .RS 4 auto bond0 iface bond0 bond-members eth0 eth1 bridge-vids 23 42 84 1337 auto br0 iface br0 bridge-ports bond0 .fi .RE .P A vlan-aware bridge with a VLAN interface on top: .P .nf .RS 4 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 .fi .RE .P .SH SEE ALSO .P \fBinterfaces\fR(5) \fBifupdown-ng.\&conf\fR(5) \fBip-link\fR(8) \fBbridge\fR(8) .P .SH AUTHORS .P Maximilian Wilhelm