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-hackers" in the body of the message
