This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 6 and 7
Revision 6 as of 2005-12-24 03:10:48
Size: 2594
Editor: pm904-09
Comment:
Revision 7 as of 2006-04-01 00:12:50
Size: 2862
Editor: UlfLamping
Comment: add link to DHT extension
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
 * ["TCP"]: Typically, BitTorrent uses ["TCP"] as its transport protocol. The well known TCP port for BitTorrent traffic is 6881-6889.  * ["TCP"]: Typically, BitTorrent uses ["TCP"] as its transport protocol. The well known TCP port for BitTorrent traffic is 6881-6889 (and 6969 for the tracer port). The DHT extension uses various UDP ports negotiated by the peers.
Line 44: Line 44:
 Capture only the BitTorrent tracker traffic over one of the default ports (6881): {{{  Capture only the BitTorrent tracker traffic over one of the default ports (e.g. 6881): {{{
Line 54: Line 54:
 * [http://www.bittorrent.org/Draft_DHT_protocol.html distributed sloppy hash table protocol] UDP based BitTorrent extension for distributed trackers (the UDP port number is negotiated)
 * [http://hippie.oofle.com/tiki-index.php?page=BitTorrent Hippie protocol signature description] the TCP and UDP protocol signatures which might be used to heuristically identify the BitTorrent protocol
Line 56: Line 58:

I've seen the usage of the TCP port 6969 while using BitTorrent. Is this the new web based tracker or simply a virus? - ''UlfLamping''

Apparently this is a typical "tracker" port, whereas 6881+ are typical client ports.

BitTorrent

XXX - BitTorrent is a protocol designed for transferring files. It is peer-to-peer in nature, as users connect to each other directly to send and receive portions of the file. However, there is a central server (called a tracker) which coordinates the action of all such peers. The tracker only manages connections, it does not have any knowledge of the contents of the files being distributed, and therefore a large number of users can be supported with relatively limited tracker bandwidth.

History

XXX - add a brief description of BitTorrent history

Protocol dependencies

  • ["TCP"]: Typically, BitTorrent uses ["TCP"] as its transport protocol. The well known TCP port for BitTorrent traffic is 6881-6889 (and 6969 for the tracer port). The DHT extension uses various UDP ports negotiated by the peers.

Example traffic

XXX - Add example traffic here (as plain text or Ethereal screenshot).

Ethereal

The BitTorrent dissector is (fully functional, partially functional, not existing, ... whatever the current state is).

Preference Settings

(XXX add links to preference settings affecting how PROTO is dissected).

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically.

  • attachment:SampleCaptures/PROTO.pcap

Display Filter

A complete list of BitTorrent display filter fields can be found in the [http://www.ethereal.com/docs/dfref/b/bittorrent.html display filter reference]

  • Show only the BitTorrent based traffic:

     bittorrent 

Note: implemented in Ethereal post 0.10.12!

Capture Filter

You cannot directly filter BitTorrent protocols while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one.

  • Capture only the BitTorrent tracker traffic over one of the default ports (e.g. 6881):

     tcp port 6881 

XXX - how to filter the tcp port range 6881-6889?

Discussion

BitTorrent (last edited 2019-03-18 22:16:09 by JimDeLaHunt)