Revision history [back]

There are mentions in a couple places that zuc is not supported/enabled.
Either add a comment to 16384: rrc container not decoded in F1AP asking for clarification or open a new Gitlab issue attaching the capture file and linking back to this question.

16384: rrc container not decoded in F1AP includes the comment:

Note that in the pcap attached ZUC ciphering is activated, so all messages after the RRC Security Mode Complete do not decode properly.

packet-pdcp-nr.c:

    { nia3,         "NIA3 (ZUC)" },
...
    { nea3,         "NEA3 (ZUC)" },

Frame 2429 of your capture has:

securityAlgorithmConfig
    cipheringAlgorithm: nea1 (1)
    integrityProtAlgorithm: nia3 (3)

1716: PDCP-NR: Add ZUC Cipher/integrity calls.

As with Snow3G, we can't distribute Wireshark with NIA3/NEA3 implementations linked in, but provide f8/f9 calls that may be enabled in private builds.

There are mentions in a couple places that zuc is not supported/enabled.
Either add a comment to 16384: rrc container not decoded in F1AP asking for clarification or open a new Gitlab issue attaching the capture file and linking back to this question.question. If you open a new issue maybe it can be to make the expert info message clearer w.r.t zuc.

16384: rrc container not decoded in F1AP includes the comment:

Note that in the pcap attached ZUC ciphering is activated, so all messages after the RRC Security Mode Complete do not decode properly.

packet-pdcp-nr.c:

    { nia3,         "NIA3 (ZUC)" },
...
    { nea3,         "NEA3 (ZUC)" },

Frame 2429 of your capture has:

securityAlgorithmConfig
    cipheringAlgorithm: nea1 (1)
    integrityProtAlgorithm: nia3 (3)

1716: PDCP-NR: Add ZUC Cipher/integrity calls.

As with Snow3G, we can't distribute Wireshark with NIA3/NEA3 implementations linked in, but provide f8/f9 calls that may be enabled in private builds.