[Wireshark-dev] tshark statistics locales pitfall

Hi, I would like to bring a problem to attention which I encountered using the statistics feature of tshark (-z io,stat option). Even the simple example from the man page, -z io,stat,1,ip.addr==1.2.3.4 will not work if you have a locales setting where the decimal point is a comma instead of

Re: [Wireshark-dev] [Wireshark-commits] rev 20925: /trunk/ /trunk/: nio-ie5.c

Couldn't this be made to be an If-Modified-Since request instead? Luis On 2/25/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=20925 User: ulfl Date: 2007/02/25 03:44 PM Log: don't cache the downloaded file, so changes in the

[Wireshark-dev] local operation code in MAP

Hi All, Greetings to you. I'm adding an operation with local value 153 to GSMMAP. But dissector does not recognize 153, it reports Unknown -103. Kindly tell me how to set this value. Thanks, Bhavani. The information contained in this electronic message and any attachments to

[Wireshark-dev] Mixed application contexts in MAP

Hi, Can I add application context with 'iso(1)' OID along with contexts of 'itu-t(0)' OIDs in the same dissector development file? Thanks, Bhavani The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the

Re: [Wireshark-dev] [Wireshark-commits] rev 20908: /trunk/ /trunk/epan/dissectors/: packet-h248.c packet-h248.h packet-h248_3gpp.c packet-h248_annex_c.c packet-h248_annex_e.c packet-h248_q1950.c packe

Yes you are right I have to re-design the matching (and grouping!) of paths in an association. I did not understand from the RFC the fact that vtags were relative just to a direction of a path and not to all the paths of one direction in an association. As soon as I started to analyze captures

Re: [Wireshark-dev] [Wireshark-commits] rev 20925: /trunk/ /trunk/: nio-ie5.c

Luis Ontanon wrote: Couldn't this be made to be an If-Modified-Since request instead? Possibly later. But it's currently to avoid problems while experimenting. There will be a lot more changes to be done before this is going to be released. Regards, ULFL

Re: [Wireshark-dev] local operation code in MAP

Hi, What is the hex value shown in the bytes pane when marking localvalue in the middle pane? Best regards Anders Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För [EMAIL PROTECTED] Skickat: den 25 februari 2007 10:06 Till: wireshark-dev@wireshark.org

Re: [Wireshark-dev] Mixed application contexts in MAP

Hi,, I’m not sure what you want but see: register_ber_oid_dissector(1.3.12.2.1006.53.2.1.3, dissect_gsm_mapext_PlmnContainer, in the packet-gsm_map-template.c file and PlmnContainer in the asn1 file. Best regards Anders _ Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För

Re: [Wireshark-dev] [Wireshark-commits] rev 20908: /trunk/ /trunk/epan/dissectors/: packet-h248.c packet-h248.h packet-h248_3gpp.c packet-h248_annex_c.c packet-h248_annex_e.c packet-h248_q1950.c packe

Hi Luis, see my comments in-line. Best regards Michael On Feb 25, 2007, at 6:20 PM, Luis Ontanon wrote: Yes you are right I have to re-design the matching (and grouping!) of paths in an association. I did not understand from the RFC the fact that vtags were relative just to a direction of

Re: [Wireshark-dev] [PATCH] New menu items to copy packet data

Luis Ontanon wrote: I backed up the changes I made. And now it looks fine at least to me. BTW I'd love if someone with some knowledge of the way menus work could explain to me why I got that broken... and why adding the Tools menu did not. Luis On 2/20/07, Luis Ontanon [EMAIL PROTECTED]