Graylog2/graylog2-server

Netflow plugin, tries to show ipv4 addresses in the message for ipv6 flows

Open

#6,076 建立於 2019年7月3日

在 GitHub 查看
 (0 留言) (0 反應) (1 負責人)Java (6,945 star) (1,032 fork)batch import
#Mbuggood first issuetriaged

描述

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)

  1. Configure a flow accounting on a ipv6 enabled interface with netflow pointing to Graylog Netflow input
  2. 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:

貢獻者指南

技術棧
java
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic JavaUnderstanding of netflow protocol
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The issue is in the NetFlowFormatter.java file at line 131, specifically in the toMessage method. The current implementation only handles IPv4 headers; it needs to be extended to support IPv6 headers. Look at the netflow protocol structure for IPv6 addresses and modify the code to correctly extract source and destination IPs for both IPv4 and IPv6 flows.