RE: WCCP and SQUID does not appear to be working (and for some reason mypost doesnt seem to reach the list)

Bennet, on the other site of the Ethernet0 are all our dialup customers...
which I want to use the cache.. when .If I do the ip wccp module I get the
following errors (output from tcpdump) which disapear when I use gre
module... any ideas?

which still doesnt tell my why I dont get loggin from the machine to say
that I have visited the sites

Damien

iptraf output

 UDP from 203.44.53.119:3130 to 165.228.130.10:3130 on eth0
 UDP from 165.228.130.10:3130 to 203.44.53.119:3130 on eth0
 ICMP dest unreach (protocol) from 203.44.53.119 to 203.43.67.194 on eth0
 UDP from 203.44.53.119:3130 to 165.228.130.10:3130 on eth0
 UDP from 165.228.130.10:3130 to 203.44.53.119:3130 on eth0
 ICMP dest unreach (protocol) from 203.44.53.119 to 203.43.67.194 on eth0

ssc-ts#term mon (with debug ip icmp)
ssc-ts#
*Mar 5 08:17:41.538: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:42.406: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:43.454: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:44.410: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:45.450: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:46.498: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:47.522: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:48.402: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:49.534: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119
*Mar 5 08:17:50.414: ICMP: dst (203.43.67.194) protocol unreachable rcv
from 203.44.53.119

so obviously its not really working

any ideas?

Damien

-----Original Message-----
From: bennet [mailto:bennet]On Behalf Of Bennet Ng
Sent: Tuesday, 2 May 2000 10:57 AM
To: djcroark@ssc.net.au
Subject: Re: WCCP and SQUID does not appear to be working (and for some
reason mypost doesnt seem to reach the list)

Hi Damien,

  You do not need step 10, i.e. setting gre interface, if you have
modprobed ip_wccp._wccp.o
Also, is your interface Ethernet0 connected to the Internet (or some
sites where you want to cache)?

regards
bennet

Damien Croarken wrote:
>
> Can someone tell me why my squid (Version 2.3.STABLE2) and linux 2.2.14
> (with ip_gre module) dont seem to be working (sorry about the long
email...
> but its easier if I get all the info together at once...)
>
> This is what I have done...
>
> 1. Installed Squid
> 2. Patched the 2.2.14 Kernel (ip_gre.patch)
> 3. recompiled the kernel with IP_GRE built in
> 4. Set up transparent proxy chains
> ipchains -L
> Chain input (policy ACCEPT):
> target prot opt source destination
> ports
> REDIRECT tcp ------ 203.43.67.128/25 anywhere
any ->
> http => 3128
> REDIRECT tcp ------ 203.44.53.0/25 anywhere
any ->
> http => 3128
> REDIRECT tcp ------ 203.43.127.192/26 anywhere
any ->
> http => 3128
> ACCEPT all ------ anywhere anywhere
n/a
> ACCEPT tcp ------ anywhere bluegum.ssc.net.au
any ->
> 3128
> Chain forward (policy ACCEPT):
> Chain output (policy ACCEPT):
> 5. tested the ip chains with a machine having the squid server as its
> defualt gateway. OK
> 6. set up router (IOS (tm) 5200 Software (C5200-I-L), Version 11.2(14)P)
> ip wccp enable
> interface Ethernet0
> ip web-cache redirect
> 7. did a show ip wccp
> Global WCCP information:
> Number of web-caches: 1
> Total Packets Redirected: 1
> Redirect access-list: -none-
> Total Packets Denied Redirect: 0
> Total Packets Unassigned: 0
> 8. did a show ip wccp web-caches
> WCCP Web-Cache information:
> IP Address: 203.44.53.119
> Protocol Version: 0.4
> State: Usable
> Initial Hash Info: 00000000000000000000000000000000
> 00000000000000000000000000000000
> Assigned Hash Info: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
> FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
> Hash Allotment: 256 (100.00%)
> Packets Redirected: 1
> Connect Time: 1d01h
> 9. So all seems fine here I think
>
> 10. did the ip gre tunnel
> ip tunnel add gre1 mode gre remote 203.43.67.194 local
203.44.53.119 dev
> eth0
> ifconfig gre1 up
>
> ifconfig output
> gre1 Link encap:UNSPEC HWaddr
> CB-2C-35-77-00-00-00-00-00-00-00-00-00-00-00-00
> UP POINTOPOINT RUNNING NOARP MTU:1476 Metric:1
> RX packets:289219 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
> 11. tcpdump -f net 203.43.67.194
> 19:37:01.484925 bluegum.ssc.net.au.dls-monitor >
> ssc-ts.ssc.net.au.dls-monitor: udp 52
> 19:37:01.490405 ssc-ts.ssc.net.au.dls-monitor >
> bluegum.ssc.net.au.dls-monitor: udp 64
> 19:37:01.593280 gre-proto-0x883E (gre encap)
> 19:37:02.436650 gre-proto-0x883E (gre encap)
> 19:37:04.248255 gre-proto-0x883E (gre encap)
> 19:37:06.562313 gre-proto-0x883E (gre encap)
> 19:37:07.457133 gre-proto-0x883E (gre encap)
> 19:37:09.102398 gre-proto-0x883E (gre encap)
> 19:37:09.513423 gre-proto-0x883E (gre encap)
> 19:37:09.764110 gre-proto-0x883E (gre encap)
> 19:37:11.619907 gre-proto-0x883E (gre encap)
> 19:37:11.906829 gre-proto-0x883E (gre encap)
> 19:37:12.132244 gre-proto-0x883E (gre encap)
>
> So it seems as if it should work.... but when I look at the logs I dont
see
> my ip address in the cache log to say I have gone anywhere any ideas????
>
> Damien Croarken (confused)
Received on Tue May 02 2000 - 05:41:05 MDT