Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!pt.cs.cmu.edu!sei!sei.cmu.edu!pdb
From: pdb@sei.cmu.edu (Patrick Barron)
Newsgroups: comp.unix.wizards
Subject: Re: rwho problems between 4.2 and 4.3 hosts
Message-ID: <1415@aw.sei.cmu.edu>
Date: Mon, 25-May-87 23:29:58 EDT
Article-I.D.: aw.1415
Posted: Mon May 25 23:29:58 1987
Date-Received: Sat, 6-Jun-87 12:49:20 EDT
References: <7523@brl-adm.ARPA> <12249@topaz.rutgers.edu>
Sender: netnews@sei.cmu.edu
Reply-To: pdb@sei.cmu.edu (Pat Barron)
Organization: Carnegie-Mellon University, SEI, Pgh, Pa
Lines: 16

In article <12249@topaz.rutgers.edu> hedrick@topaz.rutgers.edu (Charles Hedrick) writes:
> [...]  Also, you should set
>ip_forward to 0 on all machines that are not gateways.  You are
>getting icmp errors back from 4.2 because they try to forward the
>packets and can't.  This is a mistake.  [...]

Just a slight correction:  the variable that controls IP packet forwarding
is "ipforwarding", not "ip_forward".  "ip_forward" is the routine that
actually does the work of forwarding a packet.

I'm not sure how it would work on 4.2 (I don't have access to 4.2 sources
anymore), but at least on Ultrix, if a host gets a packet that doesn't
belong to it, and ipforwarding == 0, then it will just generate an automatic
ICMP net unreachable message anyway, which may not be what you want.

--Pat.