Hi, community, I'm using 1.4.3 to trace the ULP message between two testing nodes, but found that it will report Malformed Packet: ULP error. [Malformed Packet: ULP] Expert Info (Error/Malformed): Malformed Packet (Exception occurred) Message: Malformed Packet (Exception occurred) Severity level: Error Group: Malformed even the msisdn part cannot be decoded successfully, does anyone know the ULP protocol version supported in 1.4.3? 0000 00 26 02 00 00 c0 00 41 90 1c 44 c9 53 ff ff ff 0010 ff ff ff fc 05 55 03 37 40 05 80 03 84 40 0f 00 0020 b0 00 28 64 00 80 asked 17 Jan '11, 22:41  eyimjia |
One Answer:
From the asn1 spec in wireshark/asn1/ulp -- Taken from OMA UserPlane Location Protocol -- http://www.openmobilealliance.org/technical/release_program/docs/SUPL/V2_0-20080627-C/OMA-TS-ULP-V2_0-20080627-C.pdf You could open a bug report at https://bugs.wireshark.org/bugzilla/ including a small capture file ilusstrating the problem. You could also try a development version from http://www.wireshark.org/download/automated/ answered 17 Jan '11, 23:01  Anders ♦ |
Thank you for your reply, I've tried the latest development version, but it still doesn't ok, I'm not sure it's a bug or a protocol compliance issue, because the protocl version I'm using is OMA-TS-ULP-V2_0-20100806-D, more elements are added compared with 20080627-C, the error was reported on a common element that I've checked no change happened between the version I'm using and the version WireShark supports. Do you have information whether Wireshark will have any plan to upgrade the ULP version?
Hi, No plans exist to upgrade any protocol, it all depends on contributors intrested in doing the updates. You could extract the asn.1 from teh OMA spec like here http://anonsvn.wireshark.org/viewvc/trunk/asn1/ulp/ attach it to a bug report and some one might update the dissector. BTW ther seems to be a version 3 as well. If you include your failing trace some one might figure out what the problem is. Regards Anders
Please refer to https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5593 if you meet similar problem.