/hub/runs/protectli-lan-endpoint-capture-counters
Published resultTest date: 2026-10-05Measured on: Protectli V1610

Protectli V1610: LAN Endpoint and Capture Counters

I also transferred fixed payloads from a bounded server on the Vault to the owned LAN client, then retained the engine counters with their actual observation windows. Successful downloads and complete packet inspection are different measurements here.

This page keeps the shared controls, retained measurements, failures, and comparison limits together. The linked files are there when you need the underlying table or method.

What you can compare here

This workload terminates on the Vault, so it is not WAN forwarding throughput. PCAP kernel drops span its full runtime without an isolated pre-LAN boundary; the Netmap stream-discard snapshot uses a different window and cannot serve as a matched loss comparison.

Related pages

Read the article Project repository

You can reuse Trevor-measured data from this page under the repository MIT terms. Retain the required notices when reusing the project documentation, and credit Trevor Unland when citing this run. Project media has separate terms in the repository.

Recorded results

Open the details under any row for the specific setup, outcome, artifact identity, and supporting file.

PCAP IDS endpoint

LAN-terminating server · four 128 MiB payloads

Published result

Measured on Protectli V1610 · Owned Vault test

Median payload rate
2370.291 Mbps
Terminating endpoint, approximate client timer; not forwarded WAN throughput.
Complete payloads
4 of 4
134,217,728 bytes each. (transfers)
Sampled core maximum
60 °C
Native samples during this endpoint workload.

Four complete rates were 2370.291 Mbps each under the recorded timer. The sampled core maximum was 60 °C.

Setup and original evidence

Protectli V1610 · OPNsense 26.7.5 / Suricata 8.0.7_1 · Owned Vault test · LAN-terminating server · four 128 MiB payloads

Pinned results and methodActual test host

Netmap IPS endpoint

LAN-terminating server · four 128 MiB payloads

Published result

Measured on Protectli V1610 · Owned Vault test

Median payload rate
848.137 Mbps
Terminating endpoint, approximate client timer; not forwarded WAN throughput.
Complete payloads
4 of 4
134,217,728 bytes each. (transfers)
Sampled core maximum
55 °C
Native samples during this endpoint workload.

Four complete rates were 848.137, 827.866, 848.808 and 848.137 Mbps. The sampled core maximum was 55 °C.

Setup and original evidence

Protectli V1610 · OPNsense 26.7.5 / Suricata 8.0.7_1 · Owned Vault test · LAN-terminating server · four 128 MiB payloads

Pinned results and methodActual test host

Capture and discard observations

Different engine windows · preserve each denominator

Published result

Measured on Protectli V1610 · Owned Vault test

PCAP kernel drops
313268 packets
Cumulative 962,578 packets across the full PCAP runtime.
Netmap stream discards
188 packets
610,614 packets in the separate 5m14s final snapshot.

PCAP cumulative counters cover 40+ minutes without a pre-LAN boundary. Netmap counters cover 5m14s after restart; its 188 discards were stream errors of unproven cause. No emitted kernel-drop counter is not a zero-loss certificate.

Setup and original evidence

Protectli V1610 · OPNsense 26.7.5 / Suricata 8.0.7_1 · Owned Vault test · Different engine windows · preserve each denominator

Pinned results and methodActual test host

Supporting evidence

Results and method

These are the few files that support this page directly. The repository holds the wider project history.

LAN payloads, counters and stability All trials, timer precision, capture windows and cleanup.Endpoint protocol Binding, finite payloads and throughput interpretation.

Controls

  • One explicit LAN bind and named client; at most four 128 MiB payloads per mode, with a 90-second server bound and no WAN listener.
  • Same unchanged Python 3.12 client and monotonic payload timing, excluding the protocol header and including receive to EOF.
  • Earlier Windows monotonic resolution was about 15.6 ms, so repeated rounded rates are approximate.
  • Servers exited after four transfers and TCP 5201 was absent afterward. Native stream protections stayed enabled.

What this run established

  • $All eight transfers returned exactly 134,217,728 bytes.
  • $PCAP rates were 2370.291 Mbps for each of four transfers. Netmap rates were 848.137, 827.866, 848.808 and 848.137 Mbps.
  • $PCAP later reported 313,268 kernel drops across 962,578 packets over 40+ minutes. These cannot all be attributed to the endpoint workload.
  • $A final Netmap snapshot at 5m14s contained 610,614 packets, 610,426 accepted and 188 stream-error discards, about 0.031%. No kernel-drop counter was emitted.
  • $A separate two-minute observation kept the same engine PID through 12 samples at 41–45 °C, with ordinary HTTPS/DNS still passing.

The Lab Notes

Get an email when I publish new hardware reviews, benchmarks, and security research. Unsubscribe anytime.

Email goes to Buttondown. Privacy details.

© 2026 Trevor Unland. All rights reserved.

PrivacyTermsRSS Feed

$ echo "Built with React + TypeScript"