Merged in 3.1.3_3. Use the LAN (or another darkstat interface) IP for the redirect if you don't want to be bothered with HSTS/DNS/reverse proxies.

After reading everything you did there, and considering it's called 'darkstat', I'm surprised you didn't use the term 'dark age' instead of 'stone age'…    ::)

on another note, it made me considering trying haproxy for a home setup...  :o

Thanks for all the effort you throw at pfsense and everything else here  8)

Fix merged in 3.1.3_2. Upgrade when available (or, preferably, uninstall before trying to upgrade to avoid any further quirks.)

2.4 beta sends those now.

MONITOR: GW_CBL is available now, adding to routing group ALLWAN 62.xxx.xxx.1|192.168.xxx.252|GW_CBL|12.661ms|4.793ms|13%|loss

THANK YOU!!!!! I've been waiting for this fix FOREVER. Glad to see this package fully working again.

You mean beyond the checkbox in the GUI to disable alerts altogether in the pfSense GUI, and another set of checkboxes in the ntopng preferences menu to do the same? Then no.  :o ::)

Check ntopng.

Hi "I got my own thread!"  :)

I found the cause but not sure if its solvable.

My pfsense is a guest in a Windows 2012 R2 Hyper-V. A reboot of the pfsense made the clock take a jump, backwards.  ::)

Running the update script manually show this:
ERROR: /var/db/rrd/ovpns2-traffic.rrd: illegal attempt to update using time 1483895952 when last update time is 1484149652 (minimum one second step)
1484149652s-1483895952s=253700s, ~1h10m …

I had the guest-service for the guest machine turned off in Hyper-V because I wanted pfsense to manage the time through NTP by it self.

I'll proceed with some trial and error here to see which combination of time-sync that's working in my setup.

Thank you. Much appreciated.

I just merged PR# 185

Razzfazz was kind enough to submit a PR: https://github.com/pfsense/FreeBSD-ports/pull/185

It just got merged, so you should be able to test in snapshots soon enough.

It's a nice web-based interface (used it in the past, don't have it installed now though)… you will definitely want to make sure you check the option to monitor the LAN addresses only, as otherwise it'll track EVERY connection that each host on your network makes.

One other note about darkstat though... its data does not persist after a reboot.

If you have Squid installed on your pfSense box, it may have cached the update files, then passed them to other computers (non-Windows 10, or Windows 10 that don't have the option to receive updates from others on the network) that were requesting them as well. Microsoft released updates that week on Tuesday, so if you have updates set to install on Friday-Saturday, then that might explain it.

@Tjh:

I tried nfsen, was a bit more difficult to get setup, but I did it. Now i visit the nfsen 'page' on my webserver…all I get is a bunch of rrd graphs (which are already present in pfsense by default, and are a lot better tbh). And still no way of splitting by IP

It can process your top talkers for you..

Bottom of the details page..  see attached pic I just set this up last night.. Or you could add this plugin
https://sourceforge.net/projects/hoststats/
HostStats allows you to look on your NetFlow data from a different point of view - it calculates statistics about network traffic of each individual host (IP address) in the network.

It not all that hard to setup ;) Took a couple of minutes - good instructions here https://www.youtube.com/watch?v=rge1mBvzj5E you don't have to watch the video I hate those!!  The instructions are in text in the comments.

But it would be nice a simple built in way to track by IP data use..

toptalkers.png
toptalkers.png_thumb

I know it's been a few weeks since you posted but how did you get vnstat?  I don't see it in my list of packages.  I'm running 2.3.2-p1.  Thanks.