Re: [SQU] acl mistaking

Everything looks correct.

a) Have your restarted/reconfigured Squid after making the change to
squid.conf?

b) Are you sure the alien IP's are still allowed access? What is said in
access.log?

--
Henrik Nordstrom
Squid hacker
Priamikov Alexei wrote:
> 
> Hello squid-users,
>    I'm happy  with my squid 2.3STABLE4. But I have a problem with a access control lists.
>    I have 2 sub nets. one (193.233.108.80/255.255.255.240) are the real IP adresses and the other ones are internal (10.10.10.0/255.255.255.0)
>    and I want to close access to my squid for the "alien" IP. Is it correct to do the following conf:
> 
> 
>    acl all src 0.0.0.0/0.0.0.0
>    acl manager proto cache_object
>    acl localhost src 127.0.0.1/255.255.255.255
> 
>    acl econnet1 src 193.233.108.80/255.255.255.240
>    acl econnet2 src 10.10.10.0/255.255.255.0
> 
>    # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
>    #
>    http_access allow econnet1
>    http_access allow econnet2
>    http_access deny all
> 
>    so my ACL works not right. all IP adresses have access to http_access. :(
> 
>    I'd be pleased to any help. so what's the point?
> 
>    PS: Sorry for bad English.
> 
> 
> --
> Best regards,
>  Priamikov  Alex                        mailto:apriam@info.novsu.ac.ru
> 
> --
> To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html