https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2426
--- Comment #8 from Walter Benton <wbenton@xxxxxxxxxxxxxxxx> 2010-03-03 09:43:29 JST ---
Per RFC-3411, 3.1.1.1. snmpEngineID
Within an administrative domain, an snmpEngineID is the unique and
unambiguous identifier of an SNMP engine. Since there is a one-to-
one association between SNMP engines and SNMP entities, it also
uniquely and unambiguously identifies the SNMP entity within that
administrative domain. Note that it is possible for SNMP entities in
different administrative domains to have the same value for
snmpEngineID. Federation of administrative domains may necessitate
assignment of new values.
That said, considering two different entities within the same domain having
duplicate Engine ID's is entirely out of the scope in question and thus need
not even be considered.
Yes, per RFC-3411, a user should have only one password, and if you'll look at
the sample Cisco configuration I provided, you'll find a unique user name with
a unique user password for each combination of auth and priv!
On another note, this Bug was opened back in 2008 and I've completed all
required testing I was doing at the time and thus haven't paid much attention
to this until you replied recently, but using WireShark Version 1.2.6 (SVN Rev
31702), the problem seems to have been resolved as the entire list is now
possible to be imported. The version I was using back then would only retain
either the first or last user entry only with the same engine ID.
Thus the Status: Resolved is correct as the problem has been fixed.
P.S. Cisco WILL allow the configurations I attached. The ONLY thing I changed
was the actual EngineID itself from the Cisco specified EngineID to the
11111111 - 66666666 which I included.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.