Ethereal-users: RE: [Ethereal-users] "Short Frame: Diameter" Problem

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: João Boto Correia <joao.correia@xxxxxxxxxx>
Date: Thu, 28 Oct 2004 10:15:03 +0100
Title: Message
Good morning,
 
Thanks a lot. It worked.
 
I would like to ask you the following: I am working with a vendor-specific implementation of Diameter. Some AVP's are specific to this vendor, meaning that Ethereal does not recognise some of them.
 
Is there anyway to "make" ethereal able to decode these vendor-specific AVP's? Can I contribute to this in some way?
 
Regards.
 
JMC
-----Original Message-----
From: Martin Regner [mailto:martin.regner@xxxxxxxxx]
Sent: quarta-feira, 27 de Outubro de 2004 18:15
To: Ethereal user support
Cc: João Boto Correia
Subject: Re: [Ethereal-users] "Short Frame: Diameter" Problem

 
You should also check the following preference setting:
 
Edit---->Prefrences---->Protocols---->TCP: Allow subbdisector to reassemble TCP streams 
 
The checkbox also needs to be checked in order to get Diameter over TCP to be reassembled.
 
 
----- Original Message -----
Sent: Wednesday, October 27, 2004 5:03 PM
Subject: RE: [Ethereal-users] "Short Frame: Diameter" Problem

Hi,
In the Edit->preferences-> open protocols go to Diameter and tick the box Reassemble Diameter messages...
 
Best regards
Anders
-----Original Message-----
From: ethereal-users-bounces@xxxxxxxxxxxx [mailto:ethereal-users-bounces@xxxxxxxxxxxx]On Behalf Of João Boto Correia
Sent: den 27 oktober 2004 16:20
To: ethereal-users@xxxxxxxxxxxx
Subject: [Ethereal-users] "Short Frame: Diameter" Problem


Hello,

I am using ethereal (version 0.10.7) to analize some Diameter messages.

However, the messages with record-type=INTERIM_RECORD are not being completely captured and they are labeled as "[Short Frame: Diameter]".

I tried to suppress some AVP's from the message and in that case the frame is being correctly captured. Is this related with the size of the frame (I am not limiting the packets size when capturing the traffic)?

I have attached an example.
<<TC_1.4.1.1.1.1.eth>>
Does anybody know how to solve this?

Thanks for any help.

João Correia
OPTIMUS
TD/EDD/COREIN
M       :       +351931013599
F       :       +351931023599

_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users