Skip to content

Main content

Network: TCP Data Offset Header Bytes Tool

Translate the valid four-bit TCP data-offset field to total header and option-byte counts; no packet-length or option-content validation.

Loading tool…

Description

Multiply the data offset, from 5 through 15, by four to obtain headerBytes.

A wire-format length may count headers, payload, padding, or only part of an enclosing message. Offsets and exclusive ends must use a clearly stated byte convention.

Multiply the data offset, from 5 through 15, by four to obtain headerBytes.

When to use this tool

Use Network: TCP Data Offset Header Bytes when you need a field-level byte count or boundary check.

How to use the tool and how it works

  1. Enter dataOffset. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Multiply the data offset, from 5 through 15, by four to obtain headerBytes. Subtract the five-word base header before multiplying to obtain optionBytes.1

Input fieldMeaning and unitsAccepted input
dataOffsetData OffsetRequired. Safe integer.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
result.headerBytesHeader BytesCalculated result member: number.
result.optionBytesOption BytesCalculated result member: number.
json
{
  "input": {
    "dataOffset": 6
  },
  "output": {
    "result": {
      "headerBytes": 24,
      "optionBytes": 4
    }
  }
}

Limitations and assumptions

  • Option bytes include any padding; their contents are not parsed.
  • Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Compare the computed span with the actual captured buffer and validate its contents separately.

References

  1. Calculation and input contract: network/tcp-data-offset-header-bytes — tool.io

Similar or alternative tools