Red Hat Bugzilla – Bug 162208
[PATCH] bonding: don't drop non-VLAN traffic
Last modified: 2007-04-18 13:28:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Description of problem:
Patch for the bonding driver that was released after FC2 went legacy. The problem was when the system had an IP it was using on its bond0 interface and an IP configured on a VLAN interface, the bond0 IP stopped working.
This is a patch submitted to netdev by Jay Vosburgh:
Change the bonding driver to not drop non-VLAN traffic when a
VLAN is configured above it. Originally fixed by Olaf Kirch
<email@example.com>; I changed his patch slightly to update comments.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Bring up a bonded interface
2. Assign an IP address to bond0, e.g. 192.168.3.5
3. Assign an IP address on a VLAN on bond0.XXX, e.g. 192.168.8.5
Actual Results: The IP address on bond0 (192.168.3.5) would stop working when the bond0.XXX interface was brought up.
Expected Results: Configured IP addresses on both bond0 and bond0.XXX should have coexisted peacefully.
Jay's post of the patch to the netdev list:
Created attachment 116185 [details]
Jay Vosburgh/Olaf Kirch's "don't drop non-VLAN traffic" patch
Did this make it into a more recent upstream kernel?
This doesn't seem to be important enough to fix just on its own, so mark it DEFER.
Any reason why this fix hasn't made it into the kernel yet? Especially Given
the length of time this BUG has been open and triviality of the patch? I
personally found this problem wasted a large amount of my time under RedHat
Enterprise 4 as it broke a machine that was working with VLAN's under a bonding
interface under Enterprise 3 and there was no obvious reason as no errors were
logged and the bonded interface just ate non VLAN packets.
Shouldn't this BUG be logged against RedHat Enterprise 4 as maybe it would get
a little more priority?
Fedora Legacy is just doing security updates.
There may be a slightly higher chance of the bug fix going in (but don't count
on it) if the patch is includes in RHEL patches.
The best way to see this fixed from Red Hat is to have a paying RHEL4 customer
call support and get an issue started with them. Legacy may fix this issue, but
it would wait until there is a security flaw in the kernel that needs to be fixed.
John W. Linville of Red Hat has proposed a patch for this issue for RHEL 4's
kernel as attachment #121717 [details] in Bug 174671 comment #2. When we next go in to
build a FC2 kernel for a security problem, this is a patch we could put in also.
This problem may be present in FC1's and FC3's kernel as well.
(Incidentally, John Linville's patch (attachment #121717 [details]) looks like exactly
the same patch that Bryan Wann submitted here (attachment 116185 [details]).)
Fedora Core 2 is now completely unmaintained. These bugs can't be fixed in that
version. If the issue still persists in current Fedora Core, please reopen.
Thank you, and sorry about this.