Squidguard - pfsense crash
-
pfsense crashes every time I try to upload shallalist. squidguard tells me the file is uploading. After a time the message disappears. I then try to "apply" and 1.) squidguard stops 2.) all settings in squidguard are removed 3.) GUI is different (selections in black down left side of page). Sometimes I can reboot the box and recover, but still no shallalist. Other times I need to reinstall pfsense on the CF and rebuild entire system. Using Alix2D13 hardware from Netgate running pfsense 1.2.3 embedded. Any input from pfsense &/or squidguard experts greatly appreciated.
Will pfsense / squidguard tell me when the blacklist db has been rebuilt? How long do I need to wait? I have followed the instructions at http://diskatel.narod.ru/sgquick.htm after configuring transparent squid proxy.
-
Using Alix2D13 hardware from Netgate running pfsense 1.2.3 embedded.Embeded not supported a packages.
-
Is there a list of packages that will run / are supported on embedded pf?
-
Since the switch to NanoBSD most packages are supported.
If you are installing from the web gui only those which are suitable appear I believe.
See: http://doc.pfsense.org/index.php/Installing_packages_on_embeddedHowever squid and squidguard is going to be pushing the limits of your box.
Also since the filesystem is mounted read only you have to configure squid to use only memory for caching I seem to recall.Steve
-
Thanks for your help. Still having issues. I've tried reinstalling squidguard but still cannot get blacklists to upload. The upload gets through about half of the categories and then stops. Any ideas as to what woud cause this? I have same issue with Shalla, MESD, and URLBlacklist. They all partial upload and then stop. My 4GB CF is only at 12%. Alix <50% memory usage and very low CPU utilization. No problems uploading snort and emerging threats lists.
-
Could it be the same problem as this post:
http://forum.pfsense.org/index.php/topic,32000.0.html
There seem to be quite a few others running squid/squidguard on Alix so it should be possible.Steve
-
Hi Steve. Yes, I think it is the same problem. I'm surprised others are not reporting the same issue. It does not seem to be an Alix issue. I believe the files are extracted into folders that are not sized correctly. Do you know who is the lead developer for this package? I'd like to get their feedback. Thank you for your responses and follow-up.
-
I reported the same issue here: http://forum.pfsense.org/index.php/topic,32923.0.html.
But still no answer. :(
I think i'll go to install full on my alix. -
The squidGuard paсkage developed based on the capabilities pfsense full hdd installation. I am unable to test(to adapt) it on embeded / nanobsd.
Sorry. -
dvserg,
I haven't looked at the code lately but the easiest fix for that kind of thing is to download and unpack things to /root/ or make /root/sg/ and put them there. If you use /tmp or /var, those are memory disks and are quite small on NanoBSD (~40MB)
-
dvserg,
I haven't looked at the code lately but the easiest fix for that kind of thing is to download and unpack things to /root/ or make /root/sg/ and put them there. If you use /tmp or /var, those are memory disks and are quite small on NanoBSD (~40MB)
Is the '/root' a ram memory disk in the HDD full install too?
-
/root is just part of the normal storage on both full and nanobsd. Not a RAM disk.
Downloading to there would let you use as much space as you need, unless the / slice fills up… which on a full install would be several GB for most people.
-
/root is just part of the normal storage on both full and nanobsd. Not a RAM disk.
Downloading to there would let you use as much space as you need, unless the / slice fills up… which on a full install would be several GB for most people.
Ok, i understood. Thanks!
