Update, this file only had a problem in "router" mode; bridge did work.
(so i could have eaten the previous question.)
However, even after removing the packet for the questionable connection,
router mode still did NOT work.
/usr/local/bin/tcpprep --auto=router -i original_file.p
Aaron, etc,
fyi: as you suspected the latest build did fix the error: (msg was something
like;) "Um, shouldn't get here.". Thanks!
Regarding the second error:
this command:
/usr/local/bin/tcpprep --minmask=24 --maxmask=16 --auto=router
--pcap=input.appcapture --cachefile=x.cache
resul
fyi: my results are similar to Bojan's.
Here's the OS:
Linux 2.6.9-6.37.ELsmp #1 SMP Tue Mar 29 15:46:31 EST 2005 x86_64 x86_64
x86_64 GNU/Linux
For each of this configurations:
./configure
./configure --enable-local-libopts
./configure --enable-local-libopts --disable-libopts-install
I recei
eed a pcap.
I think we'll have time to test with the beta. I'm not exactly sure where
I should look for it...
Let me know where, and I'll try and get back to you as soon as possible with
our results.
Thanks again.
John
On 7/18/07, Aaron Turner <[EMAIL PROTECTED]> wrote:
In
Hi.
I'm trying to do some tests with tcpreplay-3.0.1 and a tcpprep is having
problems with a couple of files. It doesn't appear that the mode is
significant as the error occurred in both bridge and router mode.
Here is the general command line:
./tcpprep -a bridge -i some_input_file -o x.cache
