# Dropped packets

**URL:** <https://community.netdata.cloud/t/dropped-packets/495>\
**Category:** Help\
**Tags:** agent\
**Created:** [November 22, 2020, 7:00pm UTC](https://community.netdata.cloud/t/dropped-packets/495 "2020-11-22T19:00:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alfrenovsky](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/alfrenovsky/32/168_2.png) [@Alfrenovsky](https://community.netdata.cloud/u/Alfrenovsky)\
**Post date:** [November 22, 2020, 7:00pm UTC](https://community.netdata.cloud/t/dropped-packets/495/1 "2020-11-22T19:00:55Z")

</div>

My netdata reports dropped packets each exactly 10 seconds.

I’ve found theres a MS NLB packet in my network (from 02:01:00:00:00:00 to FF:FF:FF:FF:FF:FF) each 10 seconds.

The curious thing is that dropped packets stops appearing while I do a thark or tcpdump (no matter if I’m using promiscuos mode or not)

I know this is not a netdata problem.

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [November 22, 2020, 7:12pm UTC](https://community.netdata.cloud/t/dropped-packets/495/2 "2020-11-22T19:12:13Z")

</div>

Hi @Alfrenovsky

> The curious thing is that dropped packets stops appearing while I do a thark or tcpdump

This is expected, the capture is done in [promiscuous mode](https://en.wikipedia.org/wiki/Promiscuous_mode). That is why nothing is dropped.

---

<div class="post-metadata">

**Author:** ![Alfrenovsky](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/alfrenovsky/32/168_2.png) [@Alfrenovsky](https://community.netdata.cloud/u/Alfrenovsky)\
**Post date:** [November 23, 2020, 11:28am UTC](https://community.netdata.cloud/t/dropped-packets/495/3 "2020-11-23T11:28:31Z")

</div>

Even if I capture with --no-promiscuous-mode I can see the packets and there’s no dropped

The dropped packets seems to be because they are from an unknown or unsupported protocol.
