Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 8947] Adding request/response tracking into COPS dissector

Date: Tue, 30 Jul 2013 13:08:36 +0000

Comment # 22 on bug 8947 from
> My question was more "If a handle is required to do request/response
> matching, does it make more sense to put the request/response fields under
> the Handle object, rather than outside of it?"  Pushing opcode/is_solicited
> was just referring to the values (passed into the subfunctions), not the
> fields themselves (which I agree should be left as is).

Some Op Code, e.g. 9 (KA), doesn't have handle object, but we can still match
request/response(see packet 1/2 in fuzz test pcap file), so I think it's better
to keep the request/response field at current level.


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