Re: SNMP support starts on branch squid3-ipv6 !! [improved]
As I said earlier the method of indexing the peers based on their IP is broken, not only because we do not sort the peers on their IP but also because there may be multiple peers on the same IP or same IP:PORT even.. 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 Regards Henrik Yeah, I though Rafael was fixing that after our earlier discussions about keys to use. I guess not (yet) though. Then we willl open the discussion on how to index the new table with several peers on the same node...(taking a look on how an iftable does...) Just walking on a solid implementation. The order still appears to be broken even if there was another level to the key. The IPA being out of order regardless of how they are configured. My reading of the code indicates its a linked-list of peers, right? If so they can/should be sorted into position using or operators on IPAddress to get around this simple case to a large degree. It will still be needed anyway if the key gets expanded later. We will see. Good to know about that -cC trick. Amos
Re: SNMP support starts on branch squid3-ipv6 !! [improved]
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
signature.asc
Description: This is a digitally signed message part
Re: SNMP support starts on branch squid3-ipv6 !! [improved]
Rafael Martinez (Squid development) wrote: 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 ? Hmm, the current CVS seems to have a few problems. One I think is sorting related with the actual stored data: ./squid.conf: cache_peer ipv4.cairo.treenetnz.com parent 3128 0 background-ping proxy-only default name=cairo4 cache_peer rio.treenetnz.com parent 80 0 background-ping proxy-only default name=rio (cairo 192.168.0.14, rio 192.168.0.12) ./test.snmp ... SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.14 = STRING: ipv4.cairo.treenetnz.com SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.12 = STRING: rio.treenetnz.com Error: OID not increasing: SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.14 = SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.12 The other IPv6-Address related: ./squid.conf: cache_peer ipv4.cairo.treenetnz.com parent 3128 0 background-ping proxy-only default name=cairo4 cache_peer ipv6.cairo.treenetnz.com parent 3128 0 background-ping proxy-only default name=cairo6 ./test.snmp ... cacheSystem number five 5 SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.14 = STRING: ipv4.cairo.treenetnz.com SNMPv2-SMI::enterprises.3495.1.5.1.1.1.0.0.0.0 = STRING: ipv6.cairo.treenetnz.com Error: OID not increasing: SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.14 = SNMPv2-SMI::enterprises.3495.1.5.1.1.1.0.0.0.0 If you don't have a multi-machine test setup I'll give you login here. I have been testing on a build server and peering a central server. Amos
Re: SNMP support starts on branch squid3-ipv6 !! [improved]
On fre, 2007-11-23 at 23:55 +1300, Amos Jeffries wrote: SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.12 = STRING: rio.treenetnz.com Error: OID not increasing: This is inherent to our broken way of indexing the peers. Not unique to ipv6 but also seen for ipv4 peers even before the ipv6 modifications, and also in Squid-2 since the day it got SNMP support.. As I said earlier the method of indexing the peers based on their IP is broken, not only because we do not sort the peers on their IP but also because there may be multiple peers on the same IP or same IP:PORT even.. Regards Henrik signature.asc Description: This is a digitally signed message part
Re: SNMP support starts on branch squid3-ipv6 !! [improved]
Henrik Nordstrom wrote: On fre, 2007-11-23 at 23:55 +1300, Amos Jeffries wrote: SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.12 = STRING: rio.treenetnz.com Error: OID not increasing: This is inherent to our broken way of indexing the peers. Not unique to ipv6 but also seen for ipv4 peers even before the ipv6 modifications, and also in Squid-2 since the day it got SNMP support.. As I said earlier the method of indexing the peers based on their IP is broken, not only because we do not sort the peers on their IP but also because there may be multiple peers on the same IP or same IP:PORT even.. Regards Henrik Yeah, I though Rafael was fixing that after our earlier discussions about keys to use. I guess not (yet) though. The order still appears to be broken even if there was another level to the key. The IPA being out of order regardless of how they are configured. My reading of the code indicates its a linked-list of peers, right? If so they can/should be sorted into position using or operators on IPAddress to get around this simple case to a large degree. It will still be needed anyway if the key gets expanded later. Good to know about that -cC trick. Amos
Re: SNMP support starts on branch squid3-ipv6 !! [improved]
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 . SNMPv2-SMI::enterprises.3495.1.1.1.0 = INTEGER: 4194301 SNMPv2-SMI::enterprises.3495.1.1.2.0 = INTEGER: 6444 SNMPv2-SMI::enterprises.3495.1.1.3.0 = Timeticks: (8244) 0:01:22.44 SNMPv2-SMI::enterprises.3495.1.2.1.0 = STRING: webmaster SNMPv2-SMI::enterprises.3495.1.2.2.0 = STRING: squid SNMPv2-SMI::enterprises.3495.1.2.3.0 = STRING: 3.0.PRE7-IPv6-CVS SNMPv2-SMI::enterprises.3495.1.2.4.0 = STRING: 49,9 SNMPv2-SMI::enterprises.3495.1.2.5.1.0 = INTEGER: 8 SNMPv2-SMI::enterprises.3495.1.2.5.2.0 = INTEGER: 100 SNMPv2-SMI::enterprises.3495.1.2.5.3.0 = INTEGER: 95 SNMPv2-SMI::enterprises.3495.1.2.5.4.0 = INTEGER: 90 SNMPv2-SMI::enterprises.3495.1.2.6.0 = SNMPv2-SMI::enterprises.3495.1.3.1.1.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.1.2.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.1.3.0 = INTEGER: 2508 SNMPv2-SMI::enterprises.3495.1.3.1.4.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.1.5.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.1.6.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.1.7.0 = Gauge32: 804 SNMPv2-SMI::enterprises.3495.1.3.1.8.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::enterprises.3495.1.3.1.9.0 = Gauge32: 0 SNMPv2-SMI::enterprises.3495.1.3.1.10.0 = Gauge32: 1014 SNMPv2-SMI::enterprises.3495.1.3.1.11.0 = Gauge32: 100 SNMPv2-SMI::enterprises.3495.1.3.1.12.0 = Gauge32: 10 SNMPv2-SMI::enterprises.3495.1.3.1.13.0 = Gauge32: 16 SNMPv2-SMI::enterprises.3495.1.3.2.1.1.0 = Counter32: 1 SNMPv2-SMI::enterprises.3495.1.3.2.1.2.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.3.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.4.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.5.0 = Counter32: 2 SNMPv2-SMI::enterprises.3495.1.3.2.1.6.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.7.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.8.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.9.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.10.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.11.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.12.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.13.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.14.0 = Gauge32: 6444 SNMPv2-SMI::enterprises.3495.1.3.2.1.15.0 = Gauge32: 1 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.1.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.1.5 = INTEGER: 5 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.1.60 = INTEGER: 60 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.2.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.2.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.2.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.3.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.3.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.3.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.4.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.4.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.4.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.5.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.5.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.5.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.6.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.6.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.6.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.7.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.7.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.7.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.8.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.8.5 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.8.60 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.9.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.9.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.9.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.10.1 = INTEGER: 100 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.10.5 = INTEGER: 100 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.10.60 = INTEGER: 100 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.11.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.11.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.11.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.4.1.1.0 = Gauge32: 7 SNMPv2-SMI::enterprises.3495.1.4.1.2.0 = Counter32: 10
Re: SNMP support starts on branch squid3-ipv6 !!
Sounds like a data access problem. This is a killer bug (pun intended). I'm not seeing any crash here. To my untrained eye it looks like its working. :-) 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 Instead: SNMPv2-SMI::enterprises.3495.1.4.1.1.0 = Gauge32: 7 SNMPv2-SMI::enterprises.3495.1.4.1.2.0 = Counter32: 11 SNMPv2-SMI::enterprises.3495.1.4.1.3.0 = Counter32: 0 The reason , in var/logs/cache.log (debug_otions 49,9) 2007/11/21 09:34:50.214| snmpTreeNext: Recursed down to requested object 2007/11/21 09:34:50.214| snmpTreeNext: Attempting to recurse up for next object 2007/11/21 09:34:50.214| addr2oid: Dest : 2007/11/21 09:34:50.214|oid = .1.64.233.183.99 2007/11/21 09:34:50.214| snmp_meshPtblFn: peer 1 requested! 2007/11/21 09:34:50.214| oid2addr: id : 2007/11/21 09:34:50.214|oid = .1.0.8.139384744.1 2007/11/21 09:34:50.214| snmpAgentResponse: error. I will investigate... The error is around in oid2addr, or its callers. I'm very close...
SNMP support starts on branch squid3-ipv6 !!
Hi, on the branch squid3-ipv6, support for SNMP is available (we need a lot of tests ...) 1.- Take in mind that, for tests, allow for SNMP access is open. allow = 1 ; All the MIB tree is exported ! 2.- To test, follow the next cook-guid (of course, choose your own user and/or installation path): bash$ ./configure --enable-ipv6 --disable-icmp* --enable-snmp --prefix= $HOME bash$ make install *if you get linking errors having to do with icmp on main.cc, comment them...(Amos?) 3.- Apply the next test script*, after editing ipv4address and ipv6address. bash$ . test.snmpd * this script works on a Debian box, having installed package snmp version 5.2.3 . If you don't have packet access, download and compile from net-snmp http://net-snmp.sourceforge.net/download.html accessing 192.168.0.10 via udp cacheSystem number one 1 SNMPv2-SMI::enterprises.3495.1.1.1.0 = INTEGER: 4194301 SNMPv2-SMI::enterprises.3495.1.1.2.0 = INTEGER: 5224 SNMPv2-SMI::enterprises.3495.1.1.3.0 = Timeticks: (461852) 1:16:58.52 cacheSystem number two 2 SNMPv2-SMI::enterprises.3495.1.2.1.0 = STRING: webmaster SNMPv2-SMI::enterprises.3495.1.2.2.0 = STRING: squid SNMPv2-SMI::enterprises.3495.1.2.3.0 = STRING: 3.0.PRE7-IPv6-CVS SNMPv2-SMI::enterprises.3495.1.2.4.0 = STRING: 49,9 SNMPv2-SMI::enterprises.3495.1.2.5.1.0 = INTEGER: 8 SNMPv2-SMI::enterprises.3495.1.2.5.2.0 = INTEGER: 100 SNMPv2-SMI::enterprises.3495.1.2.5.3.0 = INTEGER: 95 SNMPv2-SMI::enterprises.3495.1.2.5.4.0 = INTEGER: 90 SNMPv2-SMI::enterprises.3495.1.2.6.0 = cacheSystem number three 3 SNMPv2-SMI::enterprises.3495.1.3.1.1.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.1.2.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.1.3.0 = INTEGER: 2221 SNMPv2-SMI::enterprises.3495.1.3.1.4.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.1.5.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.1.6.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.1.7.0 = Gauge32: 677 SNMPv2-SMI::enterprises.3495.1.3.1.8.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::enterprises.3495.1.3.1.9.0 = Gauge32: 0 SNMPv2-SMI::enterprises.3495.1.3.1.10.0 = Gauge32: 1014 SNMPv2-SMI::enterprises.3495.1.3.1.11.0 = Gauge32: 100 SNMPv2-SMI::enterprises.3495.1.3.1.12.0 = Gauge32: 10 SNMPv2-SMI::enterprises.3495.1.3.1.13.0 = Gauge32: 16 SNMPv2-SMI::enterprises.3495.1.3.2.1.1.0 = Counter32: 1 SNMPv2-SMI::enterprises.3495.1.3.2.1.2.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.3.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.4.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.5.0 = Counter32: 2 SNMPv2-SMI::enterprises.3495.1.3.2.1.6.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.7.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.8.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.9.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.10.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.11.0 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.12.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.13.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.3.2.1.14.0 = Gauge32: 5224 SNMPv2-SMI::enterprises.3495.1.3.2.1.15.0 = Gauge32: 1 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.1.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.1.5 = INTEGER: 5 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.1.60 = INTEGER: 60 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.2.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.2.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.2.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.3.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.3.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.3.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.4.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.4.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.4.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.5.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.5.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.5.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.6.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.6.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.6.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.7.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.7.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.7.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.8.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.8.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.8.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.9.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.9.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.9.60 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.11.1 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.11.5 = INTEGER: 0 SNMPv2-SMI::enterprises.3495.1.3.2.2.1.11.60 = INTEGER: 0 End of MIB cacheSystem number four 4 SNMPv2-SMI::enterprises.3495.1.4.1.1.0 = Gauge32: 4 SNMPv2-SMI::enterprises.3495.1.4.1.2.0 = Counter32: 0 SNMPv2-SMI::enterprises.3495.1.4.1.3.0 = Counter32: 0
Re: SNMP support starts on branch squid3-ipv6 !!
Hi, on the branch squid3-ipv6, support for SNMP is available (we need a lot of tests ...) 1.- Take in mind that, for tests, allow for SNMP access is open. allow = 1 ; All the MIB tree is exported ! 2.- To test, follow the next cook-guid (of course, choose your own user and/or installation path): bash$ ./configure --enable-ipv6 --disable-icmp* --enable-snmp --prefix= $HOME bash$ make install *if you get linking errors having to do with icmp on main.cc, comment them...(Amos?) Should compile OK with or without ICMP. Any problems, yes let me know. The bugs there are still in the packet-level formatting which can cause desired ICMP helpers to close early. 3.- Apply the next test script*, after editing ipv4address and ipv6address. bash$ . test.snmpd * this script works on a Debian box, having installed package snmp version 5.2.3 . If you don't have packet access, download and compile from net-snmp http://net-snmp.sourceforge.net/download.html Amos
Re: SNMP support starts on branch squid3-ipv6 !!
2.- To test, follow the next cook-guid (of course, choose your own user and/or installation path): 1.- By the way, I forgot some necessary changes on squid.conf acl snmppublic snmp_community public snmp_port 3401 snmp_access allow snmppublic all debug_options 49,9 Some traces on cache.txt 2.- Squid seems to die if at least the Squid server has not attended a first cache service... 3.- Tests on cache peer table are required... I don't know how to configure Squid for adding cache peers... 2007/11/19 21:13:10.441| snmpInit: Building SNMP mib tree structure 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.10 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.9 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.8 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.7 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.6 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.5 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.4 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.3 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.2 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1.1 2007/11/19 21:13:10.441| snmpAddNode: Children : 10, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2.1 2007/11/19 21:13:10.441| snmpAddNode: Children : 1, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.2 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.14 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.13 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.12 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.11 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.10 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.9 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.8 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.7 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.6 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.5 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.4 2007/11/19 21:13:10.441| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.441|oid = .1.3.6.1.4.1.3495.1.5.1.1.3 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.5.1.1.2 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.5.1.1.1 2007/11/19 21:13:10.442| snmpAddNode: Children : 14, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.5.1.1 2007/11/19 21:13:10.442| snmpAddNode: Children : 1, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.5.1 2007/11/19 21:13:10.442| snmpAddNode: Children : 2, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.5 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.4.3.3 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.4.3.2 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.4.3.1 2007/11/19 21:13:10.442| snmpAddNode: Children : 3, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.4.3 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.4.2.7 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.4.2.6 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid = .1.3.6.1.4.1.3495.1.4.2.5 2007/11/19 21:13:10.442| snmpAddNode: Children : 0, Oid : 2007/11/19 21:13:10.442|oid
Re: SNMP support starts on branch squid3-ipv6 !!
2.- To test, follow the next cook-guid (of course, choose your own user and/or installation path): 1.- By the way, I forgot some necessary changes on squid.conf acl snmppublic snmp_community public snmp_port 3401 snmp_access allow snmppublic all debug_options 49,9 Some traces on cache.txt 2.- Squid seems to die if at least the Squid server has not attended a first cache service... Sounds like a data access problem. This is a killer bug (pun intended). I'm not seeing any crash here. To my untrained eye it looks like its working. :-) 3.- Tests on cache peer table are required... I don't know how to configure Squid for adding cache peers... This test config redirects all google.com traffic through the peering mechanism. To test the results do google web search before the SNMP peer data request. cache_peer www.google.com 80 0 no-query name=google acl googleSite dstdomain google.com cache_peer_access google !googleSite never_direct googleSite Amos
