[Wireshark-dev] F1AP Messages are not getting dissected correctly.

2020-12-16 Thread Simran Kumawat 
Hi Sir/Ma'am,

This is Simran Kumawat, Project Associate at 5G-TestBed Project, IIT
Hyderabad.
I am working on the F1AP interface currently, I observed a few things as
mentioned below.
Wireshark is dissecting f1ap msgs like this -
1. Initiating Message --> Initiating Message
2. SuccessfulOutcome Message> Initiating Message
3. UnsuccessfulOutcome Message-> SuccessfulOutcome Message
The information contained is also the same but the problem is  only at
this moment. for example ,
wireshark is dissecting F1SetupResponse > F1SetupRequest and

F1SetupFailure> F1SetupResponse
with the same content. There is no problem in the code because after
decoding at receiver side, I am printing the info contained in the packet.
I am attaching the wireshark capture for your reference and logs from
sender and receiver side.

I request you to please check with the issue mentioned above.
In case of any query, please get back to me.




Thanks and Regards,
Simran Kumawat
Project Associate, 5G-TestBed
IITH

-- 


Disclaimer:- 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 email. Please notify the sender 
immediately and destroy all copies of this message and any attachments. The 
views expressed in this E-mail message (including the enclosure/(s) or 
attachment/(s) if any) are those of the individual sender, except where the 
sender expressly, and with authority, states them to be the views of IIT 
Hyderabad. Before opening any mail and attachments please check them for 
viruses, malware, and the sender email address is indeed from IITH domain. 
IITH does not accept any liability for malware infected mails.

 12-16-2020 13:13:34.245931 [ INFO ] | [gNB  ] | wn5gNrBsPsF1apTst.c +208 
|  main| Listening
 12-16-2020 13:13:38.655137 [ INFO ] | [gNB  ] | wn5gNrBsPsF1apTst.c +219 
|  main| Accepted
 12-16-2020 13:13:38.655151 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apSctpApi.c +237 |  wnF1apRecvSctpMsg | F1 SCTP succefully 
received msg
 12-16-2020 13:13:38.655154 [ INFO ] | [gNB  ] | wn5gNrBsPsF1apTst.c +228 
|  main| After SCTP received data is 40
 12-16-2020 13:13:38.655180 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1CDecoder.c +57 |  wnF1apDecodePdu | F1AP decoding 
successfull
UnsuccessfulOutcome ::= {
procedureCode: 1
criticality: 0 (reject)
value: F1SetupFailure ::= {
protocolIEs: ProtocolIE-Container ::= {
F1SetupFailureIEs ::= {
id: 78
criticality: 0 (reject)
value: 20
}
F1SetupFailureIEs ::= {
id: 0
criticality: 1 (ignore)
value: 0 (unspecified)
}
}
}
}
 12-16-2020 13:13:38.655200 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apHandler.c +4516 |  wnF1SetupFlr | TranscationID is 20
 12-16-2020 13:13:38.655204 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apHandler.c +4521 |  wnF1SetupFlr | radioNetwork is 0
 12-16-2020 13:13:38.655206 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apHandler.c +4523 |  wnF1SetupFlr | Transport is 0
 12-16-2020 13:13:38.655207 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apHandler.c +4525 |  wnF1SetupFlr | protocol is 0
 12-16-2020 13:13:38.655209 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apHandler.c +4527 |  wnF1SetupFlr | misc is 0
 12-16-2020 13:13:38.655281 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apSctpApi.c +237 |  wnF1apRecvSctpMsg | F1 SCTP succefully 
received msg
 12-16-2020 13:13:38.654944 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1CEncoder.c +56 |  wnF1EncodePdu | Encoded data is 18
 12-16-2020 13:13:38.654964 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apApi.c +2331 |  wnF1StupFail | F1AP | encoding successful
 12-16-2020 13:13:38.654977 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1CDecoder.c +58 |  wnF1apDecodePdu | F1AP decoding 
successfull


1





78


20



0












 12-16-2020 13:13:38.655023 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apSctpApi.c +150 |  wnConnSocket | F1AP socket created 
successfully
 12-16-2020 13:13:38.655100 [ INFO ] | [gNB  ] | 
../csrc/wn5gNrBsPsF1apSctpApi.c +172 |  wnConnSocket | F1AP sock connected : 0 3



Re: [Wireshark-dev] F1AP Messages are not getting dissected correctly.

2020-12-16 Thread Pascal Quantin 
Dear Simran,

Le mer. 16 déc. 2020 à 17:38, Simran Kumawat 
a écrit :

> Hi Sir/Ma'am,
>
> This is Simran Kumawat, Project Associate at 5G-TestBed Project, IIT
> Hyderabad.
> I am working on the F1AP interface currently, I observed a few things as
> mentioned below.
> Wireshark is dissecting f1ap msgs like this -
> 1. Initiating Message --> Initiating Message
> 2. SuccessfulOutcome Message> Initiating Message
> 3. UnsuccessfulOutcome Message-> SuccessfulOutcome Message
> The information contained is also the same but the problem is  only at
> this moment. for example ,
> wireshark is dissecting F1SetupResponse > F1SetupRequest and
>
> F1SetupFailure> F1SetupResponse
> with the same content. There is no problem in the code because after
> decoding at receiver side, I am printing the info contained in the packet.
> I am attaching the wireshark capture for your reference and logs from
> sender and receiver side.
>
> I request you to please check with the issue mentioned above.
> In case of any query, please get back to me.
>

Wireshark decodes your pcap as:
F1 Application Protocol
F1AP-PDU: successfulOutcome (1)
successfulOutcome
procedureCode: id-F1Setup (1)
criticality: reject (0)
value
F1SetupResponse
protocolIEs: 2 items
Item 0: id-TransactionID
ProtocolIE-Field
id: id-TransactionID (78)
criticality: reject (0)
value
TransactionID: 20
Item 1: id-Cause
ProtocolIE-Field
id: id-Cause (0)
criticality: reject (0)
value
Cause: radioNetwork (0)
radioNetwork: unspecified (0)

Which matches the decoding obtained with other ASN.1 engines (like
https://asn1.io/asn1playground/ for example, as seen below):
F1AP-PDU ::= successfulOutcome : {
  procedureCode 1,
  criticality reject,
  value F1SetupResponse : {
protocolIEs {
  {
id 78,
criticality reject,
value TransactionID : 20
  },
  {
id 0,
criticality reject,
value OCTET STRING : '00'H
  }
}
  }
}

So the bug is on your side.

Best regards,
Pascal.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] [Outreachy] Internship blog 2020 post #2

2020-12-16 Thread Joey Salazar via Wireshark-dev 
Hi all,

A short blog entry on "I was running the version that I didn't rebuild" here 
[1].

Check it out! The next one will be there in 2 weeks.


--
Joey

[1] jsal.home.blog/2020/12/15/everybody-struggles

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Rebuild u/gtk/pixbuf-csource.c/h

2020-12-16 Thread Lucio Di-Giovannantonio via Wireshark-dev 
Hello to everyone,

I'm building Wireshark from an old trunk 2.4.7, and I need to add 
"myimage_pb_data" to pixbuf-csource.c (pixbuf-csource.h), starting from 
"myimage.png" file.

The problem is that pixbuf-csource files are generated, but I don't know how 
rebuild them to add my image, anyone know how to do that?

Regards
Lucio


Lucio Di Giovannantonio
Senior Software Developer

Keysight Technologies Italy srl - unico socio
Via Policarpo Petrocchi 4 - 20127 Milano (MI) - Italy

Tel: +39 02 923 98108, Telnet: 239 8108
Web. www.keysight.com


[Prisma_eMailSignature]







___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe