Parent Setup?

At the moment we do not have our own parent but rely on a parent outside the organisation which we have no control over. Want I want to do is setup our own parent which will handle all the ACLs and authentication (instead of what we have now, ACLs on all squid boxes).

Bit of background info:
-----------------------
We have around 18 sites using squid, our WAN is a star type setup with the firewall+parent proxy being at the center (beyond our control). Setting up a parent is no problem but with the WAN the way it is a parent will cause traffic problems for the link it is placed on.

Current Setup
--------------------------------

  squid o o squid
           \ /
            \ /
             \ /
 squid o -- o current parent+gateway to the Internet
             \
                \
                 \
                    Internet

Proposed Setup
-------------------------------

  squid o o parent
           \ /
            \ /
             \ /
 squid o -- o parent+gateway to the Internet (our parent will use this parent)
               \
                \
                 \
                    Internet

Our parent does not have to store objects but just handle the ACLs and authentication.

What have other ppl done?

I came across this is the FAQ:

        Proxy Forwarding
        ----------------
        cache_peer parentcache.foo.com parent 3128 0 no-query default
        acl all src 0.0.0.0/0.0.0.0
        never_direct allow all

Will this do what I want ie, my parent not caching just forwarding?
 
How much traffic does a forwarding setup cause?

thanx.

------------------------------------------------------
Dean Grubb
Customer Support Officer
TAFE Tasmania - Devonport Campus
email: grubbda@tafe.tas.edu.au
------------------------------------------------------
Received on Mon Feb 14 2000 - 00:20:41 MST