Re: [squid-users] Wccp and squid problem

Sukhjit,

I'm running WCCP since last 1 year and did not get any problem. please check
your i see you packets and also check is wccp module loaded via commaned

lsmod|grep wccp

-- 
Best Regs,
Masood Ahmad Shah
System Administrator
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
|   * * * * * * * * * * * * * * * * * * * * * * * *
|   Fibre Net (Pvt) Ltd. Lahore, Pakistan
|   Tel: +92-42-6677024
|   Mobile: +92-300-4277367
|   http://www.fibre.net.pk
|   * * * * * * * * * * * * * * * * * * * * * * * *
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
----- Original Message ----- 
From: "Sukhjit Singh" <sukhjits@emmtel.com>
To: <squid-users@squid-cache.org>
Cc: <squid-users@squid-cache.org>
Sent: Thursday, July 31, 2003 8:27 AM
Subject: [squid-users] Wccp and squid problem
| Hi all squid users,
|
| i am running sorry i was running squid +wccp v 2 for one moth and suddenly
| there was a problem and my squid stoped responding, it was figured out
that
| the squid was working fine ( by using it as a proxy i check it) and only
| problem was with the wccp module or wccp problem on the cisco router.Has
| anybody faced the same situation, kindly tellme.
|
| Presently i am running squid and redirecting the traffic from router with
| the help of PBR (Policy Based routing).it is working fine but has his own
| drawbacks.
|
| So it is a kind request to all the developers who are researching on squid
| to take care of this part of the squid to ( means connectivity with the
| router), or we can just stop using wccp.
|
|
|    Regards
|
|    Sukhjit Singh
|    Network Administrator
|    Emmsons Infotech Ltd.
|    SCO 13-14-15, Sec 34A,
|    Chandigarh-160 022
|    (Ph): +91 172 606664
|    sukhjits@emmtel.com
|    http://www.emmtel.com
|
| ----- Original Message -----
| From: <ahuxtable@sola.com.au>
| To: <squid-users@squid-cache.org>
| Sent: Thursday, July 31, 2003 8:31 AM
| Subject: [squid-users] Cache peer and never_direct
|
|
| > Hi,
| > After a little help.  I have a setup here where I want to force all
| > users to use a cache
| > peer *except a few*.
| >
| > I am also using NTLM auth and NT Global group checking
| >
| > It seems to be partially working where the 'direct' users always go
direct
| > but the 'peered' users
| > are only partialy using the peer (some requests are going direct).
| >
| > Squid.conf snippet:
| >
|
#***************************************************************************
| > ********************
| > external_acl_type NT_global_group %LOGIN
/usr/local/squid/libexec/wb_group
| >
| > acl DirectProxyUsers external NT_global_group <Group1>
| > acl PeerProxyUsers external NT_global_group <Group2>
| > acl password proxy_auth REQUIRED
| >
| > never_direct allow all
| >
| > always_direct allow DirectProxyUsers
| >
| > Http_access allow password PeerProxyUsers
| > Http_access allow password DirectProxyUsers
| >
| >
|
#***************************************************************************
| > ********************
| >
| > I have confirmed that the external ACL is working ok. If I remove the
| > always_direct line then
| > all requests go to the peer as expected. If I change the
| 'DirectProxyUsers'
| > ACL to a  standard 'SRC'
| > or something then it also works as expected (just DirectProxyUsers go
| > direct). Is there an issue with
| > using an external helper with an always_direct or something?
| >
| > As it is, it seems that about 2 in 5 of requests from the users that
match
| > the 'PeerProxyUsers' ACL still
| > Go direct. Why?
| >
| > Thanks in Advance,
| > Andrew
| >
|
|