Kibana shows inverse source destination

The machine is capturing 6 interfaces on a virtual machine for which promiscuous mode is enabled.

Searching in kibana repeatedly reveals the source and destination flow to be inverse to what one would expect. Is there any way to correct this thru configuration and if so in what component ?