Hi Andreas,
"ip wccp redirect exclude out" only makes sense if you have a "ip wccp redirect out"
on a L3 interface on the router.
It's purpose is to avoid redirecting an already optimised packet, comming from a L3-interface where the WAAS/Riverbed device is connected, once more.
A double redirect will, in a WAAS setup, cause the WAAS device to drop the packet, because
it suspects a routing loop... don't know what Riverbed does.
Running only with "ip wccp redirect in" on both the WAN and LAN interface will cause :
1) a packet comming in from the LAN, is supposed to be unoptimised, and will be redirected
2) a packet comming in from the WAN, is supposed to be optimised, and will also redirected
3) an IP-interface with only the WAAS/Riverbed connected should NEVER be redirected !
If you cannot isolate your WAAr/Riverbed in it's own L3 subnet (subinterface/VLAN),
and therefore have to place it in the "ordinary" LAN subnet, packets from the WAAS/Riverbed will becomes candidates for redirection (even with "ip wccp redirect in"), you'll need to use "WCCP negotiated Return", but don't know whether Riverbed supports this,
Riverbed normally uses "tunnels" on the WAN side, and this makes the WCCP setup somewhat different.
You should really consult the Riverbed documentation or their support
... or migrate to Cisco WAAS ;-)
Best regards
Finn Poulsen