You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: