Hi,
if I try to get a SNMP table from one of our printers, scli hangs forever.
Here is what happens on the network:
scli-host -> printer PDU GET-NEXT (24 objects) printer -> scli-host PDU RESPONSE (Error: TOOBIG)
Here is the debug output from libsnmp:
g_async_send for ipi New request: 99b38 sending Pdu for ipi, version 0 Sending packet on IPv4, 416 bytes [ Dump of paket ] SNMP Timeout called Received packet on IPv4, 417 bytes [ Dump of paket ] Calling done callback for request: 99b38 SNMP Timeout called SNMP Timeout called SNMP Timeout called SNMP Timeout called SNMP Timeout called SNMP Timeout called SNMP Timeout called SNMP Timeout called [... and so on ...]
I would expect a smaller sized retransmit but couldn't find it anywhere. Is this a known problem?
Oliver -- !! This message is brought to you via the `stools' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to stools-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/stools/ for more information.
Oliver Wellnitz writes:
Oliver> if I try to get a SNMP table from one of our printers, scli Oliver> hangs forever.
Oliver> Here is what happens on the network:
Oliver> scli-host -> printer PDU GET-NEXT (24 objects) printer -> Oliver> scli-host PDU RESPONSE (Error: TOOBIG)
[...]
Oliver> I would expect a smaller sized retransmit but couldn't find it Oliver> anywhere. Is this a known problem?
Yes. There are actually two problems here. The first problem is that the code fails to signal the problem back to the application which causes scli to just hang. The second problem is of course the fact that the code is not smart enough to react to a tooBig error by changing the table retrieval strategy.
You are of course welcome to submit patches to fix one or all of these problems. :-)
/js
participants (2)
-
Juergen Schoenwaelder
-
Oliver Wellnitz