For those that had confirmed bug reports, please check if the issue is resolved. Thank you for helping.
(note – some reported issues may not be addressed in this version, but please do write and report details)
What’s new in 6.23rc11 (2014-Dec-02 15:07):
*) pptp - fixed problem where tunnel stopped transmitting packets under heavy load;
*) web proxy - caching in RAM for boards with 32MB or less RAM will not cache any content;
*) leds - removed ‘led’ command and added support for ‘on’, ‘off’ types under ‘system leds’;
*) files - allow to move files between different disks in winbox;
*) dhcpv4 server - fix adding address lists from radius;
*) dhcpv4 server - make radius classless static route tag as dhcp vendor specific;
*) smb - fixed HDD used/free space reporting
*) made powerpc metarouters work again (were broken in v6.22);
*) disks - fixed fat32 formatting where some bogus files with strange names were created
(to delete existing files reformatting is needed);
*) disks - fixed problem where some of USB disks were not recognized;
*) fetch - allow checking certificate trust without crl checking;
*) userman - fix more web session problems when user uses
customer and administrator interfaces at the same time;
*) snmp - fix external storage info reporting;
*) snmp - fix bulk walk problem introduced in v6.20;
*) fix tunnels - keep keepalive disabled for existing tunnels when upgrading;
*) fix tunnels - mtu for eoip tunnels was not allowed
to be set less than 1280 since 6.20;
*) using routing-marks could lead to tunnel loop detection to turn off tunnels;
Please don’t rush this release or feel pressure to release it sooner than it is ready. Take your time. There is no rush. Rushing software makes for bad software.
There are new regressions with MetaROUTER in 6.23rc compared to 6.22 on MIPS. The PPC MetaROUTER fix that I was told was in rc11 is not in there at all. I have either filed tickets about these things today or responded to emails from existing tickets.
There are also stability problems with MR on MIPS that I have been running into in recent releases that I am trying to peg down and compose a ticket about. If I run a MetaROUTER on 6.12 or newer, I risk freezing, crashes, and reboots. But if I want to have stable PPP services without memory leaks, or if I want to use CAPsMAN, I need to run 6.13, and if I want to use CAPsMAN without problems, I need to run at least 6.16. So I am stuck and getting frustrated, as are my customers…
I dream of the day I can upgrade to a version to fix a bug, and not have 3 new regressions pop up.
Nathan, thank you very much for your note. My colleague [Janis] was waiting for reply from you.
We have retested your issue on PPC metarouter, you are right it is still present.
Developers are applied the fix, next version (most likely 6.23) will include the fix!
Thanks for this topic. In future, make it for all RC version before release. It is usefull.
I have question about wireless. Now there are 3 wireless packages:
“wireless”
“wireless-fp”
“wireless-cm2”
Have you plan merge this packages?
Now there is quite a problem to which package to choose?
Which is best for NV2 AUTO settings? For P2P link?
Which is best for NV2 fixed tdma period size settings?
Which is best for Nstream stability (disconnecting)?
Etc etc …
Thanks
I also opened a new ticket (2014120366000046) about new MIPS MetaROUTER issues that got broken between 6.22 and 6.23rc, about 8 hours ago.
I am actually in North America, in the west coast region/timezone. I have been staying up very late these past couple of weeks in order to try to catch you guys while you are awake because I want to help you get the information that you need to get these bugs fixed. And I need these bugs to be fixed.
There are still more serious issues that I know won’t get fixed before 6.23 is released that have been around for a few versions, but I will go insane if 6.23 comes out and introduces additional bugs that break things that already worked, piled on top of the bugs that still need to get fixed in future versions.
Maybe it would be wise to have an rc12 release first instead of rushing headlong into final?
Yes, we will optimise wireless packages in the future to make them more obvious!
For most wireless installations wireless-fp package should be used, the only exception when your setup requires CAPsMANv2, then wireless-cm package is the right one.
People which upgrade from “wireless” to “wireless-fp” have problem with packetloss (about 1%) if NV2 is used. There is topic about this.
Is this problem now solved? Thanks
santa,
there was issue reported by user, when DHCP client renewed the lease, the process failed due to problems with adding entry to address-list.
Now issue is fixed!
While you are at it, Virtual Ethernet interfaces for MetaROUTERs have not been working in Winbox for PowerPC boards for many, many versions. (No Virtual Ethernet option in Interface add [+] drop-down, and double-clicking on a VIF interface doesn’t do anything.) Since this problem wasn’t introduced in 6.23, I don’t expect it to get fixed right away, but it’s yet another MetaROUTER-related Winbox issue.
Okay, I can also confirm that PowerPC crash after 5 minutes of uptime when using MetaROUTER is fixed. Also, the uptime clock skipping from 4m55s to 5m5s is also fixed!
Excellent. Now that they don’t reboot every 5 minutes, I can continue to stress-test RB1xxx for other MetaROUTER-related crashes.
honzam, few more comments about your topic and wireless packages!
“wireless-fp” has newer features such as capsman and 11ac support with all of the old feature, for those features, it include significant other background changes from “wireless.” It is only default installed on new manufactured devices so as to safely avoid any problems on installed devices. Currently we have no reported issues for this package.
“wireless-cm2” has a new capsman version that is not backward compatible with the original capman and is still in beta – therefore a separate package.
In v7, there will only be one wireless package including all new feature. We may have one merged package for v6 in the future, but that will only be decided when capsman v2 is out of beta.
