> But not in the intended way....:-(
>
> We should watch somewhat like :
>
> SNMPv2-SMI::enterprises.3495.1.4.1.1.1.64.233.183.99 = Gauge32: 7
> SNMPv2-SMI::enterprises.3495.1.4.1.2.1.64.233.183.99 = Counter32: 11
> SNMPv2-SMI::enterprises.3495.1.4.1.3.1.64.233.183.99 = Counter32: 0
>
Well, 4 index was not the intended subtree. Rather index 5.
Last changeds : see what happens with next peer configuration !
cache_peer www.google.es parent 80 0 no-query name=google
acl googleSite dstdomain google.es
cache_peer_access google deny !googleSite
never_direct allow googleSite
See the results are now :
¡ The tree spawns cache peer's nodes in rigth way ... !
I need to more intensive tests with IPv6 cache_peers ! Amos ?
Next goal: the client table: client_db.cc is not ready for IPv6 .
This archive was generated by hypermail pre-2.1.9 : Sat Dec 01 2007 - 12:00:05 MST