Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Nov 2000 11:35:47 -0500
From:      "Batra, Lalit M" <batralm@jmu.edu>
To:        Nick Slager <nicks@albury.net.au>
Cc:        questions@FreeBSD.ORG, unix -jmu <geek@ruff.cs.jmu.edu>
Subject:   Re: tcpdump: bad file format
Message-ID:  <EXECMAIL.1001116113547.A@hppav.jmu.edu>
In-Reply-To: <20001116220021.B36386@albury.net.au>
References:  <20001116220021.B36386@albury.net.au> <EXECMAIL.1001116031908.A@artvandelay.jmu.edu>   

next in thread | previous in thread | raw e-mail | index | archive | help
What you are saying has been tried but I get the same 
result.I ac read the file otherwise. This has some thing to 
do with pcap.h.NAy ideas



On Thu, 16 Nov 2000 22:00:21 +1100 Nick Slager <nicks@albury.net.au> 
wrote:

> Thus spake Batra, Lalit M (batralm@jmu.edu):
> 
> > I am doing some network experimenst(FREEBSD), Using 
> > Tcpdump.I cannot convert the tcpdump "output.dmp" into 
> > binary form so thatt i can use Tcptrace and then xplot to 
> > see the packets.
> > Following are the steps which i am doing:-
> > 1) tcpdump -i xl1 host 192.168.20.2 > output.dmp
> > 2) tcpdump -r output.dmp
> > ERROR: bad dump file format.????
> > I have also tried -w option , same error.
> 
> How exactly are you using -w? It should be like this:
> 
>   tcpdump -i xl1 -w output.dmp host 192.168.20.2
> 
> You can't just redirect the ascii output; you must use -w.
> 
> 
> Nick
> 
> -- 
>  From a Sun Microsystems bug report (#4102680):
>   "Workaround: don't pound on the mouse like a wild monkey."
> 

-- 
Batra, Lalit M
batralm@jmu.edu



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EXECMAIL.1001116113547.A>