I've only tested this on 5.20 and 5.22 so far, but from "some" hosts, I
get a non-response from ROS devices running (at least) these versions of
ROS.
It doesn't affect all hosts, but on the hosts it does affect, I
essentially get a timeout to SNMP queries.
Example attempting to do a walk on a 5.22 ROS device:
snmpwalk -Lo -v 1 -c <community> 10.13.100.24 system
Timeout: No Response from 10.13.100.24
Example attempting to do a walk on a 4.17 device:
snmpwalk -Lo -v 1 -c <community> 10.13.100.18 system
SNMPv2-MIB::sysDescr.0 = STRING: router
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.14988.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2037440000) 235
days, 19:33:20.00
SNMPv2-MIB::sysContact.0 = STRING: <contact>
SNMPv2-MIB::sysName.0 = STRING: <name>
SNMPv2-MIB::sysLocation.0 = STRING: <loc>
SNMPv2-MIB::sysServices.0 = INTEGER: 78
Curiously, when I attempt the same thing on the same two devices from a
different linux host, both queries work. Routing to both hosts is the
same (and checks out).
I've got an open topic on the mikrotik forum:
http://forum.mikrotik.com/viewtopic.php?f=2&t=68437
No responses; I suspect everyone is on holiday.
--
bp
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20121225/c8181395/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
