Why? Since localhost couldn't be resolved correctly, snmpd was trying to
match localhost.com when it created its in-memory ACL. You really should
fix your localhost resolution. This is what my host file looks like on
one of my marcuscom machines:
127.0.0.1 localhost.marcuscom.com localhost
Joe
On Tue, 18 Sep 2001, Chojin wrote:
> # sec.name source community
> com2sec local 127.0.0.1 public
> com2sec localrw 127.0.0.1 private
>
> hehe now it works!
>
> problem came from localhost that was not correctly resolved (but why?)
> ----- Original Message -----
> From: "Joe Clarke" <[EMAIL PROTECTED]>
> To: "Chojin" <[EMAIL PROTECTED]>
> Cc: "Jean-Francois Dive" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Tuesday, September 18, 2001 12:40 AM
> Subject: Re: Problem with snmpd
>
>
> > Those look fine. What about nslookup localhost (or if you're using hosts
> > before bind, what does /etc/hosts look like)? It may be that localhost
> > resolves to something other than 127.0.0.1. Have you tried:
> >
> > snmpwalk 127.0.0.1 public system
> >
> > ? That should also work.
> >
> > Joe
> >
> > On Tue, 18 Sep 2001, Chojin wrote:
> >
> > > >I compiled /usr/ports/net/net-snmp
> > > me too
> > >
> > > #netstat -a
> > > Active Internet connections (including servers)
> > > Proto Recv-Q Send-Q Local Address Foreign Address
> (state)
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1618
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1616
> TIME_WAIT
> > > tcp4 0 0 chojin.adsl.neri.4110 208.141.100.35.socks
> TIME_WAIT
> > > tcp4 0 0 chojin.adsl.neri.4108 208.141.100.35.socks
> TIME_WAIT
> > > tcp4 0 0 chojin.adsl.neri.4107 208.141.100.35.socks
> TIME_WAIT
> > > tcp4 0 0 chojin.adsl.neri.4105 Hacker.gs.2532
> SYN_SENT
> > > tcp4 0 0 chojin.adsl.neri.4103 208.141.100.35.socks
> TIME_WAIT
> > > tcp4 0 0 chojin.adsl.neri.4100 Hacker.gs.2532
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.smtp rdu57-28-046.nc..1889
> TIME_WAIT
> > > tcp4 0 0 chojin.adsl.neri.4098 AFontenayssB-101.3340
> SYN_SENT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1615
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1613
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1612
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1610
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1609
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1607
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1606
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1604
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1603
> TIME_WAIT
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1601
> TIME_WAIT
> > > tcp4 0 0 chojin.adsl.neri.auth Hacker.gs.1628
> > > FIN_WAIT_2
> > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1597
> TIME_WAIT
> > > tcp4 0 0 chojin.adsl.neri.4084 Hacker.gs.2532
> > > FIN_WAIT_2
> > > tcp4 0 0 chojin.adsl.neri.3832 deneb.freedomshe.4386
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3682 deneb.freedomshe.4969
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.netbi chojin.lan.tarak.1299
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1742 ACBD133F.ipt.aol.1031
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1809 aboukir-101-1-4-.5557
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1493 paris.fr.eu.unde.6667
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1481 undernet.span.ch.6667
> > > ESTABLISHED
> > > tcp4 0 0 *.http *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.4950 arne.swip.net.6669
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.4730 no-security.net.8367
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.4540 irc.carrier1.net.6667
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.ssh chojin.lan.tarak.2099
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3145 ACBE8C24.ipt.aol.3419
> > > ESTABLISHED
> > > tcp4 0 55 tarakan.lan.tara.22006 chojin.lan.tarak.1980
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3070 entrechat.net.6667
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36867
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36875
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36870
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1657 skippy.solidshel.2843
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1390 entrechat.net.6668
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1380 powertech.no.eu..afs3-
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1379 uu194-7-27-98.un.8080
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.4267 chojin.adsl.neri.1373
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1373 chojin.adsl.neri.4267
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1742 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.3337 chojin.adsl.neri.1254
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1254 chojin.adsl.neri.3337
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3337 208.141.100.35.30790
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1208 208.141.100.35.socks
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1204 208.141.100.35.socks
> > > ESTABLISHED
> > > tcp4 0 0 *.3331 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.1198 skippy.solidshel.2843
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.dec-n *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2787
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2778
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3337 box1.TyranZ.3847
> > > ESTABLISHED
> > > tcp4 0 0 *.3337 *.* LISTE
> N
> > > tcp4 0 0 chojin.adsl.neri.1112 skippy.solidshel.2843
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.domai *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.1084 TyranZ.20801
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1080 ircnet.kaptech.6667
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1072
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.1072 tarakan.lan.tara.6667
> > > ESTABLISHED
> > > tcp4 0 0 *.2211 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.1065 AVelizy-101-2-2-.1982
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1063 irc1-2.free.fr.6667
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1062 hitomi.ecranbleu.dec-n
> > > ESTABLISHED
> > > tcp4 0 0 *.12345 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1534
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1524
> > > ESTABLISHED
> > > tcp4 0 0 *.22011 *.*
> LISTEN
> > > tcp4 0 48 tarakan.lan.tara.ssh chojin.lan.tarak.1164
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1048
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.1048 tarakan.lan.tara.6667
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1047 www.skydirect.ne.6667
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.4400 tarakan.lan.tara.1042
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.1042 tarakan.lan.tara.4400
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1041 bloob.oxyd.fr.4400
> > > ESTABLISHED
> > > tcp4 0 0 *.4400 *.*
> LISTEN
> > > tcp4 0 0 *.6669 *.*
> LISTEN
> > > tcp4 0 0 *.6668 *.*
> LISTEN
> > > tcp4 0 0 *.6667 *.*
> LISTEN
> > > tcp4 0 0 *.6665 *.*
> LISTEN
> > > tcp4 0 0 *.6666 *.*
> LISTEN
> > > tcp4 0 0 *.4401 *.*
> LISTEN
> > > tcp4 0 0 *.13333 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.1035 rinka.nerim.net.6667
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.3682 chojin.adsl.neri.1032
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1032 chojin.adsl.neri.3682
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.1031 irc.planetintern.6667
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.21003 chojin.lan.tarak.1163
> > > ESTABLISHED
> > > tcp4 0 0 tarakan.lan.tara.22002 chojin.lan.tarak.1162
> > > ESTABLISHED
> > > tcp4 0 0 chojin.adsl.neri.2532 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.4695 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.3418 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.4267 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.6632 *.*
> LISTEN
> > > tcp4 0 0 chojin.adsl.neri.3682 *.*
> LISTEN
> > > tcp4 0 0 *.netbios-ssn *.*
> LISTEN
> > > tcp46 0 0 *.22005 *.*
> LISTEN
> > > tcp4 0 0 *.22005 *.*
> LISTEN
> > > tcp46 0 0 *.22006 *.*
> LISTEN
> > > tcp46 0 0 *.22002 *.*
> LISTEN
> > > tcp4 0 0 *.22006 *.*
> LISTEN
> > > tcp46 0 0 *.21003 *.*
> LISTEN
> > > tcp4 0 0 *.21003 *.*
> LISTEN
> > > tcp4 0 0 *.22002 *.*
> LISTEN
> > > tcp4 0 0 tarakan.lan.tara.11982 *.*
> LISTEN
> > > tcp46 0 0 *.auth *.*
> LISTEN
> > > tcp4 0 0 *.submission *.*
> LISTEN
> > > tcp4 0 0 *.smtp *.*
> LISTEN
> > > tcp4 0 0 *.ssh *.*
> LISTEN
> > > tcp46 0 0 *.ssh *.*
> LISTEN
> > > tcp4 0 0 *.swat *.*
> LISTEN
> > > tcp4 0 0 *.auth *.*
> LISTEN
> > > tcp4 0 0 *.pop3 *.*
> LISTEN
> > > tcp6 0 0 *.ftp *.*
> LISTEN
> > > tcp4 0 0 *.ftp *.*
> LISTEN
> > > tcp4 0 0 *.sunrpc *.*
> LISTEN
> > > tcp4 0 0 localhost.domain *.*
> LISTEN
> > > tcp4 0 0 tarakan.lan.tara.domai *.*
> LISTEN
> > > tcp4 0 0 modem-adsl.domain *.*
> LISTEN
> > > udp4 0 0 *.4659 *.*
> > > udp4 0 0 *.snmp *.*
> > > udp4 0 0 localhost.3336 *.*
> > > udp4 0 0 *.3704 *.*
> > > udp4 0 0 *.2409 *.*
> > > udp4 0 0 chojin.adsl.neri.domai *.*
> > > udp4 0 0 *.1488 *.*
> > > udp4 0 0 *.* *.*
> > > udp4 0 0 *.1380 *.*
> > > udp4 0 0 *.afs3-bos *.*
> > > udp4 0 0 *.4183 *.*
> > > udp4 0 0 *.1291 *.*
> > > udp4 0 0 *.1244 *.*
> > > udp4 0 0 tarakan.lan.tara.netbi *.*
> > > udp4 0 0 tarakan.lan.tara.netbi *.*
> > > udp4 0 0 *.netbios-dgm *.*
> > > udp4 0 0 *.netbios-ns *.*
> > > udp4 0 0 *.10000 *.*
> > > udp4 0 0 chojin.adsl.neri.1124 chojin.adsl.neri.syslo
> > > udp4 0 0 *.bootps *.*
> > > udp4 0 0 *.sunrpc *.*
> > > udp4 0 0 *.1028 *.*
> > > udp4 0 0 localhost.domain *.*
> > > udp4 0 0 tarakan.lan.tara.domai *.*
> > > udp4 0 0 modem-adsl.domain *.*
> > > udp4 0 0 *.syslog *.*
> > > udp6 0 0 *.syslog *.*
> > > ip 4 0 0 *.* *.*
> > > icm4 0 0 *.* *.*
> > > ip64 0 0 *.* *.*
> > > Netgraph sockets
> > > Type Recv-Q Send-Q Node Address #Hooks
> > > ctrl 0 0
> > > data 0 0
> > > Active UNIX domain sockets
> > > Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr
> > > d04c2d80 stream 0 0 d04f9580 0 0 0
> > > /var/pwcheck/pwcheck
> > > d04c2e40 stream 0 0 d04f7240 0 0 0
> > > /tmp/.s.PGSQL.5432
> > > d04c2f40 stream 0 0 d04bd800 0 0 0
> > > /var/run/ndc
> > > d04c2d00 dgram 0 0 0 d04c2fc0 0 d04c2c80
> > > d04c2c80 dgram 0 0 0 d04c2fc0 0 d04c2e00
> > > d04c2e00 dgram 0 0 0 d04c2fc0 0 d04c2dc0
> > > d04c2dc0 dgram 0 0 0 d04c2fc0 0 d04c2e80
> > > d04c2e80 dgram 0 0 0 d04c2fc0 0 d04c2ec0
> > > d04c2ec0 dgram 0 0 0 d04c2fc0 0 d04c2f00
> > > d04c2f00 dgram 0 0 0 d04c2fc0 0 d04c2f80
> > > d04c2f80 dgram 0 0 0 d04c2fc0 0 0
> > > d04c2fc0 dgram 0 0 d04be940 0 d04c2d00 0
> > > /var/run/log
> > >
> > > #ifconfig -a
> > > ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > > inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255
> > > inet6 fe80::24f:49ff:fe0a:b2dd%ed0 prefixlen 64 scopeid 0x1
> > > ether 00:4f:49:0a:b2:dd
> > > ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > > inet 192.168.69.1 netmask 0xffffff00 broadcast 192.168.69.255
> > > inet6 fe80::5054:5ff:fef9:761d%ed1 prefixlen 64 scopeid 0x2
> > > ether 52:54:05:f9:76:1d
> > > lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
> > > faith0: flags=8000<MULTICAST> mtu 1500
> > > stf0: flags=0<> mtu 1280
> > > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> > > inet6 ::1 prefixlen 128
> > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
> > > inet 127.0.0.1 netmask 0xff000000
> > > ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
> > > sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
> > > tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492
> > > inet6 fe80::24f:49ff:fe0a:b2dd%tun0 prefixlen 64 scopeid 0x9
> > > inet 62.4.22.98 --> 194.206.78.3 netmask 0xff000000
> > > Opened by PID 168
> > >
> > > Anything wrong?
> > >
> > > ----- Original Message -----
> > > From: "Joe Clarke" <[EMAIL PROTECTED]>
> > > To: "Chojin" <[EMAIL PROTECTED]>
> > > Cc: "Jean-Francois Dive" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>;
> > > <[EMAIL PROTECTED]>
> > > Sent: Tuesday, September 18, 2001 12:31 AM
> > > Subject: Re: Problem with snmpd
> > >
> > >
> > > > What does netstat -a and ifconfig -a show? Something is not right on
> your
> > > > machine. I compiled /usr/ports/net/net-snmp and it worked out of the
> box.
> > > > I'm using the default /usr/local/etc/rc.d/snmpd.sh script to start
> snmpd.
> > > >
> > > > Joe
> > > >
> > > > On Tue, 18 Sep 2001, Chojin wrote:
> > > >
> > > > > My default location is /usr/local/share/snmp/snmpd.conf
> > > > > I used your file (just modified for 192.168... lan).
> > > > > To be sure snmpd uses the good file I used -c
> > > > > #/usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf
> > > > > #ps aux | grep snmpd
> > > > > root 81374 7.2 0.4 3256 2624 p0 S 12:25AM 0:00.15
> > > > > /usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf
> > > > > #snmpwalk -v 1 localhost public system
> > > > > Timeout: No Response from localhost
> > > > >
> > > > > As you see, without success...
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Joe Clarke" <[EMAIL PROTECTED]>
> > > > > To: "Chojin" <[EMAIL PROTECTED]>
> > > > > Cc: "Jean-Francois Dive" <[EMAIL PROTECTED]>;
> > > <[EMAIL PROTECTED]>;
> > > > > <[EMAIL PROTECTED]>
> > > > > Sent: Tuesday, September 18, 2001 12:18 AM
> > > > > Subject: Re: Problem with snmpd
> > > > >
> > > > >
> > > > > > Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and
> > > > > > 4.4-STABLE as of an hour ago. Attached is my entire config file.
> I
> > > keep
> > > > > > it in /usr/local/lib/snmp (which is the default location).
> > > > > >
> > > > > > Joe
> > > > > >
> > > > > > On Mon, 17 Sep 2001, Chojin wrote:
> > > > > >
> > > > > > > I didn't resolved my problem.
> > > > > > > Even after upgraded to 4.4-stable (because there was maybe a bug
> in
> > > > > snmpd
> > > > > > > :-p).
> > > > > > >
> > > > > > > I don't know what I could do.
> > > > > > >
> > > > > > > ----- Original Message -----
> > > > > > > From: "Chojin" <[EMAIL PROTECTED]>
> > > > > > > To: "Joe Clarke" <[EMAIL PROTECTED]>
> > > > > > > Cc: "Jean-Francois Dive" <[EMAIL PROTECTED]>;
> > > > > <[EMAIL PROTECTED]>;
> > > > > > > <[EMAIL PROTECTED]>
> > > > > > > Sent: Wednesday, September 12, 2001 9:30 PM
> > > > > > > Subject: Re: Problem with snmpd
> > > > > > >
> > > > > > >
> > > > > > > > I tried your snmpd.conf but with no success :'(
> > > > > > > > ----- Original Message -----
> > > > > > > > From: "Joe Clarke" <[EMAIL PROTECTED]>
> > > > > > > > To: "Chojin" <[EMAIL PROTECTED]>
> > > > > > > > Cc: "Jean-Francois Dive" <[EMAIL PROTECTED]>;
> > > > > > > <[EMAIL PROTECTED]>;
> > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > Sent: Wednesday, September 12, 2001 8:34 PM
> > > > > > > > Subject: Re: Problem with snmpd
> > > > > > > >
> > > > > > > >
> > > > > > > > > Can you send your snmp.conf file? These are the relevant
> bits
> > > of
> > > > > mine:
> > > > > > > > >
> > > > > > > > > com2sec local localhost public
> > > > > > > > > com2sec localrw localhost private
> > > > > > > > > com2sec mynetwork 172.18.0.0/24 public
> > > > > > > > > com2sec mynetworkrw 172.18.0.0/24 private
> > > > > > > > >
> > > > > > > > > ####
> > > > > > > > > # Second, map the security names into group names:
> > > > > > > > >
> > > > > > > > > # sec.model sec.name
> > > > > > > > > group LocalRWGroup v1 localrw
> > > > > > > > > group LocalRWGroup v2c localrw
> > > > > > > > > group LocalRWGroup usm localrw
> > > > > > > > > group LocalROGroup v1 local
> > > > > > > > > group LocalROGroup v2c local
> > > > > > > > > group LocalROGroup usm local
> > > > > > > > > group NetROGroup v1 mynetwork
> > > > > > > > > group NetROGroup v2c mynetwork
> > > > > > > > > group NetROGroup usm mynetwork
> > > > > > > > > group NetRWGroup v1 mynetworkrw
> > > > > > > > > group NetRWGroup v2c mynetworkrw
> > > > > > > > > group NetRWGroup usm mynetworkrw
> > > > > > > > >
> > > > > > > > > ####
> > > > > > > > > # Third, create a view for us to let the groups have rights
> to:
> > > > > > > > >
> > > > > > > > > # incl/excl subtree mask
> > > > > > > > > view all included .1 80
> > > > > > > > >
> > > > > > > > > ####
> > > > > > > > > # Finally, grant the 2 groups access to the 1 view with
> > > different
> > > > > > > > > # write permissions:
> > > > > > > > >
> > > > > > > > > # context sec.model sec.level match read
> write
> > > > > notif
> > > > > > > > > access LocalROGroup "" any noauth exact all
> > > none
> > > > > > > none
> > > > > > > > > access LocalRWGroup "" any noauth exact all
> > > all
> > > > > > > none
> > > > > > > > > access NetROGroup "" any noauth exact all
> > > none
> > > > > > > none
> > > > > > > > > access NetRWGroup "" any noauth exact all
> > > all
> > > > > > > none
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > public@localhost does work on my machine.
> > > > > > > > >
> > > > > > > > > Joe
> > > > > > > > >
> > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote:
> > > > > > > > >
> > > > > > > > > > I used TMRTGCHO as community name before, but since I've
> got
> > > this
> > > > > > > > problem I
> > > > > > > > > > use now public.
> > > > > > > > > > Request from localhost or any other interface doesn't
> work.
> > > > > > > > > > I cleaned snmpd.log, restarted snmpd:
> > > > > > > > > > #/usr/local/sbin/snmpd -D -c
> > > /usr/local/share/snmp/snmpd.conf -l
> > > > > > > > > > /var/log/snmpd.log
> > > > > > > > > >
> > > > > > > > > > and a new one is located at
> > > > > http://www.tarakan-network.com/snmpd.log
> > > > > > > (I
> > > > > > > > did
> > > > > > > > > > a snmpwalk and snmpget for public@localhost but no
> success)
> > > > > > > > > >
> > > > > > > > > > ----- Original Message -----
> > > > > > > > > > From: "Jean-Francois Dive" <[EMAIL PROTECTED]>
> > > > > > > > > > To: "Chojin" <[EMAIL PROTECTED]>
> > > > > > > > > > Sent: Wednesday, September 12, 2001 10:38 AM
> > > > > > > > > > Subject: Re: Problem with snmpd
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > Hi (salut)
> > > > > > > > > > >
> > > > > > > > > > > In fact, i see some successfull request with the
> community:
> > > > > > > > > > > TMRTGCHO and no attemps with the localhost one... seems
> > > pretty
> > > > > odd.
> > > > > > > > did
> > > > > > > > > > > you only got those requests from localhost not working ?
> > > > > > > > > > >
> > > > > > > > > > > Otherwise, purge the log file, be *sure* that no
> requests
> > > are
> > > > > > > comming
> > > > > > > > from
> > > > > > > > > > > somewhere else and resart to see some failures...
> > > > > > > > > > >
> > > > > > > > > > > JeF
> > > > > > > > > > >
> > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I launched in debug mode
> > > > > > > > > > > > #/usr/local/sbin/snmpd -D -c
> > > > > /usr/local/share/snmp/snmpd.conf -l
> > > > > > > > > > > > /var/log/snmpd.log
> > > > > > > > > > > > I attached snmpd.log
> > > > > > > > > > > > There are so many informations I can't detect the
> problem
> > > :pp
> > > > > > > > > > > >
> > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > From: "Jean-Francois Dive" <[EMAIL PROTECTED]>
> > > > > > > > > > > > To: "Chojin" <[EMAIL PROTECTED]>
> > > > > > > > > > > > Cc: <[EMAIL PROTECTED]>;
> > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM
> > > > > > > > > > > > Subject: Re: Problem with snmpd
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > i think it is possible to start the snmpd and not
> send
> > > it to
> > > > > > > > > > backgroud,
> > > > > > > > > > > > > and see if it does printout some error
> > > messages..Otherwise
> > > > > use
> > > > > > > the
> > > > > > > > > > truss
> > > > > > > > > > > > > command to follow the syscalls made by the daemon
> while
> > > > > > > processing
> > > > > > > > > > your
> > > > > > > > > > > > > request, this could point you to a problem..
> > > > > > > > > > > > >
> > > > > > > > > > > > > JeF
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > snmpd.log is empty...
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I did #netstat -an | grep 161
> > > > > > > > > > > > > > udp4 0 0 *.161 *.*
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > port 161 exists then it should work...
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > From: "Jean-Francois Dive" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > To: "Chojin" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > Cc: <[EMAIL PROTECTED]>;
> > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM
> > > > > > > > > > > > > > Subject: Re: Problem with snmpd
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > So you have any traces in a log file or
> something
> > > > > similar ?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > JeF
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Hello,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I have a problem with snmpd.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I
> didn't
> > > modify
> > > > > any
> > > > > > > > > > > > setting ),
> > > > > > > > > > > > > > snmpd
> > > > > > > > > > > > > > > > didn't work anymore:
> > > > > > > > > > > > > > > > When I do a snmpwalk or snmpget to
> > > public@localhost it
> > > > > > > > doesn't
> > > > > > > > > > > > respond.
> > > > > > > > > > > > > > > > I checked snmpd, recreated snmpd.conf and
> launched
> > > > > again
> > > > > > > > snmpd
> > > > > > > > > > > > with -c
> > > > > > > > > > > > > > > > and -l to be sure it uses the correct files.
> > > > > > > > > > > > > > > > But even if snmpd is in background process,
> > > > > > > > public@localhost
> > > > > > > > > > > > doesn't
> > > > > > > > > > > > > > work.
> > > > > > > > > > > > > > > > I don't have any firewall rule that block it.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > #snmpwalk localhost public
> > > > > > > > > > > > > > > > Timeout: No Response from localhost
> > > > > > > > > > > > > > > > #snmpget localhost public SysName
> > > > > > > > > > > > > > > > Timeout: No Response from localhost.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to
> > > 4.4-RC,
> > > > > it
> > > > > > > > didn't
> > > > > > > > > > > > change
> > > > > > > > > > > > > > > > anything for snmpd.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > If someone has got any idea...
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Chojin
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > To Unsubscribe: send mail to
> [EMAIL PROTECTED]
> > > > > > > > > > > > > > > > with "unsubscribe freebsd-hackers" in the body
> of
> > > the
> > > > > > > > message
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > > > > > > > > with "unsubscribe freebsd-questions" in the body of the
> > > message
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > > > > > > > with "unsubscribe freebsd-questions" in the body of the
> message
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > > > > > > with "unsubscribe freebsd-questions" in the body of the
> message
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-questions" in the body of the message
> >
>
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
