Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!rpi!clarkson!news.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.dcom.lans Subject: Re: Ethernet vs. ARCnet for a Novell lan Message-ID: Date: 30 Oct 90 18:33:53 GMT References: <1990Oct29.161448.24234@cs.odu.edu> Sender: news@news.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 23 In-Reply-To: hedrick@athos.rutgers.edu's message of 30 Oct 90 04:23:05 GMT Nntp-Posting-Host: sun.soe.clarkson.edu In article hedrick@athos.rutgers.edu (Charles Hedrick) writes: Of course if the software gets into a loop sending packets continuously, it's pretty hard to expect any network technology to do much to fix that. It won't necessarily take down the network, but it will certainly create a heavy load. Ha! I was working on a little Ethernet monitoring program (using Clarkson's packet drivers, of course) that put the packet driver into promiscuous mode. That's all well and good, but I forgot to take it *out* of promiscuous mode. Then I ran Phil Karn's TCP/IP package, which likes to do IP routing. It tried to route *every* packet on the net back out onto the same net! This put a heavy load on the net, but it also greatly confused our sun workstations. It was kind of neat. I could unplug my machine, and the net worked again. Plug it back in again, and viola, instant confusion. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600 It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.