Wireshark does not decode content of NMR field.

gsm11.11
etsi_cat
nmr
retag add tags

Hi. i'm working with SIM-card pro-active command. So,i have an example of response to command PROVIDE LOCAL INFORMATION with NMR data in it. But NMR data are not decoded. Can you explain-why and if it's a bug then you will make a patch? It's from my real trace:

GSM SIM 11.11
    1000 .... = Class Coding: ETSI TS 102.221 (0x8)
    .... 00.. = Secure Messaging Indication: No SM used between terminal and card (0x0)
    .... ..00 = Logical Channel number: 0
    Instruction: TERMINAL RESPONSE (0x14)
    Card Application Tookit ETSI TS 102.223
        Command details: 012602
            Command Number: 0x01
            Command Type: PROVIDE LOCAL INFORMATION (0x26)
            Command Qualifier: Network Measurement results (0x02)
        Device identity: 8281
            Source Device ID: Terminal (Card Reader) (0x82)
            Destination Device ID: SIM / USIM / UICC (0x81)
        Result: 06
            Result: Command performed successfully, limited service (0x06)
        Network Measurement Results: 0000000000000000b84ea5f0c7370100
        GSM/3G BCCH channel list: 
    Status Word: 9000 Normal ending of the command

EvgenSe

asked 2019-04-02 06:01:53 +0000

23.8k

grahamb

updated 2019-04-02 09:40:02 +0000

edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

The packet-etsi_card_app_toolkit.c file doesn't dissect that tag (0x16). That might have been an unintentional omission or perhaps the author just had no way to test it. Whatever the reason, if you want it to be dissected, you should submit a Wireshark bug report asking for it to be dissected. Note that there appear to be others not handled too, among them these candidates:

    { 0x07, "Capability configuration parameters" },
    { 0x09, "3GPP SS string" },
    { 0x0a, "3GPP USSD string" },
    { 0x0c, "3GPP Cell Broadcast page" },
    { 0x10, "Item identifier" },
    { 0x11, "Response length" },
    { 0x12, "File List" },
    { 0x16, "Network Measurement Results" },
    { 0x17, "Default Text" },
    { 0x18, "Items Next Action Indicator" },
    { 0x1a, "GSM/3G Cause" },
    { 0x1c, "transaction identifier" },
    { 0x1d, "GSM/3G BCCH channel list" },
    { 0x1e, "Icon identifier" },
    { 0x1f, "Item Icon identifier list" },
    { 0x20, "Card reader status" },
    { 0x21, "Card ATR / eCAT sequence number" },
    { 0x22, "C-APDU / Encrypted TLV list" },
    { 0x23, "R-APDU / SA template" },
    { 0x24, "Timer identifier" },
    { 0x27, "Call control requested action" },
    { 0x2a, "GSM/3G BC Repeat Indicator" },
    { 0x2b, "Immediate response" },
    { 0x30, "Browser Identity" },
    { 0x31, "URL / URI" },
    { 0x33, "Provisioning Reference File" },
    { 0x34, "Browser Termination Cause" },
    { 0x36, "Channel data" },
    { 0x37, "Channel data length" },
    { 0x38, "Channel status" },
    { 0x3a, "Card reader identifier / REFRESH Enforcement Policy" },
    { 0x3b, "File Update Information" },
    { 0x41, "Service Record" },
    { 0x42, "Device Filter" },
    { 0x43, "Service Search" },
    { 0x44, "Attribute information" },
    { 0x45, "Service Availability" },
    { 0x46, "3GPP2 ESN" },
    { 0x48, "3GPP2 CDMA-SMS-TPDU" },
    { 0x49, "Remote Entity Address" },
    { 0x4a, "3GPP I-WLAN Identifier" },
    { 0x4b, "3GPP I-WLAN Access Status" },
    { 0x50, "Text attribute" },
    { 0x51, "Item text attribute list" },
    { 0x52, "3GPP PDP Context Activation parameter" },
    { 0x53, "Contactless state request" },
    { 0x54, "Conactless functionality state" },
    { 0x55, "3GPP CSG cell selection status" },
    { 0x56, "3GPP CSG ID" },
    { 0x57, "3GPP HNB name" },
    { 0x60, "MAC" },
    { 0x61, "Emergency Call Object" },
    { 0x62, "IMEISV" },
    { 0x63, "Battery state" },
    { 0x64, "Browsing status" },
    { 0x65, "Network Search Mode" },
    { 0x66, "Frame Layout" },
    { 0x67, "Frames Information" },
    { 0x68, "Frame identifier" },
    { 0x6a, "Multimedia Message Reference" },
    { 0x6b, "Multimedia Message Identifier" },
    { 0x6c, "Multimedia Message Transfer Status" },
    { 0x6d, "MEID" },
    { 0x6e, "Multimedia Message Content Identifier" },
    { 0x6f, "Multimedia Message Notification" },
    { 0x70, "Last Envelope" },
    { 0x71, "Registry application data" },
    { 0x72, "3GPP PLMNwAcT List" },
    { 0x75, "3GPP Rejection Cause Code" },
    { 0x7b, "ACTIVATE descriptor" },
    { 0x7e, "3GPP CSG ID list" },
    { 0xaa, "IP address list" },
    { 0xbb, "Surrounding macrocells" },

Note that just because a bug report is filed doesn't mean support will be added. By far the best way for something to be supported is if you can write it yourself and submit a patch.

11.1k

cmaynard

answered 2019-04-02 15:35:56 +0000, updated 2019-04-02 16:43:26 +0000

edit flag offensive 0 remove flag delete link

Comments

Thanks,Christopher. I tryed to do it manually, i.e. to dissect it from dump byte-by-byte,but the problem is in source to decode it. I had almost broke my brain reading 3GPP 35.331(UTRAN), 36331(EUTRAN/LTE) and 41.008(GERAN) and trying to implement knowledges i got form them. And unfortunatly-i'm not a programmer(coder). p.s. i'd submitted a bug report.

EvgenSe (2019-04-03 05:20:30 +0000) edit

p.s. i'd submitted a bug report.

That's bug 15665.

Guy Harris (2019-04-03 05:32:46 +0000) edit

add a comment see more comments

Wireshark does not decode content of NMR field.

Comments

1 Answer

Comments

Your Answer

Wireshark does not decode content of NMR field. edit

Comments

1 Answer

Comments

Your Answer

Wireshark does not decode content of NMR field.