| Bug ID |
11247
|
| Summary |
Subnet name resolution doesn't always work.
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.99.7 (v1.99.7rc0-39-g4ed7cc7 from master)
Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.12.16, with Pango 1.36.8,
with
WinPcap (4_1_3), with libz 1.2.8, with GLib 2.42.0, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built May 20 2015), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.2.15, with Gcrypt 1.6.2, with AirPcap 4.1.3 build 3348.
Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz (with SSE4.2), with 8072MB of
physical memory.
Built using Microsoft Visual C++ 10.0 build 30319
--
Having recently discovered the subnets feature, I started playing with it and
discovered that the subnet name resolution feature doesn't always work. I will
post a sample subnets file along with a sample capture file to illustrate the
problem.
You are receiving this mail because:
- You are watching all bug changes.