Torch not detecting ICMP traffic

RouterOS General
1

Folks,
I’ve noticed with 2.9.17 and 2.9.18 that the Torch tool doesn’t seem to detect/show any ICMP traffic. I’ve set up some pinging tests through a chain of routers and my 2.9.x Torch tools don’t see the traffic but a 2.8.28 router I have in the chain sees it just fine.

2

what configuration you are using for torch ?
I’ve no problems with my 2.9.18 torch.

3

I’m selecting one of any of the interfaces, checking all the boxes in the Collect options, no ip filters and any port and for protocol either any or 1(icmp).
If I have any protocol selected, and I sort on the protocol column, no icmp ever shows up.
If I filter on icmp protocol, I never see any traffic, regardless of interface selected.
I’ve never had this problem on 2.8.28 or other earlier versions.

4

this works without problem,
tool torch ether1 protocol=any [any other additional settings];
ICMP is shown in traffic.

5

Well then, I need to find out what’s up with mine. Or what can block the traffic from torch being able to see it. Recall earlier I stated I had a 2.8.28 that showed icmp traffic just fine in torch. Last night I upgraded that router to 2.9.18. Guess what? I no longer see icmp traffic in torch. Not one line.
I’ve just went through and disabled most of the firewall filters that I can to see if it’s that is what’s blocking it but to no avail.
I don’t dispute it works for you, but I assure you it’s not working for me.
That leads me to think that it is either my setup that is different/wrong or there is something in the upgrade process that happens.

6

Completely unrelated to torch, but we stumbeled upon another problem with systems upgraded from 2.8 to 2.9 yesterday (wireless encryption not working). Re-Installing the same system from scratch directly to 2.9 solved the problem. A simple “system reset” did NOT help.

So perhaps it really is a bug in the upgrade process. If possible, could you do a re-install on one of the systems in order to get some more hints where the problem could be?

Best regards,
Christian Meis

7

It’s the same for me. No ICMP traffic in Torch. This box was also an upgrade from 2.8.28.

Regards

Andrew

8

Me too, no ICMP in torch on 2.9.x upgraded or not, routerboard or PC

9

Ouch, two of the routers I can’t really touch during the day, so reinstalling
is not likely to happen. But the third router is a brand new box purchased with the os. It arrived with 2.9.14 on it but I can’t verify the problem existed in that version. I first noticed it on that box which at that time had 2.9.17.
I upgraded to 2.9.18 but to no avail.
I can say this box in all likelyhood has never had a version prior to 2.9 on it.

10

Just tried on a customers’ machine with 2.9.18 on it:

Can perfectly see ICMP traffic in torch by doing

/tool torch ether1_public protocol=icmp

Best regards,
Christian Meis

11

Works here: (on 2.9.18)

PRO.. TX RX TX-PACKETS RX-PACKETS
icmp 480bps 480bps 1 1

PRO.. TX RX TX-PACKETS RX-PACKETS
icmp 928bps 928bps 2 2

PRO.. TX RX TX-PACKETS RX-PACKETS
icmp 480bps 480bps 1 1

PRO.. TX RX TX-PACKETS RX-PACKETS

I’m starting to wonder if the upgrades are causing corrupted configs somehow too… (not that configuration is stored for torch though) for the life of me I can’t get BGP to function correctly in > 2.9.8 but everyone else states its working fine. I’m going to reload this one from scratch to see if that helps.

Just out of curiousity - we had a similiar issue with packet sniffer, it would find ICMP from anyone and not just the filtered range… and sometimes it wouldn’t show any. So many if torch has too many ‘limiters’ it will drop icmp all together?

12

This is getting stranger.

I was using WinBox previously so I tried it from the command line. Works OK.

Fired up Winbox - it’s working now !!!

The difference is, I’m now checking on the Internal interface and not the external but firewall rules aren’t the problem because I was getting ping replies before, just nothing in Torch. Just checked the external interface again and it’s working there as well.

Regards

Andrew

13

Looks like this is a Winbox problem as it’s stopped working again. CLI is still OK though.

Regards

Andrew

14

I had never tried torch from the command line. It definitely appears to be a winbox problem. I opened a new terminal in winbox, issued the torch interface protocol=icmp command and it works fine. While that was running, I opened the gui torch on the same interface, same protocol and saw no traffic.

Thanks guys! Now I know mikrotik has a problem.
And to think I was safe to wait 15 or so releases into a major version upgrade…

15

You probably we’re safe, this didn’t cause any downtime right? I think this is a minor annoyance and will be fixed now that its known. Although, if you don’t bother to report it to support@ it will probably never get fixed.

Sam

16

Could you give more details, when torch doesn’t work ?

I’ve tried both Winbox and console, ICMP traffic are shown:
Ping to x.x.x.x, when x.x.x.x is address assigned to interface=ether1,

  1. Winbox torch configuration, ‘/’ placed on ‘src-address’, ‘dst-address’ and ‘protocol’;
    src,address=0.0.0.0/0
    dst-address=0.0.0.0/0
    Protocol=any
    Interface=ether1
    Entry timeout=00:00:03

  2. Console configuration,
    tool torch ether1 protocol=any

17

In Winbox if you check “Port” then you will not see ICMP even though port is “any”. This is different to 2.8 which allows you to tick the port option.

So now I am seeing ICMP :slight_smile: annoying though as sometimes it is nice to torch everything at the same time.