# Cisco filebeat module not listening on port as configured

**URL:** <https://discuss.elastic.co/t/cisco-filebeat-module-not-listening-on-port-as-configured/341988>\
**Category:** Elasticsearch\
**Created:** [August 30, 2023, 2:30pm UTC](https://discuss.elastic.co/t/cisco-filebeat-module-not-listening-on-port-as-configured/341988 "2023-08-30T14:30:08Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![artschooldropout](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@artschooldropout](https://discuss.elastic.co/u/artschooldropout)\
**Post date:** [August 30, 2023, 5:42pm UTC](https://discuss.elastic.co/t/cisco-filebeat-module-not-listening-on-port-as-configured/341988/9 "2023-08-30T17:42:33Z")

</div>

Looks like someone else had the same issue: [Filebeat Cisco Module: Listening on IPV6 only?](https://discuss.elastic.co/t/filebeat-cisco-module-listening-on-ipv6-only/229716)

So in the cisco.yml file, I specified the host IP instead of 0.0.0.0. That seems to have helped:

```auto
netstat -nulp
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 127.0.0.53:53 0.0.0.0:* -
udp 0 0 [host IP]:9002 0.0.0.0:* -

```

I tried to netcat a message:

```auto
$ echo ‘hello’ | nc -v -u -w 0 [host IP] 9002
Connection to [host IP] 9002 port [udp/*] succeeded!

```

However, I see nothing in the logs.

---

_[View the full topic](https://discuss.elastic.co/t/cisco-filebeat-module-not-listening-on-port-as-configured/341988)._