Re: [squid-users] ACL "all" & squid3

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Tue, 01 Mar 2011 22:11:51 +1300

On 01/03/11 21:04, Voy User wrote:
> I know questions about 'all' splay tree warning has been asked in the list before& I found
> the reply at
> http://www.mail-archive.com/squid-users@squid-cache.org/msg57540.html
>
> However, my question is slightly different.
> I am using squid3 with debian lenny.
>
> I am using squid3 with webmin (yeah, I know a lot of people don't like webmin).
> The webmin squid module hasn't been updated for squid3 - so it doesn't know about
> the 'all' acl being inbuilt. So if I do not have the all acl in squid.conf& try to
> all rules using webmin, I don't see 'all' in the list of acl's it gives to 'Allow'
> and 'Deny'.
>
> I have a few options
<snip>
> 2) I continue using squid3& define the all acl.
>
> acl all src 0.0.0.0/0.0.0.0
>
> This gives me the foll warning
> --------------
> Restarting Squid HTTP Proxy 3.0: squid3 Waiting.....................done.
> 2011/03/01 13:13:33 WARNING: '0.0.0.0/0.0.0.0' is a subnetwork of '0.0.0.0/0.0.0.0'
> 2011/03/01 13:13:33 WARNING: because of this '0.0.0.0/0.0.0.0' is ignored to keep splay tree searching predictable
> 2011/03/01 13:13:33 WARNING: You should probably remove '0.0.0.0/0.0.0.0' from the ACL named 'all'

Yes it can be ignored if you must. It will just make a lot of noise on
every start, restart and reconfigure.

The safe way to define it for all squid versions 2.6+ is:

    acl all src all

> 2011/03/01 13:13:33 squid.conf line 2575: http_access allow
> 2011/03/01 13:13:33 aclParseAccessLine: Access line contains no ACL's, skipping

This part is a separate issue. Something has screwed up your http_access
line. That should have a WARNING on it as well.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.11
   Beta testers wanted for 3.2.0.5
Received on Tue Mar 01 2011 - 09:12:03 MST

This archive was generated by hypermail 2.2.0 : Tue Mar 01 2011 - 12:00:06 MST