Hi I'm testing out some code that is both sending and receiving traps from net-snmp I have noticed that if you double quote the community string in snmpd.conf like this:
trap2sink 10.10.10.10 "public" It will actually send the trap with the quotes in the community string. I verified this in wireshark. However when I use snmptrapd it will not authenticate that community string when entered as either "public" or public. Wasn't able to find a way to authenticate with the quotes as it seems to interpret the configuration differently than snmpd.conf. I know that it works properly if I drop the quotes in snmpd.conf so tempted to just head this route; but if we desired to be able to support community strings that contain a space how can that be accomplished without sending the trap with the quotes in the packet? Or are spaces disallowed in community strings in snmp all together? I searched through some of the RFCs and it looked like they just say it is an octet string without a whole lot of qualification about the specific characters allowed. I did some searches on various vendors and it looked like some allow space and some do not so curious if net-snmp has some way of handling them? Thanks for any advice in this matter, Jared
------------------------------------------------------------------------------
_______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
