Description
Decode the three-bit flags field into reservedSet, dontFragment, and moreFragments.
Packet headers encode several meanings in fixed-width fields. Bit positions, network byte order, and reserved values must be distinguished from validation of an entire message.
Decode the three-bit flags field into reservedSet, dontFragment, and moreFragments.
When to use this tool
Use Network: IPv4 Header Flags Df Mf Pair when you need to decode or encode one explicit packet field.
How to use the tool and how it works
- Enter flags. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Decode the three-bit flags field into reservedSet, dontFragment, and moreFragments.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| flags | Flags | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
| result.reservedSet | Reserved Set | Calculated result member: boolean. |
| result.dontFragment | Dont Fragment | Calculated result member: boolean. |
| result.moreFragments | More Fragments | Calculated result member: boolean. |
{
"input": {
"flags": 3
},
"output": {
"result": {
"reservedSet": false,
"dontFragment": true,
"moreFragments": true
}
}
}Limitations and assumptions
- The reserved flag is exposed rather than rejected; contradictory or invalid packet combinations remain the caller's responsibility.
- 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
Inspect the complete captured header and apply the relevant protocol's structural and state rules.
References
Similar or alternative tools
- Network: IPv4 Fragment Offset Byte Position
Multiply fragmentOffset in 0-8191 by eight to obtain the byte offset within the original payload.
- IPv4 Fragment Last Payload Boundary
Add offsetUnits × 8 to payloadBytes and reject an exclusive end beyond 65515.