From owner-freebsd-bugs Wed Oct 25 07:23:53 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA15422 for bugs-outgoing; Wed, 25 Oct 1995 07:23:53 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA15416 for ; Wed, 25 Oct 1995 07:23:49 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA07418; Wed, 25 Oct 1995 10:23:33 -0400 Date: Wed, 25 Oct 1995 10:23:33 -0400 From: "Garrett A. Wollman" Message-Id: <9510251423.AA07418@halloran-eldar.lcs.mit.edu> To: Poul-Henning Kamp Cc: mikebo@tellabs.com, bugs@freebsd.org Subject: Re: 2.1.0-951020-SNAP: Major bug in NFS again! In-Reply-To: <3185.814611965@critter.tfs.com> References: <9510250513.AA12294@tellabk.tellabs.com> <3185.814611965@critter.tfs.com> Sender: owner-bugs@freebsd.org Precedence: bulk [CC list trimmed] < said: > The other way would be to connect(2) the udp socket or alternatively > to use tcp (and nfsv3 ?)... Actually, connect(2) is what is presently being done and part of what causes the breakage. From mount_nfs(8): -c For UDP mount points, do not do a connect(2). This must be used for servers that do not reply to requests from the standard NFS port number 2049. Unfortunately, I don't believe that even this option will help, since the problem is that the server is replying from an address that the client has no way of knowing represents the same host. But it may be worth a try. (This option can also be accessed through the deprecated syntax `noconn'.) -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant