From owner-freebsd-current@FreeBSD.ORG Mon Mar 3 08:08: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 85D171065675 for ; Mon, 3 Mar 2008 08:08:15 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from cp65.agava.net (cp65.agava.net [89.108.66.215]) by mx1.freebsd.org (Postfix) with ESMTP id 3F9228FC13 for ; Mon, 3 Mar 2008 08:08:14 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by cp65.agava.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1JW5H4-0003xn-1L for freebsd-current@freebsd.org; Mon, 03 Mar 2008 10:39:50 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 4E60D7A15 for ; Mon, 3 Mar 2008 10:35:49 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 454A717023; Mon, 3 Mar 2008 10:36:18 +0300 (MSK) Date: Mon, 3 Mar 2008 10:36:18 +0300 From: Dmitry Marakasov To: freebsd-current@freebsd.org Message-ID: <20080303073618.GA54342@hades.panopticon> Mail-Followup-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp65.agava.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - amdmi3.ru X-Source: X-Source-Args: X-Source-Dir: Subject: 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:08:15 -0000 Hi! I've just noticed that there are some strangenesses related to NFS 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. Next, tcpdump output is confusing as well: 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 124 access [|nfs] what the heck is 834052435 in 192.168.0.32.834052435 > 192.168.0.1.2049 line? For other tcp connections source port is shown there as expected. -- Dmitry A. Marakasov | jabber: amdmi3@jabber.ru amdmi3@amdmi3.ru | http://www.amdmi3.ru