| Bug ID | 
          10770
           | 
        
        
          | Summary | 
          new riemann protocol dissector doesn't work for TCP, only UDP
           | 
        
        
          | Product | 
          Wireshark
           | 
        
        
          | Version | 
          1.99.x (Experimental)
           | 
        
        
          | Hardware | 
          x86
           | 
        
        
          | OS | 
          All
           | 
        
        
          | Status | 
          UNCONFIRMED
           | 
        
        
          | Severity | 
          Enhancement
           | 
        
        
          | Priority | 
          Low
           | 
        
        
          | Component | 
          Dissection engine (libwireshark)
           | 
        
        
          | Assignee | 
          [email protected]
           | 
        
        
          | Reporter | 
          [email protected]
           | 
        
      
        
        Build Information:
TShark (Wireshark) 1.99.1 (v1.99.1-0-g4c229ca from (detached)
Copyright 1998-2014 Gerald Combs <[email protected]> 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 libpcap, with POSIX capabilities (Linux), with libnl 3,
with libz 1.2.8, with GLib 2.42.0, with SMI 0.4.8, with c-ares 1.10.0, with Lua
5.2, with GnuTLS 3.3.8, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP.
Running on Linux 3.16.0-4-amd64, with locale en_US.UTF-8, with libpcap version
1.6.2, with libz 1.2.8, with GnuTLS 3.3.8, with Gcrypt 1.6.2.
Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz (with SSE4.2)
Built using gcc 4.9.1.
--
Riemann accepts data over both TCP and UDP. TCP is the preferred protocol in
the riemann ecosystem because of reliability and better performance.
Not sure if it's a bug or it is so by design, but "Riemann" only shows up in
the "Decode As..." list when analyzing a pcap from an UDP session between a
riemann client and server.
         
      
      
      You are receiving this mail because:
      
      
          - You are watching all bug changes.