I would use cache_peer_access for all of the rules.
acl ftp proto ftp
# neighbour_1: domain .pl, except for ftp
cache_peer neighbour_1 parent 3128 3130 default
acl pl dstdomain .pl
cache_peer_access neighbour_1 allow pl !ftp
# neighbour_2: domains .com .net .org and all ftp
cache_peer neighbour_2 parent 3128 3130 default
acl com dstdomain .com .net .org
cache_peer_access neighbour_2 allow com
cache_peer_access neighbour_2 allow ftp
# neighbour_3: all the rest, but no ftp
cache_peer neighbour_3 parent 3128 3130
cache_peer_access neighbour_3 deny ftp
# no direct ftp access
never_direct allow ftp
This makes neigbhbour_3 the last resort parent for everything, except
for FTP which will fail if 2 is down.
/Henrik
PANDOR wrote:
>
> Hello, sorry to bother you, but how to solve this problem?
>
> My_Squid
> ========
> neighbour_1 ------------ domain .pl (all but no ftp)
> neighbour_2 ------------ domains .com .net .org ( and all the ftp's)
> neighbour_3 ------------ rest (all but no ftp)
> no direct ftp access
> ***************************
>
> acl ftpaccess proto ftp
>
> cache_peer neighbour_1 sibling 3128 3130
> cache_peer neighbour_2 sibling 3128 3130
>
>
> cache_peer_domain neighbour_1 .pl
> cache_peer_domain neighbour_2 .com .net .org
> cache_peer_access neighbour_1 deny ftpaccess
> cache_peer_access neighbour_3 deny ftpaccess
>
> never_direct allow ftpaccess
> ********************************
>
> but with those setting only ftp requests for .com .net and .org domain
> are processed through neighbour_2, all others are not processed due
> to no source for them
>
> THANK you in advance,
>
> Bye, PANDOR
-- To unsubscribe, see http://www.squid-cache.org/mailing-lists.htmlReceived on Thu Oct 19 2000 - 13:49:58 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:55:48 MST