You would need to know the IP Address of each client and a network definition for each one, create a network group containing all the clients definitions and then use a drop rule.
Or put them on thier own subnet and drop that subnet
you can't in Webadmin! If you enable the proxy all IP adresses covered by allowed networks can access the web - the rules are in an AUTO table which are processed before the USR tables.
Yes there is another Method, for the http-proxy you can define "allowed networks" but for that you must make a networkobjekt for every workstation that you would allow to connect to the internet but only for ip-addresses not for users.
Maybe somebody should consider adding an option for not allowed hosts in the Proxy HTTP Menu ? This should be very useful, I think. Or maybe adding a new rule status, ie. for dropping, covering proxy settings ?
However, to coin what another user said, you could, with a bit of planning have a happy medium.
Example for bocking the last 16 addresses:
On a 192.168.0.0/24 network, you could define say a /28 at the end of the range and then assign (either statically or via DHCP reservation) those specific users to that reserved block.
Then in your definitions, define the following networks and add them to one Network group (assuming you reserved the /28 at the end)
However, to coin what another user said, you could, with a bit of planning have a happy medium.
Example for bocking the last 16 addresses:
On a 192.168.0.0/24 network, you could define say a /28 at the end of the range and then assign (either statically or via DHCP reservation) those specific users to that reserved block.
Then in your definitions, define the following networks and add them to one Network group (assuming you reserved the /28 at the end)
And a variation on this need is to be able to configure Squid for the "always_direct" directive. My needs are to transparently proxy for internet bound URIs but go direct for my DMZ servers (no benefit caching local servers). Or is there another way?
