I got the first problem solved, with the child forwarding all requests to the parent. But the second problem still exists. My college does not run a dns server, could that be the problem? Or am i missing something in the configuration? Foll are the entries related to dns in my conf as I have kept them...
# cache_dns_program /usr/lib/squid/ # dns_children 5 # dns_retransmit_interval 5 seconds # dns_timeout 5 minutes # dns_defnames off dns_nameservers 10.0.1.1 negative_ttl 5 minutes # positive_dns_ttl 6 hours # negative_dns_ttl 5 minutes visible_hostname none #hostname_aliases none
Thank You
Dave Raven wrote:
Add login=PASS to the end of your cache peer line, this will instruct it to pass up any login information in the request.
-----Original Message-----
From: Swaroop Shere [mailto:[EMAIL PROTECTED] Sent: 20 August 2004 09:40 AM
To: [EMAIL PROTECTED]
Subject: [squid-users] hierarchy problerms
Importance: High
Hello,
I am a college student trying to implement a
hierarchy of proxy servers as a part of a project. The
parent is at 10.0.1.1, while the child is at
10.0.2.55. While, i am configuring the child, I have
no control over the parent. (I have to give a written
application for any services from the authorities wrt
the parent) They have enabled the icp port. After my
initial configuration, the child squid started
successfully. I have kept no authentication at the
child (comments kept at all authentication
parameters), but the parent requires authentication,
it uses some microsoft module (sorry, i am still a
newbie).
Now i have 2 problems. First:
Whenever a browser configured to request the child tries to access a local website (eg http://10.0.0.222), it gets a prompt for username and password, whose title shows 10.0.2.55 and even if i enter the same username and passwd that i use for the parent, it gives me an authentication error. Through tcpdump, i found out that the child squid is not forwarding the username and password to the parent. The error page that the client recieves, shows that the error is generated by the parent squid (10.0.1.1). Also, all requests from the clients through the parent directly are served.
Second:
Whenever a browser configured to request the child squid tries to access a remote website (eg www.google.com), the client does not get any prompt for proxy username and password, and finally gives an error, that the page is not found. If the same client is configured to request the parent (10.0.1.1), it gets the pages. What could be this problem?
Please help, Thank you.
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
