Skip to content
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.

Wrong flow exporter ip #414

Closed
bdonfouet opened this issue Sep 18, 2019 · 2 comments
Closed

Wrong flow exporter ip #414

bdonfouet opened this issue Sep 18, 2019 · 2 comments

Comments

@bdonfouet
Copy link

Hello,
i'm testing elastiflow since fews days and it a great netflow analyser!
Since yesterday, when i install it, the flow exporter ip il always the ip of the bridge network created by the docker-compose commande. Ive tried to reinstall wiping everything, but got the same result.
any clue where can be the problem?

Thanks

@robcowart
Copy link
Owner

This is actually a Docker issue, which unfortunately has resulted in many issues being opened and closed without any real resolution. You can read more details here... moby/libnetwork#1994

The only way to ensure you have access to the original source IP is to use host networking. This is how I run my own Logstash instances, as well as other UDP listeners.

@sergey-safarov
Copy link

Looks that is root of issue
moby/libnetwork#2423

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants