Hi Dave, I modified the community name to "public1" in com2sec as you suggested, sent the snmpv2 request using "public1" and the request is forwarded by SNMPD to subagent. I could access the same "table1" registered by two subagents with two different contexts by sending different community names in snmpv2 request.
Thanks a lot for all your help. Regards, Suresh. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: Tuesday, January 08, 2008 10:32 PM To: Pamidipati Suresh-G20238 Cc: net-snmp-users@lists.sourceforge.net Subject: Re: SNMPD not responding when a context name is given in the request On 08/01/2008, Pamidipati Suresh-G20238 <[EMAIL PROTECTED]> wrote: > With the below configuration specified in snmpd.conf, I am able to > access the table1 using the context name in SNMPV3 requests. Good. > But when I > send snmpv2 request using community name "public", the request is not > reaching the subagent. > rwcommunity public > com2sec -Cn context1 user1 default public My best guess is that these are two separate access control settings, and the first (default context) is masking the second. Try changing this to com2sec -Cn context1 user1 default public1 and run the query using "-c public1" > rwuser user1 noAuthNoPriv .1.3.6.1 > createUser user1 MD5 user123 DES I'd also suggest that you use a *different* username in the "com2sec" line, from your rwuser/createUser settings. These are all completely separate access control settings - so re-using the same names will lead to confusion (at best), or a broken setup. > As mentioned in snmpd.conf man page, com2sec converts the community > name to security name in the given context. So here, as per my > understanding, the community name "public" shall be converted to > security/user name "user1" which is configured. It should do, yes. > I could not find what's the reason for SNMPD not forwarding the > request to subagent when snmpv2 request was given. Probably because you've got other access control stuff that's being used instead. Always try working with the smallest possible snmpd.conf file. Once you've got each individual bit working, you can look at stitching it all together. Dave ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
