From owner-freebsd-hackers  Thu Oct 26 07:17:49 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id HAA07470
          for hackers-outgoing; Thu, 26 Oct 1995 07:17:49 -0700
Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA07463
          ; Thu, 26 Oct 1995 07:17:44 -0700
From: mikebo@tellabs.com
Received: from sunc210.tellabs.com by tellab5.lisle.tellabs.com with smtp
	(Smail3.1.29.1 #4) id m0t8T7E-000jBzC; Thu, 26 Oct 95 09:17 CDT
Received: by sunc210.tellabs.com (SMI-8.6/1.9)
	id JAA01701; Thu, 26 Oct 1995 09:17:03 -0500
Message-Id: <199510261417.JAA01701@sunc210.tellabs.com>
Subject: Re: 2.1.0-951020-SNAP: Major bug in NFS again!
To: davew@sees.bangor.ac.uk (Mr D Whitehead)
Date: Thu, 26 Oct 1995 09:17:03 -0500 (CDT)
Cc: bugs@freebsd.org, hackers@freebsd.org
In-Reply-To: <17209.9510252357@hermes.sees.bangor.ac.uk> from "Mr D Whitehead" at Oct 25, 95 11:57:09 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
Precedence: bulk

Dave wrote:
> > 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.
> > > 
> > 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
>                   ^^^^^
>                   I beg to differ, we are using 2.0.5R (from the CD) and
> it _was_ the solution to our problem!
> 
> > 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.
> 
I did try "noconn" while monitoring with snoop and a Sniffer, and under
2.0.5R (from the CD also), it did not solve the problem of differing
ip_addrs. My traces showed ICMP Destination unreachable (Bad port) with
or without noconn. But, there's no arguing with results. I couldn't get
it to work, and documented it months ago. No sense going back now...
- 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
--------------------------------------------------------------------------