Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!hao!gatech!bloom-beacon!mit-eddie!bbn!rochester!PT.CS.CMU.EDU!sei!sei.cmu.edu!pdb
From: pdb@sei.cmu.edu (Patrick Barron)
Newsgroups: comp.dcom.lans
Subject: Re: Latest news on our ether errors
Message-ID: <4333@aw.sei.cmu.edu>
Date: 24 Feb 88 00:30:16 GMT
References: <8403@g.ms.uky.edu> <4097@lll-winken.llnl.gov> <678@kaos.UUCP>
Sender: netnews@sei.cmu.edu
Reply-To: pdb@sei.cmu.edu (Pat Barron)
Organization: Carnegie-Mellon University, SEI, Pgh, Pa
Lines: 10

In article <678@kaos.UUCP> romkey@kaos.UUCP (John Romkey) writes:
>That should only happen if you have a mix of 4.2 machines and later systems
>which broadcast according to spec on the same ethernet. There's a variable
>in the kernel which controls IP forwarding and you can use adb to turn
>it off, but I don't remember the name of the variable.

It's called, oddly enough, "ipforwarding".  There's another variable called
"ipprintfs" which, if set to 1 while ipforwarding is set to 1, will print
a message on the console every time the machine attempts to forward a packet.

--Pat.