# Pachetbeat: not deterministic src/dst assignment

**URL:** <https://discuss.elastic.co/t/pachetbeat-not-deterministic-src-dst-assignment/48851>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [April 30, 2016, 8:22am UTC](https://discuss.elastic.co/t/pachetbeat-not-deterministic-src-dst-assignment/48851 "2016-04-30T08:22:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kofemann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kofemann/32/9495_2.png) [@kofemann](https://discuss.elastic.co/u/kofemann)\
**Post date:** [April 30, 2016, 8:22am UTC](https://discuss.elastic.co/t/pachetbeat-not-deterministic-src-dst-assignment/48851/1 "2016-04-30T08:22:10Z")

</div>

Hi folks,

With NFS beat we have notice that some time client and server ip addresses are mixed up. My understanding is that roles are assigned when a first packet is seen btypacketbeat. If you are in the middle of then it may happen that reply from a client seen first. Is it know behavior or NFS beat is not handle it correct?

Thanks,  
kofemann.

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [May 2, 2016, 4:14pm UTC](https://discuss.elastic.co/t/pachetbeat-not-deterministic-src-dst-assignment/48851/2 "2016-05-02T16:14:12Z")

</div>

NFS beat? You mean packetbeat? The NFS protocol analyzer transactions or flows have 'wrong' src/dst order? I think NFS transactions (being based on some RPC) order depends by originator of particular RPC call. For flows it depends on first seen packet.

---

<div class="post-metadata">

**Author:** ![kofemann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kofemann/32/9495_2.png) [@kofemann](https://discuss.elastic.co/u/kofemann)\
**Post date:** [May 2, 2016, 7:01pm UTC](https://discuss.elastic.co/t/pachetbeat-not-deterministic-src-dst-assignment/48851/3 "2016-05-02T19:01:04Z")

</div>

In the mean while, I have figured out. If you process request and **dir** in the Parse method is TspDirectionOriginal, then src and dst in correct order. Other wise you have to swap it. I was expected, that direction is always bound to the port number. But this is also ok, if you know about it 🙂

---

<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 5, 2017, 9:52pm UTC](https://discuss.elastic.co/t/pachetbeat-not-deterministic-src-dst-assignment/48851/4 "2017-07-05T21:52:34Z")

</div>