Bug 20051 - linuxconf does not create virtual ip aliases correctly
Summary: linuxconf does not create virtual ip aliases correctly
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Dale Lovelace
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-30 19:21 UTC by Need Real Name
Modified: 2007-04-18 16:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-10-30 19:21:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Need Real Name 2000-10-30 19:21:18 UTC 
When IP aliases are created in linuxconf it makes files 
in /etc/sysconfig/network-scripts, however these ifcfg files will not 
work. They have no device line and therefore will not bring the virtual 
interface up. 

Also, when a range of addresses is specified the range designation such as 
192.168.0.1-25 is placed in the first virtual device file as the IP 
address.

It would be nice if a selection could be made whether to start these 
interfaces on boot or not.
Comment 1 Nalin Dahyabhai 2000-10-30 20:20:12 UTC 
You can't bring a virtual interface up without the "real" interface it goes
with.  The next time eth0 is brought up (either at boot or manually), the
virtual interfaces will come up.
Note You need to log in before you can comment on or make changes to this bug.