Date: Fri, 14 Oct 2005 17:24:09 -0400 From: Chuck Lever <cel@citi.umich.edu> To: Jim Rees <rees@umich.edu> Cc: fs@freebsd.org Subject: Re: FreeBSD NFS server not responding to TCP SYN packets from Linux/SunOS clients Message-ID: <435021F9.5090302@citi.umich.edu> In-Reply-To: <20051014211624.6E4D61BB35@citi.umich.edu> References: <20051014211624.6E4D61BB35@citi.umich.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?435021F9.5090302>