Time Based restriction with Squid & Squid Guard

muffin

You can workaround this with a script on cron until somebody finds what is wrong.

What would the command be to restart squidguard?

phil.davis

On my test 2.1DEV 1G nanobsd system, I did:

pkg_add -r http://files.pfsense.org/packages/8/All/squid-2.7.9_1.tbz

It loads dependencies also, (cyrus, openldap, perl) spits out a lot of messages about things that don't exist during the perl phase. But none of this installs the pfSense-specific bits - the items on the web configurator menus and the php that goes with it. But, of course, it doesn't show up in "Installed Packages". So I can't configure Squid using the web configurator. It would be nice if the "Available Packages" list showed newer versions of the packages. But I have no idea how that list is loaded from a server somewhere.

Am I trying to do this all too early? Are the packages for 2.1DEV not up and running properly yet?
or
Are there more commands I can execute to install all the remaining pfSense bits of the package?

Also, how do I know which version and type of packages are supposed to go with 2.1DEV?

There are new tbz packages available dated 5 March, but there are also pbi packages with the same version numbers that have been there a while. I guess that the pbi packages are intended for using pbi_add with future systems based on FreeBSD9.

How does the "Available Packages" page know which version to offer?

Sorry for all the questions - I think I now need to read up on the whole development environment to get involved with testing or debugging!

marcelloc

I think the way cino does to install packages on 2.1 on his 2.1 pfsense are

Install pfsense package with gui and then go to console
Install freebsd package with pkg_add.

phil.davis

I started agaain with a freshly made CF card of 2.1-DEVELOPMENT. Although the "Available Packages" page just show 2.7.9, it actually fetches the 2.7.9_1 pbi file. I discovered that 2.1 is usig the pbi package system, so it is the pbi files that are used for this.
squid loads, I take all the defaults then just select "transparent proxy". It doesn't start, no "squid" user and no /var/squid/cache, so I did

pw useradd -g proxy -s /sbin/nologin -d /var/squid -n squid
chown -R squid /var/squid
mkdir /var/squid/cache
squid -z

This makes the squid user, gives it rights to /var/squid, makes the cache dir and initialises the cache.

Now /var/squid/logs/cache.log has good-looking messages in it. A process starts, but thenn it is gone by the time I can look for it from the command line. So there is some other issue still with getting squid running on 2.1-DEVELOPMENT (at least with nanobsd).

I will post this in the more appropriate 2.1 forum topic.

wibz

any workaround on this problem ?
a cron job to restart squidguard or a fix on squidguard config it self ?