ntopng VS pfSense

and use software: https://www.ntop.org/

InfluxDB 2.0 Support (ntopng github)

For what it's worth, there used to be a package in many Linux repositories called "ntop" [1] but became less popular when they went commercial. There is still a community version but I have no idea how popular it is any more. It was quite popular prior to projects like PiHole. Perhaps the older ntop has fallen out of favor so maybe there won't be any confusion.

[1] - https://www.ntop.org/

Have you seen https://github.com/ntop/ntopng?

NTOP -- Traffic Analysis.

One of the comments suggests using a managed switch that supports port mirroring, and installing a Flow collector on the connected system. Google netflow collector for software options. Something like ntop may work. See... HowTo Monitor Traffic in SMEs and Home Networks: A Primer

What can I do to implement GeoIP support into ntopng? The instructions I found on the internet (e.g. https://github.com/ntop/ntopng/blob/dev/doc/README.geolocation.md) did not seem to fit the case.

One option is Firewalla Gold Plus, or you could buy a mini PC like it and run pfSense/OPNsense yourself.

Download and install pfsense as a virtual machine or partition: https://www.pfsense.org Configure it with the rules you want: https://youtu.be/VAGFGppSt74 Play with it, but be careful because it will block all traffic unless you check everything properly.

Another option is Firewalla, or buy a mini PC like it and run pfSense/OPNsense yourself. Two similar concepts, with the cost being either money or your DIY time. A lot of Firewalla users say that it's much easier for home use than pfSense/OPNsense, so you might find it worthwhile to spend a little more on it upfront and have to tinker less.

If you want firewall, I think you can use https://www.pfsense.org/ or https://opnsense.org/ , maybe running on an old PC or a Raspberry Pi. Not sure.

I've recently started using OPNsense. It's similar to pfSense, but seems to be considered a little more user-friendly.

For most router issues, I recommend people always put them in to dumb bridge mode and put a proper firewall like pfsense or opnsense as your gateway.

I have found that my historical average packet loss is about 0.02%. Something distinctly changed around 4/20 of this year, and now the average packet loss has gone up to 0.05% with spikes even higher, associated with periods of elevated ping times. It rarely did that before. Typically the IPv6 stack has more problems than v4 (especially an incident of packet loss on 4/28), and neither has been trouble-free since I started service in early 2020. My data comes from a pfSense installation.

I have done this using the Pfsense