# odd large swing in capture loss

**URL:** <https://community.zeek.org/t/odd-large-swing-in-capture-loss/4523>\
**Category:** Zeek\
**Created:** [December 1, 2016, 12:56pm UTC](https://community.zeek.org/t/odd-large-swing-in-capture-loss/4523 "2016-12-01T12:56:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![erik\_clark](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@erik\_clark](https://community.zeek.org/u/erik_clark)\
**Post date:** [December 1, 2016, 12:56pm UTC](https://community.zeek.org/t/odd-large-swing-in-capture-loss/4523/1 "2016-12-01T12:56:29Z")

</div>

I have been running Bro with af\_packet for some time now, but this morning I noticed I have a massive capture loss, on the order of 10-30% capture loss across the workers. Could this be because I did not have checksums turned off in local.bro?

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:44pm UTC](https://community.zeek.org/t/odd-large-swing-in-capture-loss/4523/2 "2022-05-06T15:44:21Z")

</div>