Bug 4431 - Incorrect handling of non-aliased interfaces (lo and eth)
Incorrect handling of non-aliased interfaces (lo and eth)
Status: CLOSED NEXTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
6.0
All Linux
low Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-08 19:40 EDT by hhaygood
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-09 11:03:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description hhaygood 1999-08-08 19:40:50 EDT
System is stock RHL6.0/Intel.  Noticed problem after
building 2.2.10 from pristine source, don't know if it's
related.

/etc/sysconfig/network-scripts/ifup-post, lines 20-22 read:

if [ "$ISALIAS" = no ] ; then
    /etc/sysconfig/network-scripts/ifup-aliases ${DEVICE}
fi

Thus, it's trying to bring up alias interfaces when it
explicitly knows that there are none.  Only effect on my
system is to cause modprobe errors ("modprobe: can't locate
module eth0:0" [to eth0:49]),
but I suspect that this will cause fairly major hassles for
those who do use alias interfaces.  (The converse of the
effect that I see is that interfaces that include aliases
will not be properly brought up.)

Simple fix is to replace "no" with "yes" on line 20.  It
appears to work just fine for me, and makes sense logically.

Hal Haygood, RHCE
hhaygood@earthlink.net
Comment 1 Bill Nottingham 1999-08-09 11:01:59 EDT
That's not how it works. The 'ISALIAS' checks to see whether
the current interface is an alias; because you don't want
to bring up interfaces for an alias.

The problem is that you compiled the kernel without aliasing
support, and linuxconf's behaviour in this case is not very
good (it's what's causing these messages). Either comment
out the portion of ifup-aliases that refers to linuxconf, or
upgrade to the latest initscripts in Raw Hide, which has this
already done.

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