Bug 92453
| Summary: | Fails to account for ONBOOT for virtual interfaces | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Yoda <gbj> |
| Component: | initscripts | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | rvokal |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-06-06 15:55:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
There is ONPARENT=no. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: When a system boots it brings up the network interfaces eth0 eth1 etc. In some cases there is a good reason to use more than one IP Address on an interface, for example eth0:1 eth0:2 etc. In some cases it is necessary to selectively bring up those virtual interfaces. Say eth0:1 but not eth0:2 To do this we use the ONBOOT=yes or ONBOOT=no in the ifcfg-eth0:1 etc. However in RedHat9 this directive is ignored for virtual interfaces. The problem lies in /etc/sysconfig/network-scripts/ifup-aliases if [ "$no_devices_are_up" = "yes" ]; then setup_this=yes else ... fi To give this a quick fix I changed it to: (NOTE != ) if [ "X$ONBOOT" != "Xyes" ]; then setup_this=no elif [ "$no_devices_are_up" = "yes" ]; then setup_this=yes else ... fi Version-Release number of selected component (if applicable): initscripts-7.14-1 How reproducible: Always Steps to Reproduce: 1. Set ONBOOT=no in /etc/sysconfig/network-scripts/ifcfg-eth0:4 2. Reboot machine or service network restart 3. run ifconfig to find eth0:4 up Actual Results: interface eth0:4 was up Expected Results: interface eth0:4 should not be up Additional info: I am submitting as a security fix as it may open up an interface when it was not expected and a security policy may not take this into account