From owner-freebsd-hackers Fri Aug 30 08:49:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA28101 for hackers-outgoing; Fri, 30 Aug 1996 08:49:46 -0700 (PDT) Received: from lobster.wellfleet.com (lobster.corpeast.baynetworks.com [192.32.253.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA28087 for ; Fri, 30 Aug 1996 08:49:41 -0700 (PDT) Received: from pobox.BayNetworks.com by lobster.wellfleet.com (SMI-8.6/SMI-4.1) id LAA19281; Fri, 30 Aug 1996 11:52:13 -0400 Received: from tuva.engeast.baynetworks.com by pobox.BayNetworks.com (4.1/SMI-4.1) id AA14803; Fri, 30 Aug 96 11:48:58 EDT Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.7.5/8.7.3) with ESMTP id LAA10680 for ; Fri, 30 Aug 1996 11:48:57 -0400 (EDT) Message-Id: <199608301548.LAA10680@tuva.engeast.baynetworks.com> X-Mailer: exmh version 1.6.7 5/3/96 To: hackers@freebsd.org Subject: Sun NFS interop problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Aug 1996 11:48:57 -0400 From: Robert Withrow 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. I have worked around it by adding static routes on the sun, but that is geting cumbersome now that we have so many FreeBSD workstations (Yay.. They are displacing the suns cause the P6_200 FreeBSD machines beat the crap out of anything sun makes for twice the bucks, and once you configure them right, you can hardly tell the difference). So, can someone tell me where this check is in the FreeBSD code, so I can try to disable it? -- Robert Withrow -- (+1 508 436 8256) BWithrow@BayNetworks.com