I run a snmpwalk against the pfsense and I get as a response an IpAdress 0.0.0.0
This is wird as the monitoring tool try on the iP 0.0.0.0 that doesn't exist
arp doesn't show this IP
In the conf xml file there is no 0.0.0.0
From where this ip come from and how I can remove this ip?
Thank you

I've noticed an issue with bsnmpd on pfSense where the path and parameters for certain processes are not returned, for example the built-in NGINX processes running the pfSense GUI. Is this a known issue? We need this kind of functionality for Zabbix monitoring.

I found some old threads regarding monitoring CARP via snmp.
There is no problem in monitoring the interfaces up/down state but it seems that CARP does not have interfaces anymore.

Does anyone have an idea if CARP monitoring via snmp is possible?

Thank you!

Greetings
Sebastian

gif or gif0 :

### The following interface is commented out because:
* has no ifSpeed property

ovpns devices:

### The following interface is commented out because:
### * has no ifSpeed property

ovpnc devices:

### The following interface is commented out because:
### * has no ifSpeed property

No effect for administratively DOWN or operationally DOWN interfaces, or softwareLoopback devices: e.g.:

enc or enc0 :

### * it is administratively DOWN
### * it is operationally DOWN
### * has no ifSpeed property

lo or lo0 :

### * it is a Software Loopback interface
### * has no ifSpeed property

pflog or pflog0 :

### * it is administratively DOWN
### * it is operationally DOWN
### * has no ifSpeed property

pfsync or pfsync0 :

### * it is administratively DOWN
### * it is operationally DOWN
### * has no ifSpeed property

The solution was to change cfgmaker arguments:

/usr/bin/cfgmaker --zero-speed=10000000 -o outfile.cfg community@object 

Additionally, --ifdesc=descr changed the Title to start with device or device.vlan where appropriate.

Here is the site that gave me the hint:
https://aacable.wordpress.com/2014/07/07/mrtg-monitoring-with-esxi-hosted-guest-return-interface-is-commented-has-no-ifspeed-property/

https://oss.oetiker.ch/mrtg/doc/cfgmaker.en.html

However, cfgmaker does not have an argument for enabling monitoring of loopback devices, though there is a more complicated method to work around that using something such as '--if-filter=($default_iftype && $if_admin)' with type 24, softwareLoopback as documented at the website above or something like below:

"--if-filter=($default || $if_type==24)"

The positional order is important, all flags need to precede community@router. --if-filter carries a caveat:

--if-filter=f     Test every interface against filter f to decide wether
                   or not to include that interface into the collection.
                   Currently f is being evaluated as a Perl expression
                   and it's truth value is used to reject or accept the
                   interface.
                   (Experimental, under development, might change)

The resulting command line argument contains double quotes:

/usr/bin/cfgmaker --ifdesc=descr --zero-speed=10000000 "--if-filter=($default 
|| $if_type==24)" -o outfile.cfg community@router

If you run into an issue with the shell interpreting the contents, switch to the double quotes to single quotes.

Now lo0 is monitored by MRTG using bsnmpd. To monitor lo0 and everything ethernet:

/usr/bin/cfgmaker --ifdesc=descr --zero-speed=10000000 "--if-filter=($default 
|| $if_type==24 || $if_type==6)" -o outfile.cfg community@router

Initially, I thought it was a blip due to a service restarting, and the SNMP check happening at the same time, but the alert didn't go away.
I knew it was a false alert because DHCP was clearly working, so I looked into the root cause of the false alert.

The actual issue was that the ISC process name 'dhcpd' is replaced by 'kea-dhcp4' and 'kea-dhcp6', so the old process name isn't running anymore, and that is what Zabbix was looking for.

below is the basic snmpwalk to check the relevant OID:

% snmpwalk [pfsense-server] .1.3.6.1.2.1.25.4.2.1.2 | grep dhcp
HOST-RESOURCES-MIB::hrSWRunName.13707 = STRING: "kea-dhcp4"
HOST-RESOURCES-MIB::hrSWRunName.13916 = STRING: "kea-dhcp6"
HOST-RESOURCES-MIB::hrSWRunName.56040 = STRING: "dhcpleases"

The correction needed is on the Zabbix side to look for the new processes (clone the DHCP monitoring template, change the SNMP OID check to look for the new process names, and disable the previous one.)

I am posting it on the pfSense SNMP forum as as FYI in case anyone else is monitoring pfSense DHCP service via SNMP since it would affect any SNMP monitor searching by process name when switching between ISC and Kea DHCP.

Just thought I would give back to the community to monitor your pfSense for temperature through SNMP. Find this useful please leave a comment.

Prerequisites:
NET-SNMP package from pfSense
LibreNMS
SSH access to pfSense with basic VI editing skills
Linux skills

Log into pfSense to Shell (8):
Create a file called gettemps.sh through VI:
vi /root/gettemps.sh

File content:
#!/bin/sh
/sbin/sysctl dev.cpu | /usr/bin/awk '/temperature/ {print $2;}' | sed 's/[F]//g'

Save and quit the file.

Make it executable:
chmod the file to make it executable
chmod +x /root/gettemps.sh

Go to pfSense > Services > NET-SNMP > Host Information
Add into the Extended Commands
Name: gettemps
Program: /root/gettemps.sh
Save
(note: the Name in the screenshot has been chopped off - it is gettemps)

Go to pfSense SSH
If running SNMP v3 use (replace variables):
snmpget -v 3 -l authPriv -a SHA -A [password] -u snmp -x AES -X [password] [fw-hostip] nsExtendOutputFull."gettemps"

If running SNMP v2c use (replace variables):
snmpwalk -c public -v 2c [fw-hostip] nsExtendOutLine."gettemps"
Output should look like this below:
NET-SNMP-EXTEND-MIB::nsExtendOutputFull."gettemps" = STRING:
44.0C
48.0C
44.0C
47.0C

Take the MIB after the two colons(::) nsExtendOutputFull."gettemps" that you get (my example is above) and add it to the LibreNMS Custom OID field. Set limits etc. Save it off.

Wait about 15 minutes and there will be a chart drawn up.

To view the data now go to:
You can now monitor your temperature of the pfSense through LibreNMS.

Any issues let me know. Thanks.
M.

References:
https://forum.netgate.com/topic/107545/reading-out-the-temperature/4
https://www.reddit.com/r/PFSENSE/comments/cnjddc/howto_retrieve_cpu_temp_and_other_data_over_snmp/

I would like to monitor the status of a pfSense pppoe port so that I can power cycle/reboot my DSL modem if the connection goes down. The modem is operating in bridge mode and is connected to the WAN ethernet port. The snmp operational status (1.3.6.1.2.1.2.2.1.8) for the active (i.e. passing traffic) pppoe port is 5 which i think means dormant. Shouldn't I be getting a value of 1 (up)?

TIA,
Tom

Since I enabled LLDP logs look like this.

Dec 12 14:08:01 	lldpd 	58121 	cannot connect to /var/agentx/master: No such file or directory
Dec 12 14:08:01 	lldpd 	58609 	Warning: Failed to connect to the agentx master agent ([NIL]):
Dec 12 14:07:29 	lldpd 	36100 	cannot connect to /var/agentx/master: No such file or directory
Dec 12 14:07:29 	lldpd 	36214 	cannot connect to /var/agentx/master: No such file or directory
Dec 12 14:07:29 	lldpd 	36972 	Warning: Failed to connect to the agentx master agent ([NIL]):

Everything up to the latest, can't figure out what's wrong.
Any hint how I fix this?

Can access the LLDP GUI part from menu/services/LLDP,
never reach the page for this settings.

Going trough Menu/Status/Service and the the link on the service for settings works sometimes to reach the settings.

And, just now the GUI hung so I can't access it all...

Edit: more info
Even though i unchecked LLDPs active (I turned it off). Logged still spamed and the service indicated as it was still running. Could stop it either...