Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!mips!sgi!vjs@rhyolite.wpd.sgi.com
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Question on forwarding broadcasts
Summary: ipforwarding := 0
Message-ID: <70711@sgi.sgi.com>
Date: 29 Sep 90 18:20:47 GMT
References: <1990Sep28.143945.7440@ultra.com> <11858@medusa.cs.purdue.edu>
Sender: guest@sgi.sgi.com
Distribution: comp
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 17

In article <11858@medusa.cs.purdue.edu>, smb@cs.purdue.EDU (Scott Ballew) writes:
> Hold it!  In your configuration, Host B should NOT be forwarding ANY
> packets at all, unless it is configured as a gateway. ...

Right!  I wish I had said that.  (I did think it; trust me.)
Don't the Host Requirements say the same?

For various reasons, I bet the original poster is running workstations with
two interfaces, one ethernet and one other kind.  I bet the workstations
have either 4.2BSD or 4.3BSD TCP/IP, where having two interfaces turns on
IP forwarding.  If so, the easy solution is to set the kernel variable
ipforwarding to 0.  That can be done with adb on some systems and by
editing configuration files on some other systems.



Vernon Schryver,    vjs@sgi.com.