Want package for squidanalyzer. INSTRUCTIONS AND FILES TO INSTALL
-
thanks hopefully it goes well :)
Also I had lightsquid before and umm…i think it broke it :( any way to fix perl again to get lightsquid working?
Thank you
-
Lightsquid hmm not really looked into what it uses to run. Squidanalyzer is so much more indepth .. wish someone would make a package for it. I am not really that skilled to make yet. and not know the system well enough to know if I will break something till I try it.
I may try tomorrow to get squid analyzer going again. if so I post what I did. I got a clean machine here as I reinstalled cause of too much modding to it got it messy..
-
Thanks man :) you made something really special ;D appreciate your work
-
got this working on my virtualbox THANKS your the MAN! ;)
-
care to share?
-
Well I got it working again. I just copied the files in my tutorial into the /temp/squidanalyzer for the temp.rar (which I had to extract in windows then copy the files over to the directory.
Then the squidanalyzer.rar I copied into /usr/local/www/squidanalyzer
Perl was already version 1.6.2 in my
2.2.6-RELEASE (amd64)
built on Mon Dec 21 14:50:08 CST 2015
FreeBSD firewall.wholesale-florida.com 10.1-RELEASE-p25 FreeBSD 10.1-RELEASE-p25 #0 c39b63e(releng/10.1)-dirty: Mon Dec 21 15:20:13 CST 2015 root@pfs22-amd64-builder:/usr/obj.RELENG_2_2.amd64/usr/pfSensesrc/src.RELENG_2_2/sys/pfSense_SMP.10 amd64Version
-
Oh I do need the /temp/squidanalyzer folder.. hmm finding which perl will work.
pkg install perl5-5.20.3_8
This seems to put the perl back and not break anything but can't get new data to come in with that
cd /temp/squidanalyzer/ && perl squid-analyzer -r -c /etc/squidanalyzer/squidanalyzer.conf /var/squid/logs/access.log /var/squid/logs/
I did have to put the files in /etc/squidanalyzer this is why some get missing config.
-
ok got it!
this is command that worked
cd /temp/squidanalyzer/ && perl squid-analyzer -d -l /etc/squidanalyzer/squidanalyzer.conf /var/squid/logs/access.log /var/squid/logs/
-
Hmm if we only had a package :)
-
I know. I will try learn how to make one. I am pretty good at learning this stuff. I did do programming in the past so not too much to learn I think. If I find the right tools. and maybe a video on how
-
Is there no one who knows how to make packages willing to try to make this one?
-
wish I had money for a bounty. Someone has to be interested with the package for this. And have the skills to do.. maybe even someone with money for bounty to find the right person to do it.
-
its been a while havent tried it until today still no luck :(
First
cd /temp/squidanalyzer/ && perl squid-analyzer -d -l /etc/squidanalyzer/squidanalyzer.conf /var/squid/logs/access.log /var/squid/logs/
The issue with that the route /etc/squidanalyzer/squidanalyzer.conf it was not created or did i miss something?
I would then unzip temp folder on windows and then place it in the / directory (root) of pfSense
then the squidanalyzer.rar unzip it on a windows copy that folder to /usr/local/www/
but had no luck im going to see if next week ill post a bounty
-
I have done some work to make it the newest version 6.5 and works good. I know now why some people have had some issues.. I really hope someone can make package. Let me know if I should zip up and make easy install for people
-
Thank you to Topper and Cino for your input here.
After a lot of reading this is what worked for me:
1. Thousands of additional FreeBSD packages can be installed on pfSense as noted here: https://doc.pfsense.org/index.php/Installing_FreeBSD_Packages
2. In the Index of those FreeBSD packages at this link http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/ you will find that SquidAnalyzer is available as "squidanalyzer-6.5.txz"
3. In the shell enter "pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/squidanalyzer-6.5.txz" (without quotes)
4. You will receive a confirmation of the install. The squidanalyzer.conf file is in usr/local/etc/squidreport/
5. Run the command manually once: cd /usr/local/bin/ && perl squid-analyzer
6. Set this as a cron job to your desire frequency
7. You should be able to access SquidAnalyzer at x.x.x.x/squidreport
It is cleaner to use pkg to install a FreeBSD package than to use WinSCP to copy and paste items from dropbox into your firewall installation. ;)
-
Thank you to Topper and Cino for your input here.
After a lot of reading this is what worked for me:
1. Thousands of additional FreeBSD packages can be installed on pfSense as noted here: https://doc.pfsense.org/index.php/Installing_FreeBSD_Packages
2. In the Index of those FreeBSD packages at this link http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/ you will find that SquidAnalyzer is available as "squidanalyzer-6.5.txz"
3. In the shell enter "pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/squidanalyzer-6.5.txz" (without quotes)
4. You will receive a confirmation of the install. The squidanalyzer.conf file is in usr/local/etc/squidreport/
5. Run the command manually once: cd /usr/local/bin/ && perl squid-analyzer
6. Set this as a cron job to your desire frequency
7. You should be able to access SquidAnalyzer at x.x.x.x/squidreport
It is cleaner to use pkg to install a FreeBSD package than to use WinSCP to copy and paste items from dropbox into your firewall installation. ;)
At step 5 I get this error:
[2.3.3-RELEASE][admin@xxxx.lan]/usr/local/bin: cd /usr/local/bin/ && perl squid-analyzer -r -c /var/squid/logs/access.log ERROR: you must give a valid output directory. See option: Output
Also, the output from the pkg install says:
Message from squidanalyzer-6.5: ----------------------------------------------------------------------------- 1\. Modify your httpd.conf to allow access to HTML output like follow: Alias /squidreport /usr/local/www/squidreport <directory usr="" local="" www="" squidreport="">Options -Indexes FollowSymLinks MultiViews AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.1</directory> 2\. If necessary, give additional host access to SquidAnalyzer in httpd.conf. Restart and ensure that httpd is running. 3\. Browse to http://my.host.dom/squidreport/ to ensure that things are working properly. 4\. Setup a cronjob to run squid-analyzer daily: # SquidAnalyzer log reporting daily 0 2 * * * /usr/local/bin/squid-analyzer > /dev/null 2>&1 or run it manually. For more information, see /usr/local/share/doc/squidanalyzer/README file.
Where is the httpd.conf file located?
-
There is no httpd.conf anywhere, obviously. Apache is not part of pfSense install.
-
Well not obvious to a non developer home user like myself, but now I know. Thanks.
I'm a bit out of my league without a walk through on this one, so I will have to hope for a package as well..
If I run "pkg delete squidanalyzer-6.5.txz" will I break anything? (will that even work?)
-
At step 5 I get this error:
[2.3.3-RELEASE][admin@xxxx.lan]/usr/local/bin: cd /usr/local/bin/ && perl squid-analyzer -r -c /var/squid/logs/access.log ERROR: you must give a valid output directory. See option: Output
AR15USR no need to uninstall the package, you are almost there. I failed to mention in my install notes that there is no httpd.conf. Instead there is squidanalyzer.conf and it is asking for a valid output directory. This file is located in
/usr/local/etc/squidreport/
You can edit squidanalyzer.conf by navigating to Diagnostics>Edit File>Browse and browse to that location. Or you can paste /usr/local/etc/squidreport/ into the "Path to be edited" bar and choose "Browse." Either way will get to the folder you need to be in to see squidanalyzer.conf
You can find your default Log Store Directory settings under Services>Squid Proxy Server>General. That log file location needs to be entered into the squidanalyzer.conf file. It is likely the default directory /var/squid/logs/access.log See below the section of the .conf file you will need to edit.
# Set the path to the Squid, squidGuard and/or ufdbGuard log files LogFile /var/squid/logs/access.log
Once you edit the .conf file, run this command again: cd /usr/local/bin/ && perl squid-analyzer
Then navigate to x.x.x.x/squidreport and enjoy.
Let us know how it goes.
-
Thanks for the help Presbuteros. I got the squidanalyzer.conf file edited and ran the command. It took a while to finish but it did so with no error.
When I pointed my browser to http://192.168.1.1/squidreport I get "403 Forbidden nginx".
EDIT: It works if I go to http://192.168.1.1/squidreport/2017/
I browsed the /squidreport folder and there is no .html file in there:/usr/local/www/squidreport .. 2016 2017 images SquidAnalyzer.current flotr2.js sorttable.js squidanalyzer.css