From owner-freebsd-net@FreeBSD.ORG  Sat Apr 10 04:23:26 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A5B3D16A4CE
	for <freebsd-net@freebsd.org>; Sat, 10 Apr 2004 04:23:26 -0700 (PDT)
Received: from kogut3.o2.pl (kogut3.go2.pl [212.126.20.24])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4F85843D54
	for <freebsd-net@freebsd.org>; Sat, 10 Apr 2004 04:23:23 -0700 (PDT)
	(envelope-from knockefreebsd@o2.pl)
Received: from ALFA (rekin7.go2.pl [212.126.20.19])
	by kogut3.o2.pl (Postfix) with ESMTP id D439C77E82
	for <freebsd-net@freebsd.org>; Sat, 10 Apr 2004 13:23:21 +0200 (CEST)
Message-ID: <001901c41eee$3f09c0b0$df5561d9@ALFA>
From: "Knocke" <knockefreebsd@o2.pl>
To: <freebsd-net@freebsd.org>
Date: Sat, 10 Apr 2004 13:23:24 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.1
Subject: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Apr 2004 11:23:26 -0000

Hi!

I'm about to get a bit deeper into TCP world, recently experienced a =
problem - I need to have a real-time image of actual active TCP socket =
state, its most important variables like: cwnd, ssthresh, S and R =
windows, etc,=20
I thought I'd be possible to see using tcpdump, but as far as I know =
it;s only a packet dumper based on datalink layer, so it knows nothing =
about current machine's socket states. I've been searching the Internet =
for a quite long time, and couldn't find anything smarter than different =
packet analysers etc.=20

Could somebode give me hint what to do? Is there any tool to connect to =
existing TCP socket and dump its state per each segment sent or =
received? Or any other way to achive the goal? It could be also a kind =
of dedicated benchmark tool (lice ttcp) that comes togehter with what i =
need, I don't necesarly need to track existing sshd or apache owned =
sockets.=20

kh