Re: [Wireshark-dev] PortableApps build failure with SVN 24028

2008-01-08 Thread Joerg Mayer
On Tue, Jan 08, 2008 at 08:27:03AM +0100, Graeme Lunt wrote: (The fix is to cd back to ../portableapps/win32, rather than ../u3/win32, at the end of the nsis-bits target in makefile.nmake.) Committed revision 24031. -- Joerg Mayer [EMAIL PROTECTED] We

[Wireshark-dev] 3GPP RLC and MAC protocols support

2008-01-08 Thread munish . dayal
Hi, Is anybody working on dissectors for 3GPP-UMTS- RLC and MAC protocols ? Or are these dissectors already available somewhere ? Thanks Regards, Munish *** Aricent-Unclassified *** DISCLAIMER: This message is proprietary to Aricent and is

[Wireshark-dev] bytes

2008-01-08 Thread bijjou2000
hi I want spend a 9 bytes address as a hex value (0x. ) , I tried as follows; proto_tree_add_bytes_format_value(lon_tree, hf_unicast, tvb, offset,9,lon_unicast,0xX,lon_unicast); { hf_unicast, { Unicast, lon.Unicast, FT_BYTES, BASE_HEX ,NULL, 0x0, unicast,

Re: [Wireshark-dev] bytes

2008-01-08 Thread bijjou2000
i do the same as you. the problem is the zero in behind of the address. can you tell me witch tvb_get_funktion is right in this case. De: [EMAIL PROTECTED] A: wireshark-dev@wireshark.org Objet: Re: [Wireshark-dev] bytes Date: Tue, 8 Jan 2008 18:32:25 +0530 While trying to

Re: [Wireshark-dev] bytes

2008-01-08 Thread Abhik Sarkar
Hi, Perhaps what you can try is something like this: - tvb_memcpy the 9 address bytes into a new byte array (let's say the array is called address_bytes). - then use something like this: proto_tree_add_bytes_format_value(lon_tree, hf_unicast, tvb,

Re: [Wireshark-dev] 3GPP RLC and MAC protocols support

2008-01-08 Thread Neil Piercy
I'm looking at the same issue for my company and came to similar conclusion. At present we've gone down the route of (c) for a quick try, but I think it will soon be coming unstuck - it certainly isn't general enough to feed back yet. We haven't yet got any MAC/RLC dissection, but would be happy

Re: [Wireshark-dev] 3GPP RLC and MAC protocols support

2008-01-08 Thread Martin Mathieson
On Jan 8, 2008 6:05 PM, Neil Piercy [EMAIL PROTECTED] wrote: I'm looking at the same issue for my company and came to similar conclusion. At present we've gone down the route of (c) for a quick try, but I think it will soon be coming unstuck - it certainly isn't general enough to feed back

Re: [Wireshark-dev] bytes

2008-01-08 Thread bijjou2000
hi i have try it as follows, but it don't work : guint8 address_bytes; guint8 lon_unicast; tvb_memcpy(tvb,(guint8 *)lon_unicast, offset, 9); proto_tree_add_bytes_format_value(lon_tree, hf_unicast, tvb, offset,9,lon_unicast,0x%s,bytes_to_str(address_bytes,9)); {hf_unicast, {unicast;

Re: [Wireshark-dev] 3GPP RLC and MAC protocols support

2008-01-08 Thread Anders Broman
Hi, In rrc.cnf do something similar to whats done in RANAP --- Snip from ranap.cnf --- #.FN_BODY NAS-PDU VAL_PTR = nas_pdu_tvb tvbuff_t *nas_pdu_tvb=NULL; %(DEFAULT_BODY)s if (nas_pdu_tvb) dissector_try_port(nas_pdu_dissector_table, 0x1, nas_pdu_tvb,

[Wireshark-dev] ENC: Wireshark-dev: Re: RTCP frame length error indication in RTCP with a Bye chunk

2008-01-08 Thread Herculano Antonio Lambert Duarte
Hi! Sorry for the delay. Attached is a packet with a RTCP Bye, and the error indication. Thank you for your attention. Best regards, Herculano =

Re: [Wireshark-dev] 3GPP RLC and MAC protocols support

2008-01-08 Thread munish . dayal
Hi, My requirement is basically the whole stack (no ciphering for the time being). RRC RLC MAC FP UDP Could you pls share the details of the approach you took with FP. What kind of filled-in-struct, and how it can be filled from NBAP configuration messages. For RLC/MAC also, I

Re: [Wireshark-dev] ENC: Wireshark-dev: Re: RTCP frame length error indication in RTCP with a Bye chunk

2008-01-08 Thread Jaap Keuter
Hi, That string isn't NULL terminated, but the code expects it to be. See packet-rtcp.c:dissect_rtcp_bye(). It even counts that NULL byte, which doesn't exist. Then the BYE message is expected to be padded out to fit word size. Counting the non existing NULL byte makes it pad 3 more bytes to