On Mon, 15 Jun 2009 12:59:43 +0545 type "enable-acl-counter" first
match only packet btw. make fun Mitko Samit <[email protected]> wrote: > Yes, it is using client IP but only just cannot see the packets match in > the counter.....in another casee...I also don't see any packet match > counter in "show access-list xxx" like in cisco. > > I don't know why..! > > Regards, > Samit > > Oliver Adam wrote: > > Are you sure the cache server is going to use the client IP as source > > address for its packets? The spoofing counters look for packets coming > > from the cache servers MAC address using a non-cache IP address. The > > counter are not going to increase in case there is no such traffic. > > > > R, Oliver > > > > At 15:44 07.06.2009, Samit wrote: > >> >> Cache Server Name Admin-status Hash-distribution > >> >> bluecoat 6 0 > >> >> > >> >> HTTP Traffic From <-> to Web-Caches > >> >> > >> >> Name: bluecoat IP: 192.168.40.142 State: 6 Groups = 1 3 > >> >> > >> >> Host->Web-cache > >> >> Web-cache->Host > >> >> State CurCon TotCon Packets Octets Packets > >> >> Octets > >> >> Spoof pkt Spoof oct Spoof pkt > >> >> Spoof oct > >> >> Web-Server active 0 0 4515919 2068851043 0 0 > >> >> > >> >> 0 0 0 0 > >> >> > >> >> Client active 5903 187341446 252270927 3288932869 > >> >> 16098549142944827043 > >> >> Total 5903 187341446 256786846 1062816616 > >> >> 16098549142944827043 > > > > > > > > > > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > -- <[email protected]> _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
