Graylog2/graylog2-server
Ver no GitHubNetflow plugin, tries to show ipv4 addresses in the message for ipv6 flows
Open
#6.076 aberto em 3 de jul. de 2019
#Mbuggood first issuetriaged
Métricas do repositório
- Stars
- (6.945 stars)
- Métricas de merge de PR
- (Mesclagem média 8d 19h) (297 fundiu PRs em 30d)
Description
Redirecting netflow statistics directly to graylog using sysctl net.netflow.destination=ip:port and configuring an Netflow UDP input to process all the incoming stats.
Expected Behavior
In the message it should show source and destination ip.
Current Behavior
Only does so for ipv4
Possible Solution
Change toMessage to use either ipv4 or ipv6 header for the flow.
Steps to Reproduce (for bugs)
- Configure a flow accounting on a ipv6 enabled interface with netflow pointing to Graylog Netflow input
- Look for messages with null values for source and destination
- Graylog Version: Graylog 3.0.2+1686930 on aac10c1cf381 (Oracle Corporation 1.8.0_212 on Linux 5.1.0)
- Elasticsearch Version:
- MongoDB Version:
- Operating System:
- Browser version: