ETA on Beta3?

Mikrotik Staff do you have an ETA on the Beta3?
1-3weeks? :slight_smile:

Many fundamental changes (kernel upgrade) so it will take a few more days. Probably next week.

Hi Normis,

Sounds promising :slight_smile: looking forward to it.
Keep up the good work!

6.0beta3 RB433UAH 30min CPU ? … winbox 2-43%CPU

RB133 5.17rc1 OK
RB433UAH_6.0beta3.jpg

Translation: We’re too busy playing Diablo 3. Check again after we hit level 60 and finish inferno mode. :smiling_imp:

j/k … I’m sure they’re hard at work putting in lots of awesomeness into this and it takes a while sometimes to make it work good.

Any news Normis on beta3? :slight_smile:

it will take a while. So no ETA.

Some hints on whats to come in beta3? :slight_smile:

this is the major change which takes a while:

*) upgraded drivers and kernel (to linux-3.3.5);

Okay no new features ? :slight_smile:

what about new routing?..

If it is not released, then there must be multiple versions of 6.0beta3 because I saw a link for it a week or so ago, and so I downloaded it and I’ve been using it already.

Look around, the link for it may still be active.
routeros_6b3.jpg

Just like any version, we make many builds before releasing to public.

Is there a Beta of the beta3? :slight_smile:
And if so where can I get it to try? I have an RB800…

6.0beta3 (16.05. 2012) load CPU winbox (www statistics OK)
6.0beta3 (04.06. 2012) load CPU RB433UAH statistics tools/profile/www -80% problems with displaying charts … [load CPU Winbox => OK corrected?]

Normis, 6.0beta3 from date 4.6.2012 is based on new kernel? Thanks

6.0beta3 = Linux Kernel 3.3.5

Here’s a bug with b3:

Sometimes, after awhile (days), I can no longer connect with Winbox. Everything else keeps working fine, but the router won’t respond to a winbox connection. Power cycling the router makes winbox connect fine again.

Another bug with beta3 04.05.2012 and RB711. Restarting every 5minutes. In log is - Router was rebooted without proper schutdown.
With 5.17 uptime a lot of days

Sounds like watchdog. Uncheck the watchdog timer and see if that fixes it.