- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI would like to know how to configure the snmpd.conf
I would like to limit the query by certain network addresses, can I restrict them in the snmp.conf
What is com2sec in the snmp.conf example mean? Is it a group, a person? Can I change it
Thank you
kk44
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: MysidiaPosted on 2009-05-09 at 19:56:31ID: 24346658
com2sec is a _command_ that maps a SNMPv2 community to a "security name"
SNMP Security name is a concept from SNMPv3 the latest version of SNMP protocol.
Most equipment is still using SNMPv2, which doesnot support the concept of "security name"
MAPPING a snmpv2 community to a security name, means it is _AS IF_ they used that security name.
You would typically do something like this:
# sec.name source community
#define a security name 'mysecname1' for 'mysnmpcommunity'
com2sec mysecname1 default mysnmpcommunity
#(makes snmpv1 queries you mapped to 'mysecname1' part of 'mysecgroup1')
group mysecgroup1 v1 mysecname1
#(the same for snmpv2 queries)
group mysecgroup1 v2c mysecname1
#Defines a SNMP 'view' as the OID .1, and everything below it.
view myview1 included .1
#Gives 'mysecgroup1' access to see the things in the SNMP view 'myview1'
# but no write or notify access.
# group context model level prefix read-view write notify
access mysecgroup1 "" any noauth exact myview1 none none
# Note that many of the fields in the 'access' definition are SNMPv3-specific.
Now, you want to restrict access to a limited number of network addresses,
then
replace
com2sec mysecname1 default mysnmpcommunity
With
com2sec mysecname1 127.0.0.1/32 mysnmpcommunity
com2sec mysecname1 192.168.3.5/24 mysnmpcommunity2
com2sec mysecname1 172.36.15.3/22 mysnmpcommunity3
Add to your hearts content.
An alternative is to comment out all the snmpv3 lines
i.e.
instead of using 'com2sec' 'access' 'group' and 'view' statements,
the OLD way of configuring communities is to specify them like this in
snmpd.conf
rocommunity mycommunity1 127.0.0.1
rocommunity mycommunity1 192.168.5.3/32
rocommunity mycommunity2 192.168.5.4/32
rocommunity mycommunity3 172.44.0.8/23