ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 10966] New: Flow graph will not display using "standard so

Date: Sun, 15 Feb 2015 13:31:07 +0000
Bug ID 10966
Summary Flow graph will not display using "standard source/destination address"; network (IP) addresses are always used
Product Wireshark
Version 1.12.3
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Common utilities (libwsutil)
Assignee [email protected]
Reporter [email protected]

Build Information:
Version 1.12.3 (v1.12.3-0-gbb3e9a0 from master-1.12)

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 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-4200U CPU @ 1.60GHz, with 12185MB 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.
--
When the Flow Graph is selected, the window opens which, among other options,
gives you the choice of "Standard source/destination addresses" or "Network
source/destination addresses". Regardless of which option is selected, the
network source/destination adddresses are used.

This worked properly in version 1.10.8. It does not work in v 1.12.2 or 1.12.3.


You are receiving this mail because:
  • You are watching all bug changes.