 | 1 | initial version |
The packet-etsi_card_app_tookkit.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. Be far the best way for something to be supported is if you can write it yourself and submit a patch.
| | 2 | No.2 Revision |
The packet-etsi_card_app_tookkit.cpacket-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. Be far the best way for something to be supported is if you can write it yourself and submit a patch.
| | 3 | No.3 Revision |
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. Be By far the best way for something to be supported is if you can write it yourself and submit a patch.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.