I've bricked several RB532s and a couple of 532As with the latest 6.33 - both with netinstall and by upgrading from 6.7.
Going to try downgrading them all to 5.26 using netinstall now.
What's the highest version of routeros 6.x that's known to work on RB532 (32mb RAM) with R52 wireless card?
Re: RB532 + routeros mipsle 6.33 = fail
Thanks @jarda - netinstall of 6.32.3 brought those dead routers back.
Re: RB532 + routeros mipsle 6.33 = fail
i have tested and worked ok for me with rb532 this version all_packages-mipsle-6.33.2 ...
Re: RB532 + routeros mipsle 6.33 = fail
i have installed 6.32.2 and work ok
-
-
ALDISBEHMANIS
just joined
- Posts: 16
- Joined:
Re: RB532 + routeros mipsle 6.33 = fail
I confirm!
Same problem here.
Updated 6.33 ->6.33.3 = CRASH! Does not come back from reboot. Had to power down and power UP.
Did clean reinstall from 5.21->6.32.x->6.33.3
Making export compact file=xxx complains about upnp config backup.
Probably problem is with this stuff somewhere.
upnp is one of fixes for 6.33.3
Same problem here.
Updated 6.33 ->6.33.3 = CRASH! Does not come back from reboot. Had to power down and power UP.
Did clean reinstall from 5.21->6.32.x->6.33.3
Making export compact file=xxx complains about upnp config backup.
Probably problem is with this stuff somewhere.
upnp is one of fixes for 6.33.3
Re: RB532 + routeros mipsle 6.33 = fail
MIkroTik support is working on this problem, we recommend to keep using v6.32.3 (bugfix) until it is fixed in v6.33.x
Re: RB532 + routeros mipsle 6.33 = fail
I can confirm this bug. RB532 dont work with 6.33.3. After downgrade to 6.32.2 works well
Re: RB532 + routeros mipsle 6.33 = fail
It is more then 14days old bug.MIkroTik support is working on this problem, we recommend to keep using v6.32.3 (bugfix) until it is fixed in v6.33.x
And 6.33.3 is for mipsle still on download page without any warning !! Why you don´t write warning for MIPSLE?
When released 6.33.4 with fix?
Thanks
Re: RB532 + routeros mipsle 6.33 = fail
did or do you use UPnP anyway; e.g. do you have it activated?I confirm!
Same problem here.
Updated 6.33 ->6.33.3 = CRASH! Does not come back from reboot. Had to power down and power UP.
Did clean reinstall from 5.21->6.32.x->6.33.3
Making export compact file=xxx complains about upnp config backup.
Probably problem is with this stuff somewhere.
upnp is one of fixes for 6.33.3
Re: RB532 + routeros mipsle 6.33 = fail
how many years ago do you have that rb532??
Re: RB532 + routeros mipsle 6.33 = fail
here are some observations of 6.33.3 on RB532a. my own 50cents donation 
very simple configuration here, eth1 goes to internet gateway, rest if's bridged , constituting local network . srcnat between them. wifi wmia-123ag(r) configured , however not used
as others mentioned before: system finishes booting maybe 3 times out of 10 power cycles, however if it goes properly then stopping of terminal communication might happen (from under winbox); didn't notice that with serial console yet.
i have experienced total hangs of whole system. sometimes just after rebooting, sometime after few hours
i use DNS service from localnetwork, with about 200 static definitions - mainly for blocking internet advertisements.
after some uptime, seems it is really random, situations happened where DNS service probably got hanged or crashed , and hostname resolutions became unavailable. i've noticed that winbox showed no previously defined static definitions then, and cached list was also empty. and also "servers" , "Dynamic servers" and "allow remote req" checkbox showed as service was totaly deconfigured
i wasn't able to login with winbox from time to time. before repowering all hardware
and finally pretty interesting observation i made - believe it's helpful. board has RTC set up by hand, i don't use SNTP
noticed that with 6.33.3 real time clock slows down ! quite much. didn't do precise estimation, but remember it drifts down a few hours per day.
maybe 6.33.x included some specific bug correlated with MIPS platform? some internal CPU timers, clock dividers are setup inappropriately. or any other evil thing was silently introduced with MIPS specific kernel hacks... i don't know.....
please, give any feedback if last info was useful for removing bug
right now downgraded to 6.32.3 and after 2 days uptime it works fine.
/edit: i forgot one thing yet, winbox dashboard likes to show 100% load when system becomes broken
very simple configuration here, eth1 goes to internet gateway, rest if's bridged , constituting local network . srcnat between them. wifi wmia-123ag(r) configured , however not used
as others mentioned before: system finishes booting maybe 3 times out of 10 power cycles, however if it goes properly then stopping of terminal communication might happen (from under winbox); didn't notice that with serial console yet.
i have experienced total hangs of whole system. sometimes just after rebooting, sometime after few hours
i use DNS service from localnetwork, with about 200 static definitions - mainly for blocking internet advertisements.
after some uptime, seems it is really random, situations happened where DNS service probably got hanged or crashed , and hostname resolutions became unavailable. i've noticed that winbox showed no previously defined static definitions then, and cached list was also empty. and also "servers" , "Dynamic servers" and "allow remote req" checkbox showed as service was totaly deconfigured
i wasn't able to login with winbox from time to time. before repowering all hardware
and finally pretty interesting observation i made - believe it's helpful. board has RTC set up by hand, i don't use SNTP
noticed that with 6.33.3 real time clock slows down ! quite much. didn't do precise estimation, but remember it drifts down a few hours per day.
maybe 6.33.x included some specific bug correlated with MIPS platform? some internal CPU timers, clock dividers are setup inappropriately. or any other evil thing was silently introduced with MIPS specific kernel hacks... i don't know.....
please, give any feedback if last info was useful for removing bug
right now downgraded to 6.32.3 and after 2 days uptime it works fine.
/edit: i forgot one thing yet, winbox dashboard likes to show 100% load when system becomes broken
Re:
What's wrong with age of 532s? They are great devices regardless of their age.
nothing wrong only curious about the longevity of a routerboard device like that
Re: RB532 + routeros mipsle 6.33 = fail
What's new in 6.33.5 (2015-Dec-28 09:13):
*) mipsle - architecture support dropped (last fully supported version 6.32.3);
*) mipsle - architecture support dropped (last fully supported version 6.32.3);
Re: RB532 + routeros mipsle 6.33 = fail
It is end for MIPSLE. But why is missing this warning?What's new in 6.33.5 (2015-Dec-28 09:13):
*) mipsle - architecture support dropped (last fully supported version 6.32.3);
RB111, RB112, RB133C, RB150 devices are not supported in v6, please use v5.
-
-
TomjNorthIdaho
Forum Guru
- Posts: 1546
- Joined:
- Location: North Idaho
- Contact:
Re: RB532 + routeros mipsle 6.33 = fail
I never noticed this topic:
I have a bunch of mipsle (Crossroads and RB500) boards.
I was not aware until very recently that the support for these products came to a grinding halt.
I have some of my mipsle based boards running 6.33.5 using the Mikrotik NV2 protocol and have never had any problems - except one of my 5xx boards needs to be remotely power cycled via my PDU sometimes if I software-reboot it.
My mibsle 6.33.5 boards are all in a production environment and work just fine - the only issue I have had is there is no longer any newer firmware support.
I even have a Crossroads with 6.33.5 using superchannel and with NV2 making a 15k connection.
North Idaho Tom Jones
I have a bunch of mipsle (Crossroads and RB500) boards.
I was not aware until very recently that the support for these products came to a grinding halt.
I have some of my mipsle based boards running 6.33.5 using the Mikrotik NV2 protocol and have never had any problems - except one of my 5xx boards needs to be remotely power cycled via my PDU sometimes if I software-reboot it.
My mibsle 6.33.5 boards are all in a production environment and work just fine - the only issue I have had is there is no longer any newer firmware support.
I even have a Crossroads with 6.33.5 using superchannel and with NV2 making a 15k connection.
North Idaho Tom Jones