-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set SNMPTrap community string (feature request) #13
Comments
Could you please at least describe in the documentation that only one community string can be used at this moment? |
@mvhconsult done in the README! |
This request seems like a no-brainer... |
@dstones Your pull request is welcome! |
Any progress on this one, are we anywhere near a realease with custom community strings? |
Was any progress made on this? |
Any update on allowing other (or wildcard all) communities? We have a system where there are no way to change them... :| |
@joschi - Any idea why the limitation exists? I'm not stunningly familiar with Java or SNMP4J, but it seems like a There are references in the SNMP4J documentation for creating a So where is the hard-coded reference to The only potential place I can thight it might be, is
null to the constructor of TransportStateReference , but I can't quite follow where that is used, either.
|
Hi,
in reference to Jochens reply to my Mailing List entry:
https://groups.google.com/forum/?hl=en#!searchin/graylog2/snmp/graylog2/0eX-OTXuouw/806cNHLDCQAJ
As Jochen wrote the community string "public" is hardcoded in the plugin.
The plugin is working well with Graylog 2.0.1 on CentOS 6.7 but only with the default community string "public".
It is needed to set the community string.
In a first step it would be ok to configure it in /etc/graylog/server/server.conf or in a another file.
Best solution would be in the configuration window in Graylog Web as shown here:
https://github.com/Graylog2/graylog-plugin-snmp/blob/master/images/snmp-input-1.png
Thanks for the good work
Chris
The text was updated successfully, but these errors were encountered: