diff options
| author | Jesse Gross <jesse@nicira.com> | 2009-10-12 13:09:51 -0700 |
|---|---|---|
| committer | Jesse Gross <jesse@nicira.com> | 2009-10-20 10:52:31 -0700 |
| commit | 3a55ef14838f9552fa824b90599aa2a6493bb04a (patch) | |
| tree | cf3478efe1885ad81324ecce3ed9032c35e48849 /vswitchd/INTERNALS | |
| parent | 450f38cf3c84f7b6f4722e174d824f328b4414f8 (diff) | |
| download | openvswitch-3a55ef14838f9552fa824b90599aa2a6493bb04a.tar.gz | |
bonding: Drop unicast packets which have a different learned port.
Drop packets received on a bond port if we have learned a different
source port for that MAC. We were already doing this for multicast
packets but extend the logic to unicast packets as well since the
same situation can occur if the connected switch has not learned the
MAC address and is flooding. Otherwise vSwitch will learn the bond
port as the source of that MAC.
Bug #2167
Diffstat (limited to 'vswitchd/INTERNALS')
| -rw-r--r-- | vswitchd/INTERNALS | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/vswitchd/INTERNALS b/vswitchd/INTERNALS index 49a415880..5873dc177 100644 --- a/vswitchd/INTERNALS +++ b/vswitchd/INTERNALS @@ -83,12 +83,12 @@ received on other slaves are dropped. Otherwise, every multicast packet would be duplicated, once for every bond slave, because the physical switch attached to the bond will flood those packets. -Bonding also drops some multicast packets received on the active -slave: those for the vswitch has learned that the packet's MAC is on a -port other than the bond port itself. This is because it is likely -that the vswitch itself sent the multicast packet out the bond port, -on a slave other than the active slave, and is now receiving the -packet back on the active slave. However, the vswitch makes an +Bonding also drops received packets when the vswitch has learned that +the packet's MAC is on a port other than the bond port itself. This is +because it is likely that the vswitch itself sent the packet out the +bond port on a different slave and is now receiving the packet back. +This occurs when the packet is multicast or the physical switch has not +yet learned the MAC and is flooding it. However, the vswitch makes an exception to this rule for broadcast ARP replies, which indicate that the MAC has moved to another switch, probably due to VM migration. (ARP replies are normally unicast, so this exception does not match |