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

2007-02-27 Thread Anders Broman 
Hi,
My bad the complete encoding should be 02 02 88 99 ( Integer(02) length(02)
Value(88 99).
Best regards
Anders

Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Anders Broman (AL/EAB)
Skickat: den 27 februari 2007 17:55
Till: Developer support list for Wireshark
Ämne: Re: [Wireshark-dev] local operation code in MAP

Hi,
Shouldn't the encoded value be H'81 H'19(153) ?
Best regards
Anders

From: [EMAIL PROTECTED] on behalf of
[EMAIL PROTECTED]
Sent: Tue 2/27/2007 3:14 PM
To: wireshark-dev@wireshark.org
Subject: Re: [Wireshark-dev] local operation code in MAP
Hi,
 
I’ve given the value for operation code, not the ASN1 compiler.
 
I’ve tried below suggestion but still got the problem.
Operation code length : 02, and the operation code : H’81 H’99.
 
I tried to print the opcode value read from dissect_ber_integer,
dissect_ber_integer64
They print negative number for int format & huge positive number for
unsigned format.
 
Best Regards,
Bhavani.
 
 
 
From: [EMAIL PROTECTED]
Date: Tue, 27 Feb 2007 13:05:42 +0100

  Hi,
 
You said:
"Hex value shown, in the bytes pane is 99."
Is this value field by yourself, or by an ASN1 compiler ?
I think, It could be a problem of long form encoding.
Could you try to use H'81 H'99 instead of H'99 for the operation code in
the message to decode ?
 
Regards
Florent
 

From: DurgaBhavani Uppuluru 
Sent: Tuesday, February 27, 2007 12:08 PM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP
 
Hi Again,
 
I’ve tried latest svn version files too, still I get the same problem.
I’ve added gsmmap, ranap directories & packet-gtp.c from svn Revision 20934,
on top of wireshark-0.99.5 sources.
 
Please help me.
 
Best Regards,
Bhavani.

From: DurgaBhavani Uppuluru 
Sent: Tuesday, February 27, 2007 9:41 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP
 
Hi,
 
I’m using wireshark 0.99.5 sources.
The below code is right. 
I’ve added the operations in the same way.
 
Here are the steps followed:
 
My GSMMAP.asn files looks
 
1. OperationLocalvalue ::= INTEGER{
    updateLocation (2),
    :
    noteMM-Event (89),
    operation1(152),
    operation2(153)
}
 
2. Operation descriptions of operation1 & operation2 are added
 
3. packet-gsm_map-template.c is updated with
 
gsm_map_opr_code_strings[]={
{   2, "updateLocation" },
:
{   152, "operation1" },
{   153, "operation2" }
}
 
dissect_invokeData()
switch(opcode){
  case  2: /*updateLocation*/ dissect_gsm_map_UpdateLocationArg();  break;
    :
  case 152: /*operation 1*/ dissect_gsm_map_Operation1Arg(); break;
  case 153: /*operation 2*/ dissect_gsm_map_Operation2Arg(); break;
}
return offset;
}
    
3. makefile is used to generate packet-gsm_map.c, packet-gsm_map.h.
Options used with asn2wrs are:
python ../../tools/asn2wrs.py -b -e -p gsm_map -c gsmmap.cnf -s
packet-gsm_map-template GSMMAP.asn
 
4. Generated packet-gsm_map.c, packet-gsm_map.h are copied to
../../epan/dissectors folder.
Standard makefile present in the wireshark-0.99.5 directory is used to build
the wireshark exe.
 
The same steps when followed with operation codes with 90,91 or 94,95  work
fine.
 
Thanks for your time.
 
Best Regards,
Bhavani.
 
From: "Anders Broman \(AL/EAB\)" <[EMAIL PROTECTED]>
Date: Mon, 26 Feb 2007 16:21:09 +0100
Hi,
Are you running the latest SVN version of Wireshark?
I asume that "adding an operation with local value 153 to GSMMAP" means that
you are editing the sources,
what happens if you change:
GSMMAPOperationLocalvalue ::= INTEGER{
 updateLocation (2),
:
 noteMM-Event (89)
    } 
To:
 noteMM-Event (89),
 your-string(153)
    } 
in GSMMAP.asn and rebuild the dissector using asn2wrs?
Best regards
Anders
 

From: DurgaBhavani Uppuluru 
Sent: Monday, February 26, 2007 10:46 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP
 
Hi Anders,
 
Hex value shown, in the bytes pane is 99.
I’ve tried other numbers too (>150) and I get similar result.
 
Best Regards,
Bhavani.
 
From: "Anders Broman" <[EMAIL PROTECTED]>
Date: Sun, 25 Feb 2007 19:55:43 +0100
Hi,
What is the hex value shown in the bytes pane when marking localvalue in the
middle pane?
Best regards
Anders
 

From: DurgaBhavani Uppuluru
Sent: Sunday, February 25, 2007 2:36 PM
To: 'wireshark-dev@wireshark.org'
Subject: 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 valu

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

2007-02-27 Thread Anders Broman \(AL/EAB\) 
Hi,
Shouldn't the encoded value be H'81 H'19(153) ?
Best regards
Anders



From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED]
Sent: Tue 2/27/2007 3:14 PM
To: wireshark-dev@wireshark.org
Subject: Re: [Wireshark-dev] local operation code in MAP



Hi,

 

I've given the value for operation code, not the ASN1 compiler.

 

I've tried below suggestion but still got the problem.

Operation code length : 02, and the operation code : H'81 H'99.

 

I tried to print the opcode value read from dissect_ber_integer, 
dissect_ber_integer64

They print negative number for int format & huge positive number for unsigned 
format.

 

Best Regards,

Bhavani.

 

 

 

From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
Date: Tue, 27 Feb 2007 13:05:42 +0100




  Hi,
 
You said:
"Hex value shown, in the bytes pane is 99."
Is this value field by yourself, or by an ASN1 compiler ?
I think, It could be a problem of long form encoding.
Could you try to use H'81 H'99 instead of H'99 for the operation code in
the message to decode ?
 
Regards
Florent

 



From: DurgaBhavani Uppuluru 
Sent: Tuesday, February 27, 2007 12:08 PM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi Again,

 

I've tried latest svn version files too, still I get the same problem.

I've added gsmmap, ranap directories & packet-gtp.c from svn Revision 20934, on 
top of wireshark-0.99.5 sources.

 

Please help me.

 

Best Regards,

Bhavani.



From: DurgaBhavani Uppuluru 

Sent: Tuesday, February 27, 2007 9:41 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi,

 

I'm using wireshark 0.99.5 sources.

The below code is right. 

I've added the operations in the same way.

 

Here are the steps followed:

 

My GSMMAP.asn files looks

 

1. OperationLocalvalue ::= INTEGER{

updateLocation (2),

:

noteMM-Event (89),

operation1(152),

operation2(153)

}

 

2. Operation descriptions of operation1 & operation2 are added

 

3. packet-gsm_map-template.c is updated with

 

gsm_map_opr_code_strings[]={

{   2, "updateLocation" },

:

{   152, "operation1" },

{   153, "operation2" }

}

 

dissect_invokeData()

switch(opcode){

  case  2: /*updateLocation*/ dissect_gsm_map_UpdateLocationArg();  break;

:

  case 152: /*operation 1*/ dissect_gsm_map_Operation1Arg(); break;

  case 153: /*operation 2*/ dissect_gsm_map_Operation2Arg(); break;

}

return offset;

}



3. makefile is used to generate packet-gsm_map.c, packet-gsm_map.h.

Options used with asn2wrs are:

python ../../tools/asn2wrs.py -b -e -p gsm_map -c gsmmap.cnf -s 
packet-gsm_map-template GSMMAP.asn

 

4. Generated packet-gsm_map.c, packet-gsm_map.h are copied to 
../../epan/dissectors folder.

Standard makefile present in the wireshark-0.99.5 directory is used to build 
the wireshark exe.

 

The same steps when followed with operation codes with 90,91 or 94,95  work 
fine.

 

Thanks for your time.

 

Best Regards,

Bhavani.

 

From: "Anders Broman \(AL/EAB\)" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
Date: Mon, 26 Feb 2007 16:21:09 +0100

Hi,

Are you running the latest SVN version of Wireshark?

I asume that "adding an operation with local value 153 to GSMMAP" means that 
you are editing the sources,

what happens if you change:

GSMMAPOperationLocalvalue ::= INTEGER{
 updateLocation (2),

:

 noteMM-Event (89)
} 

To:

 noteMM-Event (89),

 your-string(153)
} 

in GSMMAP.asn and rebuild the dissector using asn2wrs?

Best regards

Anders

 



From: DurgaBhavani Uppuluru 

Sent: Monday, February 26, 2007 10:46 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi Anders,

 

Hex value shown, in the bytes pane is 99.

I've tried other numbers too (>150) and I get similar result.

 

Best Regards,

Bhavani.

 

From: "Anders Broman" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
Date: Sun, 25 Feb 2007 19:55:43 +0100

Hi,
What is the hex value shown in the bytes pane when marking localvalue in the
middle pane?
Best regards
Anders

 



From: DurgaBhavani Uppuluru
Sent: Sunday, February 25, 2007 2:36 PM
To: 'wireshark-dev@wireshark.org'
Subject: 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 
this message are intended for the exclusive

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

2007-02-27 Thread Florent . Drouin 


Right, I did check the encoding of an integer value:

Integer Value   Ber Encoding
0 02 01 00
127   02 01 7F
128   02 02 00 80
256   02 02 01 00
-128  02 01 80

Regards
Florent




  <[EMAIL PROTECTED]
  
  ipro.com>To:  
   
  Sent by: cc:  

  [EMAIL PROTECTED] Subject: Re: [Wireshark-dev] 
local operation code in MAP 
  reshark.org   





  27/02/2007 15:46  

  Please respond to 

  Developer support list

  for Wireshark 







Hi,

I've made the following changes in the packet:
opcode length : 2 bytes
opcode value : 00 99.

It works.

Thanks a lot for your help.

Regards,
Bhavani.

From: DurgaBhavani Uppuluru
Sent: Tuesday, February 27, 2007 7:44 PM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

Hi,

I've given the value for operation code, not the ASN1 compiler.

I've tried below suggestion but still got the problem.
Operation code length : 02, and the operation code : H'81 H'99.

I tried to print the opcode value read from dissect_ber_integer,
dissect_ber_integer64
They print negative number for int format & huge positive number for
unsigned format.

Best Regards,
Bhavani.



From: [EMAIL PROTECTED]
Date: Tue, 27 Feb 2007 13:05:42 +0100

  Hi,

You said:
"Hex value shown, in the bytes pane is 99."
Is this value field by yourself, or by an ASN1 compiler ?
I think, It could be a problem of long form encoding.
Could you try to use H'81 H'99 instead of H'99 for the operation code in
the message to decode ?

Regards
Florent


From: DurgaBhavani Uppuluru
Sent: Tuesday, February 27, 2007 12:08 PM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

Hi Again,

I've tried latest svn version files too, still I get the same problem.
I've added gsmmap, ranap directories & packet-gtp.c from svn Revision
20934, on top of wireshark-0.99.5 sources.

Please help me.

Best Regards,
Bhavani.

From: DurgaBhavani Uppuluru
Sent: Tuesday, February 27, 2007 9:41 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

Hi,

I'm using wireshark 0.99.5 sources.
The below code is right.
I've added the operations in the same way.

Here are the steps followed:

My GSMMAP.asn files looks

1. OperationLocalvalue ::= INTEGER{
updateLocation (2),
:
noteMM-Event (89),
operation1(152),
operation2(153)
}

2. Operation descriptions of operation1 & operation2 are added

3. packet-gsm_map-template.c is updated with

gsm_map_opr_code_strings[]={
{   2, "updateLocation" },
:
{   152, "operation1" },
{   153, "operation2" }
}

dissect_invokeData()
switch(opcode){
  case  2: /*updateLocation*/ dissect_gsm_map_UpdateLocationArg();  break;
:
  case 152: /*operation 1*/ dissect_gsm_map_Operation1Arg(); break;
  case 153: /*operation 2*/ dissect_gsm_map_Operation2Arg(); break;
}
return offset;
}

3. makefile is used to generate packet-gsm_map.c, packet-gsm_map.h.
Options used with asn2wrs are:
python ../../tools/asn2wrs.py -b -e -p gsm_map -c gsmmap.cnf -s
packet-gsm_map-template GSMMAP.asn

4. Generated packet-gsm_map.c, packet-gsm_map.h are copied to
../../epan/dissectors folder.
Standard makefile present in the wireshark-0.99.5 directory is used to
build the wireshark exe.

The same steps when followed with operation codes with 90,91 or 94,95  w

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

2007-02-27 Thread durgabhavani.uppuluru 

Hi,

 

I've made the following changes in the packet:

opcode length : 2 bytes

opcode value : 00 99.

 

It works.

 

Thanks a lot for your help.

 

Regards,

Bhavani.



From: DurgaBhavani Uppuluru 

Sent: Tuesday, February 27, 2007 7:44 PM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi,

 

I've given the value for operation code, not the ASN1 compiler.

 

I've tried below suggestion but still got the problem.

Operation code length : 02, and the operation code : H'81 H'99.

 

I tried to print the opcode value read from dissect_ber_integer,
dissect_ber_integer64

They print negative number for int format & huge positive number for
unsigned format.

 

Best Regards,

Bhavani.

 

 

 

From: [EMAIL PROTECTED]
 
Date: Tue, 27 Feb 2007 13:05:42 +0100



  Hi,
 
You said:
"Hex value shown, in the bytes pane is 99."
Is this value field by yourself, or by an ASN1 compiler ?
I think, It could be a problem of long form encoding.
Could you try to use H'81 H'99 instead of H'99 for the operation code in
the message to decode ?
 
Regards
Florent

 



From: DurgaBhavani Uppuluru 
Sent: Tuesday, February 27, 2007 12:08 PM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi Again,

 

I've tried latest svn version files too, still I get the same problem.

I've added gsmmap, ranap directories & packet-gtp.c from svn Revision
20934, on top of wireshark-0.99.5 sources.

 

Please help me.

 

Best Regards,

Bhavani.



From: DurgaBhavani Uppuluru 

Sent: Tuesday, February 27, 2007 9:41 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi,

 

I'm using wireshark 0.99.5 sources.

The below code is right. 

I've added the operations in the same way.

 

Here are the steps followed:

 

My GSMMAP.asn files looks

 

1. OperationLocalvalue ::= INTEGER{

updateLocation (2),

:

noteMM-Event (89),

operation1(152),

operation2(153)

}

 

2. Operation descriptions of operation1 & operation2 are added

 

3. packet-gsm_map-template.c is updated with

 

gsm_map_opr_code_strings[]={

{   2, "updateLocation" },

:

{   152, "operation1" },

{   153, "operation2" }

}

 

dissect_invokeData()

switch(opcode){

  case  2: /*updateLocation*/ dissect_gsm_map_UpdateLocationArg();
break;

:

  case 152: /*operation 1*/ dissect_gsm_map_Operation1Arg(); break;

  case 153: /*operation 2*/ dissect_gsm_map_Operation2Arg(); break;

}

return offset;

}



3. makefile is used to generate packet-gsm_map.c, packet-gsm_map.h.

Options used with asn2wrs are:

python ../../tools/asn2wrs.py -b -e -p gsm_map -c gsmmap.cnf -s
packet-gsm_map-template GSMMAP.asn

 

4. Generated packet-gsm_map.c, packet-gsm_map.h are copied to
../../epan/dissectors folder.

Standard makefile present in the wireshark-0.99.5 directory is used to
build the wireshark exe.

 

The same steps when followed with operation codes with 90,91 or 94,95
work fine.

 

Thanks for your time.

 

Best Regards,

Bhavani.

 

From: "Anders Broman \(AL/EAB\)" <[EMAIL PROTECTED]
 >
Date: Mon, 26 Feb 2007 16:21:09 +0100

Hi,

Are you running the latest SVN version of Wireshark?

I asume that "adding an operation with local value 153 to GSMMAP" means
that you are editing the sources,

what happens if you change:

GSMMAPOperationLocalvalue ::= INTEGER{
 updateLocation (2),

:

 noteMM-Event (89)
} 

To:

 noteMM-Event (89),

 your-string(153)
} 

in GSMMAP.asn and rebuild the dissector using asn2wrs?

Best regards

Anders

 



From: DurgaBhavani Uppuluru 

Sent: Monday, February 26, 2007 10:46 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi Anders,

 

Hex value shown, in the bytes pane is 99.

I've tried other numbers too (>150) and I get similar result.

 

Best Regards,

Bhavani.

 

From: "Anders Broman" <[EMAIL PROTECTED]
 >
Date: Sun, 25 Feb 2007 19:55:43 +0100

Hi,
What is the hex value shown in the bytes pane when marking localvalue in
the
middle pane?
Best regards
Anders

 



From: DurgaBhavani Uppuluru
Sent: Sunday, February 25, 2007 2:36 PM
To: 'wireshark-dev@wireshark.org'
Subject: 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 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or

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

2007-02-27 Thread durgabhavani.uppuluru 

Hi,

 

I've given the value for operation code, not the ASN1 compiler.

 

I've tried below suggestion but still got the problem.

Operation code length : 02, and the operation code : H'81 H'99.

 

I tried to print the opcode value read from dissect_ber_integer,
dissect_ber_integer64

They print negative number for int format & huge positive number for
unsigned format.

 

Best Regards,

Bhavani.

 

 

 

From: [EMAIL PROTECTED]
 
Date: Tue, 27 Feb 2007 13:05:42 +0100




  Hi,
 
You said:
"Hex value shown, in the bytes pane is 99."
Is this value field by yourself, or by an ASN1 compiler ?
I think, It could be a problem of long form encoding.
Could you try to use H'81 H'99 instead of H'99 for the operation code in
the message to decode ?
 
Regards
Florent

 



From: DurgaBhavani Uppuluru 
Sent: Tuesday, February 27, 2007 12:08 PM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi Again,

 

I've tried latest svn version files too, still I get the same problem.

I've added gsmmap, ranap directories & packet-gtp.c from svn Revision
20934, on top of wireshark-0.99.5 sources.

 

Please help me.

 

Best Regards,

Bhavani.



From: DurgaBhavani Uppuluru 

Sent: Tuesday, February 27, 2007 9:41 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi,

 

I'm using wireshark 0.99.5 sources.

The below code is right. 

I've added the operations in the same way.

 

Here are the steps followed:

 

My GSMMAP.asn files looks

 

1. OperationLocalvalue ::= INTEGER{

updateLocation (2),

:

noteMM-Event (89),

operation1(152),

operation2(153)

}

 

2. Operation descriptions of operation1 & operation2 are added

 

3. packet-gsm_map-template.c is updated with

 

gsm_map_opr_code_strings[]={

{   2, "updateLocation" },

:

{   152, "operation1" },

{   153, "operation2" }

}

 

dissect_invokeData()

switch(opcode){

  case  2: /*updateLocation*/ dissect_gsm_map_UpdateLocationArg();
break;

:

  case 152: /*operation 1*/ dissect_gsm_map_Operation1Arg(); break;

  case 153: /*operation 2*/ dissect_gsm_map_Operation2Arg(); break;

}

return offset;

}



3. makefile is used to generate packet-gsm_map.c, packet-gsm_map.h.

Options used with asn2wrs are:

python ../../tools/asn2wrs.py -b -e -p gsm_map -c gsmmap.cnf -s
packet-gsm_map-template GSMMAP.asn

 

4. Generated packet-gsm_map.c, packet-gsm_map.h are copied to
../../epan/dissectors folder.

Standard makefile present in the wireshark-0.99.5 directory is used to
build the wireshark exe.

 

The same steps when followed with operation codes with 90,91 or 94,95
work fine.

 

Thanks for your time.

 

Best Regards,

Bhavani.

 

From: "Anders Broman \(AL/EAB\)" <[EMAIL PROTECTED]
 >
Date: Mon, 26 Feb 2007 16:21:09 +0100

Hi,

Are you running the latest SVN version of Wireshark?

I asume that "adding an operation with local value 153 to GSMMAP" means
that you are editing the sources,

what happens if you change:

GSMMAPOperationLocalvalue ::= INTEGER{
 updateLocation (2),

:

 noteMM-Event (89)
} 

To:

 noteMM-Event (89),

 your-string(153)
} 

in GSMMAP.asn and rebuild the dissector using asn2wrs?

Best regards

Anders

 



From: DurgaBhavani Uppuluru 

Sent: Monday, February 26, 2007 10:46 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi Anders,

 

Hex value shown, in the bytes pane is 99.

I've tried other numbers too (>150) and I get similar result.

 

Best Regards,

Bhavani.

 

From: "Anders Broman" <[EMAIL PROTECTED]
 >
Date: Sun, 25 Feb 2007 19:55:43 +0100

Hi,
What is the hex value shown in the bytes pane when marking localvalue in
the
middle pane?
Best regards
Anders

 



From: DurgaBhavani Uppuluru
Sent: Sunday, February 25, 2007 2:36 PM
To: 'wireshark-dev@wireshark.org'
Subject: 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 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
em

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

2007-02-27 Thread Florent . Drouin 

  Hi,

You said:
"Hex value shown, in the bytes pane is 99."
Is this value field by yourself, or by an ASN1 compiler ?
I think, It could be a problem of long form encoding.
Could you try to use H'81 H'99 instead of H'99 for the operation code in
the message to decode ?

Regards
Florent







  <[EMAIL PROTECTED]
  
  ipro.com>To:  
   
  Sent by: cc:  

  [EMAIL PROTECTED]         Subject: Re: [Wireshark-dev] 
local operation code in MAP 
  reshark.org   





  27/02/2007 07:37  

  Please respond to 

  Developer support list

  for Wireshark 







Hi Again,

I've tried latest svn version files too, still I get the same problem.
I've added gsmmap, ranap directories & packet-gtp.c from svn Revision
20934, on top of wireshark-0.99.5 sources.

Please help me.

Best Regards,
Bhavani.

From: DurgaBhavani Uppuluru
Sent: Tuesday, February 27, 2007 9:41 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

Hi,

I'm using wireshark 0.99.5 sources.
The below code is right.
I've added the operations in the same way.

Here are the steps followed:

My GSMMAP.asn files looks

1. OperationLocalvalue ::= INTEGER{
updateLocation (2),
:
noteMM-Event (89),
operation1(152),
operation2(153)
}

2. Operation descriptions of operation1 & operation2 are added

3. packet-gsm_map-template.c is updated with

gsm_map_opr_code_strings[]={
{   2, "updateLocation" },
:
{   152, "operation1" },
{   153, "operation2" }
}

dissect_invokeData()
switch(opcode){
  case  2: /*updateLocation*/ dissect_gsm_map_UpdateLocationArg();  break;
:
  case 152: /*operation 1*/ dissect_gsm_map_Operation1Arg(); break;
  case 153: /*operation 2*/ dissect_gsm_map_Operation2Arg(); break;
}
return offset;
}

3. makefile is used to generate packet-gsm_map.c, packet-gsm_map.h.
Options used with asn2wrs are:
python ../../tools/asn2wrs.py -b -e -p gsm_map -c gsmmap.cnf -s
packet-gsm_map-template GSMMAP.asn

4. Generated packet-gsm_map.c, packet-gsm_map.h are copied to
../../epan/dissectors folder.
Standard makefile present in the wireshark-0.99.5 directory is used to
build the wireshark exe.

The same steps when followed with operation codes with 90,91 or 94,95  work
fine.

Thanks for your time.

Best Regards,
Bhavani.

From: "Anders Broman \(AL/EAB\)" <[EMAIL PROTECTED]>
Date: Mon, 26 Feb 2007 16:21:09 +0100




 Hi,
 Are you running the latest SVN version of Wireshark?   
 I asume that "adding an operation with local value 153 to GSMMAP" means
 that you are editing the sources,  
 what happens if you change:
 GSMMAPOperationLocalvalue ::= INTEGER{ 
  updateLocation (2),   
 :  
  noteMM-Event (89) 
 }  
 To:
  noteMM-Event (89),
  your-string(153)

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

2007-02-26 Thread durgabhavani.uppuluru 

Hi Again,

 

I've tried latest svn version files too, still I get the same problem.

I've added gsmmap, ranap directories & packet-gtp.c from svn Revision
20934, on top of wireshark-0.99.5 sources.

 

Please help me.

 

Best Regards,

Bhavani.



From: DurgaBhavani Uppuluru 

Sent: Tuesday, February 27, 2007 9:41 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi,

 

I'm using wireshark 0.99.5 sources.

The below code is right. 

I've added the operations in the same way.

 

Here are the steps followed:

 

My GSMMAP.asn files looks

 

1. OperationLocalvalue ::= INTEGER{

updateLocation (2),

:

noteMM-Event (89),

operation1(152),

operation2(153)

}

 

2. Operation descriptions of operation1 & operation2 are added

 

3. packet-gsm_map-template.c is updated with

 

gsm_map_opr_code_strings[]={

{   2, "updateLocation" },

:

{   152, "operation1" },

{   153, "operation2" }

}

 

dissect_invokeData()

switch(opcode){

  case  2: /*updateLocation*/ dissect_gsm_map_UpdateLocationArg();
break;

:

  case 152: /*operation 1*/ dissect_gsm_map_Operation1Arg(); break;

  case 153: /*operation 2*/ dissect_gsm_map_Operation2Arg(); break;

}

return offset;

}



3. makefile is used to generate packet-gsm_map.c, packet-gsm_map.h.

Options used with asn2wrs are:

python ../../tools/asn2wrs.py -b -e -p gsm_map -c gsmmap.cnf -s
packet-gsm_map-template GSMMAP.asn

 

4. Generated packet-gsm_map.c, packet-gsm_map.h are copied to
../../epan/dissectors folder.

Standard makefile present in the wireshark-0.99.5 directory is used to
build the wireshark exe.

 

The same steps when followed with operation codes with 90,91 or 94,95
work fine.

 

Thanks for your time.

 

Best Regards,

Bhavani.

 

From: "Anders Broman \(AL/EAB\)" <[EMAIL PROTECTED]
 >
Date: Mon, 26 Feb 2007 16:21:09 +0100



Hi,

Are you running the latest SVN version of Wireshark?

I asume that "adding an operation with local value 153 to GSMMAP" means
that you are editing the sources,

what happens if you change:

GSMMAPOperationLocalvalue ::= INTEGER{
 updateLocation (2),

:

 noteMM-Event (89)
} 

To:

 noteMM-Event (89),

 your-string(153)
} 

in GSMMAP.asn and rebuild the dissector using asn2wrs?

Best regards

Anders

 



From: DurgaBhavani Uppuluru 

Sent: Monday, February 26, 2007 10:46 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi Anders,

 

Hex value shown, in the bytes pane is 99.

I've tried other numbers too (>150) and I get similar result.

 

Best Regards,

Bhavani.

 

From: "Anders Broman" <[EMAIL PROTECTED]
 >
Date: Sun, 25 Feb 2007 19:55:43 +0100

Hi,
What is the hex value shown in the bytes pane when marking localvalue in
the
middle pane?
Best regards
Anders

 



From: DurgaBhavani Uppuluru
Sent: Sunday, February 25, 2007 2:36 PM
To: 'wireshark-dev@wireshark.org'
Subject: 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 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.
 
www.wipro.com___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev

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

2007-02-26 Thread durgabhavani.uppuluru 

Hi,

 

I'm using wireshark 0.99.5 sources.

The below code is right. 

I've added the operations in the same way.

 

Here are the steps followed:

 

My GSMMAP.asn files looks

 

1. OperationLocalvalue ::= INTEGER{

updateLocation (2),

:

noteMM-Event (89),

operation1(152),

operation2(153)

}

 

2. Operation descriptions of operation1 & operation2 are added

 

3. packet-gsm_map-template.c is updated with

 

gsm_map_opr_code_strings[]={

{   2, "updateLocation" },

:

{   152, "operation1" },

{   153, "operation2" }

}

 

dissect_invokeData()

switch(opcode){

  case  2: /*updateLocation*/ dissect_gsm_map_UpdateLocationArg();
break;

:

  case 152: /*operation 1*/ dissect_gsm_map_Operation1Arg(); break;

  case 153: /*operation 2*/ dissect_gsm_map_Operation2Arg(); break;

}

return offset;

}



3. makefile is used to generate packet-gsm_map.c, packet-gsm_map.h.

Options used with asn2wrs are:

python ../../tools/asn2wrs.py -b -e -p gsm_map -c gsmmap.cnf -s
packet-gsm_map-template GSMMAP.asn

 

4. Generated packet-gsm_map.c, packet-gsm_map.h are copied to
../../epan/dissectors folder.

Standard makefile present in the wireshark-0.99.5 directory is used to
build the wireshark exe.

 

The same steps when followed with operation codes with 90,91 or 94,95
work fine.

 

Thanks for your time.

 

Best Regards,

Bhavani.

 

From: "Anders Broman \(AL/EAB\)" <[EMAIL PROTECTED]
 >
Date: Mon, 26 Feb 2007 16:21:09 +0100




Hi,

Are you running the latest SVN version of Wireshark?

I asume that "adding an operation with local value 153 to GSMMAP" means
that you are editing the sources,

what happens if you change:

GSMMAPOperationLocalvalue ::= INTEGER{
 updateLocation (2),

:

 noteMM-Event (89)
} 

To:

 noteMM-Event (89),

 your-string(153)
} 

in GSMMAP.asn and rebuild the dissector using asn2wrs?

Best regards

Anders

 



From: DurgaBhavani Uppuluru 

Sent: Monday, February 26, 2007 10:46 AM
To: 'wireshark-dev@wireshark.org'
Subject: RE: local operation code in MAP

 

Hi Anders,

 

Hex value shown, in the bytes pane is 99.

I've tried other numbers too (>150) and I get similar result.

 

Best Regards,

Bhavani.

 

From: "Anders Broman" <[EMAIL PROTECTED]
 >
Date: Sun, 25 Feb 2007 19:55:43 +0100



Hi,
What is the hex value shown in the bytes pane when marking localvalue in
the
middle pane?
Best regards
Anders

 



From: DurgaBhavani Uppuluru
Sent: Sunday, February 25, 2007 2:36 PM
To: 'wireshark-dev@wireshark.org'
Subject: 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 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.
 
www.wipro.com___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev

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

2007-02-26 Thread Anders Broman \(AL/EAB\) 
Hi,
Are you running the latest SVN version of Wireshark?
I asume that "adding an operation with local value 153 to GSMMAP" means
that you are editing the sources,
what happens if you change:
GSMMAPOperationLocalvalue ::= INTEGER{
 updateLocation (2),
:
 noteMM-Event (89)
} 
To:
 noteMM-Event (89),
 your-string(153)
} 
in GSMMAP.asn and rebuild the dissector using asn2wrs?
Best regards
Anders
 


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: den 26 februari 2007 06:16
To: wireshark-dev@wireshark.org
Subject: Re: [Wireshark-dev] local operation code in MAP



Hi Anders,

 

Hex value shown, in the bytes pane is 99.

I've tried other numbers too (>150) and I get similar result.

 

Best Regards,

Bhavani.

 

From: "Anders Broman" <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> >
Date: Sun, 25 Feb 2007 19:55:43 +0100




Hi,
What is the hex value shown in the bytes pane when marking localvalue in
the
middle pane?
Best regards
Anders

 



From: DurgaBhavani Uppuluru
Sent: Sunday, February 25, 2007 2:36 PM
To: 'wireshark-dev@wireshark.org'
Subject: 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 this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.

www.wipro.com

___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev

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

2007-02-26 Thread durgabhavani.uppuluru 

Hi Anders,

 

Hex value shown, in the bytes pane is 99.

I've tried other numbers too (>150) and I get similar result.

 

Best Regards,

Bhavani.

 

From: "Anders Broman" <[EMAIL PROTECTED]
 >
Date: Sun, 25 Feb 2007 19:55:43 +0100




Hi,
What is the hex value shown in the bytes pane when marking localvalue in
the
middle pane?
Best regards
Anders

 



From: DurgaBhavani Uppuluru
Sent: Sunday, February 25, 2007 2:36 PM
To: 'wireshark-dev@wireshark.org'
Subject: 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 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.
 
www.wipro.com___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev

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

2007-02-25 Thread Anders Broman 
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
Ämne: [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.

___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev