On Thu, Dec 4, 2008 at 12:46 AM, Jay Vosburgh <fubar@xxxxxxxxxx> wrote: > Matthew Kent <matt@xxxxxxxxxxxx> wrote: > >>Trying to determine if I have a misconfiguration, misunderstanding or >>have stumbled on a bug. I think there is a bug here although the description doesn't sound like the buggy case. Here is the specific configuration that produces the same message and I think should not: A bond in fail-over mode, either both or just one PHY connected. VLANs configured on the bond device. Two of the bond VLAN interfaces members of the same bridge, stp enabled. An external bridge device (actually a fancy transparent traffic shaper with a history of occasional seizure) connecting the same two VLANs. A router on the higher-numbered (so less preferred by STP) VLAN. So the nominal case is for STP to block forwarding, but if the traffic shaper fails then the bridge will start sending traffic direct to the router. Now when the traffic shaper is forwarding traffic, the BPDUs sent out the preferred port come back on the non-preferred port and force it into blocking mode as desired. But the "received packet with own address as source address" message is logged. _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
