Bug 20051 – linuxconf does not create virtual ip aliases correctly

Bug 20051 - linuxconf does not create virtual ip aliases correctly

Summary:	linuxconf does not create virtual ip aliases correctly

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	linuxconf (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Nalin Dahyabhai
QA Contact:	Dale Lovelace
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-10-30 14:21 EST by Need Real Name
Modified:	2007-04-18 12:29 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-10-30 14:21:20 EST
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.)

Groups: None (edit)

Description Need Real Name 2000-10-30 14:21:18 EST

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 15:20:12 EST

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.