Cannot list a particular directory through NFS with UDP
freebsd at jdc.parodius.com
Thu Dec 31 19:23:51 UTC 2009
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 <file> host 192.168.1.1" and then email me <file> 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.
> 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 at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
More information about the freebsd-stable