From owner-freebsd-hackers  Fri Aug 30 11:16:19 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA11286
          for hackers-outgoing; Fri, 30 Aug 1996 11:16:19 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA11275
          for <hackers@FreeBSD.ORG>; Fri, 30 Aug 1996 11:16:14 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA00819; Fri, 30 Aug 1996 11:04:02 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199608301804.LAA00819@phaeton.artisoft.com>
Subject: Re: Sun NFS interop problem
To: bwithrow@baynetworks.com (Robert Withrow)
Date: Fri, 30 Aug 1996 11:04:02 -0700 (MST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <199608301548.LAA10680@tuva.engeast.baynetworks.com> from "Robert Withrow" at Aug 30, 96 11:48:57 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I wrote about this a while ago, but I still (2.1.5) have the problem
> interoping with sun NFS where the FreeBSD machine sends a message
> to one sun machine port and gets a reply from another port on the
> sun machine and drops it.

[ ... ]

> So, can someone tell me where this check is in the FreeBSD code,
> so I can try to disable it?

Look in the anti-spoofing code.  The reason it's there is to prevent
someone from outside taking over a local NFS connection and raping your
file system.  The Sun looks like two machines: the valid machine, and
a spoofer trying to hack NFS.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.