On 7/20/07, Aaron Turner <[EMAIL PROTECTED]> wrote:
> On 7/20/07, john mcnicholas <[EMAIL PROTECTED]> wrote:
> >267> /usr/local/bin/tcpprep --print-stats=x.services.cache
> >Primary packets:0
> >Secondary packets: 44717
> >Skipped packets:0
> >--
On 7/20/07, john mcnicholas <[EMAIL PROTECTED]> wrote:
> 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.
I'd proba
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
This connection is probably your problem:
. [10.252.95.13:0 <-> 10.119.58.167:0 ] : 1 connections : 0 bytes
tcpprep in the "auto" modes uses a weighted approach, and the 1
connection/0 bytes sounds likely to not be enough to trigger a
definite decision. Using a lower --ratio value (say 1
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
