[Michael Tuexen <Michael.Tuexen@xxxxxxxxxxxxxxxxx>]

Hi Amit,

this is a bug in ethereal. It is working with older versions and has
to be fixed.

Normally you can run

tcpdump -w /tmp/fifo

and

ethereal -i /tmp/fifo

and it works.

Best regards
Michael

On May 19, 2005, at 12:15 Uhr, Amit Dang wrote:

> Hi Michael,
>     I tried reading from FIFO but it fails.
> Tethereal is able to show the captured data using "tethereal -i 
> /tmp/datafifo" but ethereal is not able to display the captured 
> packet.
> For detailed information please refer following mail that we posted on 
> ethereal-user list (subject: [Ethereal-users] Tethereal can, Ethereal 
> cannot)
>  
> ------------------------------------------------------------------
> I am using named pipes (FIFO) to read captured data. My problem is 
> that Tethereal is able to show the captured data using
>     "tethereal -i /tmp/myfifo"
>
> but ethereal is not able to display the captured packets. Am using 
> following command:
>     "ethereal -i /tmp/myfifo -kl"
> Ethereal just says that theres nothing to display as no data has been 
> captured. I can confirm that its reading the right FIFO as it does 
> identify a wrong formatted data, whenever I try to write some junk 
> data (read non-pcap conforming data) on the pipe.
>
> Following command is being used in both the above cases to write 
> captured data on FIFO
>     "cat packets.pcap > /tmp/myfifo"   /* myfifo has been created 
> using "mknod p"*/
>
> Ironically, the file "packets.pcap" has been created after capturing 
> data on my host's network interface using *Ethereal* itself.
> ------------------------------------------------------------------
>  
> Thanks in Advance,
> Amit Dang_______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev