Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    How are you building the bridge? On my machine I have /etc/network/interfaces build the bridge with only the primary ethernet adapter connected and the bridge gets the MAC address of the ethernet adapter. It's probably worth updating the question with how you're building it. Commented Oct 1, 2022 at 11:54
  • @StephenHarris see the update on my answer about the MAC address not inherited anymore Commented Oct 1, 2022 at 12:38
  • @StephenHarris Some time ago, I have created the bridge manually on both machines and have assigned one ethernet adapter to it (/dev/eno1 in my case), but there are virtual VM network devices which get dynamically added and removed from it as VMs start and stop. The IP configuration of the bridge is in /etc/network/interfaces (as in your case). That worked so far, except for the problem with the MAC address. In the meantime, I could confirm that A.B's answer is correct. Commented Oct 1, 2022 at 15:36
  • 1
    @A.B it may matter how the bridge is created. In /etc/network/interfaces on my Debian 11 machine I have bridge_hw enp2s0 in the br0 definition. That may be what lets it get inherited; % /usr/bin/lsb_release -a | grep Descr; ifconfig enp2s0 | grep ether ; ifconfig br0 | grep ether Description: Debian GNU/Linux 11 (bullseye) ether 18:d6:c7:05:89:07 txqueuelen 1000 (Ethernet) ether 18:d6:c7:05:89:07 txqueuelen 1000 (Ethernet) iface enp2s0 inet manual auto br0 iface br0 inet dhcp bridge_ports enp2s0 bridge_hw enp2s0 Commented Oct 1, 2022 at 19:48