Am Dienstag, den 02.03.2010, 00:44 +1300 schrieb Amos Jeffries: > > > > Your actual full configuration would be a help. > Squid does not deal with interfaces. It only handles IPs. > OK, i made my way a little bit further. It seems it's a acl problem, which is a little bit strange or i don't understand IP-Adresses and subnetting any more. What i have is the following: #Recommended minimum configuration: 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 to_localhost dst 127.0.0.1/8 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT acl TRACE method TRACE .... http_access deny TRACE http_access deny exclude_neofonie http_access deny exclude_infometrics http_access allow to_localhost http_access deny all This should be ok for all 127.0.0.0/8 addressess i have (127.0.0.1 - 31). 127.0.0.1 - 21 & 127.0.0.27 - 31 are working with this configuration, but not 127.0.0.22 - 26). Only when i give for example 127.0.0.22 a seperate acl, i get the connect to the apache for the url behind that. additional: acl too_localhost dst 127.0.0.22 http_access allow too_localhost Where do i have the fault? Alex
