Hi to all.
I want to block web.whatsapp.com in some users.
But i already have those users in other group.
I suppose this is not a problem if i put the acl in some order... but its
not working.
For example, i have group
I-FULL: user1, user2, user3
I-RESTRINGIDOS: user1
This is my config file
###
I dont know if i explain well myself...
i just want block some web access (facebook, web.whatsapp, etc.) to just a
few users from a large group.
Thanks
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squ
Indeed.
Just enumerate this users in acl and put this acl above group acl.
05.12.2017 4:17, erdosain9 пишет:
> I dont know if i explain well myself...
> i just want block some web access (facebook, web.whatsapp, etc.) to just a
> few users from a large group.
> Thanks
>
>
>
> --
> Sent from:
>
Sorry, i dont understand.
Just enumerate the user in a acl?
a common acl or a kerberos acl??
can you put me a example please?
Thanks
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing
05.12.2017 4:38, erdosain9 пишет:
> Sorry, i dont understand.
> Just enumerate the user in a acl?
Not just. You will have an subset of users which will fires first on
specific URL.
Same like any firewall works, squid process acls from top to bottom.
>
> a common acl or a kerberos acl??
No matter.
Well, something like this (just to illustrate principe, dont copy and
paste ;)):
# Subset who don't have access to web whatsapp
acl no_web_whatsapp src IP1 IP2 IP3 IP4
acl web_whatsapp dstdomain web.whatsapp.com
# Group incouding IP1-IP4; the rest of group has access to web whatsapp
acl your_group
But, that's exactly the problem.
Thats what i do.
I do a have this large group
i-full
and a small group with a few users from i-full, the small group is called
i-restringidos.
And put i-restringidos in the top... (as you can see in my config file)
But, is not working. They can go trough the web
mmm
Ok, thanks
i do that but, with users (calling a new group in the domain). Instead of
this i can do a list of users in a file??
Anyway, i do that, but instead of
http access deny acl acl
i do
http access allow acl !acl
This will be the problem? or is the same? (the same "in other words")
05.12.2017 5:06, erdosain9 пишет:
> mmm
>
> Ok, thanks
> i do that but, with users (calling a new group in the domain). Instead of
> this i can do a list of users in a file??
> Anyway, i do that, but instead of
> http access deny acl acl
>
> i do
>
> http access allow acl !acl
>
> This will be th
On 05/12/17 11:59, erdosain9 wrote:
But, that's exactly the problem.
Thats what i do.
I do a have this large group
i-full
and a small group with a few users from i-full, the small group is called
i-restringidos.
And put i-restringidos in the top... (as you can see in my config file)
But, is no
Amos, you are as always deep and brief. I did not look carefully at the
list of rules;)
05.12.2017 5:16, Amos Jeffries пишет:
> On 05/12/17 11:59, erdosain9 wrote:
>> But, that's exactly the problem.
>>
>> Thats what i do.
>> I do a have this large group
>> i-full
>> and a small group with a few
Thanks Amos.
Let's be clear ... this configuration was working exactly as I wanted it to.
The users in each of those groups (i-full, sin_autenticacion, i-limitados)
navigated without problems. So that they did not navigate, I simply took
them out of one of those groups, period. Everything works as
Hi,
In general, the basic idea is this:
ACLs:
LARGEGROUP (eg. all users)
SMALLGROUP (subset of LARGEGROUP you want to further filter)
SMALLBLACKLIST (site list for SMALLGROUP)
http_access deny SMALLGROUP SMALLBLACKLIST
http_access allow LARGEGROUP [whatever]
http_access deny all
You could
On 05/12/17 13:07, erdosain9 wrote:
Thanks Amos.
Let's be clear ... this configuration was working exactly as I wanted it to.
The users in each of those groups (i-full, sin_autenticacion, i-limitados)
navigated without problems. So that they did not navigate, I simply took
them out of one of tho
14 matches
Mail list logo
