Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2489

Summary:	networking loopback interface not correctly loaded on startup
Product:	[Retired] Red Hat Linux	Reporter:	kevmcc
Component:	netkit-base	Assignee:	Jay Turner <jturner>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.0	CC:	kevmcc, srevivo
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:	1999-06-04 15:19:41 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 kevmcc 1999-05-03 03:34:03 UTC

The networking loopback interface is not correctly loaded in
the Redhat 6.0 package, as well as in the 5.2 version, which
causes apache and any other packages that depend on the
loopback interface to function incorrectly. I solved this
problem by simply adding in the appropriate entries in my
/etc/sysconfig/network-scripts/ifcfg-lo file. The only thing
that was in there was the BOOTPROTO=none flag. I discovered
this when I tried to ping my lo interface and my eth0 card
and received no packets. I'm not sure if this is a real bug,
as I have pretty much "bastardized" my entire system by
mixing packages from different releases, but on my 5.2 box,
was a regular install, that I have yet to touch. Please
check this out and advise me further.
Kevin McConnell

Comment 1 Jay Turner 1999-06-04 15:19:59 UTC

Unable to relicate this in the test lab on either 6.0 nor 5.2
systems.  Both have complete ifcfg-lo files by default at install.