ROS 5.8 on rb4.xx problem!

RouterOS General
1

Today I planned to net-install several rb4xx’s I had on the shelf with bigger or smaller issues.

All boards came out a working environment with 5.6 running without issues, some boards never used before.

Netinstalled 5.8, dhcp, routerboard, wireless and system package.

After reboot and setting boot sequence back disconnected routers, connected to my normal PC and logged into winbox via mac (find mac address with little neigbour button in winbox loader)

All boards work fine, can see the interfaces, can open dhcp-cl window to put dhcp-client to ehter1.
First open terminal in winbox, upgraded firmware to 2.37, reboot the unit and log in again. No problem.
Usually set the dhcp-client only now, logoff and login with winbox to the unit… slower as usuall…

Look at the interfaces, no interfaces!
Look in terminal, is not starting up!
Look in the dhcp-cl window, no options available. (And if was set before, list is empty, even although the IP address comes up in the winbox-neighbour).
Look in address, empty!

After upgrading several rb411’s and rb433’s it looks to me that the issue only comes up after the firmware upgrade to 2.37


Over the last days also upgrades some 100 80 rb411’s and some 10 rb433’s (incl. AH’s) and they all work fine! (Although I had Ethernet ports flapping where it didn’t happen before… :frowning: )

So it only happens with units on my desk.
I used different cables, no difference.
All cards are without any wireless interfaces.

Can anybody repeat this? On this moment I can not configure any rb4xx boards any more for use! I have some 8 of these with the same issue!

(I also updated on my desk several rb7115Hn boards and they don’t have the issue. Same for some grooves and SXT’s.

Still investigating the matter, but maybe more readers find the same…

2

Boot one failing unit up while still connected by serial to terminal session. Terminal session shows nothing strange..
This board is only accessible by winbox via mac. I could set dhcp-cl in the terminal session and it shows its getting IP address.
After that winbox-neigbour sees the IP address but cannot log-in to it.
So logged in with winbox by mac and succeeded after a second. In winbox all menus with interfaces stay empty.

After some 5 to 10 minutes interfaces seem appear.
When the interfaces appeared I can also login by winbox/IP address. Although windows are taking a split second longer than normal I can open everything normally.

During all this I monitor the CPU usages and that always stays very low…

3

Ok, I have been playing with 2 rb433’s.
Both only are able to access by winbox if IP is set. Mac access is not possible so have to log in with terminal to start dhcp-client. After the unit has been given IP from server I can log in on that IP. But it takes a second.

Second unit I could log in by mac after 15 mins waiting! Only after such time interface came up and thus dhcp-cl could be set…

4

Have you checked your CPU frequency in /system routerboard settings print?

http://forum.mikrotik.com/t/corrupt-boot-loader-rb493g/51605/1

I’m making a wild guess that a CPU frequency of 100MHz could cause winbox responses to be slow enough to not populate your winbox client, but your SSH or serial terminal could appear to be working correctly.

5

Hi Rudy.

Last couple of days I’ve been around with netinstall X 433AH, UAH and 411AR.

Using mac access sometimes disconnects in the middle of some file transfer or without any other reason.

But as i netinstalled IPV6 package and I am using a EeePC 900 + Windows 7 … instead of use IPV4 MAC (IP=0.0.0.0 for a unconfigured unit) … I tried IPV6 address and works like a charm. Pix below is a 5.6 version I did not upgraded yet.

Regards;

6

Freq’s are fine in terminal. So we can exclude this…

7

Hi my friend,
Ok, so explain to me:
With netinstall you also install the IPV6 package… Does anything have to be enabled?
Then with a normal W7 (or XP) you open winbox and then what? Does the IPV6 address come up in neighbour? How do I go from here?

8

Hi Rudy:

Yes I installed IPV6 within Netinstall and that’s it. I’m using Windows 7.

As soon as I launched Winbox and click at the small box to scan for devices there was 2 lines (same eth mac on both).

One of them with IPV4 address = 0.0.0.0 as usual.

Another one with a IPV6 address just below.

The I just clicked at IPV6 address and got access to it.

I did not touch anything because was my first access after netinstal.

[Edited]This pix was taken some minutes ago from some units that’s already configured with IPV4 addresses trhu a switch at the bench. For a fresh install IPV4 = 0.0.0.0[/Edited]

Regards;