Date: Sun, 20 Feb 2005 20:46:51 -0800 From: Julian Elischer <julian@elischer.org> To: Julian Elischer <julian@elischer.org> Cc: net@freebsd.org Subject: Re: ABI suggestions? Message-ID: <421967BB.5010807@elischer.org> In-Reply-To: <4219671C.4050002@elischer.org> References: <42192D78.6070600@elischer.org> <20050220193909.K1739@odysseus.silby.com> <4219671C.4050002@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?421967BB.5010807>