Off-topic but interesting to this audience: since the last update, Fritz boxes support Wireguard.

https://en.avm.de/news/the-latest-news-from-fritz/2022/wireg...

This is neat.

A word of caution, depending on how the network is laid out, this could cause severe bandwidth overhead if there isn't a dedicated, and unmonitored, interface for the capture to flow over.

One needs to be careful not to have the captured traffic flowing out to the monitor via an interface that's being monitored, otherwise load will snowball.

The example here omits eth1, so I'm presuming that's the path the capture takes, but it would have been nice to see the author call this out. Otherwise, without some sort of capture-side filter, which the fritzdump.sh script and example doesn't seem to include, the capture will include a copy of the monitoring stream and the bandwidth will snowball.

There's also the issue of the monitoring port likely not able to capture full bandwidth of the aggregate of the other ports being monitored. Since the buffer in the device likely isn't unlimited, there's a possibility for lost data during times of high traffic.

Fritzboxes have the best non-OpenWRT OS IMHO

I’ve been doing something similar at home for years. An OpenBSD box at the egress point exports IPFIX data to nfdump and I designed custom charts for myself using the legacy dygraphs. IPFIX plus nfdump is wonderful as I can quickly use a tcpdump-like interface to very quickly search against data from months ago and the dygraphs charting allows me to easily see traffic patterns with the ability to quickly zoom in.

Slightly off-topic: "an" should not be used with words beginning with H, unless the H is unvoiced, such as "an homage".