Write stuff in the conf file ( and here I am TRULY just guessing)
My Netdata is on 192.168.10.15
My group is called homered-conram
That is all I know in advance
conf file:
########################################
# homered-conram added aug 30 2025
####
# First, map the community name (COMMUNITY) into a security name
# (local and mynetwork, depending on where the request is coming
# from):
# sec.name source community
com2sec local localhost public
com2sec localnet 192.168.10.0/24 homered-conram
####
# Second, map the security names into group names:
# sec.model sec.name
group MyRWGroup v1 local
group MyRWGroup v2c local
group MyRWGroup usm local
group MyROGroup v1 mynetwork
group MyROGroup v2c mynetwork
group MyROGroup usm mynetwork
group localgroup v1 localnet
group localgroup v2c localnet
####
# Third, create a view for us to let the groups have rights to:
# incl/excl subtree mask
view all included .1 80
view all included .1
####
# Finally, grant the 2 groups access to the 1 view with different
# write permissions:
# context sec.model sec.level match read write notif
access MyROGroup "" any noauth exact all none none
access MyRWGroup "" any noauth exact all all none
access localgroup "" any noauth exact all none none
dunno if to remove the other groups or what
In any case my Netdata files sems ok, I have defined that thing in it, and while I do not expect you guys to be experts in Netdata, you are in IPFire.
IPFire is not responding running the command
snmpwalk -v2c -c homered-conram 192.168.10.1
I get no errors in Netdata, but it does not seem to present any data from IPFire, nor is IPFire selectable anywhere.
All seems just werd and uber complex, in other interfaces you seem to be able to enable smtp and name your group and it works.
I am not sure if placing it as 1 may affect something, still figuring out rule priorities as I go, but that open the Netdata IP to Green network at port UDP 161 according to info I looked up.
By using these lines, and making a new conf file with all the rest of its content gone:
# Allow Netdata on 192.168.10.15 to query SNMP using v2c and community “homered-conram”com2sec netdata 192.168.10.15 homered-conramgroup netgroup v2c netdataview all included .1access netgroup “” any noauth exact all none nonerocommunity homered-conram 192.168.10.15
on IPFire:
/etc/rc.d/init.d/netsnmpd restart
on Netdata:
snmpwalk -v2c -c homered-conram 192.168.10.1
generated loads of response
Need to review once more and see it it actuiall arrives but looks good do far.
Oh, and the FW Destination rule is NOT to Firewall… it is to Standard Netwrok Green … works
Right now I have data collection listening and working via port 161 with FW Destination Standard Network Green.
Changed that again, FW Destination Firewall: Green and from what I can see… (I have yet to see IPFire in the Netdata interface), the snmp collection does seem to work, despite the fw rule stating Policy blocked.
I restarted the Netdata module several times and it still collected, so I guess there is more ways to skin this cat, but only one way to do it right.
Well, placing Netdat on a separate sever (inside a Proxmox Node Server in my case) is because I want it to monitor all my machines on the network, not just IPFire, even if IPFire is more important than, say, my virtual test machines.
As it is I might look at Cacti, but I am leaning towards LibreNMS or Zabbix but I have to look them up a bit.
Keeping the same configuration in IPFire SNMP I have now launched a LibreNMS setup and while extremely tedious to setup and configure, in my opinion, it also worked pulling machine data…