I have a problem instaling the MK 3.4 on RB 133, the system comes unstable an the board reset constantly, the system resources show me the processor in 100% all the time. Anyone have the solution for this case?
why not use 3.6, and if the problem repeats - send the supout.rif file to support. we will see what’s wrong there
My opinion is that the rb133 are slow for the v3. Use 2.9.x on this boards or turn off everything what you don’t need (connection tracking, not needed packages) and try it.
that’s not true. we have many RB1xx deployed on v3 and they work perfectly.
I have some which works but there is many which not. And I think that you can only say that v3 works well with rb1xx if it works on every board.
I used the rb133 only for wireless to ethernet bridge. No routing, no connection tracking, no firewall rules and only 3-4Mb traffic went through. And I couldn’t log in, the cpu always 100%, sometimes reboot. This works fine with 2.9.51. So I think it don’t work.
I have this trouble not only one router. And what about the rb153? There is the possibility to use more interface, but how if it’s slow?
everything depends on configuration and optimization
Normis, i had try 3.6 on RB133C used as wireless bridge station wds. Working fine at first but, when i add a bridge srcnat rules: chain=srcnat out-interface=wlan1 action=src-nat to-src-mac-address=mac of the wireless card, the RB keeps rebooting until i dissassociate it from the AP side. It worked fine with 3.4, any idea,
Michael Plourde
Digicom Technologies
nope. we would need to reproduce this. please send more info to support and we’ll see
I have RB133 with 3.6 and it’s working very well.