Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!dutrun!duteca!dutepp0!etstjan
From: etstjan@dutepp0.et.tudelft.nl (Jan van Oorschot)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Nasty NetCure side effect
Message-ID: <.667153435@dutepp0>
Date: 21 Feb 91 16:23:55 GMT
References: <10608@aggie.ucdavis.edu>
Sender: news@duteca
Lines: 35

ccruss@pollux (Russ Hobby) writes:

>I picked up NetCure (Netmon) and although it still seems to have a few
>bugs to work out, it looks very nice.


>I assume what happened was that Netmon left the packet driver in promiscuous
>mode. When KA9Q was started it received all packets, not just the ones
>addresssed to it on the ethernet. Since the IP packets were not for the
>PC,  KA9Q then forwarded the packets back onto the ethernet. To make matters
>worse the PC also received its own packets and forward those too. 
>Fortunatly it would miss its own packet after a times and stop the chain.

	Your quite right, NetMon doesn't put the packet driver
	back to normal. I would advise you to remove the packet
	driver after using NetMon, you can do that with the 
	"termin" utility (see packet-driver package).
	Put all the commands that start NetMon in a batch file, 
	something like

		termin 0x7a
		wd8003e 0x7a 0x3 0x280 0xd000
		netmon
		termin 0x7a

	KA9Q should configure the packet-driver to it's needs, and 
	disable the promiscuous mode, but we're not all perfect,
	sorry for the trouble.

Jan

-- Ir. Jan van Oorschot.             --- Email: JPMvOorschot@et.tudelft.nl --
-- Data Network Performance Analysis Project                               --
-- CARDIT, Delft University of Technology ------------ Tel: (31)-15-786179 --
-- P.O.Box 5031, 2600 GA Delft, The Netherlands ------ Fax: (31)-15-784898 --


Brought to you by Super Global Mega Corp .com