| Bug ID |
11292
|
| Summary |
Tshark: output format of rpc.xid changed from Hex to Integer
|
| Product |
Wireshark
|
| Version |
1.12.6
|
| Hardware |
x86
|
| OS |
Red Hat
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
TShark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13675 [details]
Pcap to reproduce problem.
Build Information:
tshark -v
TShark 1.12.6rc0-46-g107a626 (Git Rev Unknown from unknown)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GLib 2.28.8, with libpcap, with libz 1.2.3, without
POSIX
capabilities, without libnl, without SMI, without c-ares, without ADNS, without
Lua, without Python, with GnuTLS 2.8.5, with Gcrypt 1.4.5, with MIT Kerberos,
without GeoIP.
Running on Linux 2.6.32-504.16.2.el6.x86_64, with locale en_US.UTF-8, with
libpcap version 1.3.0, with libz 1.2.3.
Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
Built using gcc 4.4.7 20120313 (Red Hat 4.4.7-11).
--
This is found in a pre-release version of Tshark.
tshark -r tshark.rpc.xid.pcap -Y rpc -Tfields -e rpc.xid
1833506422
1833506422
1833506424
1678770204
1833506424
1678770204
1833506426
1833506426
1833506427
1833506427
rpc.xid (NFS transaction ids) used to be printed out in Hex, and now it is in
integer format. Is there a reason for the change? This breaks parsing scripts
that depend on the output format.
Thank you.
KH
You are receiving this mail because:
- You are watching all bug changes.