From owner-freebsd-hackers Thu Dec 16 10: 7: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dns1.sports.gov.uk (dns1.sports.gov.uk [212.125.74.131]) by hub.freebsd.org (Postfix) with ESMTP id 9ACA3151F2 for ; Thu, 16 Dec 1999 10:06:56 -0800 (PST) (envelope-from ad@dns1.sports.gov.uk) Received: from ad (helo=localhost) by dns1.sports.gov.uk with local-esmtp (Exim 3.03 #1) id 11yfDk-0005Xw-00; Thu, 16 Dec 1999 18:01:44 +0000 Date: Thu, 16 Dec 1999 18:01:44 +0000 (GMT) From: Andy Doran X-Sender: ad@dns1.sports.gov.uk To: Matthew Dillon Cc: Cillian Sharkey , hackers@FreeBSD.ORG Subject: Re: Strange problem with NFS In-Reply-To: <199912161707.JAA54566@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Dec 1999, Matthew Dillon wrote: > Looks like a firewall to me. Either a firewall in a router > sitting between the hosts, or an ipfw setup sitting on one or the > other host. I set up the NFS server in question ages ago. I haven't looked at the problem, but... The server does use ipfw. The broken client is on the same subnet as the working ones and nothing in the server's ipfw ruleset refers directly to the broken client. - ad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message