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

Bug 3627

Summary:	catastrophic IPX broadcast storm from autoconfigure of IPX interfaces
Product:	[Retired] Red Hat Linux	Reporter:	nicku
Component:	ncpfs	Assignee:	David Lawrence <dkl>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0	CC:	nicku
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-07-29 16:53:06 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 nicku 1999-06-21 23:03:44 UTC

When configure IPX networking with linuxconfig to use
automatic interface in a large
network with many other clients running Windows 9x and
Novell 4.11 servers, an IPX broadcast storm brings down the
whole network, making it unusable for anything.
This causes the BIG BOSS to investigate, resulting in
bans on the use of Red Hat Linux.

Comment 1 Bill Nottingham 1999-06-21 23:12:59 UTC

Uh-oh. What does it get autoconfigured to, or does it not
get that far?

What do the ipx-related lines in
/etc/sysconfig/network-scripts/ifcfg-*
say?

Does it do this only if you do auto_interface select,
auto_primary select, or both?

(I realize that some of this may be difficult to determine
in the wake of the broadcast storms...)

Do you have a tcpdump that shows where the broadcast storms
begin/come from/etc.?

Comment 2 Bill Nottingham 1999-07-29 16:53:59 UTC

this seems to have been solved with the removal of the wrong frame
type.