Hi Rick, Sorry for the delayed reply, but I have had little time available with Christmas.
On Fri, Dec 18, 2009 at 03:23:44PM -0500, Rick Macklem wrote:
>
> > 00:00:01.953196 IP (tos 0x0, ttl 64, id 48966, offset 0, flags [none],
> > proto UDP (17), length 168) 192.168.1.1.3819288094 > 192.168.1.222.2049:
> > 140 readdir [|nfs]
> > 00:00:01.953665 IP (tos 0x0, ttl 64, id 27028, offset 0, flags [+], proto
> > UDP (17), length 1500) 192.168.1.222.2049 > 192.168.1.1.3819288094: reply
> > ok 1472 readdir POST: DIR 755 ids 0/0 [|nfs]
> > 00:00:01.953711 IP (tos 0x0, ttl 64, id 27028, offset 1480, flags [none],
> > proto UDP (17), length 632) 192.168.1.222 > 192.168.1.1: udp
> >
> 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.
FYI, I've tried to use "rdirplus" option from NetBSD NFS client as a
workaround but the mount stalls in UDP (works in TCP). If you are also
interested in this problem, I can provide a trace quickly this time :).
Regards,
--
Jeremie Le Hen
Humans are born free and equal. But some are more equal than the others.
Coluche
pcap.nfs-udp
Description: Binary data
_______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
