Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12818] Cassandra CQL dissector not processing later CQL minor version

Wireshark-bugs: [Wireshark-bugs] [Bug 12818] Cassandra CQL dissector not processing later CQL mi

Date: Sun, 04 Sep 2016 19:38:59 +0000

What	Removed	Added
CC		[email protected]

Comment # 2 on bug 12818 from [email protected]

It looks like you've captured V4 of the protocol. This dissector was not
written for the V4 protocol, only V3.

The VERSION byte is 0x03 or 0x83 for V3, and 0x04 or 0x84 for V4.

References:
V3:
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=doc/native_protocol_v3.spec;hb=refs/heads/trunk
V4:
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=doc/native_protocol_v4.spec;hb=refs/heads/trunk

I believe the property "CQL_VERSION"="3.4.2" returned by the server is a
reference to the dialect of CQL spoken by the server, not the on-the-wire
protocol version.

The V4 protocol has significant enough changes that the V3 dissector is
unlikely to work out of the box.

You are receiving this mail because:

You are watching all bug changes.

References:
- [Wireshark-bugs] [Bug 12818] New: Cassandra CQL dissector not processing later CQL minor version
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 12141] disable the "relative sequence numbers" in TCP protocol of Preference, the "time sequence(tcptrace)" still show relative sequence number
Next by Date: [Wireshark-bugs] [Bug 12793] Expert Info ssl.resumed incorrect after TLS renegotiate
Previous by thread: [Wireshark-bugs] [Bug 12818] Cassandra CQL dissector not processing later CQL minor version
Next by thread: [Wireshark-bugs] [Bug 12818] Cassandra CQL dissector don't support v4 native protocol
Index(es):
- Date
- Thread