@Lockie happy to help

OK thats a lot better there though there is a lot of crap to filter out. I was able to get most of the crap out by filtering for PSH+ACK like so: 'tcp[13] == 24' Theres still some junk in there though and it'd be nice to have more LFs in there between packets but this is definitely way better, thanks!

@johnpoz said in Simple package for monitoring IP up status: why not provide it to the community? Never said I wouldn't. But likely just remain as a patch file that can be NAME/IP configured by the user before applying. Not sure there is a demand for more configuration than that. Based on the thread here (and no others I can find) Seems the interested usage group would be really low (ie me). Hard to tell, as the only original responses to this thread were both suggesting to do something else. @johnpoz said in Simple package for monitoring IP up status: why would there even be a thread asking for such a thing in the first place because I originally asked the question, not being able to find anything? is this a trick question LOL Anyway thanks for the feedback, it was just something to occupy a few cycles.

what if i didn't want to loose data :(

@SteveITS Brilliant - uninstall/reinstall fixed it; thanks!

@trusmith said in Ntopng service will not start because Redis service is not running: Posting this here for anyone who's about to give up on life trying to sort this. Now I'm not saying that this is the ACTUAL solution, but this is what worked for me and surprisingly no post/thread seems to be talking about it clearly. For most people, if none of the above mentioned solutions worked for you all you need to do is the following in the exact same order: Uninstall ntopng from the WebGUI Package Manager successfully. Reboot Delete the ntopng folder in /var/db/ Delete the redis conf file in /usr/local/etc/redis.conf (it will be recreated again with the defaults once you reinstall the pkg) Reboot From the WebGUI, install ntopng and then go to settings and enable it. It will probably fail at this point but don't worry as most people give up at this stage. Reboot Once the system comes up, ntop should be running. Hardly a groundbreaking solution but missing step # 7 was the culprit for me. Hope this helps others like myself. Now I'm not sure which hook, argument, port, sock or permission is the reason behind this issue, but let's agree that there definitley is a bug which needs squashing. Thanks & Regards, John Excellent solution, worked for me! Thanks!

@SteveITS I have checked these settings, i'll monitor and see how it look. Thanks for the advice.

@insmod https://forum.netgate.com/topic/180932/howto-monitoring-the-system-and-network-by-netdata-pfsense-plus Using the Plus will make it much easier.