Editing
TCP/IP Stack
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== 4. Anatomy of a TCP Packet == Every TCP segment contains control fields in the header and a chunk of data. These fields help manage the flow and structure. {| class="wikitable" ! Header Field !! What It Does |- | Source Port || Chosen by the sender to identify its own app |- | Destination Port || Tells the receiver which service should handle the data (e.g. port 80 for web) |- | Source IP || The sender’s IP address |- | Destination IP || The target machine’s IP address |- | Sequence Number || Tracks where this data fits in the overall stream |- | Acknowledgment Number || Confirms what data has been received so far |- | Flags || Signal events like start (SYN), end (FIN), or errors (RST) |- | Window Size || Controls how much data can be sent before pausing |- | Checksum || Used to detect if the packet was changed during transit |- | Payload || The actual content — like text, commands, files, etc. |}
Summary:
Please note that all contributions to HackOps may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
HackOps:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
Edit source
View history
More
Search
Navigation
Tools
What links here
Related changes
Special pages
Page information