Hi!
While looking at this bug I have found several things that I'd like to
summarize here:
On 2008 a patch (commit 92c0574f11598c8036f81e27d2e8bdd6eed7d76d) was
submitted that allowed to set the mac of the bridge, this patch is included
on 3.2, thus in wheezy.
What wasn't included there was a fix for the bridge to work if the address
you set is not the address of one of its interfaces, this was fixed on
commit 43598813386f6205edf3c21f1fe97f731ccb4f15 on the way to 3.3, so from
3.3 on you can set the address you like to a bridge using:
ip link set br0 address ...
However it wasn't until commit 30313a3d5794472c3548d7288e306a5492030370
which is included on 3.15-rc5 that ip link add br0 address ... type bridge
was fixed. Before if you did this you could get a non real hardware bridge
in an unknown state that kind of worked (like Lukas has explained) or a real
hardware bridge that wouldn't work and which was fixed by this commit.
However I believe this commit also makes Lukas setup nonworking (Lukas, I'd
like to get feedback from you on this).
So... unless Lukas tells me his setup is still working on 3.15-rc5 or later
what I'm going to implement is... continue creating the bridge like we have
done till now, set the hw address of all the interfaces to the wanted bridge
hw address on 3.2 and previous versions, and set the hw address of the
bridge using the ip link set command on all versions (this may not work on
some old kernels, but we also will be setting the hw address of the bridge
interfaces on them, so we'll get the wanted address anyway and there is no
better alternative anyway).
Well, once I have clarified this and if nobody complaints about this I'll
upload a new version that fixes the kernel version check I had on last
package and implements what I have stated here.
Thanks to all of you guys for all the feedback I have received.
Regards.
--
Manty/BestiaTester -> http://manty.net
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
