From owner-freebsd-current@FreeBSD.ORG Mon Mar 3 08:51:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 426C81065670 for ; Mon, 3 Mar 2008 08:51:15 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.freebsd.org (Postfix) with ESMTP id D2ABF8FC1B for ; Mon, 3 Mar 2008 08:51:14 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail13.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m238pBZn026064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 3 Mar 2008 19:51:12 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m238pB8G091242 for ; Mon, 3 Mar 2008 19:51:11 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m238pBBm091241 for freebsd-current@freebsd.org; Mon, 3 Mar 2008 19:51:11 +1100 (EST) (envelope-from peter) Date: Mon, 3 Mar 2008 19:51:11 +1100 From: Peter Jeremy To: freebsd-current@freebsd.org Message-ID: <20080303085111.GN90593@server.vk2pj.dyndns.org> References: <20080303073618.GA54342@hades.panopticon> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: <20080303073618.GA54342@hades.panopticon> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: NFS connection strangeness X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2008 08:51:15 -0000 --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--