Message-ID: <3AEF07FD.7269D95F@jack.see.plym.ac.uk> Date: Tue, 01 May 2001 20:01:17 +0100 From: Bogdan Ghita <b.ghita@jack.see.plym.ac.uk> Subject: Using NLANR traces as input
Hello everybody
Has anybody succesfully tried to analyse NLANR files? I downloaded from
the NLANR website a few traces, enabled NLANR in Makefile, and tried to
run an analysis and...it didn't work. I don't know where the problem is,
whether there is a problem with the traces (e.g. the format changed,
although the format from the website matches the one from the tcptrace
distribution) or tcptrace just doesn't work with NLANR traces. The only
hint I found was in Makefile:
# define GROK_NLANR if you want tcptrace to understand the
output
# format of the various NLANL
tools
# (this doesn't work well yet, not recommended - Sat Dec 19, 1998)
Unfortunately, in my case, it didn't work at all. The analysis runs
continuously (it doesn't even stop, I don't know why, probably it
doesn't read from where it should...), the packets are 'empty' (all the
fields are 0, besides the TCP seqno which has the same value for a whole
trace)
Does anybody have a patch or are there any suggestions regarding an
improvement?
Thank you
Best regards
Bogdan Ghita
----------------------------------------------------------------------------
To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
majordomo@tcptrace.org.
This archive was generated by hypermail 2b30 : 05/02/01 EDT