---
title: "Robin Hayer (@robinhayer) | Hashnode"
description: "Senior Security Automation Engineer | OT/ICS & Cloud Security | Detection Engineering | Go & Python. Read the latest articles by Robin Hayer on Hashnode."
url: "https://hashnode.com/@robinhayer"
---

@robinhayer

# Robin Hayer

@robinhayer · Toronto, Canada · Joined August 2026

Senior Security Automation Engineer | OT/ICS & Cloud Security | Detection Engineering | Go & Python

### [The tool said it wrote 48 packets. Only 44 were there](https://robinhayer.hashnode.dev/pcapsplitter-file-collision-tcp-session-reuse?utm_source=hashnode&utm_medium=feed)

Exit code zero said success, but the packet count said otherwise.

5 min read · [robinhayer.hashnode.dev](https://robinhayer.hashnode.dev/pcapsplitter-file-collision-tcp-session-reuse?utm_source=hashnode&utm_medium=feed)

[Sep 21](https://hashnode.com/posts/pcapsplitter-file-collision-tcp-session-reuse/6ab07e6b76ee31e90b4bb4c5)

### [Concurrency Without a Parallel Parser: Splitting PCAPs by Session](https://robinhayer.hashnode.dev/concurrency-without-a-parallel-parser?utm_source=hashnode&utm_medium=feed)

tshark needs linear state, so I moved the concurrency upstream — and hit a corrupted-output problem on the way.

5 min read · [robinhayer.hashnode.dev](https://robinhayer.hashnode.dev/concurrency-without-a-parallel-parser?utm_source=hashnode&utm_medium=feed)

[Aug 26](https://hashnode.com/posts/concurrency-without-a-parallel-parser/6a8eba2c964c1d5aabe05ce9)

### [The 2.5 GB Wall: Why My tshark Wrapper Died, and How Streaming Fixed It](https://robinhayer.hashnode.dev/the-2-5-gb-wall?utm_source=hashnode&utm_medium=feed)

Three queries, a single-threaded tool, and a file too big for memory.

4 min read · [robinhayer.hashnode.dev](https://robinhayer.hashnode.dev/the-2-5-gb-wall?utm_source=hashnode&utm_medium=feed)

[Aug 10](https://hashnode.com/posts/the-2-5-gb-wall/6a794076482c7fa8d20a768f)
