v6.48beta [testing] is released!

There seems to be testing but internal. We start 6.48 at version beta twelve.

The flash write counter is a big problem despite it not be actual writes. It will decrease the resell value of your router because the write counter is extremely high due to this bug. This bug alone should have been tackled by 6.47.1 version at a earlier moment.

I don’t think it is wise to have two active beta’s side by side, being developed.

*) ppp - added “ipv6-routes” parameter to “secrets” menu;
*) ppp - added support for “Framed-IPv6-Route” RADIUS attribute;
*) ppp - allow specifying pool name for “remote-ipv6-prefix-pool” parameter;

Does any of these changes mean it will help with this http://forum.mikrotik.com/t/ipv6-configuration-on-pppoe-interface/140890/1

There will continue to be 6.X versions for the foreseeable future as not all the chip sets out there will be able to support the new linux kernel in 7.X

@msatter What feature sets are you using in the versions with the flash write counter issue that are preventing you from just rolling back to a version without this issue?

What is not able to support the new linux kernel in v7? (other than really old devices, ex. mipsle)

From what I have seen, any MikroTik model that is currently sold works with v7, and probably most of those from the past several years that have been discontinued.

I am sorry, but I won’t go for that.

Upgrade issues from System Package menu should be resolved now.

I actually has the same though. The v6.47 is supposed to be the stable one, but with that bug fixing I am not inclined to deploy it to my Tik.

Updated RBM33G and LtAP LTE kit successfully.

R11e-LTE-US keeps working well after update.

Regards.

*) w60g - added “mdmg-fix” parameter for RBwAP60Gx3 (CLI only);

After update no traffic flows through to station devices. cannot mactel to them or macping. Downgraded back to 6.46.6

Yes it is 802.1BR


I wondered the same thing. I suspect it may come fairly quickly, the CCR2004 is using it internally, so the code is already in place.

Testing the hap ac ^ 2 router with a 0-1% CPU load showed that there is no difference between the power consumption of 6.47 and 6.48beta12 firmware. In both cases, it is 5.2-5.4W

Did you enable the on demand CPU scaling?

/system routerboard settings set cpu-frequency=auto

Now I tried it, the result: with any frequency, consumption does not change, only the full load on the processor increases it by about one watt.

Weird stuff … the cpu-frequency setting. On my RB951G running ROS 6.46.5 it is possible to set cpu-frequency as well as cpu-mode … which can be set to either regular or power-save. However, both print output and export keep quiet about this setting regardless the value. I’m not going to bother measuring the power draw to check if there’s a difference.
On my RBD52G (hAP ac2) running same ROS version it is not possible to set cpu-mode … it is not listed as possible argument to set command.

OK, Question, is it possible to provide an overview of the properties and syntax of the port-controller and port-extender CLI menu? This would be helpful and much appreciated

crs3xx - added initial Bridge Port Extender support (CLI only);
crs3xx - added initial Controlling Bridge support for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices (CLI only);

cheers

H

Let me tell you that this 802.1BR support makes me very excited :slight_smile:

FInally some effort by Mikrotik Team for development of IPv6. :astonished:

Please add Radius Accounting for Delegated-IPv6-Prefix over PPPOE

Still no fix mentioned for discarded IPv6 Neighbor solicitations entering the bridge when igmp-snooping is enabled.
It’s really annoying not being able to use IPv6 and igmp-snooping together on the same bridge.

I Wonder why still many people are not demanding IPv6 features.
IPv6 is now in trend and it is really beneficial because it consumes less resource and No NAT tensions

Multihoming and load balancing?..