Re: [squid-users] Squid wont talk to parent cache, ICP not working?

On 23/01/2012 9:31 p.m., someone wrote:
> Ok guys im trying to setup my existing and fully functional squid 3.1.6
> box on squeeze to talk to an identical squid box upstream, but it is not
> working, I cant see any requests in access.log on the upstream box of
> the downstream box fetching from it.

Okay.
> cache.log shows the following
>
> upstream box (parent):
>
> 2012/01/23 00:17:15| Adding nameserver 192.168.1.1 from squid.conf
> 2012/01/23 00:17:15| Accepting HTTP connections at 192.168.1.205:3128,
> FD 11.
> 2012/01/23 00:17:15| Accepting ICP messages at [::]:3129, FD 12.
> 2012/01/23 00:17:15| HTCP Disabled.
> 2012/01/23 00:17:15| Configuring Sibling 192.168.1.40/3128/3129
> 2012/01/23 00:17:15| Loaded Icons.
> 2012/01/23 00:17:15| Ready to serve requests.
>
> downstream box (sibling):(should I even conf this as a sibling?

No. Siblings are "sideways" in the hierarchy upstream/downstream
traffic flow.
http://wiki.squid-cache.org/Features/CacheHierarchy

> Also note that Nmap UDP -sU port scans from both hosts to eachother,
> show no open port on 3129 which im using for my ICP port.

You say "both". But there are *three* proxies in your shown config.
192.168.1.205 (upstream), 192.168.1.105 (downstream), and 192.168.1.40
(sibling of upstream)

Internet
|
up(205) -- sibling (40)
|
down (105)
|
clients

The parent proxy does not need configuring to know about any specific
downstream proxies. Except to allow ICP or HTCP queries and
forward-proxy traffic from them.

Amos
Received on Mon Jan 23 2012 - 10:25:38 MST