Ok, I thought you would understand my previous thread with lukas, I was trying to set up the bridge address with ip link set on an experimental package I have on my desktop but on kernel 3.2 my results were this:
If I force it with my method it sets the mac on the bridge and it is forced, but the net doesn't work, which means that at least on 3.2 with a e1000 if the bridge and the card don't have the same mac it won't work. However if I add another card to the bridge with the mac of the bridge it will work ok, sending traffic through any of the cards. So it seems bridge related rather than driver related. Which basically means that at least on 3.2 if the bridge is forced to a mac that is not part of it, it won't work. However the same setup on 3.11 did seem to work, so I suppose that this was solved somewhere in the middle. What I'd be willing to do is to implement the old behaviour for the old kernels and the new one for the newer kernels, but the question is... on what kernel did this really start to work? I think that the patch you were talking about would work ok (no mac changes) if the assigned mac is part of the bridge, but on older kernels (at least up to and including 3.2) it won't work if the mac is not part of the bridge or if the card with that mac leaves the bridge. I didn't have the time to investigate at which version this was solved, it would be good if somebody had any hint on this. I hope this clarifies a bit, if you need more info just let me know. Regards. On May 03 2014, Leoš Bitto wrote: > > > > 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. -- Manty/BestiaTester -> http://manty.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
