Bug #3883
closedChanging SNMP Bind Interface does not change actual bind interface of SNMP service.
100%
Description
Version
2.1.4-RELEASE (amd64)
built on Fri Jun 20 12:59:50 EDT 2014
FreeBSD 8.3-RELEASE-p16
CPU Type
Intel(R) Xeon(TM) CPU 3.00GHz
4 CPUs: 2 package(s) x 1 core(s) x 2 HTT threads
--
I've been trying to change the bind interface of the SNMP service. However, using the web interface and selecting any interface including "all" does not appear to affect the SNMP service. It will only listen and respond on the LAN interface address.
Also tried stopping the service, editing /var/etc/snmpd.conf, and restarting the service. The begemotSnmpdPortStatus IP address is restored to the LAN interface address.
Updated by Jim Pingle about 10 years ago
- Status changed from New to Rejected
I can't reproduce this on 2.1.5, please post on the forum for assistance/diagnosis. If a bug can be confirmed, this may be reopened.
Bound to All:
: sockstat | grep 'bsnmp.*161' root bsnmpd 5278 5 udp4 *:161 *:* : grep dPortStatus /var/etc/snmpd.conf begemotSnmpdPortStatus.0.0.0.0.161 = 1
Bind to LAN:
: sockstat | grep 'bsnmp.*161' root bsnmpd 71167 5 udp4 192.168.28.1:161 *:* : grep dPortStatus /var/etc/snmpd.conf begemotSnmpdPortStatus.192.168.28.1.161 = 1
Moved back to Any:
: sockstat | grep 'bsnmp.*161' root bsnmpd 33527 5 udp4 *:161 *:* : grep dPortStatus /var/etc/snmpd.conf begemotSnmpdPortStatus.0.0.0.0.161 = 1
Updated by J B about 10 years ago
There are six interfaces on this system. This is the output for binding to interface All, LAN, two other interfaces, and localhost
[2.1.4-RELEASE][admin@x]/root(12): sockstat | grep 'bsnmp.*161'
root bsnmpd 217 10 udp4 192.168.5.252:161 *:*
[2.1.4-RELEASE][admin@x]/root(13): grep dPortStatus /var/etc/snmpd.conf
begemotSnmpdPortStatus.192.168.5.252.161 = 1
Interface "Any" is not an option.
Updated by Jim Pingle about 10 years ago
At a minimum, upgrade to 2.1.5. If you still have a problem, post on the forum.
Updated by David Wood about 9 years ago
There is a report of a problem with 2.2.4 at https://forum.pfsense.org/index.php?topic=101538
Updated by Phillip Davis about 9 years ago
This should fix it:
https://github.com/pfsense/pfsense/pull/2000
Updated by Phillip Davis about 9 years ago
I am guessing that the OP has (had) the old "snmp" "bindlan" set in config.xml
With the code in 2.2.4 or before, that would have overridden whatever new selection of "bindip" that was made.
Could this be "unrejected" and target version set to 2.2.5?
Updated by Renato Botelho almost 9 years ago
- Status changed from Rejected to Feedback
- Target version set to 2.3
- % Done changed from 0 to 100
Fixed by https://github.com/pfsense/pfsense/pull/2088, thanks Phil!
Updated by Jim Thompson almost 9 years ago
- Assignee set to Jim Pingle
assigned for feedback evaluation and closure.
Updated by Jim Pingle almost 9 years ago
- Status changed from Feedback to Resolved
Bind setting works right even with that old tag in place now. Closing.
Updated by Chris Buechler over 8 years ago
- Affected Version changed from 2.1.x to All