SNMP runs on port 161, so to avoid interfering with your system's SNMP daemon, squid's SNMP server runs on port 3401. You'll need to make sure you specify that port when you want to query squid and not your system. If you are running *nix you can actually use the proxy feature of SNMP and forward requests from your system daemon to your SNMP daemon. Here's what i have in my SNMPd config: proxy -v 1 -c communityname localhost:3401 1.3.6.1.4.1.3495.1 With this in my SNMPd config, i can query my system daemon for both system and squid values. Hope this helps. Thanks, Bryan On Wed, 2006-08-16 at 10:52 -0400, Birol AKBAY wrote: > Hi, > I have an installed version 2.6.STABLE1 with --enable-snmp. > > I have those lines on squid.conf > > snmp_port = 3401 > acl localhost src 127.0.0.1/255.255.255.255 > acl snmpok snmp_community public > snmp_access allow snmpok all > snmp_access deny all > > snmpwalk raises an error > Failed SNMP agent query from : 127.0.0.1. > > netstat result > # netstat -an | grep 3401 > udp 0 0 0.0.0.0:3401 0.0.0.0:* > > So I think squid is listening port 3401. > The question : Are there another config lines or another program like > snmpd to achieve a succesfull connection? > > I have succesfully connected to my FW and router to get data for MRTG. > > Do you have any suggestions? > > Thanks. > -- > Birol AKBAY > birolakbay@xxxxxxxxx > >
