← Complete project index

Infrastructure & Operations / Built / deployed

Network Payload Capture Pipeline

Minimal capability-bounded packet capture path that parses a live tcpdump stream into bounded payload snapshots consumed by the operations UI.

STATUSBuilt / deployed
AREAInfrastructure & Operations
STACK5 documented technologies
INTEGRATIONS2 connected / bounded services
01

OVERVIEW

What I built.

Minimal capability-bounded packet capture path that parses a live tcpdump stream into bounded payload snapshots consumed by the operations UI.

01

Built a deliberately capability-bounded packet-capture runtime around tcpdump.

02

Disabled persistent PCAP storage and promiscuous mode while keeping only bounded parsed payload snippets.

03

Connected the resulting snapshots to the Operations Portal's network views.

02

SYSTEM ARCHITECTURE

How the system is divided.

01
Architecture boundary

Host network -> tcpdump container with CAP_NET_RAW -> host parser -> bounded rolling JSON snapshot -> operations UI.

02
Architecture boundary

The capture container is read-only and does not receive broad host privileges.

03
Architecture boundary

Long-term packet archives are intentionally avoided in this path.

03

NETWORK / DATA FLOW

What talks to what.

04

TECHNOLOGY STACK

The technical surface.

01tcpdump
02PCAP
03Linux capabilities
04JSON
05Docker
05

IMPLEMENTATION

How it works in practice.

  1. 01

    Host network -> tcpdump container with CAP_NET_RAW -> host parser -> bounded rolling JSON snapshot -> operations UI.

  2. 02

    The capture container is read-only and does not receive broad host privileges.

  3. 03

    Long-term packet archives are intentionally avoided in this path.

06

TESTING & VALIDATION

How I know it works.

TEST 01

Container capability review

TEST 02

Read-only filesystem check

TEST 03

Promiscuous mode disabled

TEST 04

Bounded payload retention

TEST 05

Live snapshot consumption by UI

TEST 06

No persistent PCAP volume

07

EXTERNAL SERVICES & DEPENDENCIES

What sits outside the core.

CORENetwork Payload Capture Pipeline
08

ENGINEERING EVIDENCE

Artifacts behind the claims.

01Capture image
02CAP_NET_RAW-only policy
03Rolling JSON snapshot
04Network UI integration
05Collector scripts
09

BOUNDARIES / CONSTRAINTS

What the project does not pretend to solve.

Designed for debugging evidence, not unrestricted surveillance

No persistent packet archive in this path

Payload snippets are intentionally bounded

10

RESULT / CURRENT STATE

What this produced.

A narrow packet-evidence pipeline useful for debugging without turning the monitoring stack into an unrestricted capture appliance.