I have a problem querying routerboards with SNMP when there are multiple paths to it. the Dude always shows services down when they are not because snmp is replying using the ip / interface it leaves on. Mikrotik - please allow SNMP to be bound to a specific address!



There are literally 5 paths to get to this router. If the dude happens to request snmp probes on the nearest IP address it will work, otherwise the other 4 paths do not reply with the correct source ip and the response is ignored. And then dude shows outages.

I cannot run conntrack on this router and use nat ... too many async routes and overhead. Is there any other way around this besides rearranging the order of ips in the dude every time a path changes?

4 years later: This is still an unsolved problem...

There is one key fact they don't tell you.

I had asymetrical routing to my routers and snmp failed !

the outbound packet goes out the interface it came in on. it doesn't follow the routing table, if was to solve some other problem I am not sure what but..

I suggest (to support) that they need to comment that in the notes otherwise people like you and i will run into these issues.


Interestingly i snmpquery a bridge ( loopback) ip address...

I have now moved to the ip address of the closest interface (I have to know one )

A

Set a routing mark in mangle output src port 161 have that routing table point back to your app. It sucks but it works. Only seems to happen with multiple routing tables.