Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Sep 2001 23:55:28 +0200
From:      "Chojin" <freebsd@tarakan-network.com>
To:        "Chojin" <freebsd@tarakan-network.com>, "Joe Clarke" <marcus@marcuscom.com>
Cc:        "Jean-Francois Dive" <jef@linuxbe.org>, <freebsd-questions@FreeBSD.ORG>, <freebsd-hackers@FreeBSD.ORG>
Subject:   Re: Problem with snmpd
Message-ID:  <00c501c13fc3$9e9aeb10$0245a8c0@chojin>
References:  <20010912143244.B43876-100000@shumai.marcuscom.com> <017801c13bc1$5bc3a580$0245a8c0@chojin>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
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" <freebsd@tarakan-network.com>
To: "Joe Clarke" <marcus@marcuscom.com>
Cc: "Jean-Francois Dive" <jef@linuxbe.org>; <freebsd-questions@FreeBSD.ORG>;
<freebsd-hackers@FreeBSD.ORG>
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" <marcus@marcuscom.com>
> To: "Chojin" <freebsd@tarakan-network.com>
> Cc: "Jean-Francois Dive" <jef@linuxbe.org>;
<freebsd-questions@FreeBSD.ORG>;
> <freebsd-hackers@FreeBSD.ORG>
> 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" <jef@linuxbe.org>
> > > To: "Chojin" <freebsd@tarakan-network.com>
> > > 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" <jef@linuxbe.org>
> > > > > To: "Chojin" <freebsd@tarakan-network.com>
> > > > > Cc: <freebsd-questions@FreeBSD.ORG>; <freebsd-hackers@FreeBSD.ORG>
> > > > > 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" <jef@linuxbe.org>
> > > > > > > To: "Chojin" <freebsd@tarakan-network.com>
> > > > > > > Cc: <freebsd-questions@FreeBSD.ORG>;
> <freebsd-hackers@FreeBSD.ORG>
> > > > > > > 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 majordomo@FreeBSD.org
> > > > > > > > > with "unsubscribe freebsd-hackers" in the body of the
> message
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-questions" in the body of the message
> > >
> > >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
> >
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
>

[-- Attachment #2 --]
com2sec local     localhost       public
com2sec localrw   localhost       private
com2sec mynetwork 192.168.0.0/24 public
com2sec mynetworkrw 192.168.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


rocommunity  public localhost
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00c501c13fc3$9e9aeb10$0245a8c0>