Bug 676708 - [PATCH] VLAN configs do not work when renaming ethernet interfaces to non-numeric.
[PATCH] VLAN configs do not work when renaming ethernet interfaces to non-num...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: initscripts Maintenance Team
Depends On:
Blocks: 682269 501533
  Show dependency treegraph
Reported: 2011-02-10 16:33 EST by Matt Domsch
Modified: 2011-05-19 09:52 EDT (History)
12 users (show)

See Also:
Fixed In Version: initscripts-9.03.21-1.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 462095
Last Closed: 2011-05-19 09:52:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matt Domsch 2011-02-10 16:33:54 EST
+++ This bug was initially created as a clone of Bug #462095 +++

Description of problem:

When setting up vlans on ethernet interfaces that have letters in the device file name (ethWAN, ethVZ, ethLAN, etc) instead of numbers only (eth0, eth1, eth5, etc) running 'service network restart' fails when trying to enable the VLANs.

It also appears, looking at the /sbin/ifup script, that it will allow VLAN ID's to be specified in excess of 4095. This is not as critical an issue, though.

How reproducible:

Every time

Steps to Reproduce:
1. rename eth0 to ethLAN
2. create a ethLAN.100 config file, and enable VLANs in /etc/sysconfig/network
3. execute 'service network restart'
Actual results:

error messages come up when the VLANS are supposed to be configured

Expected results:

VLANS are configured

Additional info:

Attached is a patch to /sbin/ifup that fixes both the problems indicated in the summary.

--- Additional comment from jim.nelson@neteasyinc.com on 2008-09-12 11:28:51 EDT ---

Created attachment 316590 [details]
Patch to /sbin/ifup

--- Additional comment from notting@redhat.com on 2008-09-12 11:54:56 EDT ---

It's not really a sufficient patch - after all, you could name your devices Tom, Dick, and Harry.

--- Additional comment from jim.nelson@neteasyinc.com on 2008-09-12 12:14:19 EDT ---

I'm torn - although you could, indeed, name an ethernet interface anything you want, using eth* and bond* prefixes for network interfaces is the normal way to designate these things.  Since VLANs are specific to ethernet interfaces, I'd see it as a reasonable restriction.

I could resubmit if it would make sense to open up ethernet interfaces to any name.

--- Additional comment from notting@redhat.com on 2009-03-19 16:39:43 EDT ---

*** Bug 440603 has been marked as a duplicate of this bug. ***

--- Additional comment from matt_domsch@dell.com on 2011-02-10 16:08:28 EST ---

diff --git a/sysconfig/network-scripts/ifup b/sysconfig/network-scripts/ifup
index 1eaabab..d296508 100755
--- a/sysconfig/network-scripts/ifup
+++ b/sysconfig/network-scripts/ifup
@@ -73,9 +73,9 @@ fi
 # Ethernet 802.1Q VLAN support
 if [ "${VLAN}" = "yes" ] && [ "$ISALIAS" = "no" ]; then
-    MATCH='^(eth|hsi|bond)[0-9]+\.[0-9]{1,4}$'
+    MATCH='^.+\.[0-9]{1,4}$'
     if [[ "${DEVICE}" =~ $MATCH ]]; then
-       VID=$(echo "${DEVICE}" | LC_ALL=C sed 's/^[a-z0-9]*\.0*\([0-9]\+\)/\1/')
+       VID=$(echo "${DEVICE}" | LC_ALL=C sed 's/^.*\.\([0-9]\+\)/\1/')

--- Additional comment from matt_domsch@dell.com on 2011-02-10 16:17:45 EST ---

Created attachment 478120 [details]

Patch removes any naming requirement on device names before adding the .1234 VLAN ID.

No sense testing for ID > 4096, vconfig will throw an error that point which the sysadmin can read just as well.
Comment 5 errata-xmlrpc 2011-05-19 09:52:04 EDT
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.


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