I sent him a reply almost 10 hours ago.Nathan, thank you very much for your note. My colleague [Janis] was waiting for reply from you.
Maybe it would be wise to have an rc12 release first instead of rushing headlong into final?Developers are applied the fix, next version (most likely 6.23) will include the fix!
People which upgrade from "wireless" to "wireless-fp" have problem with packetloss (about 1%) if NV2 is used. There is topic about this.honzam,
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.
See this: http://forum.mikrotik.com/viewtopic.php ... packetlosshonzam,
Please provide us with support output file and detailed test report, when 1% decrease on the link is present.
We have not noticed such issue!
*) dhcpv4 server - fix adding address lists from radius;
I can now boot RouterOS MetaROUTERs on MIPS boards. Good, thank you. However, MetaROUTER interface is still missing from Winbox. This worked on 6.22.Nathan, metarouter issue you reported is fixed on the version from the link!
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.Nathan,
thank you for the report, it is correct. Issue already reported, working on the fix!
AgreedThumbs up for this informative post and also for any post that serves towards greater visibility into the development/testing process.
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.
Steps to reproduce:However, it seems we are not able to repeat the particular issue. It works for us on 6.23, probably more details are required.
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.
Do you have anything in the logs?I just did this upgrade on two RB411GL boards and they didn't come up after the reboot/upgrade. I had to hard power them off at the sites and power them back on.
I agree.Mikrotik peeps. If this is how you handle new OS upgrades/releases then you will regain everything that was lost here in the community and then some. I realize this might be very difficult but....it is very helpful for the users of your software/hardware. Please consider releasing fewer software changes and releasing more RCs to people here. I think most of us would troubleshoot this and see if things go well.
As always, thank you for the great products
ConfirmSee this: http://forum.mikrotik.com/viewtopic.php ... packetlosshonzam,
Please provide us with support output file and detailed test report, when 1% decrease on the link is present.
We have not noticed such issue!
I make new test link with wireless-fb and if problem appear -> SUPOUT to suppport
Hi Sergejs.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!
So does this mean you were finally able to reproduce this very easy to reproduce problem?Nathan, thank you for step by step instruction. Bug report is submitted, but most likely it will be fixed in the next RouterOS version.
+1MikroTik folks: This thread is an excellent example of how you should be handling new release candidates before they are released. Allow those who have experienced problems in the past to test with the new release candidate publicly and make the candidate better before releasing it. Release it only when any recently introduced bugs are fixed and no new problems are confirmed. It may cause your release cycle to lengthen slightly, but it is critical that you get the bugs eliminated and do not introduce new ones through this more public testing process.
A process like this will contribute to regaining your users' confidence.
Please write to support we have not revived any mails from you.All though not mentioned in the change log there is supposed to be a fix for the AC lockups. So far so good but only time will tell
Thank you for the answer.DjM, we have our own OPENVPN code, that does not have any relations to ovpn mentioned in the link.
No test in 6.22. Rc test versions today and write my observations.Sob,
wrobli, Do you have such issue with the latest 6.23rc? Could you provide us with support output file from your link?
So should I understand it that my config, which has been correct for 10+ years, suddenly became incorrect? Could you please give me some hints how that happened and what do you think is wrong with it? If it isn't clear, those five commands are complete router config, I made it as bare as possible for testing.Sob, 6to4 works fine for us with correct configuration.
Please try to run following command in order to try fix your situation:So should I understand it that my config, which has been correct for 10+ years, suddenly became incorrect? Could you please give me some hints how that happened and what do you think is wrong with it? If it isn't clear, those five commands are complete router config, I made it as bare as possible for testing.Sob, 6to4 works fine for us with correct configuration.
Unfortunately, one of the two routers rebooted itself 8h33m into the test. Darn. Should have known that I would jinx it by talking optimistically about it. I will continue to try to hunt for a way to easily reproduce the crash.So maybe fixing that one bug actually fixed all occurrences of RB1100 MR crashes (wouldn't that be great?). I am not calling it yet, and will let the test continue to run overnight.
Is this issue being worked on for a later release or is it going to be a problem for a while?*) using routing-marks could lead to tunnel loop detection to turn off tunnels;
We are currently fixing last issues with 6.23:
- secondary disk formatting;
- other minor issues.
We plan to make a full release of v6.23 soon.
http://www.mikrotik.com/download/share/ ... latest.zip
http://www.mikrotik.com/download#rc
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;
Nope, does not change anything. I'll send supout from router to support. Although it should be easier if you tested the same config yourself, rather then digging through supout data. It's just few commands and it reliably did not work on any router I tried (three so far)."/interface 6to4 set x !keepalive"
I've seen it constantly since 6.22. All my production routers that were affected by this are holding at 6.21.1 and seem fine right now.schrotn, it might be present in the previous versions.
I think you have misinterpreted its presence in the release notes. If it is in the release notes, then that means they think it is fixed, not that it is a known issue. So I think what sergejs is saying is that it is already fixed in 6.23, as was also restated in this other thread more clearly and explicitly: http://forum.mikrotik.com/viewtopic.php ... =1#p459094I was just curious if you foresee this being a long term issue or one you are already working on for one of the next couple releases.
Not that I could see.Do you have anything in the logs?I just did this upgrade on two RB411GL boards and they didn't come up after the reboot/upgrade. I had to hard power them off at the sites and power them back on.