Project

General

Profile

Actions
Copy link

Bug #956

closed

# cannot be used in SNMP configuration

Added by Adam Thompson almost 16 years ago. Updated almost 16 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
SNMP
Target version:
2.0
Start date:
10/15/2010
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

Actual problem is a # character can't be used in any of the SNMP configuration fields. Original post follows.

Running 2.0-BETA4 (i386) built on Thu Oct 14 01:16:12 EDT 2010 FreeBSD 8.1-RELEASE-p1

Oct 15 15:11:44 pfsense snmpd44594: unexpected character 0xa
Oct 15 15:11:44 pfsense snmpd44594: in file /var/etc/snmpd.conf line 25
Oct 15 15:11:44 pfsense snmpd44594: error in config file

Unsurprisingly, "bsnmpd" service always shows "stopped".

Don't know a lot about this config file's syntax, but on line 9, changing

system := 1     # pfSense
to
     system := "1"     # pfSense

at least allows bsnmpd to start. That fix doesn't make sense to me, but it works anyway. Deleting the comment also seems to do the trick. This might relate to the way bsnmpd parses its config file - if everything after a ":=" is copied verbatim and comments ignored...?

Actions
Copy link

Also available in: Atom