# Packetbeat Conundrum

**URL:** <https://discuss.elastic.co/t/packetbeat-conundrum/183781>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [May 31, 2019, 6:19pm UTC](https://discuss.elastic.co/t/packetbeat-conundrum/183781 "2019-05-31T18:19:10Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![thev0yager](https://avatars.discourse-cdn.com/v4/letter/t/c5a1d2/32.png) [@thev0yager](https://discuss.elastic.co/u/thev0yager)\
**Post date:** [June 4, 2019, 5:43pm UTC](https://discuss.elastic.co/t/packetbeat-conundrum/183781/21 "2019-06-04T17:43:02Z")

</div>

I realized this a little bit ago. That we don't have our dev environment configured to talk on any ports accept what is needed for the internet. So it makes sense that packetbeat isn't working, but it does make sense that logstash can't talk to elasticsearch. I posted my yml file for that a little bit ago.

---

<div class="post-metadata">

**Author:** ![thev0yager](https://avatars.discourse-cdn.com/v4/letter/t/c5a1d2/32.png) [@thev0yager](https://discuss.elastic.co/u/thev0yager)\
**Post date:** [June 4, 2019, 5:43pm UTC](https://discuss.elastic.co/t/packetbeat-conundrum/183781/22 "2019-06-04T17:43:50Z")

</div>

And when I did that ipconfig ens160 it couldn't find the NIC.

---

<div class="post-metadata">

**Author:** ![thev0yager](https://avatars.discourse-cdn.com/v4/letter/t/c5a1d2/32.png) [@thev0yager](https://discuss.elastic.co/u/thev0yager)\
**Post date:** [June 5, 2019, 3:57pm UTC](https://discuss.elastic.co/t/packetbeat-conundrum/183781/23 "2019-06-05T15:57:22Z")

</div>

Is there anything else I can do?

---

<div class="post-metadata">

**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\
**Post date:** [June 6, 2019, 7:18pm UTC](https://discuss.elastic.co/t/packetbeat-conundrum/183781/24 "2019-06-06T19:18:38Z")

</div>

Hi @theV0yager,

What is the current status of your problem? I'm getting a bit lost.

The last log you pasted if failing because the `ens160` device does not exists.

> Exiting: Sniffer main loop failed: Error starting sniffer: Error opening adapter: The system cannot find the device specified. (20) ~~~

Have you managed to configure Packetbeat with the right network device? In this situation Packetbeat is not even starting so I won't blame Logstash yet.

---

<div class="post-metadata">

**Author:** ![thev0yager](https://avatars.discourse-cdn.com/v4/letter/t/c5a1d2/32.png) [@thev0yager](https://discuss.elastic.co/u/thev0yager)\
**Post date:** [June 6, 2019, 7:21pm UTC](https://discuss.elastic.co/t/packetbeat-conundrum/183781/25 "2019-06-06T19:21:33Z")

</div>

Unfortunately the network device that I want packetbeat to communicate with is not setup to receive that kind of information yet. So, while I wait for that to be configured I am setting up the cluster in its entirety.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 4, 2019, 9:21pm UTC](https://discuss.elastic.co/t/packetbeat-conundrum/183781/26 "2019-07-04T21:21:44Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

[Previous page](https://discuss.elastic.co/t/packetbeat-conundrum/183781.md?page=1)