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 13 and 15 (spanning 2 versions)
Revision 13 as of 2011-07-19 02:47:48
Size: 3216
Editor: WenchaoWang
Comment: add TCP history
Revision 15 as of 2020-07-23 01:43:52
Size: 3163
Editor: ChuckCraft
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
When Vint Cerf and Bob Kahn first wrote the specifications for the protocol in 1973, the Internet was prohibited from commercial use. In May, 1974, the Institute of Electrical and Electronic Engineers (IEEE) published a paper entitled "''A Protocol for Packet Network Interconnection''^[[http://en.wikipedia.org/wiki/Transmission_Control_Protocol#cite_note-1]]^." As the paper's authors, Cerf and Kahn described an internetworking protocol for sharing resources using packet-switching among the nodes. A central control component of this model was the ''Transmission Control Program'' that incorporated both connection-oriented links and datagram services between hosts. The monolithic Transmission Control Program was later divided into a modular architecture consisting of the ''Transmission Control Protocol'' at the connection-oriented layer and the ''Internet Protocol'' at the internetworking (datagram) layer. The model became known informally as ''TCP/IP'', although formally it was henceforth called the ''Internet Protocol Suite''. When Vint Cerf and Bob Kahn first wrote the specifications for the protocol in 1973, the Internet was prohibited from commercial use. In May, 1974, the Institute of Electrical and Electronic Engineers (IEEE) published a paper entitled "''A Protocol for Packet Network Interconnection''." As the paper's authors, Cerf and Kahn described an internetworking protocol for sharing resources using packet-switching among the nodes. A central control component of this model was the ''Transmission Control Program'' that incorporated both connection-oriented links and datagram services between hosts. The monolithic Transmission Control Program was later divided into a modular architecture consisting of the ''Transmission Control Protocol'' at the connection-oriented layer and the ''Internet Protocol'' at the internetworking (datagram) layer. The model became known informally as ''TCP/IP'', although formally it was henceforth called the ''Internet Protocol Suite''.
Line 29: Line 29:
 * [[TCP_Relative_Sequence_Numbers]]  * [[TCP_Relative_Sequence_Numbers]] and TCP Window Scaling

Transmission Control Protocol (TCP)

The TCP protocol provides stream based connection oriented transfer of data of the InternetProtocolFamily.

It provides the described TCP port multiplexing and much more. It establishes a logical connection, which is reliable against the problems of PacketLoss, DuplicatePackets and such.

Sending a few bytes will transfer them to the remote host, without giving any additional faulty or missing bytes to the receiving application.

History

When Vint Cerf and Bob Kahn first wrote the specifications for the protocol in 1973, the Internet was prohibited from commercial use. In May, 1974, the Institute of Electrical and Electronic Engineers (IEEE) published a paper entitled "A Protocol for Packet Network Interconnection." As the paper's authors, Cerf and Kahn described an internetworking protocol for sharing resources using packet-switching among the nodes. A central control component of this model was the Transmission Control Program that incorporated both connection-oriented links and datagram services between hosts. The monolithic Transmission Control Program was later divided into a modular architecture consisting of the Transmission Control Protocol at the connection-oriented layer and the Internet Protocol at the internetworking (datagram) layer. The model became known informally as TCP/IP, although formally it was henceforth called the Internet Protocol Suite.

Protocol dependencies

  • IP: Typically, TCP uses IP as its underlying protocol. The assigned protocol number for TCP on IP is 6.

Example traffic

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

Wireshark

TCP dissector is fully functional.

You can select a TCP stream very fast by using the Follow TCP stream feature. First select a TCP packet in the packet list pane and then click the menu item Analyze/Follow TCP Stream

There are two statistical menu items for TCP available: Statistics/Endpoints which contains a tab showing all TCP endpoints (combination of IP address and TCP port) and Statistics/Conversations, which contains a tab showing all TCP conversations (combination of two endpoints).

Preference Settings

Example capture file

XXX - Add a simple example capture file. Keep it short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.

Display Filter

A complete list of TCP display filter fields can be found in the display filter reference

  • Show only the TCP based traffic:
     tcp

    Show only the traffic to and from TCP port 80 (usually HTTP):

     tcp.port == 80

Capture Filter

  • Capture only the TCP based traffic:
     tcp

  • RFC793 TRANSMISSION CONTROL PROTOCOL

Discussion

Transmission_Control_Protocol (last edited 2020-07-23 02:19:27 by ChuckCraft)