Hi Henrik,
Checked and they are different. I'm getting this in the log 2007/01/11 15:34:57| WARNING: Forwarding loop detected for: Client: 127.0.0.1 http_port: 127.0.0.1:3128 GET http://localhost/squid-internal-dynamic/netdb HTTP/1.0 Host: localhost:8081 Via: 1.0 SquidA:8080 (squid/2.6.STABLE5), 1.0 SquidC:3128 (squid/2.6.STABLE5) X-Forwarded-For: unknown, 127.0.0.1 Cache-Control: max-age=259200 Connection: Close 2007/01/11 15:35:02| WARNING: Forwarding loop detected for: Client: 127.0.0.1 http_port: 127.0.0.1:3129 GET http://localhost/squid-internal-dynamic/netdb HTTP/1.0 Host: localhost:9091 Via: 1.0 SquidB:9090 (squid/2.6.STABLE5), 1.0 SquidC:3128 (squid/2.6.STABLE5) X-Forwarded-For: unknown, 127.0.0.1 Cache-Control: max-age=259200 Connection: Close Something odd is going on as it mentions SquidC:3128 in both reports. The bottom report should connect to C on port 3129, or I would have thought... the two dansguardian instances reflect the correct port numbers in their respective config files. Any thoughts? John --- On Thu 01/11, Henrik Nordstrom < [EMAIL PROTECTED] > wrote: From: Henrik Nordstrom [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [email protected] Date: Thu, 11 Jan 2007 15:22:05 +0100 Subject: Re: [squid-users] Forwarding loop tor 2007-01-11 klockan 05:40 -0500 skrev John Halfpenny:> The system is reporting routing loops on instance C at port 3128 via 8080 and 9090. Why is this?Triple-check your visible_hostname settings. C MUST be different from Aand B.RegardsHenrikAttachment: signature.asc (0.31KB) _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web!
