@cameloid Here’s the original post I made when I discovered the bug:

https://forum.netgate.com/topic/188050/24-03-causes-sustained-rise-in-processes-count-and-memory-usage

@SOUK Home Assistant has an active Integration for pfSense via HACS.
https://github.com/travisghansen/hass-pfsense

It gives CPU, Memory, Leases, Disk etc.
HA_pfsense.png

What it doesn't give is in/out on an interface. I get this via snmp:

in OiD
1.3.6.1.2.1.2.2.1.10.6 where .6 is the interface number
out OiD
1.3.6.1.2.1.2.2.1.16.6 where .6 is the interface number

sensor: # read the Bytes in/out on an interface in an interval - platform: snmp name: asa5512x1_wan6_in host: 10.10.10.1 community: dom baseoid: 1.3.6.1.2.1.2.2.1.10.6 accept_errors: true version: 2c scan_interval: 20 - platform: snmp name: asa5512x1_wan6_out host: 10.10.10.1 community: dom baseoid: 1.3.6.1.2.1.2.2.1.16.6 accept_errors: true version: 2c scan_interval: 20 # calculate the gradiant of the bandwith of the asa5512x - platform: derivative source: sensor.asa5512x1_wan6_in unit_time: s unit: B name: asa5512x1_wan6_in_der - platform: derivative source: sensor.asa5512x1_wan6_out unit_time: s unit: B name: asa5512x1_wan6_out_der # calculate MBps and MiB between intervals of the asa5512x - platform: template sensors: asa5512x1_wan6_in_mbps: value_template: "{{ (states('sensor.asa5512x1_wan6_in_der')|float*8/1000000)|round(2) }}" unit_of_measurement: 'Mbps' friendly_name: Internet in Mbps asa5512x1_wan6_out_mbps: value_template: "{{ (states('sensor.asa5512x1_wan6_out_der')|float*8/1000000)|round(2) }}" unit_of_measurement: 'Mbps' friendly_name: Internet out Mbps asa5512x1_wan6_in_mib: value_template: "{{ (states('sensor.asa5512x1_wan6_in')|float/1000000)|round(2) }}" unit_of_measurement: 'MiB' friendly_name: Internet in MiB asa5512x1_wan6_out_mib: value_template: "{{ (states('sensor.asa5512x1_wan6_out')|float/1000000)|round(2) }}" unit_of_measurement: 'MiB' friendly_name: Internet out MiB asa5512x1_wan6_in_gib: value_template: "{{ (states('sensor.asa5512x1_wan6_in')|float/1000000000)|round(2) }}" unit_of_measurement: 'GiB' friendly_name: Internet in GiB asa5512x1_wan6_out_gib: value_template: "{{ (states('sensor.asa5512x1_wan6_out')|float/1000000000)|round(2) }}" unit_of_measurement: 'GiB' friendly_name: Internet out GiB

And for the totals (day/month):

utility_meter: # asa5512x1 wan usage asa5512x1_wan6_in_gib_monthly: source: sensor.asa5512x1_wan6_in_gib cycle: monthly name: Internet in monthly asa5512x1_wan6_in_gib_daily: source: sensor.asa5512x1_wan6_in_gib cycle: daily name: Internet in daily asa5512x1_wan6_out_gib_monthly: source: sensor.asa5512x1_wan6_out_gib cycle: monthly name: Internet out monthly asa5512x1_wan6_out_gib_daily: source: sensor.asa5512x1_wan6_out_gib cycle: daily name: Internet out daily

Hi
did you try snmpwalk?
Are you sure about the version?

@keyser Thanks for the pointer to the post! It's clear now that we'll have to wait until 24.08.

In the meantime, I'll set up a cron-controlled restart of bsnmpd on all monitored firewalls sigh :-)

@Roberto-Marcelino did you set the same community on pfsense snmp config and zabbix? Other than that, i think you just need to allow traffic from your zabbix to your wan interface on port 61161.
After you do those things, try to create the host on zabbix again

Hello @jimp
Do you have an idea of ​​the problem ?
Thanks in advance 👍

@PVuchetich2 I was using it in another way here on my network, but it seems that the solution will be to migrate by installing the Zabbix agent on pfSense itself. Thank you very much for your answer.

I must have posted this in the wrong section, or people really don't like answering SNMP questions. I'm looking for an answer on how to make sure a service starts on reboot. SNMP does not., Maybe it's a bug, maybe it's a configuration problem. If this is something that can only be answered by paid support, can someone please tell me that.

Larry

@opahla said in OID for Netgate 1541 PFSense:

Hi @Setarcos

I would like to confirm if there is any impact if I change configuration in root file of pfsense. If there is no impact then I would proceed right away. Thanks in advance for the reply.

I have been using the referenced configuration with my 7100 for the past three years without issue.

@jimp Thanks for replying.

I opened at matching feature request at https://redmine.pfsense.org/issues/14901. Crossing my fingers... :)

@abs0new Unfortunately, the issue of ownership of /var/db/nut will currently arise every time you reboot.

To remediate, you can either edit nut.inc, add a boot time shell script, or wait until I can fix the package.

We now analyzed the problem with the Support of our NAC Software. It has nothing to do with V2 or V3.
The problem is, that with pfsense+ 23.05.1 all SNMP requests get delayed by the factor 3-4.

With pfsense+ 22.05, it takes between 2-3 seconds to get the status of all Interfaces from a Switch:
2205.jpg

With pfsense+ 23.05.1, its takes between 9-11 seconds to get the status of all Interfaces from a Switch:
23051.jpg

They say, that there is probably some kind of "internal QOS" delaying SNMP requests in the new firmware, or SNMP has a very low priority in some system services.
Is that the fact? Or why does the SNMP responses get such a high delay?

The base configuration of our NAC Software is 32 OIDs per request, with 30 values per response packet in the answer, with a timeout of 2 Seconds per answer. This worked without problems under 22.05.
We could make a workaround for our NAC Software. We had to set it to 1 OID, with 8 values per packet and a timeout of 10 seconds. SNMP is working with this config again, but as I said above, with a delay factor of 3-4 compared to pfsense 22.05.