TCPDUMP is probably the wrong tool, because
a file handle will created by OS dynamicly.
If you used  ethereal, chances would be higher.

Stefan Sonnenberg-Carstens
RHCE & Systemadministrator

coolspot AG
Am Albertussee 1
D-40549 Düsseldorf

Tel:   +49 (0)2 11-5 06 61-10
Fax:  +49 (0)2 11-5 06 61-11

eMail: info@coolspot.de


Vorstand:
Roland Bongartz
Sabine Schmidt-Pischner, LL.M

Aufsichtsrat:
Dr. Jur. Marco Picozzi,
Prof. Dr.-Ing. Karl Friedrich Triebold
Gunter Wolff

HRB-Nummer: 39498
Amtsgericht Düsseldorf
Steuer-Nummer 5103/5718/0983
----- Original Message ----- 
From: "Manuel Bouyer" <bouyer@antioche.eu.org>
To: <tech-kern@netbsd.org>
Sent: Wednesday, June 16, 2004 11:09 PM
Subject: NFS questions


> Hi,
> does someone know how to find a file from a NFS server, given a filehandle
> from tcpdump ?
> 23:05:38.425334 192.168.1.17.3538769044 > 132.227.103.2.2049: 112 getattr 
> fh 16,36/1931 (DF)
>
> Maybe the easiest way would be to use fhopen() or fhstat(), but then I 
> need
> to know how to build a fhandle_t from the above information :)
>
> Also, in this trace:
> 23:01:42.771740 132.227.103.2.2049 > 192.168.1.17.3438105748: reply ok 
> 1448 readdirplus
> 23:01:42.771757 132.227.103.2.2049 > 192.168.1.17.3: reply ERR 456
> is 456 an error code ? If so, where can I find what it means ?
>
> And, last question, has anyone heard from NFS problems with a linux 2.6.6
> kernel as client ?
>
> -- 
> Manuel Bouyer <bouyer@antioche.eu.org>
>     NetBSD: 26 ans d'experience feront toujours la difference
> --
>
>