Actions
Bug #16909
closed
Special char validation for community name in SNMP service
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
SNMP
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
There are a few special characters that the GUI accepts, but the service would not start if they are used.
For example, $ and "
Tested on
26.03.1-RELEASE (amd64) built on Wed May 20 18:19:00 MSK 2026 FreeBSD 16.0-CURRENT
Files
Updated by Danilo Zrenjanin 4 days ago
- Status changed from New to Confirmed
I can confirm this behavior.
Jun 19 14:06:09 snmpd 20057 error in config file Jun 19 14:06:09 snmpd 20057 in file /var/etc/snmpd.conf line 9 Jun 19 14:06:09 snmpd 20057 in macro read pos 9 Jun 19 14:06:09 snmpd 20057 eol expected Jun 19 14:06:04 snmpd 10985 error in config file Jun 19 14:06:04 snmpd 10985 in file /var/etc/snmpd.conf line 9 Jun 19 14:06:04 snmpd 10985 in macro read pos 9 Jun 19 14:06:04 snmpd 10985 eol expected Jun 19 14:06:00 check_reload_status 498 Syncing firewall Jun 19 14:05:59 php-fpm 32985 NOTICE [Config] Configuration Change: admin@172.21.10.178 (Local Database Fallback): SNMP settings saved
Tested against:
26.03.1-RELEASE (arm) built on Wed May 20 17:19:00 CEST 2026 FreeBSD 16.0-CURRENT
Updated by Jim Pingle 4 days ago
- Project changed from pfSense Plus to pfSense
- Category changed from SNMP to SNMP
- Status changed from Confirmed to Duplicate
Duplicate of #16901 and already mostly addressed in 26.11/26.07
$ is special in that it's technically valid as part of variable substitution in bsnmp config, so it's not that it's broken, you're just not using it as bsnmpd expects, so it might still be worth rejecting.
Actions