Felix Fietkau wrote:
I did add code to netifd to take care of this a while ago, but there was
a bug that prevented it from working. This bug is fixed in the latest
version, committed in r32506
Great, I confirmed that this is working as it used to now. Thanks!
I suspect that the netifd changes are related, since that looks like the
only relevant area of major activity in the past month when this began
happening. Then again, the timing-sensitive nature means that the
underlying problem may have been present for a while, and only exposed
with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ultimately, it may just be a bad idea to have a bridge's MAC address
change once established, at least as long as the bridge still contains an
underlying interface that owns the MAC address it's using.
That is nothing netifd or OpenWrt does, it
On 6/26/12 11:02 AM, Jo-Philipp Wich wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ultimately, it may just be a bad idea to have a bridge's MAC address
change once established, at least as long as the bridge still contains an
underlying interface that owns the MAC address it's
Philip Prindeville wrote:
On 6/26/12 11:02 AM, Jo-Philipp Wich wrote:
That is nothing netifd or OpenWrt does, it is the behaviour of Linux
bridges - they'll assume the lowest MAC address of all their member ifaces.
Imo that should be changed in the Kernel, it shoud fix the bridge MAC to
On 2012-06-27 12:09 AM, Mark Mentovai wrote:
Philip Prindeville wrote:
On 6/26/12 11:02 AM, Jo-Philipp Wich wrote:
That is nothing netifd or OpenWrt does, it is the behaviour of Linux
bridges - they'll assume the lowest MAC address of all their member ifaces.
Imo that should be changed
