From owner-freebsd-fs@FreeBSD.ORG  Fri Oct 14 17:55:31 2005
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 2AB6316A41F
	for <fs@freebsd.org>; Fri, 14 Oct 2005 17:55:31 +0000 (GMT)
	(envelope-from rees@citi.umich.edu)
Received: from citi.umich.edu (citi.umich.edu [141.211.133.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9B2FD43D5D
	for <fs@freebsd.org>; Fri, 14 Oct 2005 17:55:30 +0000 (GMT)
	(envelope-from rees@citi.umich.edu)
Received: from citi.umich.edu (dumaguete.citi.umich.edu [141.211.133.51])
	by citi.umich.edu (Postfix) with ESMTP id 28D651BBE4
	for <fs@freebsd.org>; Fri, 14 Oct 2005 13:55:30 -0400 (EDT)
To: fs@freebsd.org
From: Jim Rees <rees@umich.edu>
In-Reply-To: rick@snowhite.cis.uoguelph.ca, Fri, 14 Oct 2005 13:42:58 EDT
Date: Fri, 14 Oct 2005 13:55:30 -0400
Sender: rees@citi.umich.edu
Message-Id: <20051014175530.28D651BBE4@citi.umich.edu>
Cc: 
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
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2005 17:55:31 -0000

There was a bug in the FreeBSD v3 client that it didn't retransmit at all,
even after a reconnect.  I fixed that in rev 1.125 of nfs_socket.c.  It
should now retransmit exactly once.  That could of course result in a replay
at the server, depending on what caused the reconnect.  In the case where
the server drops the connection due to inactivity, I think there is no
replay.