Bug 10180 - ip aliases not assigned with customized kernel
ip aliases not assigned with customized kernel
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-03-15 05:54 EST by Andreas J. Bathe
Modified: 2014-03-16 22:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-03-15 15:36:43 EST
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 Andreas J. Bathe 2000-03-15 05:54:44 EST
When booting with the standard rh kernel, the IP aliases get assigned.
When booting with a customized kernel where the ethernet card driver is
build into the kernel the "ifup eth0:0" command outputs

  SIOCSIFADDR: No such device
  SIOCSIFFLAGS: No such device
  SIOCSIFNETMASK: No such device
  SIOCSIFBRDADDR: No such device
  SIOCSIFFLAGS: No such device
  SIOCADDRT: No such device

and in the /var/log/messages file you find

Mar 15 11:59:42 gate modprobe: can't locate module eth0:0
Mar 15 11:59:42 gate last message repeated 4 times

or similar hints. The eth0 device is still up and modprobe tries to
reload the net driver again, obviously not recognizing that the driver
is built monolythic into the kernel.

Andreas J. Bathe <ajb@allmaxx.de>
Comment 1 Bill Nottingham 2000-03-15 10:59:59 EST
Potentially a very stupid question, but did you turn on
IP aliasing in the custom kernel?
Comment 2 Andreas J. Bathe 2000-03-15 15:36:59 EST
You're definitely right ;( It wasn't turned on. What a shame...
Sorry about that.

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