* Olaf Kirch <[EMAIL PROTECTED]> 2006-08-29 10:24 > we had bug reports from people seeing lots of spurious messages > like the following: > > kernel: peth0: received packet with own address as source address. > > and > > xenbr0: duplicate address detected! > > This is on a Xen enabled machine, with lots of Xen machines on the > same network. > > When the Xen code configures the bridge device, this will do IPv6 > autoconfiguration for the interface, and since they use synthetic MAC > addresses, there will be DAD collisions. > > When the Xen people looked for a way to disable IPv6 autoconf of the > bridge, they didn't find any way to do it without bringing up the > device first (and thereby triggering DAD).
They didn't find any because there is no need to disable it. I hardly think that the network stack should fix things that Xen got wrong. Setting dev_addr to -1 is just plain wrong, other virtual ethernet devices call random_ether_addr(), it's not a new problem at all. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html