On 01/02/07, Clement Hsu <[EMAIL PROTECTED]> wrote:
> I saw the structure of the snmp_session has a declaration of
> netsnmp_callback.
That's part of the standard process of processing an incoming PDU.
It's not really part of the public API. It's certainly not relevant to your
main requirement.
On Thu, Feb 01, 2007 at 09:17:55AM +, Dave Shield wrote:
> > When do we need to set engineID?
>
> I've no idea. Wes is the security expert, not me :-)
RFC 3411 contains the definition of the SnmpEngineID textual
convention which explains the various formats. In a nutshell, an
SnmpEngineID v
[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
On 31/0
On 31/01/07, redhouse101 <[EMAIL PROTECTED]> wrote:
> When do we need to set engineID?
I've no idea. Wes is the security expert, not me :-)
In general, unless you *know* that you need to set the engineID
explicitly, then you probably don't (and shouldn't bother).
>I
Thank you very much, Dave!
When do we need to set engineID? In man page, it states that we can set
"engineID STRING" in snmpd.conf. Which snmpd.conf, persistent one or regular
one?
RH
On 1/31/07, Dave Shield <[EMAIL PROTECTED]> wrote:
DS> The engine ID is normally set automatically when the ag
