Rafael Garabato wrote:
I am not allowed to use a packet sniffer.
You might still be able to use the "-d" option to snmpd on the server
side to dump packets.
But just supposing that the
problem is the EngineID. How can I do to solve that problem?
Configure the same engineID on both sides by putting
engineID myuniquestring
(please adjust!) into your snmpd.conf. From the snmpd.conf(5) man page:
- --- snip ---
engineID STRING
The snmpd agent needs to be configured with a unique engineID to
be able to respond to SNMPv3 messages. With this configuration
file line, the engineID will be configured from STRING.
engineIDType 1|2|3
Defines that the engineID should be built from the IPv4 address
(1), IPv6 address (2) or MAC address (3). Beware that you might
run into trouble on IP address changes!
engineIDNic interface
Defines the interface (e.g. "eth1") that should be used to
determine the MAC address in case of "engineIDType 3". Default
is eth0.
If neither an engineID, engineIDType or engineIDNic directive is
present, the value of the engineID is built from 2 fairly random ele-
ments: a random number and the current time in seconds. This is the
recommended approach.
- --- snap ---
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
