Wireshark-bugs: [Wireshark-bugs] [Bug 11641] New: Support TURN TCP (RFC 6062)
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 27 Oct 2015 19:04:07 +0000
Bug ID 11641
Summary Support TURN TCP (RFC 6062)
Product Wireshark
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity Enhancement
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter jonathan@vidyo.com 

Created attachment 13940 [details]
A pcap capture of a simple TURN/TCP setup

Build Information:
Version 2.0.0rc2-93-g294f88e (v2.0.0rc1-93-g294f88e from master-2.0)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.5, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
with
Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
with QtMultimedia, without AirPcap.

Running on Mac OS X 10.10.5, build 14F1021 (Darwin 14.5.0), with locale C, with
libpcap version 1.5.3 - Apple version 47, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0.
Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Wireshark does not recognize TURN/TCP (RFC 6062) connections.

It correctly detects the STUN traffic flowing over TCP, but the Connect and
ConnectionBind requests and responses, and the ConnectionAttempt indication,
show up as Unknown.

Mostly I suspect this should be straightforward; the subtlety will be in
handling the data connections, which do a TURN ConnectionBind request/response
and then transition to an unframed other protocol, on which dissectors should
ideally be run.

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