Wireshark-bugs: [Wireshark-bugs] [Bug 10960] New: DNS LOC data parsed as unknown data
| Bug ID |
10960
|
| Summary |
DNS LOC data parsed as unknown data
|
| Product |
Wireshark
|
| Version |
1.12.3
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
boaz.brickner@gmail.com
|
Created attachment 13447 [details]
DNS LOC unknown data
Build Information:
Version 1.12.3 (v1.12.3-0-gbb3e9a0 from master-1.12)
Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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 GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Jan 7 2015),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz, with 16345MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Discovered while working on Pcap.Net (http://pcapdot.net).
In the first attached pcap file there's a single DNS packet.
In the DNS Authoritative RRs, the 4th (and last) RR is a LOC RR.
The LOC RR data is parsed as unknown data (after the version field).
In the second attached pcap file, there's a single DNS packet.
In the DNS Additional RRs, the 3rd RR is a LOC RR.
The LOC RR data is parsed fine, without treating it as unknown data.
Why is the second packet parsed ok and the first isn't?
You are receiving this mail because:
- You are watching all bug changes.
