Bug 4070 – Neighbourhood table overflow errors

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 4070 - Neighbourhood table overflow errors

Summary:	Neighbourhood table overflow errors

Status:	CLOSED WORKSFORME

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-07-16 07:38 EDT by gp
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-09-20 11:06:31 EDT
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 gp 1999-07-16 07:38:12 EDT

After changing a client from using DHCP to using a static IP
address using netcfg I had severe errors during the reboot
concerning neighbourhood table overflow errors. Traced it
down to being a badly configured loopback device. The file
/etc/sysconfig/network-scripts/ifcfg-lo was found to be
truncated. It looked like this:

ONBOOT=yes

whereas it should look like this:

BOOTPROTO=none  DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
BROADCAST=127.255.255.255
ONBOOT=yes
BOOTPROTO=none

It appears that netcfg caused this file corruption.

Comment 1 Michael K. Johnson 1999-07-30 17:21:59 EDT

I don't see how netcfg could have done that.  If you can reproduce
it, I'd like to see the steps you took to do it so that I can make
an attempt to debug it here.  Thanks.

Comment 2 Michael K. Johnson 1999-09-20 11:06:59 EDT

Anyone who can reproduce this bug, please reopen this bug report
with an explanation of how you did it.  Thanks!

Note You need to log in before you can comment on or make changes to this bug.