> > Leos, your info seems to be of a patch from 2008, so it would be on 3.2, > wouldn't make a differencde between 3.2 and 3.11 or later, so I guess that's > not the patch, but thanks anyway. >
Just to make sure we all understand it the same way - this is what is written at https://bugzilla.redhat.com/show_bug.cgi?id=609463#c20 : In recent kernel, you can set bridge ID by setting bridge's MAC address like this: # ip link set virbr0 address 10:10:10:10:10:10 Then it is described there that this has been enabled by the kernel patch from 2008. So if you want to benefit from this patch in Debian (which includes it in the standard kernel), all you have to do is add the relevant command in /etc/network/interfaces, here is what I have there (and it really works for me - just substitute 11:22:33:44:55:66 for the real address of eth0): auto br0 iface br0 inet static bridge_ports eth0 bridge_hw 11:22:33:44:55:66 up ip link set br0 address 11:22:33:44:55:66 address 192.168.1.1 broadcast 192.168.1.255 netmask 255.255.255.0 When I had only "bridge_hw 11:22:33:44:55:66" there, the MAC address of the bridge could change when new interface was added to the bridge. After I added "up ip link set br0 address 11:22:33:44:55:66" there, the MAC address stays unchanged (thanks to the kernel patch from 2008). I think that the ideal solution of this bug would be that the Debian scripts would run "ip link set br0 address 11:22:33:44:55:66" automatically when "bridge_hw 11:22:33:44:55:66" would be there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
