Bug 579000 - [RFE] Support L2 packets under bonding layer
Summary: [RFE] Support L2 packets under bonding layer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jiri Pirko
QA Contact: Network QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-02 02:59 UTC by Subhendu Ghosh
Modified: 2015-05-05 01:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-21 10:20:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1065 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 5.7 kernel security and bug fix update 2011-07-21 09:21:37 UTC

Description Subhendu Ghosh 2010-04-02 02:59:13 UTC
Description of problem:

Backport kernel patches to support recipt of packets on real interfaces under the bonding layer:

from:
https://trac.luffy.cx/lldpd/browser/README

For bonding, you need 2.6.24 (in previous version, PACKET_ORIGDEV
affected only non multicast packets). See:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=80feaacb8a6400a9540a961b6743c69a5896b937
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8032b46489e50ef8f3992159abd0349b5b8e476c
	
Otherwise, a packet received on a bond will be affected to all
interfaces of the bond.

On 2.6.27, we are able to receive packets on real interface for bonded
devices. This allows to get neighbor information on active/backup
bonds. Without the 2.6.27, lldpd won't receive any information on
inactive slaves. Here are the patchs (thanks to Joe Eykholt):
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0d7a3681232f545c6a59f77e60f7667673ef0e93
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cc9bd5cebc0825e0fabc0186ab85806a0891104f
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f982307f22db96201e41540295f24e8dcc10c78f
	

Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
1. Install and run lldpd on RHEL5
2. 
3.
  
Actual results:

asroot_iface_init: [priv]: unable to setsockopt for master bonding device of eth3. You will get inaccurate results: Protocol not available


Expected results:
ability to send and receive lldp packets under bonding.

Additional info:

Comment 8 Linda Wang 2010-11-29 19:30:47 UTC
work on this issue in 5.7.  Thanks.

Comment 14 Jarod Wilson 2011-03-16 18:01:04 UTC
Patch(es) available in kernel-2.6.18-248.el5
Detailed testing feedback is always welcomed.

Comment 16 Liang Zheng 2011-03-22 10:35:33 UTC
Verified on -250.el5
[root@dell-t5500-01 ~]# tcpdump -i bond0 ether proto 0x88cc
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bond0, link-type EN10MB (Ethernet), capture size 96 bytes
06:32:22.647523 00:23:ae:7b:98:21 (oui Unknown) > 01:80:c2:00:00:0e (oui Unknown), ethertype Unknown (0x88cc), length 264: 
	0x0000:  0207 0400 23ae 7b98 2104 0605 626f 6e64  ....#.{.!...bond
	0x0010:  3006 0200 b40a 2064 656c 6c2d 7435 3530  0......dell-t550
	0x0020:  302d 3031 2e6c 6162 2e62 6f73 2e72 6564  0-01.lab.bos.red
	0x0030:  6861 742e 636f 6d0c 7552 6564 2048 6174  hat.com.uRed.Hat
	0x0040:  2045 6e74 6572 7072 6973 6520 4c69 6e75  .Enterprise.Linu
	0x0050:  7820  

Bonding interface can send and receive lldp packets.

Comment 17 errata-xmlrpc 2011-07-21 10:20:35 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-1065.html


Note You need to log in before you can comment on or make changes to this bug.