From owner-freebsd-stable@FreeBSD.ORG Thu Dec 31 19:23:50 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECD031065672 for ; Thu, 31 Dec 2009 19:23:50 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by mx1.freebsd.org (Postfix) with ESMTP id 94E9E8FC1D for ; Thu, 31 Dec 2009 19:23:49 +0000 (UTC) Received: from OMTA16.westchester.pa.mail.comcast.net ([76.96.62.88]) by QMTA11.westchester.pa.mail.comcast.net with comcast id Pufk1d00M1uE5Es5BvPqpu; Thu, 31 Dec 2009 19:23:50 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by OMTA16.westchester.pa.mail.comcast.net with comcast id Pvbi1d0033S48mS3cvbior; Thu, 31 Dec 2009 19:35:43 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C7C0E1E3035; Thu, 31 Dec 2009 11:23:47 -0800 (PST) Date: Thu, 31 Dec 2009 11:23:47 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20091231192347.GA7525@icarus.home.lan> References: <20091213230650.GA45540@felucia.tataz.chchile.org> <20091229125603.GC84457@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Cannot list a particular directory through NFS with UDP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2009 19:23:51 -0000 On Thu, Dec 31, 2009 at 02:23:32PM -0500, Rick Macklem wrote: > On Tue, 29 Dec 2009, Jeremie Le Hen wrote: > > [stuff snipped] > >>This appears to be the reply to the nfs readdir request, which is what > >>would be expected. It could be a problem with the content or the reply > >>or a NetBSD client issue. > >> > >>If you were to email me the raw tcpdump capture for the above, I could > >>take a look at it in wireshark (which knows how to interpret nfs) and > >>see if there is anything bogus looking in the reply. > >>("tcpdump -s 0 -w host 192.168.1.1" and then email me as an > >>attachment, should do it) > > > >You will find the pcap file attached. > > > Well, I looked at it under wireshark and the readdir reply looks fine. > (It is made up of two IP fragments, but wireshark reassembles them ok > and says the checksums are ok. The contents look like a valid Readdir > RPC reply.) Maybe NetBSD doesn't reassemble the IP fragments correctly > or has an issue w.r.t. the checksum, but Wireshark thinks it's aok. > > rick > ps: I vaguely recall that the problem went away when you used TCP > instead. Is that correct? Reading this thread and mention of IP fragments: I'm probably way off base here, but is pf(4) in use at all on the FreeBSD server? If so, see the pf.conf(5) man page, specifically the 'no-df' flag. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |