See inline comments:
>-----Original Message-----
>From: ethereal-users-bounces@xxxxxxxxxxxx
>[mailto:ethereal-users-bounces@xxxxxxxxxxxx]On Behalf Of Michael Kopp
>Sent: den 21 februari 2005 08:28
>To: ethereal-users@xxxxxxxxxxxx
>Subject: [Ethereal-users] Ethereal crashes when Diameter spans multiple
>TCPpackets
>
>
>Hi all,
>
>somebody maybe could have a look at this, Ethereal crashes when a diameter
>message spans multiple TCP packets and Diameter option "Reassemble Diameter
>messages spanning multiple TCP segments" is enabled. This happens only on
>Windows (tested with 0.10.6 / 0.10.9 / 0.10.9-SVN-13371 ). With Linux
>everything works fine.
>
>I`m sorry that I can`t provide any sample trace, cause it includes too many
>confidential data, but maybe somebody could see something with this
>pointers. I also tested on Linux (0.10.6 and 0.10.9) and there Ethereal does
>not crash.
Works on my traces on Windows, could it be libxml related?
>What else I noticed : My Diameter Application runs on 3868 and it seems some
>of my Diameter packets are only recognized as TCP and not as Diameter , I
>suspect this happens as I disabled the reassembly when diameter spans
>multiple segments ?
Yes
>(TCP/SCTP Port 3868 seems to be the new RFC assigned port , see RFC 3588
>Diameter Base Protocol - Section 2.1
>>2.1. Transport
>>
>> Transport profile is defined in [AAATRANS].
>>
>> The base Diameter protocol is run on port 3868 of both TCP [TCP] and
>> SCTP [SCTP] transport protocols.
>should this be changed in Ethereal (currently 1812 is the predefined port
>used by Diameter)
>)
The port used is configurable so this shoulden't be a big problem.
>One more thing, it seems that libxml2 is not included with the standard
>Ethereal Setup (at least not on Windows) is there any reason, I could not
>find any on the mailing list archives ? Maybe it is good to put a message
>somewhere in Diameter preferences or somewhere else that this library is not
>included but is needed for parsing the Diameter stuff ?
This is a licencing issue i belive, note however that libxml is NOT needed to dissect Diameter
messages, actually the value strings containing Diameter "translations" is more up to date than the
XML dictionary is. The only reason for using libxml is if you have a dictionary for private AVP:s I think.
You do get a warning that libxml is not present when loding a Diameter trace isn't that enough?
>Michael
>Ethereal - one of the best pieces of software I´ve ever seen !!!
--
Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users