Community discussions

MikroTik App
 
v3gard
just joined
Topic Author
Posts: 2
Joined: Sat May 24, 2014 9:09 am

SNMP traffic not detected in firewall

Sat May 24, 2014 9:25 am

I struggle getting SNMP to work on my WAN interface (that is from the Internet and towards my Mikrotik Routerboard that acts as both a router and firewall on my home network. If I run
/ip firewall filter print
, I get the following output (non-relevant rules are removed):
 0   chain=input action=accept protocol=udp dst-port=161-162 
Also, to ensure that SNMP is activated, I run this command
/snmp community print
that returns:
Flags: * - default 
 #   NAME     ADDRESSES                                          SECURITY   READ-ACCESS
 0 * public   0.0.0.0/0                                          none       yes
When I try to test the connection, by running
snmpwalk -v1 -c public <public ip address to home network>
there is no response - but even stranger, the firewall (if I look at the rules in WinBox) indicates that NO packets are detected on the rule I created!

I suspect that my ISP could be blocking UDP/161 from the internet and towards my home network, but to my knowledge I cannot verify this unless I disconnect the Mikrotik router and connect the WAN port to my computer to remove the ISP from the equation. Is there another way I can troubleshoot this?
 
User avatar
scotthammersley
Member Candidate
Member Candidate
Posts: 230
Joined: Fri Feb 22, 2013 7:16 pm
Location: Jackson, MS
Contact:

Re: SNMP traffic not detected in firewall

Fri May 30, 2014 6:42 pm

Yes, there is another to troubleshoot it. Create a VPN to the router and re-test. That will take the ISP out of the equation.
 
v3gard
just joined
Topic Author
Posts: 2
Joined: Sat May 24, 2014 9:09 am

Re: SNMP traffic not detected in firewall

Mon Jun 02, 2014 11:45 pm

Hi, thanks for the reply.

That was a good idea, but I did not have to go for that option. I sent an email to my ISP and asked if UDP/161 was blocked, and they replied that it was because they had detected a security issue with the standard router they sent out to their customers. Once I explained to them that I did not use the standard router, but a Routerboard, they opened the port.

Who is online

Users browsing this forum: eltrocadero2, sindy and 82 guests