Re: [squid-users] Fw: Update on Sattellite

From: Edward <edward@dont-contact.us>
Date: Tue, 1 May 2001 10:29:32 -0400

How stable is squid 2.5?

Just patch the acl.c file and install squid?

Thank you very much.

Best regards,

Edward Millington
(Network Administrator & Senior Technical Support Technician)
Cariaccess Communications Ltd.
Wildey
St. Michael
Barbados
1-246-430-7435
Fax : 1-246-431-0170
www.cariaccess.com

----- Original Message -----
From: "Henrik Nordstrom" <hno@hem.passagen.se>
To: "Edward" <edward@cariaccess.com>
Cc: "squid" <squid-users@squid-cache.org>
Sent: Tuesday, May 01, 2001 9:49 AM
Subject: Re: [squid-users] Fw: Update on Sattellite

> I don't see the need for an additional NIC unless you need that for your
> cabling purposes..
>
> If I understand your problem right you need to route requests from
> different clients out on different paths. There are three ways you can
> do this (and neither really requires an additional NIC, but it might
> simplify your networking cabling/routing)
>
> a) Run more than one Squid, one for each set of users
>
> b) Have a parent proxy for one of the groups (or one for each), and use
> cache_peer_access to send the correct user group there
>
> c) Use a Squid-2.5 patched with the tosaddracl patch to allow Squid to
> select different outgoing IP's for each group of users, and then set up
> your routing to have each of these IP's routed appropriately.
>
> --
> Henrik Nordstrom
> Squid Hacker
>
>
> Edward wrote:
> >
> > Hi Henrik!
> >
> > I will install 1 extra NIC.
> >
> > Assign one routable SAT address to 1 nic and a non-routable to the
other.
> >
> > I will then route the different address to different ports.
> >
> > I will then have squid listen to each port.
> >
> > We (interpacket and me), believe that this should solve the problem.
> >
> > What do you think?
> >
> > Thank you very much.
>
>
Received on Tue May 01 2001 - 08:29:21 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:59:46 MST