From owner-freebsd-net@FreeBSD.ORG Fri Oct 14 09:01:34 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D29B716A41F for ; Fri, 14 Oct 2005 09:01:34 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DAC643D45 for ; Fri, 14 Oct 2005 09:01:33 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from cs.ait.ac.th (ufo.cs.ait.ac.th [192.41.170.14]) by mail.cs.ait.ac.th (8.12.11/8.12.11) with ESMTP id j9E91SUb049527 for ; Fri, 14 Oct 2005 16:01:28 +0700 (ICT) Received: from proxy8.psu.ac.th (proxy8.psu.ac.th [202.12.74.8]) by wwws.cs.ait.ac.th (Horde MIME library) with HTTP for ; Fri, 14 Oct 2005 16:01:28 +0700 Message-ID: <20051014160128.hev160v52ossokg0@wwws.cs.ait.ac.th> Date: Fri, 14 Oct 2005 16:01:28 +0700 From: on@cs.ait.ac.th To: freebsd-net@freebsd.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-5.3 X-Virus-Scanned: on CSIM by amavisd-milter (http://www.amavis.org/) Subject: Re: FreeBSD NFS server not responding to TCP SYN packets from Linux/SunOS clients X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2005 09:01:35 -0000 Nicolas KOWALSKI wrote: > Our FreeBSD 4.10 NFS server has some problems serving files by NFS on > TCP (no problem with UDP) when the Linux (2.6) or Solaris (5.9) > clients shut down in an unclean manner (power failure). When the > clients try to mount the shares from the server after an > unclean shutdown, the mount process hang during several minutes (delay > is varying), then succeeds. That is just a wild guess, but NFS mounting would happen always at the same stage of the boot, so maybe with the same source port number and you could be facing the problem that the connection is waiting for termination on the server (close_wait or fin_wait or something)... Se source port in working example is 798 and source port in failing example is 799 certainly not random. Olivier