Bug 20051

Summary:	linuxconf does not create virtual ip aliases correctly
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <nt4_pro>
Component:	linuxconf	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED NOTABUG	QA Contact:	Dale Lovelace <dale>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
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:	---	Target Upstream Version:
Embargoed:

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.