The bridge device listed with your other networking devices does not represent the virtual bridge, it represents a virtual NIC that is connected to the bridge.

When the bridge is being used to create a private network of devices with no external connectivity, or with external connectivity provided through a device other than the bridge.

If the bridge is not required for ip routing, then it doesn't need an ip address. In this case, rather than assigning an ip address to (for example) eth0, you would assign it to the bridge device instead. When your 'primary' NIC is a member of the bridge, such that the bridge is your connectivity to the outside world. In this case it needs an ip address (because routing happens at the IP layer). When the bridge is acting as the default gateway for a group of containers or virtual machines (or even physical interfaces). However, in many cases you may have one, such as: There are many situations in which you won't have one. A linux bridge can originate things like spanning-tree protocol frames, and traffic like that needs an origin MAC address.Ī bridge does not require an ip address. Because a bridge is an ethernet device it needs a MAC address.

Linux get interface mac address