On Jan 20, 2008 12:42 PM, Thomas Anders <[EMAIL PROTECTED]> wrote:
> My gut feeling would be to extend the existing engineIDType/engineID
> functionality to cover that, i.e. to introduce a new engine ID type 4
> (raw).
>
> Whatever way you prefer, please submit your final patch to
> http://www.ne
Nathan Schrenk wrote:
> Attached is a patch that handles a new "exactEngineID" command in
> snmpd.conf. Is this something that the maintainers of NET-SNMP think is
> useful? If so, do you have any suggestions for changes, and would you
> consider adding this to a future NET-SNMP release?
My gut
On Jan 18, 2008 3:45 PM, Dave Shield <[EMAIL PROTECTED]> wrote:
> On 18/01/2008, Nathan Schrenk <[EMAIL PROTECTED]> wrote:
> >there is no way to
> > specify the engineID exactly. I'd like to be able to configure the
> engineID
> > using a command that just takes th
On 18/01/2008, Nathan Schrenk <[EMAIL PROTECTED]> wrote:
>there is no way to
> specify the engineID exactly. I'd like to be able to configure the engineID
> using a command that just takes the hex-encoded raw engineID, similar to the
> oldEngineID command.
Maybe I'
Hi,
I'm working on a project to include an SNMP agent based on NET-SNMP's snmpd
in an ethernet switch. The switch's command-line interface provides the
ability to specify the SNMP agent's engineID. This is somewhat problematic
with NET-SNMP (at least as of version 5.4.1) because there is no way
