Red Hat Bugzilla – Bug 107504
VLAN only works with eth[0-9] not with bond[0-9]
Last modified: 2014-03-16 22:39:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120
Description of problem:
The ifup script should not only rely on eth device name but should
also work with bonding when VLAN=yes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.ifup with a script that contains VLAN=yes and DEVICE=bond0
Created attachment 95297 [details]
Patch to ifup
That still doesn't solve the real problem... devices don't even need to be named
ethXX or bondXX; they can be 'tom', 'joe', or 'fred' if you want.
Do you see VLAN on something else than ethernet devices ?
Anyway, redhat-config-network can only handle ethX for Ethernet device names
... like some other scripts. So unless you fix all points, the proposed patch is
r-c-network may only be able to configure *new* devices as ethX, but it can
handle displaying configurations of devices named other things; furthermore, the
init scripts themselves can handle abitrary names.
Ok, I forgot to say that ifdown needs a fix as well.
I'd just like to chime in that it would be nice if RH supported this
officially. It actually wouldn't be too hard to setup the ifup/down
scripts so they handled VLAN interfaces by looking for 'VLAN=yes' in
the scripts themselves, regardless of name, but the switch to
'(eth|bond)' from 'eth' is trivial. I'm not sure why the change
hasn't been put in yet.
Created attachment 100226 [details]
patch to allow bonding and vlans to coexist peacefully
Note the ifup/ifdown changes still have the problem mentioned above.
Which problem? That they don't recognize every conceivable network
name? I know that. The patch is just to address the 95% case, which
is that the default install of Linux sets up the ethernet devices as
ethX and the bonding instructions reference setting them up as bondX
and the standard scripted VLAN setup uses the dot notation.
Unfortunately, right now, those three standard ideas can't be combined.
The problem as I see it is that the notion to support every possible
ethernet/vlan naming convention is holding up a patch that can fix an
issue that's affecting most standard installations involving bonded
interfaces and vlans. This has been a problem for at least 3
generations of RedHat/Fedora releases.
1) Does adding this patch improve the experience for a group of
people without negatively affecting the overall system?
2) Is there anything in the pipeline to address the larger issue
of anything-goes device names and vlans?
If the answer to 1 is "yes" and the answer to 2 is "no", how about
throwing in the patch as a stop-gap until 2 can become "yes"?
Added in CVS, will be in future builds.
IN FC2 with initscripts-7.55.1-1, vconfig-1.8-2 I can't get vlan to
come up automatically like in RH9.
The below works fine in RH9, but not in FC2. Manually adding 802.1q
interface with vconfig than issuing ifup ifcfg-eth0.1819 does work
[root@cr1lapted network-scripts]# cat ifcfg-eth0.1819
Will this also be addressed?
Can you see where it's failing? This doesn't seem related to the
original bug report.
An errata 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 the 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.
amazing that in 2012 in RH 5.8 this issue still exists OOTB....
I greatly suspect you're seeing something different that may manifest in a similar way. I suggest filing a new issue with more details.