From owner-freebsd-fs@FreeBSD.ORG Fri Oct 14 21:24:12 2005 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C6DA16A41F for ; Fri, 14 Oct 2005 21:24:12 +0000 (GMT) (envelope-from cel@citi.umich.edu) Received: from citi.umich.edu (citi.umich.edu [141.211.133.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8D6E43D62 for ; Fri, 14 Oct 2005 21:24:10 +0000 (GMT) (envelope-from cel@citi.umich.edu) Received: from [10.58.52.227] (nat-198-95-226-230.netapp.com [198.95.226.230]) by citi.umich.edu (Postfix) with ESMTP id 03B1B1BBDC; Fri, 14 Oct 2005 17:24:09 -0400 (EDT) Message-ID: <435021F9.5090302@citi.umich.edu> Date: Fri, 14 Oct 2005 17:24:09 -0400 From: Chuck Lever Organization: Network Appliance, Inc. User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jim Rees References: <20051014211624.6E4D61BB35@citi.umich.edu> In-Reply-To: <20051014211624.6E4D61BB35@citi.umich.edu> Content-Type: multipart/mixed; boundary="------------030606080804020302010005" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: fs@freebsd.org Subject: Re: FreeBSD NFS server not responding to TCP SYN packets from Linux/SunOS clients X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cel@citi.umich.edu List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2005 21:24:12 -0000 This is a multi-part message in MIME format. --------------030606080804020302010005 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Jim Rees wrote: > where is that rule stated? most NFS clients i am aware of retransmit an > RPC after 60 seconds over TCP. > > Why would they do that? because NFS/TCP implementations are usually based on pre-existing NFS/UDP implementations, which already have support for retransmitting. also, see below: some clients might assume that a server could drop an RCP request coming over a TCP connection. > I would consider that a bug. I am only familiar > with the various bsd implementations, but none of them retransmit over tcp. Solaris and Linux both do it. that doesn't mean it's the right thing to do. however, there are reasons why that would make for some interoperability issues with servers that never drop. > Are there buggy servers that drop rpc requests over tcp? Why? i don't know of a specific implementation that drops RPC requests over TCP. however, i can think of some reasons (allowed by "holes" in the various RFCs) why a server implementor might think it's OK to do. --------------030606080804020302010005--