<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ipfix on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ipfix/</link>
    <description>Recent content in Ipfix on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ipfix/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Network Flow Collectors: GoFlow2 vs softflowd vs nfdump (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-24-self-hosted-network-flow-collectors-goflow2-softflowd-nfdump-guide/</link>
      <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-24-self-hosted-network-flow-collectors-goflow2-softflowd-nfdump-guide/</guid>
      <description>&lt;p&gt;Network flow data is the backbone of traffic analysis, capacity planning, and security monitoring. Flow protocols like NetFlow (Cisco), sFlow (sampling-based), and IPFIX (IETF standard) export metadata about network traffic — source/destination IPs, ports, protocols, byte counts — without capturing full packet payloads. This makes flow data lightweight, scalable, and privacy-friendly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
