There were no packaged NPK files for 6.0b1 but I copied up all the individual files that were on my router (system -> packages).

Rebooted and ran a speed test. Looks great at 75 down / 5 up to my ISP. (I'm paying for 20 down / 2 up).

Wireless bridge to a 5.14 router works just fine. The new quickset graphs on the web page and on winbox are really handy.

We'll see how it runs after a few days. Anyone else have any comments?

MD

edit: I went ahead and upgraded the other wireless without any issue.

It works great so far.
Resource usage is WAY down in comparison to V4 and V5 flavours.

The issue where the RB751U-2HnD will not reboot without freezing during startup seems to still exist in 6.0b1

Other than that, new ROS seems great, I like the Quick Set feature. I don't have any queues setup at the moment so I can't comment on any increase in performance there.

One thing that I am curious about is why 2.6.38 was chosen as the next kernel version. 2.6.32 was likely chosen because it was considered a "Long Term Support" release. I don't think the kernel guys do LTS anymore, so I am curious how one version was chosen over another.

changed pcq-rate of active queue... all queue tree hung: avg-rate freezed on the last value, no packets were processed by queues (i.e., no limiting). rebooting the router helped

First experience with MT6 beta 01 - powerpc RB600A

1. nstreme not work properly with enable polling, nv2 working ok
2. dynamics simple queue started but not work (we are using RADIUS for
autentication & SQ)
3. BT from base ap brdge to stations sends max 5Mbit/s & receives 0,2-0,4
Mbit/s, independents of interface (wlan1-wlan4)
4. and very big problem is downgrade to older version, all wlans was set to
default

Big problem when monitoring with dude (4beta3 in my case, what happen, when new version will come)
always come in log messages continuous message in Queue Tree on my RB450 I see 2.5 till 3.5 Gbps on my WAN interface
it will be good if it's true

111111, Thank you for the report. We are aware of the problem, it is fixed at 6.0beta2 version.