We recently discovered that snmp requests to a public IP on one of our servers stopped working.
We tested this on with different routers and different providers. But behind the MT the SNMP requests timed out.
With ‘torch’ on the Interfaces we see the SNMP answers returning but not passed through the NAT service.
This was also the case with the firewall ‘disabled’.
We remember that after a firmware update some months ago, we lost the snmp on the public server IP.
This server we can also reach with a private L2 address.
Now we need to monitor servers on a public IP, but bumped into the same problem!
Today we upgraded our router to the latest 6.32.1 release, but without any problem.
You aren’t really providing enough information for people to be able to really help here. A router routes, and so it doesn’t care if the traffic is SNMP, HTTP, or anything else, a packet is a packet. So it coule be a firewall rule you have, a NAT rule that you have, a routing rule that you have, or a mangle rule that you have. At the very least an export of /ip route and /ip firewall would be a good place to start.
