From owner-freebsd-current Sun Jul 29 14: 6:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 01AF237B401 for ; Sun, 29 Jul 2001 14:06:11 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id OAA28687; Sun, 29 Jul 2001 14:06:07 -0700 (PDT) Message-ID: <3B647AE5.7B0DE04C@mindspring.com> Date: Sun, 29 Jul 2001 14:06:45 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: andrewl@nshore.com Cc: current@FreeBSD.ORG Subject: Re: NFS file locking fails from Solaris References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG andrewl@nshore.com wrote: > The Solaris client mounts the FreeBSD exported filesystem fine. I can > create, delete, and manipulate files fine. > > However, when I try to use fcntl to lock a file, the Solaris client hangs. > Normally, I would just let this go; however, Cadence (the VLSI CAD tool > company) requires locks to work in order to use its tools. Therefore, I > can't use FreeBSD as a fileserver in my environment. > > If I monitor the traffic on the line with ethereal, I see the request for > the version 4 nlockmgr from the Solaris client to the FreeBSD server. I > see the FreeBSD server respond with the correct version and port. > However, after this, I start seeing a bunch of SYN/RST packets being > thrown around, and I never see a lock request initiated from the Solaris > client. Who is sending the RST's? (= the connection you are attempting to use does not exist) Who is sending the SYN's? (= I am attempting to establis a new conneciton) This may be related to the "secure" initial sequence number generation algorithm FreeBSD uses; there have been several fixes that have backed this out in various branches. It may also be that your FreeBSD box is multihomes, and you are sending the response on an interface different that the one it was received on (and thus different than the IP address the client is expecting, so the client believes it's a spoof attempt). You should be able to fix this by setting up an explicit route on the FreeBSD box, and potentially the Sun box, depending on how arcane your network setup is. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message