Hi Pushpa,
Yes, your results were expected. They use the same encryption algorithm
but are identified under either the Cisco or ESO enterprise OID. There is
probably no way of knowing in advance which one a particular piece of
equipment will use.
- Craig
On Tue, 21 Sept 2021 at 04:22, Pushp
Hi Craig,
Following are my observations. Please let me know if the behaviour is
correct.
--snmp agent 192.168.1.12---
I added two snmpv3 users
createUser pushaaes129 SHA mypassword AES192 mypassword
createUser pushaaes129c SHA mypassword AES192C myp
Hi Pushpa,
It's a matter of identifying it.
When the packet comes in, the receiver looks at the authentication protocol
and sees one value or the other. That's why you need to specify which
method you are using.
In theory, I expect that the receiver could just look at the auth protocol
and use t
Hi Craig Small,
Thank you . This is really helpful.
If AES192 and AES192C are AES standard from different entity then are they
interchangeable ?
Eg: I did configure AES192 on snmpd and use AES192C from mibbrowser. Tool
'snmpget' fails.
It would help me if I know why CFB-AES192 (on silvercreek
Hi Pushpa,
As you have discovered, there are two AES192 standards.
When you select AES192 (with no C) this is the IETF draft Blumenthal
standard.
When you select AES192C this is the Cisco "standard".
What is the actual difference? As far as I can tell, it comes down to the
OID used for some of
