--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 03, 2008 at 10:36:18AM +0300, Dmitry Marakasov wrote:
>connections on my 7.0-RELEASE boxes. First of all, no NFS-related
>TCP connection are showed in `sockstat -4c' (not on the client, nor on
>the server), though tcpdump clearly shows that there is TCP data
>exchange with alredy existing connection.


I see the same on 6.3 so I don't think this is a 7.0 effect.

>10:30:57.280063 IP (tos 0x0, ttl 64, id 46128, offset 0, flags [DF], proto=

TCP (6), length 208) 192.168.0.32.834052435 > 192.168.0.1.2049: 156 access=
[|nfs]
>10:30:57.280279 IP (tos 0x0, ttl 64, id 24588, offset 0, flags [DF], proto=

TCP (6), length 176) 192.168.0.1.2049 > 192.168.0.32.834052435: reply ok 1=
24 access [|nfs]
>
>what the heck is 834052435 in 192.168.0.32.834052435 > 192.168.0.1.2049
>line?


It's the NFS transaction ID. See the section "NFS Requests and Replies"
in tcpdump(1).

--=20
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.

--r5Pyd7+fXNt84Ff3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHy7v//opHv/APuIcRAu75AJ0YvhpoG6SupGhGXG9WfEuni+NaLQCgpTKD
nnIxSAWXbX91CwUCdJqObmw=
=EcUG
-----END PGP SIGNATURE-----

--r5Pyd7+fXNt84Ff3--