| Bug ID |
11333
|
| Summary |
alternative coloring rule: color based on tcp.stream
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
wireshark 1.12.5 (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 GTK+ 3.16.3, with Cairo 1.14.2, with Pango 1.36.8, with
GLib 2.44.1, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
with libnl 3, without SMI, without c-ares, without ADNS, with Lua 5.2, without
Python, with GnuTLS 3.4.1, with Gcrypt 1.6.3, with MIT Kerberos, without GeoIP,
with PortAudio V19-devel (built Jan 31 2014 21:19:35), without AirPcap.
Running on Linux 4.0.7-2-ARCH, with locale de_DE.UTF-8, with libpcap version
1.6.2, with libz 1.2.8, GnuTLS 3.4.2, Gcrypt 1.6.3.
AMD E2-1800 APU with Radeon(tm) HD Graphics
Built using gcc 5.1.0.
--
This is an enhancement proposal. Current coloring rules only allow a fixed
color to be assigned to a specific filter. Sometimes it might be useful to
quickly distinguish which packets belong to which connection: Therefore I
suggest an alternative coloring mode, where the color for a packet is
calculated from the tcp.stream identifier (or a similar attribute covering also
UDP, SCTP etc)
You are receiving this mail because:
- You are watching all bug changes.