On sön, 2007-11-25 at 18:48 +0100, Rafael Martinez Torres wrote:
> Yes , I knew. For the time beeing, I'm only trying to reach the point on Squid
> 3 for the same funcionality on Squid 2, even with the wrong IP indexing
> schema
Squid-2 has both kinds of indexes for peers, and the IP based is planned
to go away at some point in time, or at least not included in a
snmpwalk.. (named OLDcachePeerEntry for the time beeing).
As index the position in squid.conf is used. Simple, but is a slight
problem if one removes peers in the middle..
I see no good reason why the same index mistake should be repeated for
IPv6.
OLDcachePeerEntry OBJECT-TYPE
SYNTAX CachePeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" An entry in cachePeerTable "
INDEX { cachePeerAddr }
::= { cachePeerTable 1 }
cachePeerEntry OBJECT-TYPE
SYNTAX CachePeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" An entry in cachePeerTable "
INDEX { cachePeerIndex }
::= { cachePeerTable 2 }
Hmm.. should update the description.. should say what the index is..
done..
" cache_peer indexed by IP address "
" cache_peer indexed by position in squid.conf "
Regards
Henrik
This archive was generated by hypermail pre-2.1.9 : Sat Dec 01 2007 - 12:00:05 MST