Date: Wed, 25 Oct 1995 15:43:18 -0500 (CDT) From: mikebo@tellabs.com To: wollman@lcs.mit.edu (Garrett A. Wollman) Cc: bugs@freebsd.org, hackers@freebsd.org, davew@sees.bangor.ac.uk Subject: Re: 2.1.0-951020-SNAP: Major bug in NFS again! Message-ID: <199510252043.PAA00582@sunc210.tellabs.com> In-Reply-To: <9510251423.AA07418@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Oct 25, 95 10:23:33 am
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett wrote: > 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'.) > Wahoo! This option did the trick, even though the ip_addrs didn't match. This option did _not_ work under 2.0.5R, due to bad hackage of the RPC code in libc. It does seem to work under 2.1.0-951020-SNAP! Come to think of it, the "bad hackage" was, in fact, a connect() being done in lib/libc/rpc/clnt_udp.c. Hopefully, now that we know this is a workaround for strict 4.4BSD net security, the "-o noconn" option will not be removed. I must admit I don't understand why a connect(2) is being done. Isn't UDP a connection- LESS protocol? Perhaps someone can explain... I am only an egg. ;v) Thanks everyone for your suggestions! - Mike -- -------------------------------------------------------------------------- Michael Borowiec - mikebo@tellabs.com - Tellabs Operations Inc. Senior Member of Technical Staff 4951 Indiana Avenue, MS 63 708-512-8211 FAX: 708-512-7099 Lisle, IL 60532 USA --------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510252043.PAA00582>