Red Hat Bugzilla – Bug 103959
ONBOOT config parameter doesn't work for network interface aliases
Last modified: 2014-03-16 22:38:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
Description of problem:
When configuring interface aliases using /etc/sysconfig/network-scripts/ifcfg-*,
parameter ONBOOT is ommited. Every time main interface is brought up during
boot, its aliases are also set up, despite of ONBOOT value.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure an alias for eth0, eg. in /etc/sysconfig/network-scripts/ifcfg-eth0:0
2. In ifcfg-eth0:0 set ONBOOT=no
Actual Results: Alias eth0:0 is up.
Expected Results: Alias eth0:0 shouldn't be up.
I found that parameter 'boot' used in /etc/rc.d/init.d/network to notify other
scripts that we are in bootup process is not pased to ifup-aliases script. Also
ifup-aliases doesn't check if ONBOOT is set or not.
Created attachment 94300 [details]
Patch for /home/amo/ifup-post
Simple workaround to make things go the right way.
Created attachment 94301 [details]
Patch for /home/amo/ifup-aliases
...and second part of a workaround.
Hm, in current trees we have ONPARENT setting to more generically define which
aliases are automatically brought up on bringing up the parent interface; I
think this adequately solves this issue.