Bug 103959 - ONBOOT config parameter doesn't work for network interface aliases
Summary: ONBOOT config parameter doesn't work for network interface aliases
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 7.3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-09-08 13:33 UTC by AxIT
Modified: 2014-03-17 02:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-09-08 16:37:36 UTC
Embargoed:


Attachments (Terms of Use)
Patch for /home/amo/ifup-post (476 bytes, patch)
2003-09-08 13:35 UTC, AxIT
no flags Details | Diff
Patch for /home/amo/ifup-aliases (884 bytes, patch)
2003-09-08 13:37 UTC, AxIT
no flags Details | Diff

Description AxIT 2003-09-08 13:33:44 UTC
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):
initscripts-6.67-1

How reproducible:
Always

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
3. Reboot

Actual Results:  Alias eth0:0 is up.

Expected Results:  Alias eth0:0 shouldn't be up.

Additional info:

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.

Comment 1 AxIT 2003-09-08 13:35:42 UTC
Created attachment 94300 [details]
Patch for /home/amo/ifup-post

Simple workaround to make things go the right way.

Comment 2 AxIT 2003-09-08 13:37:43 UTC
Created attachment 94301 [details]
Patch for /home/amo/ifup-aliases

...and second part of a workaround.

Comment 3 Bill Nottingham 2003-09-08 16:37:36 UTC
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.


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