[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-bugs
Subject:    [Wireshark-bugs] [Bug 8154] New: wireshark 1.8.4 make a wrong decode with "bt-utp" and "bt-dht" prot
From:       bugzilla-daemon () wireshark ! org
Date:       2012-12-31 8:18:16
Message-ID: bug-8154-15 () https ! bugs ! wireshark ! org/bugzilla/
[Download RAW message or body]

--1356941897.ee6A1.24836
Date: Mon, 31 Dec 2012 00:18:16 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id54

            Bug ID: 8154
           Summary: wireshark 1.8.4 make a wrong decode with "bt-utp" and
                    "bt-dht" protocol
    Classification: Unclassified
           Product: Wireshark
           Version: 1.8.4
          Hardware: x86
                OS: Windows XP
            Status: UNCONFIRMED
          Severity: Major
          Priority: Low
         Component: Wireshark
          Assignee: bugzilla-admin@wireshark.org
          Reporter: scottling1982@gmail.com

Created attachment 9749
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id—49&actioníit
utp and dht packets

Build Information:
wireshark 1.8.4
--
Dear Sir,

The last wireshark 1.8.4 make a wrong decode with bt-utp and bt-dht protocol.
When I filter the "bt-utp", it show some packets like bt-dht to me.
And if filter the "bt-dht", it show nothing to me.
Both case I am sure I have captured utp and dht packets

According to my understanding, the bt-utp protocol show follow
http://www.bittorrent.org/beps/bep_0029.html
and bt-dht show follow http://www.bittorrent.org/beps/bep_0005.html


I attached two files, which header is match the protocol of utp and dht from I
offered liked. you can see wireshark1.8.4 can't show them correctly.


Anyway, wireshark is a great app.

Scott

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

--1356941897.ee6A1.24836
Date: Mon, 31 Dec 2012 00:18:16 -0800
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html>
    <head>
      <base href="https://bugs.wireshark.org/bugzilla/" />
      <style>
        body, th, td {
            font-size: 12px;
            font-family: Arial, Helvetica, sans-serif; }
        p, pre { margin-top: 1em; }
        pre {
            font-family: Bitstream Vera Sans Mono, Consolas, Lucida Console, \
monospace;  white-space: pre-wrap;
	}
        table { border: 0; border-spacing: 0; border-collapse: collapse; }
        th, td {
            padding: 0.25em;
            padding-left: 0.5em;
            padding-right: 0.5em;
        }
        th { background: rgb(240, 240, 240); }
        th.th_top { border-bottom: 1px solid rgb(116, 126, 147); }
        th.th_left { border-right: 1px solid rgb(116, 126, 147); }
        td.removed { background-color: #ffcccc; }
        td.added { background-color: #e4ffc7; }
      </style>
    </head>
    <body><table>
        <tr>
          <th class="th_left">Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_UNCONFIRMED "
   title="UNCONFIRMED --- - wireshark 1.8.4 make a wrong decode with \
&quot;bt-utp&quot; and &quot;bt-dht&quot; protocol"  \
href="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8154">8154</a>  </td>
        </tr>

        <tr>
          <th class="th_left">Summary</th>
          <td>wireshark 1.8.4 make a wrong decode with &quot;bt-utp&quot; and \
&quot;bt-dht&quot; protocol  </td>
        </tr>

        <tr>
          <th class="th_left">Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th class="th_left">Product</th>
          <td>Wireshark
          </td>
        </tr>

        <tr>
          <th class="th_left">Version</th>
          <td>1.8.4
          </td>
        </tr>

        <tr>
          <th class="th_left">Hardware</th>
          <td>x86
          </td>
        </tr>

        <tr>
          <th class="th_left">OS</th>
          <td>Windows XP
          </td>
        </tr>

        <tr>
          <th class="th_left">Status</th>
          <td>UNCONFIRMED
          </td>
        </tr>

        <tr>
          <th class="th_left">Severity</th>
          <td>Major
          </td>
        </tr>

        <tr>
          <th class="th_left">Priority</th>
          <td>Low
          </td>
        </tr>

        <tr>
          <th class="th_left">Component</th>
          <td>Wireshark
          </td>
        </tr>

        <tr>
          <th class="th_left">Assignee</th>
          <td>bugzilla-admin&#64;wireshark.org
          </td>
        </tr>

        <tr>
          <th class="th_left">Reporter</th>
          <td>scottling1982&#64;gmail.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Created <span class=""><a href="attachment.cgi?id=9749" \
name="attach_9749" title="utp and dht packets">attachment 9749</a> <a \
href="attachment.cgi?id=9749&amp;action=edit" title="utp and dht \
packets">[details]</a></span> utp and dht packets

Build Information:
wireshark 1.8.4
--
Dear Sir,

The last wireshark 1.8.4 make a wrong decode with bt-utp and bt-dht protocol.
When I filter the &quot;bt-utp&quot;, it show some packets like bt-dht to me.
And if filter the &quot;bt-dht&quot;, it show nothing to me.
Both case I am sure I have captured utp and dht packets

According to my understanding, the bt-utp protocol show follow
<a href="http://www.bittorrent.org/beps/bep_0029.html">http://www.bittorrent.org/beps/bep_0029.html</a>
 and bt-dht show follow <a \
href="http://www.bittorrent.org/beps/bep_0005.html">http://www.bittorrent.org/beps/bep_0005.html</a>



I attached two files, which header is match the protocol of utp and dht from I
offered liked. you can see wireshark1.8.4 can't show them correctly.


Anyway, wireshark is a great app.

Scott</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are watching all bug changes.</li>
      </ul>
    </body>
</html>

--1356941897.ee6A1.24836--



___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request@wireshark.org?subject=unsubscribe

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic