RE: [squid-users] Squid 2.4STABLE1 and wccp

G'day squid-users,

> -----Original Message-----
> From: Thomas Salmen [SMTP:thomas@radionet.co.nz]
> Sent: Wednesday, July 11, 2001 11:21 AM
> To: 'francisv@dagupan.com'
> Cc: squid-users@squid-cache.org
> Subject: RE: [squid-users] Squid 2.4STABLE1 and wccp
>
>
> Yep - ipchains redirect from ports 80 and 8080 to 3128.
>
> But I've managed to get it working again - seems that wccp will only
> work with the cisco if the cache is off the primary address on the
> interface...
>
        I've had similar problems with Squid with various other things...
ICP etc going through firewalls. Squid by default uses the primary address
of the interface, except where you can explicitly specify an outgoing
address. Explicitly specifying an outgoing address can cause problems too if
you have multiple different interfaces going to different places, as you can
only specify _one_ outgoing address.

        A solution I found was to put in explicit routes to the desired
destinations on the alias device;

        route add <someparenthost> gw <gwifrequired> dev eth0:0

        Note that this will show up to "route" as simply being on "dev
eth0", but the outgoing packets to <someparenthost> will definitely use the
ip address of eth0:0

        ABO
Received on Tue Jul 10 2001 - 19:38:23 MDT