---
title: "Discussion on \"Introducing Frame Bench: read, edit and build packet captures at the byte level\" | Hashnode"
description: "Discussion on \"Introducing Frame Bench: read, edit and build packet captures at the byte level\". Read, edit, and build packet captures at the byte level: open one you have, or make one from nothing."
url: "https://hashnode.com/posts/introducing-frame-bench-read-edit-and-build-packet-captures-at-the-byte-level/6ad1ff7654d3efb4f4f5fe3e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Introducing Frame Bench: read, edit and build packet captures at the byte level](https://blog.netomize.ca/introducing-frame-bench-read-edit-and-build-packet-captures-at-the-byte-level?utm_source=hashnode&utm_medium=feed)

Read, edit, and build packet captures at the byte level: open one you have, or make one from nothing.

Oct 16 · 10 min read · blog.netomize.ca  
Read the article

-   [#pcap](https://hashnode.com/tag/pcap)
-   [#packet-crafter](https://hashnode.com/tag/packet-crafter)
-   [#pcap-analysis](https://hashnode.com/tag/pcap-analysis)
-   [#network-security](https://hashnode.com/tag/network-security)
-   [#packet-capture](https://hashnode.com/tag/packet-capture)
-   [#frame-bench](https://hashnode.com/tag/frame-bench)

## Written by

[Netomize Official Blog](https://hashnode.com/@mfmokbel)

@mfmokbel · Toronto, ON

  
[View profile](https://hashnode.com/@mfmokbel)

Defensive Cybersecurity Consultancy

We empower businesses with cutting-edge software and expert services to navigate the complexities of today's cyber landscape. Secure your network with cutting-edge software and services that ensure your safety and peace of mind!

## Responses 3

Markdown supported · ⌘↵ to post

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/introducing-frame-bench-read-edit-and-build-packet-captures-at-the-byte-level/6ad1ff7654d3efb4f4f5fe3e/comment/6ad2b17e3155b5a0737b02dc)

Editing one address and having to fix the checksums by hand is exactly where most quick capture edits go wrong. Does Frame Bench recalculate IP, TCP and UDP checksums automatically after an edit, with an option to keep a deliberately broken one for testing? A diff view between the original and edited frame would also make it easier to attach modified captures to bug reports with confidence.

[Netomize Official Blog](https://hashnode.com/@mfmokbel)

[Oct 17](https://hashnode.com/posts/introducing-frame-bench-read-edit-and-build-packet-captures-at-the-byte-level/6ad1ff7654d3efb4f4f5fe3e/comment/6ad2b17e3155b5a0737b02dc#reply-6ad33327adb0a425428139e7)

Hello,

Regarding your point "_Does Frame Bench recalculate IP, TCP and UDP checksums automatically after an edit, with an option to keep a deliberately broken one for testing?_". Yes, it does, and for other protocols too. It recomputes lengths and checksums after every edit, padding included. You may turn this auto computation off so that it doesn't auto-fix them, and instead fix them on a packet-by-packet basis, from the decoded packet or a centralized Health check window.

"_A diff view between the original and edited frame would also make it easier to attach modified captures to bug reports with confidence._" Currently, Frame Bench allows you to diff multiple **different** frames at the same time at the byte level and protocol semantics level, but not for the same frame (Byte diff of up to five frames. Export as HTML, Markdown or unified diff). We'll add the capability to “Compare with original” for the same frame, that's a good idea.

Additionally, Frame Bench supports a separate “Capture diff” window, comparing the loaded capture against another file.

Thank you, for your input. If you have any other questions, please let us know.

[StackShortlist](https://hashnode.com/@veristria)

[Oct 17](https://hashnode.com/posts/introducing-frame-bench-read-edit-and-build-packet-captures-at-the-byte-level/6ad1ff7654d3efb4f4f5fe3e/comment/6ad2b17e3155b5a0737b02dc#reply-6ad33790739d998b57978667)

Being able to switch the auto fix off per packet is the part that matters for fuzzing, so that's good to know. The separate Capture diff window covers most bug report cases already. Compare with original on a single frame would close the last gap.
