Web Activity reports



  • Good day,

    2.3.2-RELEASE-p1 (amd64)
    built on Tue Sep 27 12:13:07 CDT 2016
    FreeBSD 10.3-RELEASE-p9

    I am new to PFSense, I've had a box installed at my company and I've been using BandwidthD and Ntop and NtopNG but ever since the upgrade BandwidthD was deactivated from the system. I've been using NTopNG but it's stopped working and not responding on port 3000.

    1. How can I change the port? (I've used the edit file and found the config in /usr/local/etc/rc.d/ntopng.sh) I've changed the port..should the firewall be rebooted?
    2. are there any other monitoring programs that I can use to monitor which of my staff are going to websites theyre not supposed to? (I am using squidproxy but there are some stations that arent restricted, I need to get a report but now that NTopNG isn't working I'm stuck) :(



  • Note that bandwidthd has recently come back from the dead. It is available on 2.3.4-RELEASE and 2.4-BETA.



  • Hi Phil,

    thank you but currently I only have the option to update from 2.3.2 to 2.3.3_1. that's the only update available.
    I'm even reluctant to do the upgrade because I'm not 100% familiar with the system and don't want to mess it up.

    had the system for a few months now, not yet a year and the technician that set it up hardly gives support anymore so I am kind of stuck and can't afford to mess the firewall up as we are running a call center of 200 agents.

    how do I upgrade to 2.3.4 from this release? and would you advise it seeing that I have like 60% experience and knowledge with PFSense?



  • I don't like to give this sort of advice, because if something unexpected happens then I will not be there to support you!
    Before upgrading (and in fact at all times) you should:

    1. Have a backup of config.xml - Diagnostics->Backup&Restore
    2. Have the installation image for your system somewhere, both on a computer somewhere and on media that will work on your pfSense hardware (USB stick or CD etc), that is a version of pfSense software that you "know and love"
    3. Know how to do a full install with factory defaults, get to the webUI from that and restore your config
    4. Sort of optional - access in a timely manner to spare hardware that matches the production hardware

    Without the above, if something breaks at any moment then you have a problem.

    All that said,;

    1. I am surprised that it does not offer direct upgrade to 2.3.4
    2. I would do the upgrade to 2.3.3-p1 and then it should offer you an upgrade to 2.3.4 from there
    3. Do the 2.3.4 upgrade

    because actually there are lots of bits and pieces fixed in every release, and there have been a few security patches also in recent months.



  • Thank you so much Phil,

    I will rather to an upgrade to the other versions, i cant afford to go down for any reason.

    or, if you could help me with this issue I am facing… I've been using Ntopng for a while and a 3 months ago it stopped working. someone told me to change the port from 3000 to another port that isn't in use. I found the config file (NTopng.sh) with Winscp and checked with the PFSense Editor as well changed the port to 3001 but the firewall still points it to 3000.

    1. Should I reboot the firewall after i made the change?
    2. How do I do a port forward to NtopNG from pfsense if possible if I can't change the port like that?

    thank you so much again for the help.



  • I have no experience with NtopNG - anyone else feel free to jump in…


Log in to reply