RE: [NTISP] CACHING DEVIC

John Njuguna ( (no email) )
Fri, 14 Apr 2000 18:34:31 +0300

Example of how to do it on Cisco.

Define an access list
access-list 101 permit tcp host 10.10.10.10 any eq www

Define a route map
route-map mypolicy permit 10
match ip address 101
set ip next-hop 201.10.10.10

Apply the policy to the Incoming interface of router

ip policy route-map mypolicy

-----Original Message-----
From: ntisp-request@iea-software.com
[mailto:ntisp-request@iea-software.com]On Behalf Of Brian Johnson
Sent: Friday, April 14, 2000 7:02 PM
To: ntisp@iea-software.com
Subject: RE: [NTISP] CACHING DEVIC

> -----Original Message-----
> From: ntisp-request@iea-software.com
> [mailto:ntisp-request@iea-software.com]On Behalf Of David Payer
> Sent: Friday, April 14, 2000 6:27 AM
> To: ntisp@iea-software.com
> Subject: Re: [NTISP] CACHING DEVIC
>
>
>
> > Actually its relatively simple to tell a cisco to transparently redirect
> > traffic to a proxy server.
> > It is done by defining an ip policy and an access list.
> >
> > i.e
> > Assuming that you want to redirect all your lan traffic to a
> proxy server
> > you would do the following
>
>
> That is the point. You don't want all traffic to go through a proxy, only
> the http traffic or other defined protocols.
>

With a Cisco I can redirect traffic based on port. so I can create a
route-map with a filter to allow only port 80 traffic to be re-directed to
the cache. It is a lot easier to use WCCP if you are redirecting port 80
though.

Brian

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart