Bug 709316

Summary: bond0: received packet with own address as source address
Product: Red Hat Enterprise Linux 6 Reporter: Liang Zheng <lzheng>
Component: kernelAssignee: Andy Gospodarek <agospoda>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.1CC: arozansk, kzhang, peterm
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-06 19:35:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Reproducer none

Description Liang Zheng 2011-05-31 11:13:20 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
kernel 2.6.32-131.0.15.el6

How reproducible:
100%

Steps to Reproduce:
1.ifup eth0
2.ifup eth1
3.modprobe bonding mode=0 miimon=100
4.ifconfig bond0 up
5.ifenslave bond0 eth0 eth1
6.brctl addbr br0
7.ifconfig br0 192.168.0.1/24 up
8.brctl addif br0 bond0

9.on another system ping 192.168.0.1
10.dmesg 
you will see "bond0: received packet with own address as source address"
  
Actual results:
bond0: received packet with own address as source address

Expected results:

Additional info:[root@hp-dl580g7-01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
HWADDR="00:1B:21:4A:FE:98"
NM_CONTROLLED="yes"
ONBOOT="no"
TYPE="Ethernet"
IPADDR="192.168.1.10"
NETMASK="255.255.255.0"
BOOTPROTO="none"

[root@hp-dl580g7-01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE="eth1"
HWADDR="00:1B:21:4A:FE:99"
NM_CONTROLLED="yes"
ONBOOT="no"
TYPE="Ethernet"
IPADDR="192.168.1.11"
NETMASK="255.255.255.0"
BOOTPROTO="none"
Comment 1 Liang Zheng 2011-05-31 12:45:31 UTC 
Created attachment 501985 [details]
Reproducer
Comment 2 Andy Gospodarek 2011-06-06 19:35:21 UTC 
This happens with RR-mode bonding since the switch is unaware that the two ports are actually connected to the same device.  Working as expected.