tcptrace-bugs 6.6.1 bug with -e?

From: Stephen R Smoot (
Date: 06/28/04

Message-Id: <>
Subject: tcptrace-bugs 6.6.1 bug with -e?
Date: Mon, 28 Jun 2004 06:54:40 -0700
From: Stephen R Smoot <>

Are there known problems with -e in 6.6.1?
It usually works fine, but sometimes generates traces which have
zillions of nulls at the end, so I suspect some length field is
beign messed up somewhere.
As an exampl, I did a tcpdump, then did a tcptrace -e and
wc -c * => 8003460906 total
whereas the orig tcpdump was 21766447 chars long,
and if I look at the largest files, they have lots of nulls.

(PS as far as I can tell there are no graph/counters for concurrent tcp
sessions open, am I missing something, or should I add it?)

This archive was generated by hypermail 2.1.7 : 06/28/04 EDT