Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 11139] New: Return TCP packets aren't labeled with protocol description

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	11139
Summary	Return TCP packets aren't labeled with protocol description
Product	Wireshark
Version	1.12.4
Hardware	Other
OS	FreeBSD
Status	UNCONFIRMED
Severity	Major
Priority	Low
Component	GTK+ UI
Assignee	bugzilla-admin@wireshark.org
Reporter	yuri@rawbw.com

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
When client connects to NFS on TCP port 2049, only packets going out to the
server are labeled "NFS", and returning ones are labeled "TCP". Wireshark can
easily follow the TCP stream, therefore it can determine that return packets
are also NFS.

* So my first suggestion is to label the return packets with the same protocol,
at least for TCP

* My second suggestion is to label them hierarchically: not just "NFS" but
"TCP/NFS", (or UDP/NFS, UDP/DHCP). Explicit names are always good, makes it
more clear. If you think there will be objections, make this the user option.

* The third suggestion is to also label SYN/ACK/FIN packets with protocol.
Currently SYN/ACK/FIN packets related to some known protocol are only labeled
as "TCP". It would make sense to label them the same way as data packets.

---

      You are receiving this mail because:

• You are watching all bug changes.