incomplete function of TORCH

shielder · September 10, 2006, 6:01pm

Hi, i am a fanatic mikrotik users but i found that torch command of mikrotik is somehow incomplete. I have a user that keeps flooding my network and i found that on mrtg,but when i use torch command from mikrotik i couldn’t detect the spamming traffic from the user. I could only see the traffic using iftop command from linux. and the icmp packet couldn’t be shown on “any” protocol environment.

Torch is better on 2.8 version, on 2.9 version it’s rathe incomplete. Has anyone ever feel about this?

GotNet · September 10, 2006, 9:50pm

Yep, commented about that in the past. Checking all boxes acts as sort of a filter instead of showing “all”.

Mike

advantz · September 10, 2006, 11:56pm

yeah torch cannot detect udp packet flood I guess.

shielder · September 11, 2006, 6:14am

So how is mikrotik technical going to change this feature? I think the torch feature in 2.8 is really good, why they changed it on 2.9?

normis · September 11, 2006, 7:46am

please write specifically what parameters did you set and what kind of traffic was not detected. we need specific report so we can test it.

Cha0s · September 16, 2006, 12:28pm

In my case, when I use Torch to monitor a VPN interface it doesn’t return any connection that is related to the vpn but irrelevant connections from other interfaces on the router.

I have all the boxes checked.
src/dst address is set to 0.0.0.0/0 and protocol and port is set to ANY.

I’m not sure about this but i think this problem came up on 2.9.27 and later.

Any ideas?

GotNet · September 16, 2006, 11:35pm

http://forum.mikrotik.com//viewtopic.php?t=8970&highlight=

It was in a changelog. NOT! Spent good time finding “missing” traffic.

Cha0s · September 17, 2006, 7:47am

I guess it works but not fully.

For one VPN on my router the torch utility shows connections that don’t even exist on the interface tha vpn works on.

On another VPN connection thoudgh without the ANY parameter on the protocol field it shows the connections as expected.

I don’t recall though in 2.8.x this issue.
It worked just fine with any parameteres.

shielder · September 17, 2006, 9:48am

Seems like everyone are annoyed with torch function in 2.9 so isn’t it better to goes back to torch function just like 2.8? How is that mikrotik developer?