More and more and more 2.9 problems

RouterOS Wireless Networking
1

Pretty damning evidence against yet another firmware release if you are running MT wireless on anything beyond v2.9rc9…

They say a picture (or two) is worth a thousand words:

v2.9rc9
http://www.belwave.com/NStreme2_v2p9rc9_FDX_Test_9-20-05.jpg

v2.9.4 on the same RB532 gear only a couple minutes later
http://www.belwave.com/NStreme2_v2p9p4_FDX_Test_9-20-05.jpg

Only thing the v2.9.4 picture doesn’t show is the fact the max sustained throughput before the units crashed was 16Mbps.

So, not only is v2.9.4 no more stable than every release after and including v2.9rc10 it has twice the latency on a fully loaded circuit and less throughput.

Thank goodness for v2.9rc9!

Best,

Brad

2

Ok here ya go…

http://www.belwave.com/NStreme2_v2p9rc9_FDX_Test_From_RM1_to_RM2_at_24MB_Rate_9-20-05.jpg

http://www.belwave.com/NStreme2_v2p9p4_FDX_Test_From_RM1_to_RM2_at_24MB_Rate_Crash_9-20-05.jpg


Not only did v2.9rc9 outperform v2.9.4 by about 2MB it also did not crash like v2.9.4. Again latency was better with v2.9rc9 as well…

36MB Rate on v2.9.4 crashed so quickly I didn’t even bother taking a snapshot.

36MB Rate on v2.9rc9 did not crash, but the results were much poorer than the 18MB or 24MB rates.

BTW, rssi readings on all tests run are solid -60.

Setup:

192.168.1.70 RM Test Unit 1 3.0GHz
Ethernet

192.168.14.100 RB532 NStreme2
Wireless
192.168.14.101 RB532 NStreme2

Ethernet
192.168.1.71 RM Test Unit 2 3.0GHz


Best,

Brad

3

after the crash, please send some supout.rif files to support. we are fixing all the issues, we just need the files to see what to fix.

4

Hello Normis,

I do not believe the routers are creating any supout files. The RB532s are still accesible via their local ethernet ports after the “crash”. The NStreme2 interface just stops passing data. Simply disabling and re-enabling the NStreme2 interface will allow traffic to pass again. This may be a dumb question, but is there a way I can still get a supout file?

Many thanks,

Brad

5

/system sup-out

6

… or press the “make supout” button in winbox.