[Wireshark-dev] IMS-Information AVP not correctly parsed

2007-07-05 Thread cco
hi! the following avp: IMS-Information(876) defined by 3gpp for the rf interface is not correctly parsed by my wireshark (Version 0.99.4) anyone having the same problem? any quick fix? thanks! bye now! cristian ___ Wireshark-dev mailing list

Re: [Wireshark-dev] IMS-Information AVP not correctly parsed

2007-07-05 Thread Martin Mathieson
Assuming you're using xmllib, the quick fix for you would be to remove the IMS-Information entry from diameter/chargecontrol.xml and rely upon the better-looking entry in dictionary.xml. I'm not sure why these AVPs are defined in both places Martin On 7/5/07, cco [EMAIL PROTECTED] wrote:

Re: [Wireshark-dev] [PATCH] Add option to show unexpected BER data

2007-07-05 Thread Anders Broman
Committed revision 22244. Regards Anders -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Stig Bjørlykke Skickat: den 28 juni 2007 13:48 Till: Developer support list for Wireshark Ämne: [Wireshark-dev] [PATCH] Add option to show unexpected BER data Hi.

Re: [Wireshark-dev] IMS-Information AVP not correctly parsed

2007-07-05 Thread cco
On Thu, Jul 05, 2007 at 01:40:55PM +0100, Martin Mathieson wrote: Assuming you're using xmllib, the quick fix for you would be to remove the IMS-Information entry from diameter/chargecontrol.xml and rely upon the better-looking entry in dictionary.xml. I'm not sure why these AVPs are defined

Re: [Wireshark-dev] IMS-Information AVP not correctly parsed

2007-07-05 Thread Martin Mathieson
Change the type-name attribute to Time. Someone (maybe me, but not for a few days at best) needs to rationalise these duplicated AVPs (between dictionary.xml and chargecontrol.xml). Anders? If you get it dissecting nicely there, please do send patches to this list! Martin On 7/5/07, cco

Re: [Wireshark-dev] how to disable dissectors when I build TShark ?

2007-07-05 Thread Jean-Grégoire Foulon
On 7/5/07, Shehjar Tikoo [EMAIL PROTECTED] wrote: Jean-Grégoire Foulon wrote: I just managed to have a lib 50% smaller by removing some protocols. I will try to post a diff file here (or somewhere else) when I have a satisfying result. I think it can be useful for people trying to get a

[Wireshark-dev] diameter dissector and ntp timestamp rollover

2007-07-05 Thread cco
hi! the people designing ntp came up with a timestamp format which rolls over every 136 years (weren't there already so many broken timestamp formats?). here is the an execerpt from rfc2030 which clarifies things: As the NTP timestamp format has been in use for the last 17 years, it

Re: [Wireshark-dev] IMS-Information AVP not correctly parsed

2007-07-05 Thread cco
On Thu, Jul 05, 2007 at 04:58:17PM +0100, Martin Mathieson wrote: Change the type-name attribute to Time. Someone (maybe me, but not for a few days at best) needs to rationalise these duplicated AVPs (between dictionary.xml and chargecontrol.xml). Anders? If you get it dissecting nicely

Re: [Wireshark-dev] how to disable dissectors when I build TShark ?

2007-07-05 Thread Guy Harris
Jean-Grégoire Foulon wrote: -The Arp dissector is linked to arcnet because it calls dissector_add( arcnet.protocol_id, ARCNET_PROTO_ARP_1051, arp_handle); it is hard to detect, and I don't know if there would be an easy way to modify Wireshark code to avoid such dependencies. One

Re: [Wireshark-dev] diameter dissector and ntp timestamp rollover

2007-07-05 Thread Jaap Keuter
Hi, You could play around with ntp_fmt_ts(const guint8 *reftime) and see what happens. That function is found in packet-ntp.c and the source for the code in packet-diameter.c. Thanx, Jaap cco wrote: hi! the people designing ntp came up with a timestamp format which rolls over every 136