hello friends, I come here to warn you that the version 5rc1 torch has a bug in the part that shows the TX is always at 0, since the RX ta working ok ...

works fine for me:



show us yours, make a screenshot and post here

Normis, yes it works on base installation (installed on VMware) but not on production router.

Kamil

Image from picture is on "production router" so it works for me post screenshots of your problem

Uploaded with ImageShack.us

my router is x86.... bug continua... v5rc1 bug torch x86, v5b6 not bug torch work fine...

TOTALLY UPD: yes, I can confirm such behaviour on x86. RBs don't repeat that =)

TOTALLY UPD: yes, I can confirm such behaviour on x86. RBs don't repeat that =)

It shows your CPU usage is %100
maybe it is the causes
plz retry after reboot

could be related to multicore on x86. we are investigating.

It shows your CPU usage is %100
maybe it is the causes
plz retry after reboot

That is not a problem. The time when I made screenshot, through router was going heavy ipsec (15Mbps) traffic :)

Kamil

@ayufan

through router was going heavy ipsec (15Mbps) traffic

I'm suprised, your screenshot shows RB750.
What is your IPSec and Ethernet ports config?

Regards, Grzegorz.

I'm suprised, your screenshot shows RB750.
What is your IPSec and Ethernet ports config?

md5, des.

What kind of throughput are you getting with 3DES and AES? Just curious how the different algorithms fare on that platform, and whether 3DES is more or less one third throughput and how AES compares to that.

md5,null - 20Mbps
md5,des - 12.5Mbps
md5,3des - 6Mbps
md5,aes-128 - 15Mbps
md5,aes-192 - 14Mbps
md5,aes-256 - 13Mbps
sha1,null - 2.5Mbps
sha1,des - 2Mbps
sha1,3des - 1.5Mbps
sha1,aes-128 - 2Mbps
sha1,aes-192 - 2Mbps
sha1,aes-256 - 2Mbps
null,null - not working
null,des - 13Mbps
null,3ds - 5Mbps
null,aes-128 - 18Mbps
null,aes-192 - 16Mbps
null,aes-256 - 14.5Mbps

all traffic were comming to RB750 from x86 machine

Wow, thanks for that. I didn't expect sha1 vs md5 to make such a huge difference. sha1 is generally slower, but not by a factor of 5. Running checksums on 50MB test file with random data with OpenSSL (so disk IO routines etc are probably the same) have sha1 about 50% slower. Not that that's a particularly scientific test, but still.

Thanks a lot !!!
Karma up !!!

Regards, Grzegorz.

I have another problem

I confirm I saw this on 5.0b6 as well the tx rx on x86 wit 82576 controller. Same problem with rc1 it shows actual traffic in torch for multiple ip addresses so this is some kind of the bug. Its good to see other people also experiencing this. Using dell r200

I can confirm the multiple IP traffic torch bug. And can reproduce it easy. Was hoping it would be fixed in rc1

Wow, thanks for that. I didn't expect sha1 vs md5 to make such a huge difference. sha1 is generally slower, but not by a factor of 5. Running checksums on 50MB test file with random data with OpenSSL (so disk IO routines etc are probably the same) have sha1 about 50% slower. Not that that's a particularly scientific test, but still.

From my exp sha1 is generally 50% slower than md5, so I don't really know why it capped at 2Mbps. I have other x86 based router and sha1/3des is 50% slower than md5/des. Also I will later test it on RB450G and post results.

I have another problem

i have that same problem, but with beta 4

we are looking into the problem thank you all for reporting it.

Any fix for this when should we expect the next release? Having trouble monitoring traffic in realtime without torch

I have same issue as Inox, pleas see my screenshot, i post topic aprox 2 weeks but no reply

we have fixed this in RC2

i can confirm that rc2 torch is working!! on x86

gustkiller, where You get rc2 ?

it is a pre-release i received to test the HP Smartarray SCSI/SAS driver. Then I downgraded to rc1 because some problems with ospf.

.... Then I downgraded to rc1 because some problems with ospf.

Did you report about ospf bug? Because i'm intrested to use RC2 with ospf ...

sure!!

.... Then I downgraded to rc1 because some problems with ospf.

Did you report about ospf bug? Because i'm intrested to use RC2 with ospf ...

Just checked all my x86 RouterOS machines, and Torch works in all cases, in all machines running v5x...

IMHO, sometimes no tx traffic is telling you something other than Torch not working. If you are getting hit hard by intruders, it would possibly show a lot of rx for many IPs, but those IPs are properly not responding to the bogus or intruder attempts. Just a thought...

just wait

Sorry for flame ...
But Just gimme something new to test ...

I also have the same issue as InoX and I would love to get my hands on the fix

One thing that bothers me too is that the ports & protocols aren't listed by default any more like they used to in v3 & v4.