From owner-freebsd-net@FreeBSD.ORG  Mon Feb 21 04:47:00 2005
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 1836916A4CE
	for <net@freebsd.org>; Mon, 21 Feb 2005 04:47:00 +0000 (GMT)
Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net
	[207.115.63.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 97C8243D41
	for <net@freebsd.org>; Mon, 21 Feb 2005 04:46:59 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from [192.168.1.102] (adsl-68-124-206-88.dsl.snfc21.pacbell.net
	[68.124.206.88])j1L4kquq118832;	Sun, 20 Feb 2005 23:46:52 -0500
Message-ID: <421967BB.5010807@elischer.org>
Date: Sun, 20 Feb 2005 20:46:51 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050214
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <42192D78.6070600@elischer.org>
	<20050220193909.K1739@odysseus.silby.com> <4219671C.4050002@elischer.org>
In-Reply-To: <4219671C.4050002@elischer.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: net@freebsd.org
Subject: Re: ABI suggestions?
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: Mon, 21 Feb 2005 04:47:00 -0000

Julian Elischer wrote:
> Mike Silbersack wrote:
> 
>>
>> On Sun, 20 Feb 2005, Julian Elischer wrote:
>>
>>> I'm looking at implementing a kernel module that implelemnts an ABI 
>>> that allows a particular tcp session to be followed.
>>> I'm not terribly intereted in the data sent/received bas in the 
>>> actual session
>>> behaviour itself..
>>
>>
>>
>>> p.s. would this be generally useful (assuming it can be achieve without
>>> any overhead when compiled out)?
>>
>>
>>
>> Yes, I think that'd be very useful; when a user has a repeatable 
>> network problem, we could have them turn this on and create a detailed 
>> log file for us.  In cases of reset connections, etc, this would be 
>> quite useful.
>>
>> Doesn't TCPDEBUG do something like that already, though?  I haven't 
>> taken a look into it, perhaps I should.
>>
>> Mike "Silby" Silbersack
> 
> 
> TCPDEBUG does part of it but I don't see a way to get the output 
> directed to a listenning app that can interpret it, and I don't see a 
> way of limitiing it to particular sessions.

the last isn't quite true.. it can be made to depend on SO_DEBUG
but how does a 3rd party process set that bit?

> 
> 
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"