Hello,
I have noticed a problem on RH9.0 with the network startup process. I
have a few aliases for eth0 (eth0:1 - eth0:7) that have been tested
and work fine. We don't want some of these IP's to be active at boot
time so I changes ONBOOT=no in the config file. Simple enough. Upon
reboot each interface gets activated regardless of the state of
ONBOOT. I tried "no" and "NO".
I noticed that in the ifup script it looks for a second parameter and
if that second parameter says "boot" it will then look at the ONBOOT
parameter. So I downed the aliases. Basically eth0 and lo were
running. Issuing an "ifup eth0:1 boot" failed to start the decive as
it should. Issuing an "ifup eth0:1" starts the device as it should.
This leads me to believe that the network startup script at
/etc/rc.d/init.d/netwok has some issue with it. It seems that this
argument doesn't seem to be working on these interfaces.
Here is a sample:
DEVICE=eth0:1
BOOTPROTO=static
BROADCAST=10.0.0.255
IPADDR=10.0.0.191
NETMASK=255.255.255.0
NETWORK=10.0.0.0
ONBOOT=NO
Is there something wrong on my end? BTW, we have also tried it with
an extra empty line after the last line.
Thanks,
Gary Smith
|