Re: Source Address based Configuration Control in SNMP Agent

2018-12-18 Thread prabu varadharajan
Thanks for the response, Wes. But as per the design, my agent will be configured with only one user which can be updated as rouser or rwuser. So can you please suggest any other way to achieve this if possible? On Mon, Dec 17, 2018 at 11:01 PM Wes Hardaker < harda...@users.sourceforge.net> wrote:

Re: Source Address based Configuration Control in SNMP Agent

2018-12-18 Thread Wes Hardaker via Net-snmp-coders
prabu varadharajan writes: > But as per the design, my agent will be configured with only one user > which can be updated as rouser or rwuser. So can you please suggest > any other way to achieve this if possible? You can't have a single user with different access levels, sorry. There are hacky

Re: Source Address based Configuration Control in SNMP Agent

2018-12-18 Thread prabu varadharajan
Thanks for the input Wes. I'll check it out how the v3 proxy may help in my case. Or can we consider the security aspects of SNMPv3 and proceed without any source address filtering whereas we can have the same filter for SNMPv1 and SNMPv2c only? In this case, I can make sure the User credentials

RE: EXTERNAL: Re: 5.7.3 | snmptrap not populating EngineBoots or EngineTime for snmp v3 traps

2018-12-18 Thread Roedersheimer, Drew A. via Net-snmp-coders
Denis Hainsworth wrote: > #2899 - snmptrap bug > #2900 - snmptrapd bug > > -denis Denis, Sorry for the delayed response. I haven't had time to look at this until recently. Regarding the snmptrapd bug you created (#2900): I think this is working as expected. I compiled and tested v5.7.3 from