RS ... [turn on packet dump and] you should be able to
RS see if a packet goes out, if the agent receives it,
RS if the agent sends a response and if the app receives it.
CN Sending 93 bytes to UDP: [127.0.0.1]:161
CN : 30 5B 02 01 01 04 00 A0 54 02 04 77 0B 12 D2 02
RS Note that
...
More particularly, the dump begins:
30 5B // request sequence
02 01 01// version = SNMPv2c
04 00 // community =
A0 54 // GET PDU
etc
So the request is being sent with an empty community string
(hence it's not suprising that the agent is
...
So, snmp_open() appears to not be copying the community string.
How come? I'll look into it a bit shortly.
I think I found the problem. Around line 998 of snmplib/snmp_api.c, there is a recent
addition of:
#if !defined(DISABLE_SNMPV1) || !defined(DISABLE_SNMPV2C)
which DeMorgan
I think I found the problem. Around line 998 of snmplib/snmp_api.c,
there is a recent addition of:
#if !defined(DISABLE_SNMPV1) || !defined(DISABLE_SNMPV2C)
which DeMorgan tells us is really:
#if defined(DISABLE_SNMPV1) defined(DISABLE_SNMPV2C)
Err no.
Surely DeMorgan
On Wed, 27 Oct 2004 08:43:10 -0400 [EMAIL PROTECTED] wrote:
CRC#if !defined(DISABLE_SNMPV1) || !defined(DISABLE_SNMPV2C)
CRC
CRC which DeMorgan tells us is really:
CRC
CRC#if defined(DISABLE_SNMPV1) defined(DISABLE_SNMPV2C)
CRC
CRC and if I read the code around it properly, this says
I think I found the problem. Around line 998 of snmplib/snmp_api.c,
there is a recent addition of:
#if !defined(DISABLE_SNMPV1) || !defined(DISABLE_SNMPV2C)
which DeMorgan tells us is really:
#if defined(DISABLE_SNMPV1) defined(DISABLE_SNMPV2C)
Err no.
Surely
I can use snmpget on another system to read, for example,
system.sysDescr.0 but on-node, when I try to use the config
community to get values, snmp_get() times out.
What if you try with snmpget on that same node (not from a remote system)?
If you run essentially the same command locally:
I can use snmpget on another system to read, for example,
system.sysDescr.0 but on-node, when I try to use the config
community to get values, snmp_get() times out.
What if you try with snmpget on that same node (not from a remote
system)?If you run essentially the same command
On Tue, 26 Oct 2004 08:15:44 -0400 [EMAIL PROTECTED] wrote:
CRC The local system is an embedded system with few resources.
Does it have dns services? eg, can it look up localhost to get 127.0.0.1? Try
putting the actual IP address in the com2sec line, instead of localhost.
--
Robert Story;
On Tue, 26 Oct 2004 10:40:38 -0400 [EMAIL PROTECTED] wrote:
CRC Since snmp_synch_response() is giving me a timeout, I'm guessing that it's
CRC something about my connection setup that's broken: that I'm not finding
CRC the agent or the timeout is too short for the agent to respond or... Does
CRC
... you should be able to
see if a packet goes out, if the agent receives it, if the agent sends a
response and if the app receives it.
Thanks.
My client logs:
Sending 93 bytes to UDP: [127.0.0.1]:161
: 30 5B 02 01 01 04 00 A0 54 02 04 77 0B 12 D2 020[..T..w
0016: 01 00
Well, I've come full circle. I think I've confirmed that I have an authorization
problem.
- snmpget on the local host times out just as my client application does
- When the client times out, there's a note in the log that it tried (and failed, but
that's another issue) to send an
On Tue, 26 Oct 2004 12:07:10 -0400 [EMAIL PROTECTED] wrote:
CRC ... you should be able to
CRC see if a packet goes out, if the agent receives it, if the agent sends a
CRC response and if the app receives it.
CRC
CRC Thanks.
CRC My client logs:
CRC
CRC
CRC Sending 93 bytes to UDP:
I'm trying to see if Bug 1016849
(https://sourceforge.net/tracker/?func=detailatid=112694aid=1016849group_id=12694)
is still in 5.2. I've installed 45.2.rc1 and I'm having unrelated problems which are
preventing me from validating the bug.
My /usr/share/snmp/snmpd.conf (which works with
14 matches
Mail list logo
