[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038 --- Comment #10 from Xiaochuan Sun --- Created attachment 16539 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16539=edit decodes F1AP UL RRC TRANSFER correctly -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038 --- Comment #9 from Xiaochuan Sun --- You are right. I changed f1ap.cnf according to xxx.asn file, the UL RRC message transfer message can be decoded correctly. The below command is wrriten in the header of packet-f1ap.c file. It can generate new packet-f1ap.c file. Hope we don't need to change xxx.cnf file manually one day. "asn2wrs.py -p f1ap -c ./f1ap.cnf -s ./packet-f1ap-template -D . -O ../.. F1AP-CommonDataTypes.asn F1AP-Constants.asn F1AP-Containers.asn F1AP-IEs.asn F1AP-PDU-Contents.asn F1AP-PDU-Descriptions.asn" -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038 --- Comment #8 from Pascal Quantin --- First of all you need to regenerate paxket-f1ap.c from the ASN.1 description (using the corresponding CMkae command generat-f1ap-something, I do not remember it's exact name) and modify the F1AP.cnf file to match your updated specification and iterates until it compiles. Unless you are familiar with ASN.1 based dissector, it might take you some time. Good luck. -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038 --- Comment #7 from Xiaochuan Sun --- Created attachment 16530 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16530=edit F1AP pcap file I also attached my F1AP pcap file. Can you help indicate if there is anything wrong in rebuiding wireshark F1AP dissector from spec? -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038 --- Comment #6 from Xiaochuan Sun --- Created attachment 16529 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16529=edit F1AP-V04.00.asn Actually I have used extract_asn1_from_spec.pl to parse F1AP-V04.00.asn and generated F1AP-CommonDataTypes.asn F1AP-Constants.asn F1AP-Containers.asn F1AP-IEs.asn F1AP-PDU-Contents.asn F1AP-PDU-Descriptions.asn. Then add these asn files into epan/dissectors/asn1/f1ap directory and rebuilt wireshark. So the wireshark dissector should be aligned with F1AP-V04.00.asn spec. -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038
--- Comment #5 from Xiaochuan Sun ---
I abstracted UL RRC Message Transfer from 38473-f21.doc. There is no
id-Cells-to-be-Activated-List IE in UL RRC Message Transfer messge. Instead
Cells-to-be-Activated-List IE is present in F1 Setup Resp.
-- **
--
-- UL RRC Message Transfer
--
-- **
ULRRCMessageTransfer ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{
ULRRCMessageTransferIEs}},
...
}
ULRRCMessageTransferIEs F1AP-PROTOCOL-IES ::= {
{ ID id-gNB-CU-UE-F1AP-ID CRITICALITY
reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory
}|
{ ID id-gNB-DU-UE-F1AP-ID CRITICALITY
reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory
}|
{ ID id-SRBID
CRITICALITY reject TYPE SRBID
PRESENCE mandatory }|
{ ID id-RRCContainerCRITICALITY
reject TYPE RRCContainer PRESENCE
mandatory },
...
}
-- **
--
-- F1 Setup Response
--
-- **
F1SetupResponse ::= SEQUENCE {
protocolIEs ProtocolIE-Container {
{F1SetupResponseIEs} },
...
}
F1SetupResponseIEs F1AP-PROTOCOL-IES ::= {
{ ID id-TransactionID CRITICALITY reject
TYPE TransactionID PRESENCE mandatory
}|
{ ID id-gNB-CU-Name CRITICALITY
ignore TYPE GNB-CU-NamePRESENCE
optional }|
{ ID id-Cells-to-be-Activated-List CRITICALITY reject TYPE
Cells-to-be-Activated-List PRESENCE optional },
...
}
--
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038 --- Comment #4 from Pascal Quantin --- Please check the constant used for id-Cells-to-be-Activated-List: it's 3, the value used in your payload. It does not correspond to gnb-cu-f1ap-id. -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038
--- Comment #3 from Xiaochuan Sun ---
Below is F1AP UL RRC MESSAGE TRANSFER message definition I abstracted from
38473-f21.doc. There is no id-Cells-to-be-Activated-List IE in UL RRC Message
Transfer.
-- **
--
-- UL RRC Message Transfer
--
-- **
ULRRCMessageTransfer ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{
ULRRCMessageTransferIEs}},
...
}
ULRRCMessageTransferIEs F1AP-PROTOCOL-IES ::= {
{ ID id-gNB-CU-UE-F1AP-ID CRITICALITY
reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory
}|
{ ID id-gNB-DU-UE-F1AP-ID CRITICALITY
reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory
}|
{ ID id-SRBID
CRITICALITY reject TYPE SRBID
PRESENCE mandatory }|
{ ID id-RRCContainerCRITICALITY
reject TYPE RRCContainer PRESENCE
mandatory },
...
}
--
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038 Pascal Quantin changed: What|Removed |Added Resolution|--- |NOTABUG CC||pascal.quan...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #2 from Pascal Quantin --- Wireshark F1AP dissector in master branch is based on v15.2.1 which is the latest release available on 3GPP website and IE 3 corresponds to id-Cells-to-be-Activated-List as seen here: https://code.wireshark.org/review/gitweb?p=wireshark.git;a=blob;f=epan/dissectors/asn1/f1ap/F1AP-Constants.asn;h=9ff5a6aff013a87c0f618d8b3fb9edf071db891b;hb=refs/heads/master Presumably you are using an older and Bob backward compatible version. Not surprising for a protocol still under development, but nothing we can do on our side. -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 15038] Wireshark dissects f1ap packets wrongly using 5G f1ap dissector
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15038 Xiaochuan Sun changed: What|Removed |Added CC||xiaoc...@foxmail.com --- Comment #1 from Xiaochuan Sun --- Created attachment 16528 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16528=edit decoding result with Marben protocol dissector Attach the decoding result with Marben protocol dissector. -- You are receiving this mail because: You are watching all bug changes.___ Sent via:Wireshark-bugs mailing list Archives:https://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
