<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Flow-Analysis on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/flow-analysis/</link>
    <description>Recent content in Flow-Analysis on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/flow-analysis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted IPFIX Flow Collectors — ipfixcol2 vs nfcapd vs pmacct</title>
      <link>https://www.pistack.xyz/posts/2026-05-19-self-hosted-ipfix-flow-collectors-ipfixcol2-nfcapd-pmacct-guide/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-19-self-hosted-ipfix-flow-collectors-ipfixcol2-nfcapd-pmacct-guide/</guid>
      <description>&lt;p&gt;IPFIX (IP Flow Information Export, RFC 7011) is the IETF standard for exporting network flow data from routers, switches, and probes. While NetFlow v5/v9 are Cisco proprietary protocols, IPFIX is the open, extensible standard adopted by most modern network equipment. If you operate a self-hosted network infrastructure and need deep visibility into traffic patterns, bandwidth consumption, and application-level flows, deploying a dedicated IPFIX collector is essential.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
