Re: [Wireshark-users] Name resolve a custom column

2020-06-20 Thread Maynard, Chris via Wireshark-users

From: Wireshark-users  On Behalf Of Sri
Sent: Saturday, June 20, 2020 12:27 PM
To: wireshark-users@wireshark.org
Subject: Re: [Wireshark-users] Name resolve a custom column

No, there isn't.

What field are you referring to, exactly?  Please provide a very small capture 
file - even 1 single packet will do – that contains that field.
- Chris


---











CONFIDENTIALITY NOTICE: This message is the property of International Game 
Technology PLC and/or its subsidiaries and may contain proprietary, 
confidential or trade secret information. This message is intended solely for 
the use of the addressee. If you are not the intended recipient and have 
received this message in error, please delete this message from your system. 
Any unauthorized reading, distribution, copying, or other use of this message 
or its attachments is strictly prohibited.
___
Sent via:Wireshark-users mailing list 
Archives:https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
 mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-users] Name resolve a custom column

2020-06-20 Thread Sri
No, there isn't.


>
> Date: Wed, 17 Jun 2020 11:41:52 -0500
> From: chuck c 
> To: Community support list for Wireshark
>     
> Subject: Re: [Wireshark-users] Name resolve a custom column
> Message-ID:
>  3rh4xrfwp+ln...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Does the field you're using have a corresponding "resolved" field?
>
> $ tshark -G fields | grep -i resolved
> F   nextRDNToBeResolved dsp.nextRDNToBeResolved FT_INT32dsp
> BASE_DEC0x0 INTEGER
> F   rdnsResolveddsp.rdnsResolvedFT_INT32dsp
> BASE_DEC0x0 INTEGER
> F   Destination (resolved)  eth.dst_resolvedFT_STRING   eth
> 0x0 Destination Hardware Address (resolved)
> F   Destination OUI (resolved)  eth.dst.oui_resolvedFT_STRING
> eth 0x0 Destination Organizationally Unique Identifier
> (resolved)
> F   Source (resolved)   eth.src_resolvedFT_STRING   eth
> 0x0 Source Hardware Address (resolved)
> F   Source OUI (resolved)   eth.src.oui_resolvedFT_STRING   eth
> 0x0 Source Organizationally Unique Identifier (resolved)
> F   Address (resolved)  eth.addr_resolved   FT_STRING   eth
> 0x0 Source or Destination Hardware Address (resolved)
> F   Address OUI (resolved)  eth.addr.oui_resolved   FT_STRING   eth
> 0x0 Address Organizationally Unique Identifier (resolved)
> F   Destination address (resolved)  wlan.da_resolvedFT_STRING
> wlan0x0 Destination Hardware Address (resolved)
> F   Source address (resolved)   wlan.sa_resolvedFT_STRING
> wlan0x0 Source Hardware Address (resolved)
> F   Hardware address (resolved) wlan.addr_resolved  FT_STRING
> wlan0x0 SA, DA, BSSID, RA or TA Hardware Address
> (resolved)
> F   Receiver address (resolved) wlan.ra_resolvedFT_STRING
> wlan0x0 Receiving Station Hardware Address (resolved)
> F   Transmitter address (resolved)  wlan.ta_resolvedFT_STRING
> wlan0x0 Transmitting Station Hardware Address
> (resolved)
> F   BSS Id (resolved)   wlan.bssid_resolved FT_STRING
> wlan0x0 Basic Service Set ID (resolved)
> F   STA address (resolved)  wlan.staa_resolved  FT_STRING
> wlan0x0 Station Hardware Address (resolved)
> F   resolQNLn   mq.msgasy.resolqnln FT_UINT8mq
>  BASE_DEC0x0 MSGASYNC Resolved Queue Name Length
> F   resolQNme   mq.msgasy.resolqnme FT_STRINGZ  mq
>  0x0 MSGASYNC Resolved Queue Name
> F   Resolved Q Name..   mq.od.resolvq   FT_STRINGZ  mq
>  0x0 OD resolved queue name
> F   Resolved QMgrName   mq.od.resolvqmgrFT_STRINGZ  mq
>  0x0 OD resolved queue manager name
> F   Resolv Obj Type..   mq.od.resolvedobjtype   FT_UINT32   mq
>  BASE_DEC0x0 OD resolved object type
> F   ResQName.   mq.gmo.resolvq  FT_STRINGZ  mq  0x0
> GMO resolved queue name
> F   ResQName... mq.pmo.resolvq  FT_STRINGZ  mq  0x0
> PMO resolved queue name
> F   ResQMgr mq.pmo.resolvqmgr   FT_STRINGZ  mq
>  0x0 PMO resolved queue manager name
> F   Dfs smb.flags2.dfs  FT_BOOLEAN  smb 16  0x1000  Can
> pathnames be resolved using Dfs?
> F   Unresolved value, Missing MIB   snmp.missing_mibFT_NONE
> snmp0x0
> F   Resolved U-RNTI mac.resolved_urnti  FT_UINT32   mac
> BASE_HEX0x0 The U-RNTI of the UE which is using the C-RNTI seen
> in this frame
> F   LDev_get_ACCO: can't resolve ACCO interface pointer
> cba.acco.interface_pointer_unresolved   FT_NONE cba_pdev
> 0x0
>
> On Wed, Jun 17, 2020 at 11:24 AM Sri  wrote:
>
> > When a Custom Column is created, how can it be displayed with a resolved
> > name?
> >
> > Even when I select a resolved field in the Packet Details pane and
> > right-click to choose 'Apply as a Column', the column in the Packet List
> > pane is not name resolved.
> >
> ___
> > Sent via:Wireshark-users mailing list  >
> > Archives:https://www.wireshark.org/lists/wireshark-users
> > Unsubscribe: https://www.wi

Re: [Wireshark-users] Name resolve a custom column

2020-06-17 Thread chuck c
Does the field you're using have a corresponding "resolved" field?

$ tshark -G fields | grep -i resolved
F   nextRDNToBeResolved dsp.nextRDNToBeResolved FT_INT32dsp
BASE_DEC0x0 INTEGER
F   rdnsResolveddsp.rdnsResolvedFT_INT32dsp
BASE_DEC0x0 INTEGER
F   Destination (resolved)  eth.dst_resolvedFT_STRING   eth
0x0 Destination Hardware Address (resolved)
F   Destination OUI (resolved)  eth.dst.oui_resolvedFT_STRING
eth 0x0 Destination Organizationally Unique Identifier
(resolved)
F   Source (resolved)   eth.src_resolvedFT_STRING   eth
0x0 Source Hardware Address (resolved)
F   Source OUI (resolved)   eth.src.oui_resolvedFT_STRING   eth
0x0 Source Organizationally Unique Identifier (resolved)
F   Address (resolved)  eth.addr_resolved   FT_STRING   eth
0x0 Source or Destination Hardware Address (resolved)
F   Address OUI (resolved)  eth.addr.oui_resolved   FT_STRING   eth
0x0 Address Organizationally Unique Identifier (resolved)
F   Destination address (resolved)  wlan.da_resolvedFT_STRING
wlan0x0 Destination Hardware Address (resolved)
F   Source address (resolved)   wlan.sa_resolvedFT_STRING
wlan0x0 Source Hardware Address (resolved)
F   Hardware address (resolved) wlan.addr_resolved  FT_STRING
wlan0x0 SA, DA, BSSID, RA or TA Hardware Address
(resolved)
F   Receiver address (resolved) wlan.ra_resolvedFT_STRING
wlan0x0 Receiving Station Hardware Address (resolved)
F   Transmitter address (resolved)  wlan.ta_resolvedFT_STRING
wlan0x0 Transmitting Station Hardware Address (resolved)
F   BSS Id (resolved)   wlan.bssid_resolved FT_STRING
wlan0x0 Basic Service Set ID (resolved)
F   STA address (resolved)  wlan.staa_resolved  FT_STRING
wlan0x0 Station Hardware Address (resolved)
F   resolQNLn   mq.msgasy.resolqnln FT_UINT8mq
 BASE_DEC0x0 MSGASYNC Resolved Queue Name Length
F   resolQNme   mq.msgasy.resolqnme FT_STRINGZ  mq
 0x0 MSGASYNC Resolved Queue Name
F   Resolved Q Name..   mq.od.resolvq   FT_STRINGZ  mq
 0x0 OD resolved queue name
F   Resolved QMgrName   mq.od.resolvqmgrFT_STRINGZ  mq
 0x0 OD resolved queue manager name
F   Resolv Obj Type..   mq.od.resolvedobjtype   FT_UINT32   mq
 BASE_DEC0x0 OD resolved object type
F   ResQName.   mq.gmo.resolvq  FT_STRINGZ  mq  0x0
GMO resolved queue name
F   ResQName... mq.pmo.resolvq  FT_STRINGZ  mq  0x0
PMO resolved queue name
F   ResQMgr mq.pmo.resolvqmgr   FT_STRINGZ  mq
 0x0 PMO resolved queue manager name
F   Dfs smb.flags2.dfs  FT_BOOLEAN  smb 16  0x1000  Can
pathnames be resolved using Dfs?
F   Unresolved value, Missing MIB   snmp.missing_mibFT_NONE
snmp0x0
F   Resolved U-RNTI mac.resolved_urnti  FT_UINT32   mac
BASE_HEX0x0 The U-RNTI of the UE which is using the C-RNTI seen
in this frame
F   LDev_get_ACCO: can't resolve ACCO interface pointer
cba.acco.interface_pointer_unresolved   FT_NONE cba_pdev
0x0

On Wed, Jun 17, 2020 at 11:24 AM Sri  wrote:

> When a Custom Column is created, how can it be displayed with a resolved
> name?
>
> Even when I select a resolved field in the Packet Details pane and
> right-click to choose 'Apply as a Column', the column in the Packet List
> pane is not name resolved.
> ___
> Sent via:Wireshark-users mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
>  mailto:wireshark-users-requ...@wireshark.org
> ?subject=unsubscribe
___
Sent via:Wireshark-users mailing list 
Archives:https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
 mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe