RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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"

Created attachment 501985 [details]
Reproducer

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.