Skip to content

Main content

Network: IPv4 Fragment Offset Byte Position Tool

Translate the RFC791 thirteen-bit IPv4 fragment offset into original-payload byte position using its standardized eight-byte units; no reassembly.

Loading tool…

Description

Multiply fragmentOffset in 0-8191 by eight to obtain the byte offset within the original payload.

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 fragmentOffset in 0-8191 by eight to obtain the byte offset within the original payload.

When to use this tool

Use Network: IPv4 Fragment Offset Byte Position when you need a field-level byte count or boundary check.

How to use the tool and how it works

  1. Enter fragmentOffset. 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 fragmentOffset in 0-8191 by eight to obtain the byte offset within the original payload.1

Input fieldMeaning and unitsAccepted input
fragmentOffsetFragment OffsetRequired. Safe integer.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
result.payloadByteOffsetPayload Byte OffsetCalculated result member: number.
json
{
  "input": {
    "fragmentOffset": 10
  },
  "output": {
    "result": {
      "payloadByteOffset": 80
    }
  }
}

Limitations and assumptions

  • This is a position, not a total datagram length or a reassembly result.
  • 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/ipv4-fragment-offset-byte-position — tool.io

Similar or alternative tools