Don't use a netmaks for ranges of IP addresses. Netmasks is for denoting
whole networks.
Also, unless you want to control different access levels to the
different sites, you may collapse all of them into a single acl
definition.
To not cache, see no_cache.
To force the client to go direct, see your client documentation. This is
outside the scope of Squid as Squid cannot really tell the client it
should have gone direct instead of contacted Squid.
Regards
Henrik
Greg Darby wrote:
>
> I have an WAN which requires 5 remote sites to use the central Squid proxy
> server (1) and are unsure how to setup the acl to allow the different IP
> ranges from all remote sites.
>
> Do i use the following ?
>
> acl site1 src 131.121.0.1-131.121.0.50/255.255.255.0
> acl site2 src 132.121.0.1-132.121.0.40/255.255.255.0
> acl site3 src 192.168.10.1-192.168.10.50/255.255.255.0
> acl site4 src 172.16.1.1-172.16.1.10/255.255.255.0
> acl site5 src 171.16.1.1-171.16.10.20/255.255.255.0
> http_access allow site1
> http_access allow site2
> http_access allow site3
> http_access allow site4
> http_access allow site5
> http_access deny all
>
> Also, how can you force Squid to not cache specified websites and force the
> client to go direct?
>
> I hope you can help!
>
> Greg Darby
> Systems Administrator
> Ramelec (SA) Pty Ltd
> 2 Ontario Ave Panorama
> South Australia 5041
> Tel: +61 8 83742100
> Fax: +61 8 83742102
>
> =============================================================================================
> This email and any attachment has been checked for the presence of known Virus's by Ramelec's NTMail Virus Scanner.
Received on Mon Dec 10 2001 - 17:45:25 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:05:18 MST