While you might be able to fake that using it as a gateway with a monitor + SMTP notifications, realistically that's not feasible. The firewall isn't a monitoring system, you'd be better served by setting up a small monitoring system separate from the firewall (even something light like smokeping) to keep an eye on things like that for you.

It's not net-snmp, those won't work. It's bsnmpd.

They won't work as expected, I mean. They are not executed on poll. They likely won't work how you're intending them to work.

Yep, agreed - you're absolutely right! I did try a custom command (manually edited /var/etc/snmpd.conf) - and the command does work, but it doesn't update on demand (just like you said), rather it executes on a preset / configured schedule. That may be OK though - is there a way to set the custom commands? If not, not a biggie - would just be handy.

Thanks!

@jimp:

Someone could write up a package for net-snmp.

It probably won't make it into base because of its required dependencies, though perhaps that can be trimmed as well.

Is this made any easier by the new architecture in 2.3? I can do pkg install net-snmp easily enough, no dependencies are installed at all.

nope, xen. Past pfsense versions I've ran in the exact same config had working 64 bit counters but a recent change in 2.3 made them go away. Plenty of other OS's running in VM's here have working 64 bit counters so I'm not sure how it would be a hypervisor issue

At the moment we don't have a way to expose the patchlevel over SNMP that I can see. All it can see is the FreeBSD kernel version which won't change if the firewall update doesn't replace the kernel.

From the  OpenNMS server, you can use the snmp-request tool in the $OPENNMS_HOME/bin directory.

For example, support that the IP address of the target node is 192.168.0.8, the community string is public, and the SNMP agent is enabled using the default port with SNMPv2, the command should look like this:

/opt/opennms/bin/snmp-request -c public -v 2c -Ow 192.168.0.8 .1.3.6.1.2.1.1

This is equivalent to execute an snmpwalk like this:

snmpwalk -One -v 2c -c public 10.0.0.1 system

Actually, i can monitor process with that zabbix key : proc.num[dnsmasq]
But, "Captive portal" does not appear in the processes list.

I found the cause of the problem. I used a special character ("ß") in the SNMP location field which is not valid (I simply overlooked that error). However, I was able to enter it on the "Services: SNMP" page and it caused a hick-up in the configuration. I think it might be a good idea to check that only USASCII characters are used for sysLocation and sysContact.

Hi,
Did you manage to achieve what you were looking for here?

If you search the forum for that error, you'll find a similar thread from a week or two ago – someone tracked it down to a problem in the FreeBSD bsnmpd daemon and how it handles interface IP address queries from the SNMP client (in your case, Spiceworks or whatever NMS you have).

It's a problem in the FreeBSD bsnmpd daemon so it needs to be fixed upstream. We might have one of our devs look at it, if they have some time. See https://redmine.pfsense.org/issues/4298

tank you for replaying

how to configure  pfsense and zabbix to get values from pfsense
pfsense in snmp tab need Read Community String but its not defined in pfsense
who to configure pfsense and zabbix

I had to open a case on this with pfsense - they were able to replicate the problem not only in pfsense, but FreedBSD 10.2, which indicates that this is a bug in bsnmpd that needs to go to the attention of the FreeBSD project.  I've submitted a problem report to FreeBSD here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203264 - hopefully I formatted ti well enough that it won't rate an immediate close :)