Title: RE: [Ethereal-users] AAL5 CRC decoding
Thanks for the reply.. It actually very well explains the behaviour...
This leads to the questions:
- whether there is a tool to convert the raw packet decode into one of the 2 format you are specifying (Already tried to google a bit unsuccessfully)
- of if a tool does not exist, if we know the format of the capture files of Endace or Windows sniffer so I can artificially generate one with a bit of perl ;-).
Thx a lot for your answers.
S.
-----Original Message-----
From: ethereal-users-bounces@xxxxxxxxxxxx [mailto:ethereal-users-bounces@xxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: 12 May 2004 10:52
To: Ethereal user support
Subject: Re: [Ethereal-users] AAL5 CRC decoding
On Tue, May 11, 2004 at 06:46:34PM +0100, Serge L'Hermitte wrote:
> I just imported via text2pcap some AAL5 frames... Ethereal is decoding
> them right EXCEPT it does not treat some additional fields of the AAL5
> frame (like its CRC32 for example or its length).
text2pcap converts to libpcap format, and the only form of raw ATM currently supported in libpcap files is a format for SunATM, and SunATM does not supply the AAL5 trailer, so Ethereal does not expect to see an AAL5 trailer in libpcap ATM captures.
You'd have to convert the capture to the Windows Sniffer format or the Endace ERF format in order to get Ethereal to handle the AAL5 trailer.
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx http://www.ethereal.com/mailman/listinfo/ethereal-users
