Problems with 2.9.37 and RB 153

Hi! I’veupdated a RB153 with last routerOS (2.9.37). After update and after reboot all eth ports have stopped work. the only alive port is serial port. I have reloaded a 2.9.29 release with netinstall and now work fine ( except frequently auto-reboot ). Anyone have same problem? I’ve tried to update RB153 hoping that it could resolve the problem of auto reboot.

Could you try to reproduce the same problem again ?
Generate support output file from the router, when RB153 does not function properly at 2.9.37 and send file to the support (support@mikrotik.com).

Hi Sergejs,

I’ve reproduced same situation and I have the same problem…eth ports dead (leds off). In Interface configuration (via serial console) the eth ports are on running mode. I’ve tried to disable and enable ports without results. I’ve generated supout file and now there is another problem… How I can save file out of RB if all eth ports are dead?

Hi Sergejs,

I have installed wlan card on router and I have success to connect with RB via wlan. Now I have supout file. I’m sending it to You just now. In driver list I’ve found the Atheros drivers only… and the eth drivers???

Can anyone verify with RB112 to see if it is also effected by this?

This version (the .37 posted today) works on the 112s. But the bridge port came up as unknown so check your settings on anything that references the ethernet port.

No. The RB112 is working fine with .37. (installed it on 19 boards last night)

I do have to say i’m in a 100% routed environment, so if it affects bridge mapping to ether port, I can’t say.

This sounds like the behavior I was seeing on the RB112 with the short lived .36 build of the software though.

For grins, try forcing manual duplex settings, that brought up the ether port on the RB112 after the .36 build.

Seeya,
Dave

http://www.fab-corp.com

2 out of 20 RB have problems with ethernet. Downgrading to 2.9.30 or 2.9.35

we have found the problem: Auto MDI/X feature does not work on RB100 series with this version. That’s why only the users that were using this feature has the problems. We will fix that in v2.9.38.