# Logstash input UDP netflow codec - BUG?

**URL:** <https://discuss.elastic.co/t/logstash-input-udp-netflow-codec-bug/99098>\
**Category:** Logstash\
**Created:** [September 1, 2017, 8:04am UTC](https://discuss.elastic.co/t/logstash-input-udp-netflow-codec-bug/99098 "2017-09-01T08:04:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pierre1](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@pierre1](https://discuss.elastic.co/u/pierre1)\
**Post date:** [September 1, 2017, 8:04am UTC](https://discuss.elastic.co/t/logstash-input-udp-netflow-codec-bug/99098/1 "2017-09-01T08:04:20Z")

</div>

i think there is a bug with UDP / netflow :  
my conf :

> input {  
> udp {  
> port =\> 9556  
> codec =\> netflow {  
> versions =\> [5, 9]  
> target =\> "nf"  
> }  
> type =\> "netflow"  
> }  
> }

In all case i receive the flow  
first :

when my elk server can’t communicate with my network equipment but i can  
see the netflow in it network interface with tcpdump, i have no data  
processed  
second case :  
when my elk server can communicate with my network equipment and i  
can see the netflow in it network interface with tcpdump, i have data  
processed  
it does not mean anything, with UDP there is not communication as in TCP

---

<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:** [September 29, 2017, 8:04am UTC](https://discuss.elastic.co/t/logstash-input-udp-netflow-codec-bug/99098/2 "2017-09-29T08:04:57Z")

</div>

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