OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: FCM on February 20, 2019, 11:29:11 am

Title: [Solved]can we have the old snmp plugin too please ?
Post by: FCM on February 20, 2019, 11:29:11 am: Hello,
I use SNMP to check my distant sites (via openvpn)
Until now I used the old SNMP plugin and have no problem with it.
I tried once to make the new one work but it didn't so I let the old one.

but with the 19.1, there is only the net-snmp available. And it doesn't start at all.
When I removed the plugin and install it again I saw these :

Quote
**** This port installs snmpd, header files and libraries but does not
start snmpd by default.
If you want to auto-start snmpd and snmptrapd:, add the following to
/etc/rc.conf:

   snmpd_enable="YES"
   snmpd_flags="-a"
   snmpd_conffile="/usr/local/share/snmp/snmpd.conf /etc/snmpd.conf"
   snmptrapd_enable="YES"
   snmptrapd_flags="-a -p /var/run/snmptrapd.pid"

**** You may also specify the following make variables:

   NET_SNMP_SYS_CONTACT="zi@FreeBSD.org"
   NET_SNMP_SYS_LOCATION="USA"
   DEFAULT_SNMP_VERSION=3
   NET_SNMP_MIB_MODULES="host smux mibII/mta_sendmail ucd-snmp/diskio"
   NET_SNMP_LOGFILE=/var/log/snmpd.log
   NET_SNMP_PERSISTENTDIR=/var/net-snmp

to define default values (or to override the defaults). To avoid being
prompted during the configuration process, you should (minimally) define
the first two variables. (NET_SNMP_SYS_*)

You may also define the following to avoid all interactive configuration:

   BATCH="yes"
Checking integrity... done (0 conflicting)
Nothing to do.
So, we really have to do theses modifications to make it work ?
In that case, I prefer the old one...
I don't have an error I can use when I try to start manually the service :
Quote
root: /usr/local/etc/rc.d/snmpd: WARNING: failed to start snmpd

thanks fo any help
Title: Re: can we have the old snmp plugin too please ?
Post by: franco on February 20, 2019, 11:40:44 am: Hi,

No, you are not supposed to make manual modifications.

We cannot expect to be bug-free so we appreciate more details on “it doesn’t start at all” and are happy to fix.

The old SNMP plugins had poor FreeBSD support especially for being a freebsd base utility, so we are confident to have it removed.

Cheers,
Franco
Title: Re: can we have the old snmp plugin too please ?
Post by: FCM on February 20, 2019, 11:53:08 am: hi,
I'll try :

backend log :
Quote
Feb 20 11:44:33   configd.py: [60db9247-d6ef-4d95-b2f1-c803fcfac02d] request pfctl byte/packet counters
Feb 20 11:44:27   configd.py: [2fa07971-1ac9-4867-b40e-e33acc8ad4bf] request pfctl byte/packet counters
Feb 20 11:44:22   configd.py: [ae5ef72a-f62f-4c18-9336-961536ede693] returned exit status 1
Feb 20 11:44:22   configd.py: [ae5ef72a-f62f-4c18-9336-961536ede693] starting Net-SNMP

general log :
Quote
Feb 20 11:44:22   root: /usr/local/etc/rc.d/snmpd: WARNING: failed to start snmpd

SNMP service is enable, Community has a simple name (public) and I put the listen IP of my Centreon. I tried with the layer 3 visibility check or uncheck and that changed nothing.

What other informations can I give you ?
Title: Re: can we have the old snmp plugin too please ?
Post by: FCM on February 25, 2019, 10:21:17 am: hello,
my bad: no IP adresses in the "Listen IPs" field and the service starts and runs...
I was thinking this field was for the supervision server IP address but you put nothing and it works...
Title: Re: [Solved]can we have the old snmp plugin too please ?
Post by: mimugmail on February 25, 2019, 02:07:54 pm: Beeing empty means it listens on all IPs at port 161 :)
Title: Re: [Solved]can we have the old snmp plugin too please ?
Post by: franco on February 26, 2019, 11:38:52 pm: Ah, ok, confusion seems to have arisen from "listening IP" which must be an IP local to the firewall or left empty to listen on all addresses for remote connections.

Cheers,
Franco