[squid-users] Cannot configure WCCP with Squid

From: Pranav A. Desai <pdesai1@dont-contact.us>
Date: Thu, 21 Feb 2002 14:27:40 -0600 (CST)

Hi all!
        i am not able to configure WCCP with Squid .... I have read a lot
of posting on WCCP ... is this a problem with squid or am I doing
something wrong ... any help is appreciated ...

I have-
- Cisco 2621 ... IOS 12.0(2)
-Squid 2.3 S4

The setup is -
                ________________
                |192.168.1.X | SWITCH
                 -----------------
                | | |
                PC SQUID CISCO
                (.101) (.12) (.100)

-The default gateway of the PC is CISCO.
-I tried to connect to google.com at port 80
-the squid and the router are able to communicate
-the PC is able to access everything but port 80 ...
- the SQUID is configured as in the doc.
- the SQUID receives gre packets but doesnt seem to be doing anything ...
even the access and cache log doesnt show anything abnormal ...

do i need to do anything else ...

thanks

-pranav

---------------------------------------------------------------------------
The tcpdump of the SQUID is -

13:51:14.277529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58849, len 80)
13:51:14.277529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 744, len 92)
13:51:18.917529 192.168.1.100 > 192.168.1.12: gre 192.168.1.100 >
192.168.1.12: [] gre-proto-0x883E (ttl 255, id 94, len 84)
13:51:21.917529 192.168.1.100 > 192.168.1.12: gre 192.168.1.100 >
192.168.1.12: [] gre-proto-0x883E (ttl 255, id 95, len 84)
13:51:25.297529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58850, len 80)
13:51:25.297529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 745, len 92)
13:51:27.917529 192.168.1.100 > 192.168.1.12: gre 192.168.1.100 >
192.168.1.12: [] gre-proto-0x883E (ttl 255, id 96, len 84)
13:51:35.317529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58851, len 80)
13:51:35.317529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 746, len 92)
13:51:39.917529 192.168.1.100 > 192.168.1.12: gre 192.168.1.100 >
192.168.1.12: [] gre-proto-0x883E (ttl 255, id 97, len 84)
13:51:45.367529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58852, len 80)
13:51:45.367529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 747, len 92)
13:51:55.427529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58853, len 80)
13:51:55.427529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 748, len 92)
13:52:03.917529 192.168.1.100 > 192.168.1.12: gre 192.168.1.100 >
192.168.1.12: [] gre-proto-0x883E (ttl 255, id 98, len 84)
13:52:05.467529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58854, len 80)
13:52:05.467529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 749, len 92)
13:52:10.467529 arp who-has 192.168.1.100 tell 192.168.1.12
13:52:10.467529 arp reply 192.168.1.100 is-at 0:4:c1:36:5:40
13:52:16.247529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58855, len 80)
13:52:16.247529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 750, len 92)
13:52:26.447529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58856, len 80)
13:52:26.447529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 751, len 92)
13:52:37.377529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58857, len 80)
13:52:37.377529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 752, len 92)
13:52:47.577529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58858, len 80)
13:52:47.577529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 753, len 92)
13:52:51.917529 192.168.1.100 > 192.168.1.12: gre 192.168.1.100 >
192.168.1.12: [] gre-proto-0x883E (ttl 255, id 99, len 84)
13:52:58.497529 192.168.1.12.2048 > 192.168.1.100.2048: [udp sum ok] udp
52 (DF) (ttl 64, id 58859, len 80)
13:52:58.497529 192.168.1.100.2048 > 192.168.1.12.2048: udp 64 (ttl 255,
id 754, len 92)
---------------------------------------------------------------------------

---------------------------------------------------------------------------
the show ip wccp web-caches output of CISCO is -

2621#show ip wccp web-caches
WCCP Web-Cache information:
        IP Address: 192.168.1.12
        Protocol Version: 0.4
        State: Usable
        Initial Hash Info: 00000000000000000000000000000000
                               00000000000000000000000000000000
        Assigned Hash Info: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
                               FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
        Hash Allotment: 256 (100.00%)
        Packets Redirected: 6
        Connect Time: 01:52:29
---------------------------------------------------------------------------

---------------------------------------------------------------------------
the tcpdump of the PC is -

14:00:05.715864 testmachine.cs.uh.edu.33264 > www.google.com.http: S
3034878802:3034878802(0) win 5840 <mss 1460,sackOK,timestamp
66800268[|tcp]> (DF)
14:00:08.715864 testmachine.cs.uh.edu.33264 > www.google.com.http: S
3034878802:3034878802(0) win 5840 <mss 1460,sackOK,timestamp
66800568[|tcp]> (DF)
14:00:14.715864 testmachine.cs.uh.edu.33264 > www.google.com.http: S
3034878802:3034878802(0) win 5840 <mss 1460,sackOK,timestamp
66801168[|tcp]> (DF)
14:00:26.715864 testmachine.cs.uh.edu.33264 > www.google.com.http: S
3034878802:3034878802(0) win 5840 <mss 1460,sackOK,timestamp
66802368[|tcp]> (DF)
14:00:50.715864 testmachine.cs.uh.edu.33264 > www.google.com.http: S
3034878802:3034878802(0) win 5840 <mss 1460,sackOK,timestamp
66804768[|tcp]> (DF)
14:01:38.715864 testmachine.cs.uh.edu.33264 > www.google.com.http: S
3034878802:3034878802(0) win 5840 <mss 1460,sackOK,timestamp
66809568[|tcp]> (DF)
---------------------------------------------------------------------------

*******************************************************************
Pranav A. Desai
4309 Pease Street, Apt #6
Houston, TX - 77023
U.S.A.

Home :- (713) 926-1045
*******************************************************************

On Thu, 21 Feb 2002, Adrian Chadd wrote:

> On Wed, Feb 20, 2002, khiz code wrote:
> > Hi all
> > is there a problem with 2.4 Stable 3's implemetation of wccp
> > the squid box is directly connected to a 7513 cisco via a switch
> > after a few hours squid , though detected by the router , no hash buckets are
> > assigned to it ,and hence no packets are passed to squid
> > this is kinda strange ..
> > tcpdump shows everything as normal
> >
> > is this a problem with 2.4S3 specifically ,, i can't recollect having this
> > problem with 2.4S2 or maybe i never noticed ;-)
>
> This bug has existed for a while. I can't reproduce it on my home
> network (but then its just a little 2501 with one ethernet interface,
> so its kind of hard to test with.)
>
>
>
>
> Adrian
>
>
Received on Thu Feb 21 2002 - 13:29:30 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:06:30 MST