 | 1 | initial version |
Is this a different flavour from https://gitlab.com/wireshark/wireshark/-/blob/master/epan/dissectors/packet-nfapi.c ? That one doesn't seem to call any MAC or RRC dissectors for any payloads it finds..
I implemented a version of this for 4G (TI), and the payloads were MAC PDUs. My dissector would have inferred the direction, RNTI, RNTI-Type, size, and attached the equivalent of a filled-in mac_nr_info structure, then called the MAC-NR dissector for a tvb containing the payload. You should hopefully get good decodes all the way up the stack to IP or RRC (if PDCP keys are available, if used) - assuming the MAC/RLC/PDCP dissector preferences are appropriately set to let RRC configure them.
Notice that for RRC, you would need to call for the right dissector depending upon channel and direction, e.g. "nr-rrc.dl.dcch or nr-rrc.ul.dcch. But if you call mac-nr, it can work this out for you.
My preference was just to apply display filters for the traffic I wanted to see (but obviously these files can quickly become big/slow).
