Solved

Cascading a proxy with another one.

Posted on 2008-06-25
10
1,973 Views
Last Modified: 2013-12-16
Hi,
I have my gateway proxy server with ip 195.168.1.1 with port 8080(ACL, Site restriction given), running in Red Hat Linux 3.2.3-20. Now I am with  new proxy with ip 195.168.1.254 port 9000 with OS version Red Hat Linux 3.2.3-20. The second proxy will be used for upcountry,
Now i need to cascade 195.168.1.254 port 9000 with 195.168.1.1 with port 8080.Also i am able to browse in te second proxy configuring 195.168.1.1 as proxy server in mozila browser.
Kindly guide to configure in the squid for 195.168.1.254 port 9000 .
0
Comment
Question by:Spice_Telecom
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
10 Comments
 
LVL 27

Expert Comment

by:Nopius
ID: 21896130
> Now i need to cascade 195.168.1.254 port 9000 with 195.168.1.1 with port 8080

Do you need to configure 192.168.1.254 to use 1.1 or vice versa?

Read squid.conf file and find a cache_peer option. I recommend you to enable ICP protocol for inter-cache communication. If you can't use it:
"To have a non-ICP neighbor
#                    specify '7' for the ICP port and make sure the
#                    neighbor machine has the UDP echo port
#                    enabled in its /etc/inetd.conf file.
"

On down most (I guess it's a 1.254) proxy use the following squid.conf options on it:

http_port 9000
...[skipped]...
cache_peer 195.168.1.1 8080 7 [default]

If it is 1.1, use :
http_port 8080
cache_peer 195.168.1.254 9000 7 [default]



0
 

Author Comment

by:Spice_Telecom
ID: 21907417
HI,
Thanks . I am a beginner and teh recomendations is not working . Herewith attcahing the model diagram and conf required.


Proxy-Access.jpg
143-squid.doc
0
 
LVL 27

Accepted Solution

by:
Nopius earned 500 total points
ID: 21912585
You are using incorrect address/mask for internal network, 195.168.x.x is a legal Internet IP address space, so your clients can't access these IPs, you are warned.

1) HTTP port and HTTPS ports can't be the same:

http_port 9000
https_port 9000

fix your config like:
http_port 9000
https_port 9443

2) Not right:
cache_peer 195.168.1.1 parent 8080 0 default no-query

change to:
cache_peer 195.168.1.1 parent 8080 7 default no-query
#        icp_port:  Used for querying neighbor caches about
#                 objects.  To have a non-ICP neighbor
#                 specify '7' for the ICP port and make sure the
#                 neighbor machine has the UDP echo port
#                 enabled in its /etc/inetd.conf file.

Also open UDP port 7 (echo) on 195.168.1.1, uncomment:
/etc/inetd.conf:
#echo   dgram   udp     wait    root    internal
and restart inetd. Also open firewall rules for that port.

If you have some specific errors, please specify them also.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:Spice_Telecom
ID: 21923049
HI ,
Thanks. Now i have changed my gateway proxy to 192.168.100.1:9000. The above steps have ben followed. Previously when i connected my clients it was giveing error as Acess denieed.

Now it is giving page cannot be displayed.


New-Shot2.jpg
143-versquid.doc
0
 
LVL 27

Expert Comment

by:Nopius
ID: 21925128
Hi, Spice_Telecom.

the same problem with config, http_port and https_port can't be the same!

Now you are using 9001:
http_port 9001
https_port 9001

but that's incorrect. Use http_port 9000 as in previous config and https_port 9001.

> Previously when i connected my clients it was giveing error as Acess denieed.

That's new info. So if you got Access denied, that's a problem  in ACL rules. Every user, that uses 192.168.1.254:9000 as a proxy server will be visible as 192.168.1.1 parent proxy (because of cascading) and real IP address will be hidden, so Wite list and Black list on 192.168.1.1 should consider that HTTP access will be from 192.168.1.254.

Also tell me from what client are you trying to connect (IP address) and to what server?

0
 

Author Comment

by:Spice_Telecom
ID: 22016279
hi i am getting error as stated below

[root@SSP-VM squid]# /etc/init.d/squid reload
2008/07/16 20:01:35| squid.conf line 12: reply_body_max_size 0
2008/07/16 20:01:35| aclParseAccessLine: missing 'allow' or 'deny'.
squid: ERROR: No running copy
0
 
LVL 27

Expert Comment

by:Nopius
ID: 22020820
In a config you have sent in 1st post there is a line:

reply_body_max_size 0 allow all


Probably in most recent config you have no 'allow all', check it.
0

Featured Post

Portable, direct connect server access

The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question