6.22 released!

Wed Nov 12, 2014 8:06 pm

What's new in 6.22 (2014-Nov-11 14:46):

*) ovpn - added support for null crypto;
*) files - allow to remove empty disk folders;
*) sntp - fix problems with dns name resolving failures that were triggering
system watchdog timeout;
*) eoip/eoipv6/gre/gre6/ipip/ipipv6/6to4 tunnels have new features:
tunnels go down when no route to destination;
tunnels go down for 1 minute when transmit loop detected, warning gets logged;
new keepalive-retries setting;
keepalives enabled by default for new tunnels (10sec interval, 10 retries);
*) improved connection-state matcher in firewall - can match multiple states in one rule, supports negation;
*) added connection-nat-state matcher - can match connections that are srcnatted,dstnatted or both;
*) 100% CPU load caused by DNS service fixed;
*) 100% CPU load caused by unclassified services fixed;
*) 6to4 tunnel fixed;
*) new RouterBOOT firmware for Metal 2SHPn to improve wireless stability;

Click "Check for updates" in QuickSet or Packages menu to get the new version. This time, it should also work for v5 routers, please report if your device found the new release and how the update went.

roadracer96 · Wed Nov 12, 2014 8:20 pm

Opened a case about 6.21.1 today... VRRP IPv6 no worky worky. Backup router flaps constantly. Was working on 6.19, broken in 6.21

Guessing that fix isn't in it...

mandrade · Wed Nov 12, 2014 8:50 pm

*File not FOUND* tring download the torrent file....

BR

Wed Nov 12, 2014 8:56 pm

We will try to fix torrent shortly. Thank you very much for the report.

Please report to this forum topic everything about 6.22 RouterOS version.
If you have specific reports about older versions, please contact us by support@mikrotik.com with detailed problem report. We will try to help you and solve your problem as soon as possible.
Thank you very much for the cooperation.

pbr3000 · Wed Nov 12, 2014 9:08 pm

I have problems in address-lists and dhcp from 6.19 and all higher versions later. I submitted a report of the problem (Ticket#2014110466000984) to the v6.21.1. I tested the new version 6.22 right now and surprise: nothing has changed.
I have heard people talk here in "BugOS" to refer to "RouterOS" and tend to agree with them, unfortunately.

Wed Nov 12, 2014 9:12 pm

pbr3000, we will try to figure out what is the problem with the address-list. Thank you for the feedback.

honzam · Wed Nov 12, 2014 9:19 pm

First night build from Mikrotik? Sergejs Posted: 12 Nov 2014, 19:06
Hopefully that will be better than 6.21.1

pbr3000 · Wed Nov 12, 2014 9:42 pm

pbr3000, we will try to figure out what is the problem with the address-list. Thank you for the feedback.

Thank you! Back to 6.18 again...

karina · Wed Nov 12, 2014 11:00 pm

ver 5.21 check for updates returns "file not found" error

parrini · Wed Nov 12, 2014 11:06 pm

I have been waiting a long time for:

*) new RouterBOOT firmware for Metal 2SHPn to improve wireless stability;

I am going to test this right away... please can anyone with wireless problems in 2SHPn report here too?

Thanks!

Qper · Thu Nov 13, 2014 12:02 am

After update my RB2011 radio is very loud...

Sob · Thu Nov 13, 2014 1:06 am

*) 6to4 tunnel fixed;

Ehm, no. As a brave man, I decided to try fresh ROS 6.22 on my home router (I often misuse it for various testing, its physical reachability is big advantage

). Same simple config as last time with 6.21.1. First impression was good, both routes were reported as reachable:

ros code

0 A S  dst-address=2000::/3 gateway=::192.88.99.1%6to4 gateway-status=::192.88.99.1%6to4 reachable 
        distance=1 scope=30 target-scope=10 

 1 ADC  dst-address=2002::/16 gateway=6to4 gateway-status=6to4 reachable distance=0 scope=10 

 2 ADC  dst-address=2002:d5d3:xxxx:80::/64 gateway=internal gateway-status=internal reachable 
        distance=0 scope=10

Unfortunately, nothing was reachable from LAN. Why? Because no matter what I tried to connect to, router was returning ICMPv6 destination unreachable (type 1, code 0). Also all attempts to ping external IPv6 address directly from router failed with "no route to host". So it says it has routes, but internally it does not seem to really have them.

I recreated the same config (only required bare minimum) on clean ROS 6.22 x86 VM just to be sure that it's not influenced by something else on my router (I have a lot of stuff there). Exactly the same result. So welcome back, ROS 6.19. Looking forward to 6.23.

apteixeira · Thu Nov 13, 2014 2:57 am

Hello,

Can't RESET HTML from hotspot.

Best regards.

TheRouterYouKnow · Thu Nov 13, 2014 3:40 am

cheeze · Thu Nov 13, 2014 5:14 am

Nah....

Version 6 isn't beta. It's just that some parts of it are still not working quite as well as they need to be....

Thu Nov 13, 2014 7:12 am

Nah....

Version 6 isn't beta. It's just that some parts of it are still not working quite as well as they need to be....

And with every release it is another part, That is my definition of beta. Wasted 4h yesterday with a problem where a
ethernet port did not work when removing it out of a bridge.

Rudios · Thu Nov 13, 2014 7:18 am

Nah....

Version 6 isn't beta. It's just that some parts of it are still not working quite as well as they need to be....
And with every release it is another part, That is my definition of beta. Wasted 4h yesterday with a problem where a
ethernet port did not work when removing it out of a bridge.

What about the new feature disk
From Winbox I do not see any drives. Looking on the Files menu I see a folder called Disk1.
How can I create folders on a drive for e.g. WebProxy or logging?

Thu Nov 13, 2014 8:52 am

What about the new feature disk
From Winbox I do not see any drives. Looking on the Files menu I see a folder called Disk1.
How can I create folders on a drive for e.g. WebProxy or logging?

Here are RouterOS commands for it.

#WebProxy:
/ip proxy set cache-path=disk1/web-proxy1
#Logging:
/system logging action set disk disk-file-name=disk1/log
#User-Manager:
/tool user-manager database set db-path=disk1/user-manager

Thu Nov 13, 2014 9:05 am

I have problems in address-lists and dhcp from 6.19 and all higher versions later. I submitted a report of the problem (Ticket#2014110466000984) to the v6.21.1. I tested the new version 6.22 right now and surprise: nothing has changed.
I have heard people talk here in "BugOS" to refer to "RouterOS" and tend to agree with them, unfortunately.

The ticket is still open and solution has not been found. Sergejs asked for logs and he is still looking into this problem. The issue will be solved, when ticket is closed, and you will be notified about this problem.

cursemipn · Thu Nov 13, 2014 9:09 am

What about this problem?
http://forum.mikrotik.com/viewtopic.php?f=2&t=86119

Noa · Thu Nov 13, 2014 9:17 am

CCR series still have problems with randomly rebooting.

Thu Nov 13, 2014 9:21 am

What about this problem?
http://forum.mikrotik.com/viewtopic.php?f=2&t=86119

If you have packet loss in all versions, maybe there is some sort of hardware problem? if you have the chance, try another machine or at least other NIC

Thu Nov 13, 2014 9:22 am

After update my RB2011 radio is very loud...

please clarify what you mean by this?

Thu Nov 13, 2014 9:24 am

CCR series still have problems with randomly rebooting.

please make a supout.rif file and email it to support. when did this issue start?

Raf · Thu Nov 13, 2014 9:55 am

Groove A-52HPn has the very same problem/bug when operating in 2.4 GHz, which was in Metal 2SHPn. Metal is fixed now, so can you guys check and port this fix to Groove A-52HPn also? On A-52PHn the very same bug appears also only in 2.4 GHz.

cursemipn · Thu Nov 13, 2014 10:03 am

What about this problem?
http://forum.mikrotik.com/viewtopic.php?f=2&t=86119
If you have packet loss in all versions, maybe there is some sort of hardware problem? if you have the chance, try another machine or at least other NIC

No, we have packet loss only on version 6.8-6.22.Versions 6.5-6.7 works stable. After 20-30 minutes MT start drops packet on all interfaces. In log file we see next message "105 (no buffer space available)". We try start VM on next servers:
1. Supermicro X8DTT 12CPUs x 2.4 GHz Processor Type Inter(R) Xeon(R) CPU E5645 @ 2.40GHZ
Intel Corporation 82576 Gigabit Network Connection

2.HP Proliant DL380p Gen8 16 CPUs x 2.593 GHz Processor Type Inter(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
Broadcom Corporation NetXtreme II BCM5710 10G

Last month we buy CCR1036-8G-2S+, but his work very terribly.

Thu Nov 13, 2014 10:04 am

What about this problem?
http://forum.mikrotik.com/viewtopic.php?f=2&t=86119
If you have packet loss in all versions, maybe there is some sort of hardware problem? if you have the chance, try another machine or at least other NIC
No, we have packet loss only on version 6.8-6.22. After 20-30 minutes MT start drops packet on all interfaces. In log file we see next message "105 (no buffer space available)". We try start VM on next servers:
1. Supermicro X8DTT 12CPUs x 2.4 GHz Processor Type Inter(R) Xeon(R) CPU E5645 @ 2.40GHZ
Intel Corporation 82576 Gigabit Network Connection

2.HP Proliant DL380p Gen8 16 CPUs x 2.593 GHz Processor Type Inter(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
Broadcom Corporation NetXtreme II BCM5710 10G

Last month we buy CCR1036-8G-2S+, but his work very terribly.

Please make a supout.rif file at the moment of the packet loss and send to support.
What problems do you have with the CCR, you did not say

Visla · Thu Nov 13, 2014 10:14 am

*) 100% CPU load caused by DNS service fixed;
*) 100% CPU load caused by unclassified services fixed;
Its not fixed. I updated my CCR 1036 to 6.22 still cpu 100%. Sometimes CCR-1036 is crashing.
[Ticket#2014110166000177]

Rudios · Thu Nov 13, 2014 12:32 pm

What about the new feature disk
From Winbox I do not see any drives. Looking on the Files menu I see a folder called Disk1.
How can I create folders on a drive for e.g. WebProxy or logging?
Here are RouterOS commands for it.
Code: Select all
#WebProxy:
/ip proxy set cache-path=disk1/web-proxy1
#Logging:
/system logging action set disk disk-file-name=disk1/log
#User-Manager:
/tool user-manager database set db-path=disk1/user-manager

Ok, clear.
But how come I can't see my local drive/disk?
On the old situation (system/stores -> disk tab) there is a system disk.
Now there is nothing, unless there is a USB drive inserted.

Thu Nov 13, 2014 12:59 pm

What about the new feature disk
From Winbox I do not see any drives. Looking on the Files menu I see a folder called Disk1.
How can I create folders on a drive for e.g. WebProxy or logging?
Here are RouterOS commands for it.
Code: Select all
#WebProxy:
/ip proxy set cache-path=disk1/web-proxy1
#Logging:
/system logging action set disk disk-file-name=disk1/log
#User-Manager:
/tool user-manager database set db-path=disk1c
Ok, clear.
But how come I can't see my local drive/disk?
On the old situation (system/stores -> disk tab) there is a system disk.
Now there is nothing, unless there is a USB drive inserted.

Now "Disks" menu shows only additionally mounted drives and allows formatting them. Local drive is what you see in the File List and you can use it for the same services by changing the path: "/web-proxy1"; "/log"; "/user-manager"

keema · Thu Nov 13, 2014 1:05 pm

Reading all these comments, only hours after releasing a 3rd version in less then 2 months makes me suspicious. I'm skipping this version too.... Is it 22nd in a row already or 24th? Anyway, skipped whole v6 version. One dissapointment after another.

Thu Nov 13, 2014 1:16 pm

Reading all these comments, only hours after releasing a 3rd version in less then 2 months makes me suspicious. I'm skipping this version too.... Is it 22nd in a row already or 24th? Anyway, skipped whole v6 version. One dissapointment after another.

I can understand how this looks, but please remember that tens of thousands of users upgraded without a single issue. The problems posted here are quite unique and affect only people with specific configurations.

cursemipn · Thu Nov 13, 2014 1:23 pm

Please make a supout.rif file at the moment of the packet loss and send to support.
What problems do you have with the CCR, you did not say

About CCR. Still problem with QOS(PCQ) low bandwith. 550 Mbit/s traffic(testing in production) and all CCR's CPU goes about 78-100%(all 36 cores). 2 years ago CCR can skip only 250 Mbit/s and works only 2 core(100%) and after 1 hour goes crash.
For examle VDS can skip about 600 Mbit/s traffic with QOS,NAT.
There is only 1 minus on VDS. In ROS V5 i can appoint 8 virtual cores. In ROS V6 i can appoint 24 virtual cores but only from higt version ROS 6.19-6.22(only this versions tested on VDS in this month). In ROS 6.5-6-7 8 cores only.
In the next test, i make support.rif file.
CCR-1036 tested 2 years ago(6.0, 6.1, 6.2, 6.3) - sell device. This month(6.19,6.20,6.21,6.22) - more better balancing between cores, but still pure perfomance. Waiting.
Thats all.

NathanA · Thu Nov 13, 2014 1:49 pm

What about this problem?
http://forum.mikrotik.com/viewtopic.php?f=2&t=86119
If you have packet loss in all versions, maybe there is some sort of hardware problem? if you have the chance, try another machine or at least other NIC
No, we have packet loss only on version 6.8-6.22.Versions 6.5-6.7 works stable. After 20-30 minutes MT start drops packet on all interfaces. In log file we see next message "105 (no buffer space available)".

Wait, isn't "no buffer space available" the same message we saw when there was a bug with the PPP driver filling up the kernel route cache? In cursemipn's other thread that he linked to, he mentions his router runs a PPPoE server with hundreds of clients. He also mentions that he has no problems with 6.7 and his problems start with 6.8. RouterOS 6.8 was the version that included the large PPP driver rewrite, and for several versions after that, MikroTik had to fix tons of PPP bugs that 6.8 introduced. The kernel route cache memory leak was fixed for most PPP interfaces on 6.13, but maybe MikroTik missed one that still exists.

His packet loss issue could easily be explained by a runaway PPP driver filling up the kernel route cache, which would prevent the router from being able to transmit anything, and then the kernel route cache garbage collector intermittently managing to clear out some of the entires in the route cache (which would allow the router to once more transmit responses) before it gets filled up again.

This is the thread in question: http://forum.mikrotik.com/viewtopic.php?f=3&t=83030

To cursemipn: the next time this happens, please paste the results of "/ip route cache print" to this thread.

-- Nathan

keema · Thu Nov 13, 2014 2:09 pm

Reading all these comments, only hours after releasing a 3rd version in less then 2 months makes me suspicious. I'm skipping this version too.... Is it 22nd in a row already or 24th? Anyway, skipped whole v6 version. One dissapointment after another.
I can understand how this looks, but please remember that tens of thousands of users upgraded without a single issue. The problems posted here are quite unique and affect only people with specific configurations.

Why do you assume we don't have complex configs on our core network? I'm just being cautious. Also reading soo many negative comments on ALL V6 release threads including this one, makes me a bit worried about my decision to implement your routers in our network. All you need to do is release a STABLE version where all declared features work. Random rebooting of CCR's isn't what I had in mind and these device can be used for core network but I'm glad we are not using them.

kubik256 · Thu Nov 13, 2014 2:25 pm

Hello,

I have big trouble with our main RouterBoard RB750G. It shows up after upgrading to 6.21.1 and after upgrade to 6.22 it's still there.

All physical interfaces randomly goes down and up again (looks like they are restarting). It never happend before and we are using these RouterBoards for more than 3 years now.

There is a few lines from todays log:

Nov/13/2014 12:39:32 interface,info ether1-gateway link down
Nov/13/2014 12:39:32 interface,info ether2-local-master link down
Nov/13/2014 12:39:32 interface,info ether3-local-slave link down
Nov/13/2014 12:39:34 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 12:39:36 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 12:39:50 interface,info ether3-local-slave link up (speed 100M, full duplex)
Nov/13/2014 13:07:32 interface,info ether1-gateway link down
Nov/13/2014 13:07:32 interface,info ether2-local-master link down
Nov/13/2014 13:07:32 interface,info ether3-local-slave link down
Nov/13/2014 13:07:34 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:07:36 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:07:51 interface,info ether3-local-slave link up (speed 100M, full duplex)

I have tried to find something that can trigger this strange behavior by Wireshark, but nothing

Can somebody help?
Or can I somehow downgrade the RouterOS?

Thanks to all

Thu Nov 13, 2014 2:45 pm

Why do you assume we don't have complex configs on our core network? I'm just being cautious. Also reading soo many negative comments on

I did not say complex, I said specific. There are many ISPs running on this version now without any issues, with complext configs.
Most people having prolems are in this forum, you can see how many there are, less than 10.
We are addressing all those remaining issues, please don't worry.

Thu Nov 13, 2014 3:25 pm

It's because others are not beta testers unlike us.

Thu Nov 13, 2014 3:47 pm

It's because others are not beta testers unlike us.

we have statistics how many devices have upgraded. I don't want to argue about this, please let us concentrate on the remaining issues here. Let us discuss the release rather than nitpick

keema · Thu Nov 13, 2014 3:47 pm

Why do you assume we don't have complex configs on our core network? I'm just being cautious. Also reading soo many negative comments on
I did not say complex, I said specific. There are many ISPs running on this version now without any issues, with complext configs.
Most people having prolems are in this forum, you can see how many there are, less than 10.
We are addressing all those remaining issues, please don't worry.

Yes, you said specific not complex. But still, every major company has some specific configs and if your routers are constantly having bugs and with each new version new bugs, it is hard to say, not to worry, especially because I'm already worring the whole time v6 is out. I will wait for 6.23 but regarding previous experiences nothing will change. Some old bugs will be fixed and some new will be implemented simply because you DON'T TEST your software. When you get a critical mass of unsatisfied customers it will be a different story.
The other thing is licencing... we bought many routers (mostly 411xx) when v4 was the current version and they are upgradable to v6.x. It can be quite hard for me to accept claim that v6 will be stable before v7 comes out. These routers cannot be upgraded to v6 because of constant connect/disconnect issues over PPTP VPN. It is unstable. Period. I've been reading this forum for more then 6 years now and I have seen many answers from MT staff like, please wait for version xx.xx for this bug to be fixed. Always the same. No, the only right thing for me is to worry. Upgrading at this stage to any v6 is a no-no.

Thu Nov 13, 2014 3:52 pm

The other thing is licencing... we bought many routers (mostly 411xx) when v4 was the current version and they are upgradable to v6.x. It can be quite hard for me to accept claim that v6 will be stable before v7 comes out.

The rules have changed recently. There're no more upgrade limits existing.

keema · Thu Nov 13, 2014 3:53 pm

The other thing is licencing... we bought many routers (mostly 411xx) when v4 was the current version and they are upgradable to v6.x. It can be quite hard for me to accept claim that v6 will be stable before v7 comes out.
The rules have changed recently. There're no more upgrade limits existing.

I didn't know that. Thanks for info.

Thu Nov 13, 2014 4:03 pm

It's because others are not beta testers unlike us.
we have statistics how many devices have upgraded. I don't want to argue about this, please let us concentrate on the remaining issues here. Let us discuss the release rather than nitpick

Sure. Please concentrate on error corrections and prevent creating new ones. I am telling this repeatedly for years already and each new update still brings new errors. But on the other way I can say that generally speaking the 6 is more usable for me than 5 and even many last versions made me problems I am not thinking about going back to 5.

kubik256 · Thu Nov 13, 2014 4:22 pm

Update to this version cost me a lot of troubles!
I wish you could hear the bad words that went out here....

In every 10-30 minutes all physical (eth) ports are flapping (turning down and up again) and break down connections to 14 our local servers... very nice, I'm feeling like lab rat

This is today's log (interfaces only):
--------------------------------------------------

Nov/13/2014 12:39:32 interface,info ether1-gateway link down
Nov/13/2014 12:39:32 interface,info ether2-local-master link down
Nov/13/2014 12:39:32 interface,info ether3-local-slave link down
Nov/13/2014 12:39:34 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 12:39:36 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 12:39:50 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:07:32 interface,info ether1-gateway link down
Nov/13/2014 13:07:32 interface,info ether2-local-master link down
Nov/13/2014 13:07:32 interface,info ether3-local-slave link down
Nov/13/2014 13:07:34 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:07:36 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:07:51 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:13:46 interface,info ether1-gateway link down
Nov/13/2014 13:13:46 interface,info ether2-local-master link down
Nov/13/2014 13:13:46 interface,info ether3-local-slave link down
Nov/13/2014 13:13:48 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:13:49 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:14:04 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:31:05 interface,info ether1-gateway link down
Nov/13/2014 13:31:05 interface,info ether2-local-master link down
Nov/13/2014 13:31:05 interface,info ether3-local-slave link down
Nov/13/2014 13:31:07 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:31:09 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:31:23 interface,info ether3-local-slave link up (speed 100M, full duplex)

I changed the router to another downgraded to RouterOS 6.20.... problem fixed.
But please, never ever relase another poorly tested version as STABLE again!!!!!

marizo · Thu Nov 13, 2014 6:02 pm

Yesterday upgraded one of my Home WiFi AP (RB411UAH) from 6.21 to 6.22 - so far so good. Nothing extraordinary. For greater clarity I must say I use only few features - VirtualAP, WPA/WPA2, PPTP VPN, some basic scripts with e-mailing..

But I want to ask - why there is wireless and wireless-fp packages? If i remember correctly, there was some info about fp replaces usual package. What are the differences?

Alupis · Thu Nov 13, 2014 6:31 pm

fellas, calm down a second. any new release of any software will have some problems, not just mikrotik. if you have some core infrastructure that you cannot afford to have problems with -- don't upgrade immediately, let is play out for a few days/weeks while users who can afford to be "bleeding edge" test and report bugs back to mikrotik. that is Enterprise IT 101.

if you are going to use the new firmware and be "bleeding edge", kindly report problems to mikrotik and they will fix them. i have yet to see them just simply ignore a genuine bug report which provided enough resources to actually replicate/solve the problem.

tomaskir · Thu Nov 13, 2014 6:50 pm

i have yet to see them just simply ignore a genuine bug report which provided enough resources to actually replicate/solve the problem.

Then you have not been here long enough.

I could give you many ticket IDs which show differently...

TheRouterYouKnow · Thu Nov 13, 2014 7:36 pm

Alupis · Thu Nov 13, 2014 7:42 pm

I could give you many ticket IDs which show differently...

no point in arguing. if you work in software development for a while, you would understand tickets filed that effect only a small subset of users take the backseat to show-stopping issues (like if the router stops passing traffic or something). you can look at any major software project's bug tracking system for examples -- even something huge like the apache webserver (some tickets date back 5+ years).

Normis and other mikrotik people have said over and over, most reported "bugs" are user misconfigurations. The same is true for every software project i've developed on.

For fixing real bugs, it comes down to how severe the issues is, and how many users are effected. this is why it is important that if you are effected, you submit the information necessary for the mikrotik team to address the problem. if the issue appears to only effect you (or only a few users), it may not be fixed quickly as more important bugs will take precedence. So if you have an issue, first search to see if someone else has already submitted it, if so, don't submit a new thread/ticket - append to the existing one and provide useful info (not just a "me too!").

cdesz · Thu Nov 13, 2014 8:38 pm

High CPU usage by "console" and frequent console crashes

> tool profile
NAME CPU USAGE
ethernet all 0%
console all 81.5%
firewall all 0.5%
networking all 0%
logging all 1.5%
management all 16%
routing all 0%
profiling all 0.5%
queuing all 0%
unclassified all 0%
-- [Q quit|D dump|C-z pause]
Console has crashed; please log in again.
Connection to closed.

miszak · Thu Nov 13, 2014 11:09 pm

6to4 tunnel NO fixed !!!

Router OS 6.22

6.22.JPG

Router OS 6.19 (6to 4 work OK)

6.19.JPG

Thu Nov 13, 2014 11:13 pm

Omnitiks do not work with USB flashdisks in 6.22, 6.21.1 and 6.20. When all omnitiks downgraded to 6.18, all their attached usb flashdisks started to be accessible.

Ticket number is [Ticket#2014103066000276].

I think it was related to change from "stores" to "disks" Also the USB flash disks were not reported in snmp, even in some devices (e.g. rb2011) the usb disk works, but is not displayed in snmp also.

The versions 6.20-6.22 made problems with responses to snmp querries that caused holes in graphs making them totally unusable.

All problems fully solved by downgrade to 6.18.

Have a look at this chart:

chart.jpeg

Are you guessing what happened at 18:00? I will tell you: I have downgraded to 6.18. And I suggest to all: If you have no specific reason for it, do not go over 6.18.

Gabo · Thu Nov 13, 2014 11:18 pm

I use IPv6 and I have three /64 subnets (office 2001:DB8:3:49::/64, visitors 2001:DB8:3:50::/64 , and home automation 2001:DB8:3:51::/64). I upgraded 6.20 -> 6.22 on CRS125-24G-1S-2HnD (firmware 3.18). After upgrade that 2 of 3 IPv6 addresses were in Invalid state. I didn't find any reason why addresses were marked as invalid. I downgraded RouterOS back to 6.20 and now all of my IPv6 addresses are working again.

Thu Nov 13, 2014 11:35 pm

I am becoming closer and closer to one idea: To start testing OpenWRT on mikrotik devices instead of ROS. If I write "instead" I do not mean metarouter. Just to be clear.

visalink · Fri Nov 14, 2014 12:28 am

Why do you assume we don't have complex configs on our core network? I'm just being cautious. Also reading soo many negative comments on
I did not say complex, I said specific. There are many ISPs running on this version now without any issues, with complext configs.
Most people having prolems are in this forum, you can see how many there are, less than 10.
We are addressing all those remaining issues, please don't worry.
Yes, you said specific not complex. But still, every major company has some specific configs and if your routers are constantly having bugs and with each new version new bugs, it is hard to say, not to worry, especially because I'm already worring the whole time v6 is out. I will wait for 6.23 but regarding previous experiences nothing will change. Some old bugs will be fixed and some new will be implemented simply because you DON'T TEST your software. When you get a critical mass of unsatisfied customers it will be a different story.
The other thing is licencing... we bought many routers (mostly 411xx) when v4 was the current version and they are upgradable to v6.x. It can be quite hard for me to accept claim that v6 will be stable before v7 comes out. These routers cannot be upgraded to v6 because of constant connect/disconnect issues over PPTP VPN. It is unstable. Period. I've been reading this forum for more then 6 years now and I have seen many answers from MT staff like, please wait for version xx.xx for this bug to be fixed. Always the same. No, the only right thing for me is to worry. Upgrading at this stage to any v6 is a no-no.

Be careful, if you push a bit more of the boys mikrotik they erase his post, as did mine.

visalink · Fri Nov 14, 2014 12:35 am

Update to this version cost me a lot of troubles!
I wish you could hear the bad words that went out here....

In every 10-30 minutes all physical (eth) ports are flapping (turning down and up again) and break down connections to 14 our local servers... very nice, I'm feeling like lab rat

This is today's log (interfaces only):
--------------------------------------------------

Nov/13/2014 12:39:32 interface,info ether1-gateway link down
Nov/13/2014 12:39:32 interface,info ether2-local-master link down
Nov/13/2014 12:39:32 interface,info ether3-local-slave link down
Nov/13/2014 12:39:34 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 12:39:36 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 12:39:50 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:07:32 interface,info ether1-gateway link down
Nov/13/2014 13:07:32 interface,info ether2-local-master link down
Nov/13/2014 13:07:32 interface,info ether3-local-slave link down
Nov/13/2014 13:07:34 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:07:36 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:07:51 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:13:46 interface,info ether1-gateway link down
Nov/13/2014 13:13:46 interface,info ether2-local-master link down
Nov/13/2014 13:13:46 interface,info ether3-local-slave link down
Nov/13/2014 13:13:48 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:13:49 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:14:04 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:31:05 interface,info ether1-gateway link down
Nov/13/2014 13:31:05 interface,info ether2-local-master link down
Nov/13/2014 13:31:05 interface,info ether3-local-slave link down
Nov/13/2014 13:31:07 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:31:09 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:31:23 interface,info ether3-local-slave link up (speed 100M, full duplex)

I changed the router to another downgraded to RouterOS 6.20.... problem fixed.
But please, never ever relase another poorly tested version as STABLE again!!!!!

Normis have deleted my post for speaking the truth.
If I say that I agree with you it will delete this?

kubik256 · Fri Nov 14, 2014 12:05 pm

Update to this version cost me a lot of troubles!
I wish you could hear the bad words that went out here....

In every 10-30 minutes all physical (eth) ports are flapping (turning down and up again) and break down connections to 14 our local servers... very nice, I'm feeling like lab rat

This is today's log (interfaces only):
--------------------------------------------------

Nov/13/2014 12:39:32 interface,info ether1-gateway link down
Nov/13/2014 12:39:32 interface,info ether2-local-master link down
Nov/13/2014 12:39:32 interface,info ether3-local-slave link down
Nov/13/2014 12:39:34 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 12:39:36 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 12:39:50 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:07:32 interface,info ether1-gateway link down
Nov/13/2014 13:07:32 interface,info ether2-local-master link down
Nov/13/2014 13:07:32 interface,info ether3-local-slave link down
Nov/13/2014 13:07:34 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:07:36 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:07:51 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:13:46 interface,info ether1-gateway link down
Nov/13/2014 13:13:46 interface,info ether2-local-master link down
Nov/13/2014 13:13:46 interface,info ether3-local-slave link down
Nov/13/2014 13:13:48 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:13:49 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:14:04 interface,info ether3-local-slave link up (speed 100M, full duplex)

Nov/13/2014 13:31:05 interface,info ether1-gateway link down
Nov/13/2014 13:31:05 interface,info ether2-local-master link down
Nov/13/2014 13:31:05 interface,info ether3-local-slave link down
Nov/13/2014 13:31:07 interface,info ether2-local-master link up (speed 100M, full duplex)
Nov/13/2014 13:31:09 interface,info ether1-gateway link up (speed 1G, full duplex)
Nov/13/2014 13:31:23 interface,info ether3-local-slave link up (speed 100M, full duplex)

I changed the router to another downgraded to RouterOS 6.20.... problem fixed.
But please, never ever relase another poorly tested version as STABLE again!!!!!

Normis have deleted my post for speaking the truth.
If I say that I agree with you it will delete this?

I don't mean that post in some bad way... but my problems after upgrade to this version had a very huge fu*king effect. There are 70 employees working from many different locations on 14 our servers via VPN and all of them was disconnected almost every 15 minutes!

And yesterday there was also our accountant. After she had to redo the same work about 7 times, because connection to SQL server was broken by Mikrotik again and again, she was tring to kill me!!! This is really not funny!

I really need to know, that if I'll upgrade to new version, it will not mess up everything in our company. Next time it can cost me a job!

janisk · Fri Nov 14, 2014 12:13 pm

6to4 tunnel NO fixed !!!

Router OS 6.22
6.22.JPG
Router OS 6.19 (6to 4 work OK)
6.19.JPG

have you set MTU for 6to4 tunnel to value suggested by HE (check configuration example)

[janiskr@MikroTIk] /ipv6 route> print 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable 
 #      DST-ADDRESS              GATEWAY                  DISTANCE
 0 A S  ::/0                     2001:db8:beef:bee::1              1
 1 ADC  2001:db8:beef:bee::/64     he-tb                           0
 2 ADC  2001:db8:beef:beef::/64     lo                              0
[janiskr@MikroTIk] /ipv6 route> /ping [:resolve ipv6.google.com]
HOST                                     SIZE TTL TIME  STATUS                                                              
2a00:1450:400f:804::1003                   56  53 53ms  echo reply                                                          
2a00:1450:400f:804::1003                   56  53 54ms  echo reply                                                          
    sent=2 received=2 packet-loss=0% min-rtt=53ms avg-rtt=53ms max-rtt=54ms 

[janiskr@MikroTIk] /ipv6 route> /interface 6to4 print 
Flags: X - disabled, R - running 
 #    NAME                     MTU ACTUAL-MTU LOCAL-ADDRESS   REMOTE-ADDRESS  KEEPALIVE                                 DSCP
 0  R he-tb                   1280       1280 a.b.c.s   e.f.g.h                                          inherit

alphil · Fri Nov 14, 2014 12:42 pm

After ROS upgrade to ver.6.22 (from 6.15), my ipip tunnel is down.

Flags: X - disabled, R - running, D - dynamic 
 0     ;;; IPTunel to Ferro
       name="ipip1" mtu=1480 actual-mtu=1480 local-address=80.XX.YY.ZZ remote-address=87.XX.YY.ZZ keepalive=10,3 dscp=0 clamp-tcp-mss=no dont-fragment=no

And route to remote network is unreachable.

3   S  ;;; Route to Ferro
        dst-address=192.168.8.0/24 pref-src=192.168.2.1 gateway=ipip1 gateway-status=ipip1 unreachable distance=1 scope=30 target-scope=10

Qper · Fri Nov 14, 2014 3:45 pm

http://youtu.be/b30qRb95Ht4

I restore my backup settings and working good

npero · Fri Nov 14, 2014 5:17 pm

Why upgrade that critical router before testing by yourself on other non critical place ?
I first upgrade my home MT router everything working then update non critical part of network and after that update critical part of network. I know people using today 2.9.27 or 3.30 or 4.17 or 5.26 or 6.22 and there are happy with that version.

Don't upgrade before testing on other non critical place.
RouterBoard have option to make partition make two partition one for testing other with working system tested before is something wrong happens just switch back to tested working system.
http://wiki.mikrotik.com/wiki/Manual:Partitions

If is something very very important upgrade must me planed, tested, prepared with replaced device ready to replace.... upgrading critical part of network without precise planing is crazy. It is nice button upgrade just to try

sorry but on some places I can afford that luxury.

Alupis · Fri Nov 14, 2014 5:54 pm

Why upgrade that critical router before testing by yourself on other non critical place ?
I first upgrade my home MT router everything working then update non critical part of network and after that update critical part of network. I know people using today 2.9.27 or 3.30 or 4.17 or 5.26 or 6.22 and there are happy with that version.

Don't upgrade before testing on other non critical place.
RouterBoard have option to make partition make two partition one for testing other with working system tested before is something wrong happens just switch back to tested working system.
http://wiki.mikrotik.com/wiki/Manual:Partitions

If is something very very important upgrade must me planed, tested, prepared with replaced device ready to replace.... upgrading critical part of network without precise planing is crazy. It is nice button upgrade just to try sorry but on some places I can afford that luxury.

+1 -- too many people in this thread seem to be blindly upgrading critical infrastructure without any prior testing in their environment and then are surprised when something unexpected happens. If 6.18 works best for you, good, stay on it until a newer release works best for you.

Fri Nov 14, 2014 6:42 pm

This is correct. I also test first in my lab then waiting some time and after that if everything seems to be good I start the updates on the network from the less critical devices. Even in this case sometimes something reveals in production as devices are different and set in different ways. What I definitely hate are the errors that looks like non-finished new features breaking old good working things. This is really something that I blame mikrotik for.

Fri Nov 14, 2014 7:22 pm

Why upgrade that critical router before testing by yourself on other non critical place ?
I first upgrade my home MT router everything working then update non critical part of network and after that update critical part of network. I know people using today 2.9.27 or 3.30 or 4.17 or 5.26 or 6.22 and there are happy with that version.

Don't upgrade before testing on other non critical place.
RouterBoard have option to make partition make two partition one for testing other with working system tested before is something wrong happens just switch back to tested working system.
http://wiki.mikrotik.com/wiki/Manual:Partitions

If is something very very important upgrade must me planed, tested, prepared with replaced device ready to replace.... upgrading critical part of network without precise planing is crazy. It is nice button upgrade just to try sorry but on some places I can afford that luxury.
+1 -- too many people in this thread seem to be blindly upgrading critical infrastructure without any prior testing in their environment and then are surprised when something unexpected happens. If 6.18 works best for you, good, stay on it until a newer release works best for you.

Event testing do not help. This week I moved an ethernet interface out of a bridge on a RB1200 with 6.15 and gave it a new IP. This device ran since upgrade without problem. The port looks like it works but do not forward any traffic. Using another port works then with this IP. Testing/sniffing took me 4h with driving. Now I put a second IP on the second working port -> RB1200 reboots with kernel fault ...
So would you dare an upgrade now or would you do a factory default and take the outage with ranting customers ...
Want to install 6.15 there again or what version is surely stable ??
I do not upgrade any MT device for a while now as every upgrade may lead to unpredictable outages.
We already lost some devices while upgrading.
Quality control / Testing of MT is way to low at the moment.

marizo · Fri Nov 14, 2014 7:43 pm

Maybe MT need to add some more functionality to Update menu - version selection with pros and cons (known bugs); there can be also some test/alpha/beta/stable etc selection, so everyone could decide Update or not to update and which version to update? Just suggestion..

antoninn · Fri Nov 14, 2014 8:51 pm

From Mikrotik support page:

Support Request Instructions

When contacting us at support[at]mikrotik.com:

Make sure that you have the latest version of the RouterOS. If you don't have it, upgrade your router to the latest version and check if the problem still persists!

I administer around 200 Mikrotik devices all of version 5.26. I live with Mikrotiks from version 2. Currently I have stopped buying additional devices, because of all this mess around version 6. I want stable version because I do not want to be tester of RouterOS. I also develop software in team of 20 people, but what I see here is very sad from customer's point of view. I have also one experience with support - I have sent ticket wihout response from support. Support started to response right after my complaints in this forum. I would like Mikrotik to rethink their strategy, because current status is IMHO unsustainable.

Fri Nov 14, 2014 9:10 pm

Maybe MT need to add some more functionality to Update menu - version selection with pros and cons (known bugs); there can be also some test/alpha/beta/stable etc selection, so everyone could decide Update or not to update and which version to update? Just suggestion..

... And for me other special button: "take my chance" that randomly selects one of 6.x versions and immediately installs it.... Hahaha... Why not have some fun?

danielillu · Fri Nov 14, 2014 9:14 pm

I have noticed that there are some minor changes on the console syntax, at least on the NTP Client settings.

6.20:

/system ntp client set enabled=yes

It works.

6.22:

/system ntp client set enabled=yes 
failure: IP address of NTP server is missing

Now I cannot enable the NTP service without defining a primary-ntp address.

miszak · Sat Nov 15, 2014 1:14 am

6to4 tunnel NO fixed !!!

Router OS 6.22
6.22.JPG
Router OS 6.19 (6to 4 work OK)
6.19.JPG

have you set MTU for 6to4 tunnel to value suggested by HE (check configuration example)

[janiskr@MikroTIk] /ipv6 route> print 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable 
 #      DST-ADDRESS              GATEWAY                  DISTANCE
 0 A S  ::/0                     2001:db8:beef:bee::1              1
 1 ADC  2001:db8:beef:bee::/64     he-tb                           0
 2 ADC  2001:db8:beef:beef::/64     lo                              0
[janiskr@MikroTIk] /ipv6 route> /ping [:resolve ipv6.google.com]
HOST                                     SIZE TTL TIME  STATUS                                                              
2a00:1450:400f:804::1003                   56  53 53ms  echo reply                                                          
2a00:1450:400f:804::1003                   56  53 54ms  echo reply                                                          
    sent=2 received=2 packet-loss=0% min-rtt=53ms avg-rtt=53ms max-rtt=54ms 

[janiskr@MikroTIk] /ipv6 route> /interface 6to4 print 
Flags: X - disabled, R - running 
 #    NAME                     MTU ACTUAL-MTU LOCAL-ADDRESS   REMOTE-ADDRESS  KEEPALIVE                                 DSCP
 0  R he-tb                   1280       1280 a.b.c.s   e.f.g.h                                          inherit

I pasted config from HE,
[miszak@test] /interface 6to4> print
Flags: X - disabled, R - running
# NAME MTU LOCAL-ADDRESS REMOTE-ADDRESS
0 R ;;; Hurricane Electric IPv6 Tunnel Broker
sit1 1280 109.x.x.x 216.x.x.x
This is when I back to 6.19 tunnel 6to4

roadracer96 · Sat Nov 15, 2014 1:49 am

HE.net 6to4 tunnel works fine at home.. 6.19,6.20,6.21.1,6.22 MTU set to auto didn't work until 6.22 though. Currently running 1480 MTU and can pull 600+mbit across it up and down. CCR-1016. Also, as of the 6.21 release, I stopped MSS clamping in mangle with the new feature to auto clamp MSS on the tunnel.

infused · Sat Nov 15, 2014 4:26 am

Guys you need to check this stuff before throwing it in production. i don't like buggy releases either, but you are mad if you are putting this straight out to production/clients.

We normally wait 3-5 releases before upgrading. We have another unit on standby with the same config incase anything goes wrong. We also test it on another piece of identical hardware before upgrading.

Buster2 · Sat Nov 15, 2014 4:59 am

We normally wait 3-5 releases before upgrading. We have another unit on standby with the same config incase anything goes wrong. We also test it on another piece of identical hardware before upgrading.

So, your advantage is to wait for others to find the failures of that specific versions. If everybody thinks like you, MT will always fail with every customer (ISP).

There are two main arguments:
1st: Small (W)ISP can't afford a test bed or can't simulate _every_ condition and _every_ feature of MT they use in a testing lab.
2nd: Why can't MT itself set up an extensive testing environment to assure code quality. Test driven development is nothing magically nowadays.

warrenisarobot · Sat Nov 15, 2014 7:29 am

After upgrading to 6.22 I am getting warnings for "transmit loop detected, downing interface for 60 seconds" just as described in the logs. This is with a GRE tunnel that between two mikrotiks that was working before.

The tunnel is from one location with 2 internet providers to another location with a single internet provider. The first location has 2 tunnels setup with difference source addresses but the same destination address and the second location with the same source address but 2 different destination address. One of the tunnels works fine but the second is now useless. It was setup with a route to prefer our favored internet provider and to failover to the second if the primary's link failed.

What exactly is the loop detection supposed to do?

Disassembler · Sat Nov 15, 2014 8:11 am

It's because others are not beta testers unlike us.
we have statistics how many devices have upgraded. I don't want to argue about this, please let us concentrate on the remaining issues here. Let us discuss the release rather than nitpick

Do you also have statistics how many devices were downgraded? I'm just asking because from cca v6.7 most of my upgrades goes like:
Upgrade to latest -> Check what still was not fixed / how many new bugs were introduced -> Downgrade to last working version.
- I had problems with IPsec in earlier v6 version. After some time I gave up and built my IPsec on linux boxes.
- I had problems with CPU usage. Opened ticket, which was allegedly resolved, but there was no improvement in next release. I had to wait for 4 more versions to get rid of this.
- I had problem on RB2011s with ports disappearing from bridge after some upgrade. Fixed it manually, but if things would be working properly, I didn't had to.
- I have problems with CCRs crashing like there is no tomorrow. Had to replace one back with RB1100 as it's main router in one of my companies.
- I have problems with multiple SSTP client interfaces not coming up properly after reboot.
- I have problems (as many others) with 6to4 tunnels. Surprisingly, in 6.22 they're working at least for incoming connections but still not for outgoing.

So, yeah. Out of cca 200 devices which I have, 180 of them I'm able to upgrade without problems. But those have just DHCP, WiFi and other common stuff which any TP-Link can do as well. The rest 20, those are the core and infrastructure devices where the reliability goes above all. And those are the failing ones with every release.

I also do not understand why there isn't any extensive functional testing, regression testing or any other best practices for large-scale development in place. Like this, it really looks like there is just some git repo and after few commits and a glass of beer someone just says "OK guys, I'm feeling lucky, let's release".

Most people having prolems are in this forum, you can see how many there are, less than 10.

There are now definitely more than 10. And much more out there who have no idea about any forum or support or they simply gave up already. I certainly don't blame them.

Sat Nov 15, 2014 1:20 pm

None can have statistics about my updates or downgrades as I do not use the download button for it. Because it is not reliable and because I always use selected packages only instead upgrade pack.

brainy · Sat Nov 15, 2014 1:30 pm

Simple VRRP Setup does not work anymore ... it keeps flapping between backup and master ...

warrenisarobot · Sat Nov 15, 2014 4:28 pm

6.22 has broken the GRE tunnel we were using for redundancy, and we are getting the new warning saying "transmit loop detected ... downing interface for 60 seconds". This is a tunnel between two locations where the first location has 2 internet providers (2 different networks on 2 interfaces) and the second has one internet provider. The first location has the two tunnels that share the same destination IP, but difference source IPs. This is the location getting the failure. The second location has two tunnels with different destination IPs, but with the same source IP. This is not having problems.

What kind of loop is this supposed to be detecting? What can I do to fix this? I was having stability issues on 6.08, but switching to 6.22 breaks the tunnel setup and there is no way provided to downgrade to a version between the two.

joegoldman · Sat Nov 15, 2014 10:52 pm

MY GOD - to all the whingers - if a current or older version is working for you - DO NOT UPGRADE.

ONLY UPGRADE IF THE NEW VERSION FIXES A PROBLEM OR INTRODUCES A NEEDED FEATURE.

As any good net-ops team will do though - you should test your config in the lab before pushing out to live.

The mention above about partitioning is great too, perfect resource for this. I have a 6.13 partition from earlier in the year still, as that was most stable at the time. Happy to push back to it at any time.

NathanA · Sun Nov 16, 2014 2:25 am

MY GOD - to all the whingers - if a current or older version is working for you - DO NOT UPGRADE.

ONLY UPGRADE IF THE NEW VERSION FIXES A PROBLEM OR INTRODUCES A NEEDED FEATURE.

As any good net-ops team will do though - you should test your config in the lab before pushing out to live.

I completely agree with everything you just said. However, at the same time, if you DO upgrade *because* the new version fixes a problem that you have been having, but it introduces a new problem in another area, then you are stuck between a rock and a hard place.

I am currently in this situation right now with two different routers (both with different problems): if I stick with an older version, there is a particular bug in both cases that is a constant headache both for me and for my customer to deal with, but if I upgrade to a version that fixes that particular bug, then an entirely new regression is introduced. So I'm darned if I do and darned if I don't. There is no one version out there that gives me a bug-free experience in either case; if there was, I would run it. And I think that is what most people are frustrated with: the number of new regressions that keep getting introduced whenever they do an upgrade (often at the suggestion of MikroTik support) in order to fight off a past regression. We are forced to choose the lesser of 2 evils.

-- Nathan

infused · Sun Nov 16, 2014 4:18 am

We normally wait 3-5 releases before upgrading. We have another unit on standby with the same config incase anything goes wrong. We also test it on another piece of identical hardware before upgrading.
So, your advantage is to wait for others to find the failures of that specific versions. If everybody thinks like you, MT will always fail with every customer (ISP).

That's not my problem.

You test it first, regardless.

pbr3000 · Sun Nov 16, 2014 4:29 am

MY GOD - to all the whingers - if a current or older version is working for you - DO NOT UPGRADE.

ONLY UPGRADE IF THE NEW VERSION FIXES A PROBLEM OR INTRODUCES A NEEDED FEATURE.

As any good net-ops team will do though - you should test your config in the lab before pushing out to live.
I completely agree with everything you just said. However, at the same time, if you DO upgrade *because* the new version fixes a problem that you have been having, but it introduces a new problem in another area, then you are stuck between a rock and a hard place.

I am currently in this situation right now with two different routers (both with different problems): if I stick with an older version, there is a particular bug in both cases that is a constant headache both for me and for my customer to deal with, but if I upgrade to a version that fixes that particular bug, then an entirely new regression is introduced. So I'm darned if I do and darned if I don't. There is no one version out there that gives me a bug-free experience in either case; if there was, I would run it. And I think that is what most people are frustrated with: the number of new regressions that keep getting introduced whenever they do an upgrade (often at the suggestion of MikroTik support) in order to fight off a past regression. We are forced to choose the lesser of 2 evils.

-- Nathan

Bingo! Exactly! (Sorry for the redundancy) And there is more in my case: I have two CCR1036 in lab to test the new versions. Get the production backups and restore to the test units and all works fine. Upgrade the production units gave me instant bricked routers.
So I can't trust in my lab anymore...

Alupis · Sun Nov 16, 2014 5:44 am

guys, calm down. did you see how fast they rolled from 6.21.1 -> 6.22? like 2 weeks. THEY ARE LISTENING AND ATTEMPTING TO FIX PROBLEMS!

There was a beta upgrade -- but I assume the people complaining here did not download it, try it, and report back problems -- so MT has zero/little complains on beta software and assume it's good --> push to live and now everyone complains.

read the changelog - if you don't need a feature/fix, don't upgrade if your setup is working fine. If you do, well, report problems back in a non-whiny way with the data necessary for MT to actually fix your problem. make sure you have a backup of your Know-Good config BEFORE you attempt an upgrade. And be ready to downgrade if you do run into trouble.

Simply complaining will not solve anything.

I'm starting to think the people complaining in this thread are the ones responsible for the installations pictured in this other thread: http://forum.mikrotik.com/viewtopic.php?f=2&t=31711

infused · Sun Nov 16, 2014 5:49 am

read the changelog - if you don't need a feature/fix, don't upgrade if your setup is working fine. If you do, well, report problems back in a non-whiny way with the data necessary for MT to actually fix your problem. make sure you have a backup of your Know-Good config BEFORE you attempt an upgrade. And be ready to downgrade if you do run into trouble.

The problem is, not everything is in the change log. Like the changes to multi core support.

Alupis · Sun Nov 16, 2014 6:09 am

read the changelog - if you don't need a feature/fix, don't upgrade if your setup is working fine. If you do, well, report problems back in a non-whiny way with the data necessary for MT to actually fix your problem. make sure you have a backup of your Know-Good config BEFORE you attempt an upgrade. And be ready to downgrade if you do run into trouble.
The problem is, not everything is in the change log. Like the changes to multi core support.

Even so, don't whine about it -- do something helpful.

I have absolutely no issues with my CCR's and high cpu usage with DNS like others are saying (so multi core support is just fine for me) If I did, I would submit a supout to support and let them debug the issue. That would help me, and it would help others with the same issue.

Simply whining doesn't solve anything.

infused · Sun Nov 16, 2014 8:21 am

read the changelog - if you don't need a feature/fix, don't upgrade if your setup is working fine. If you do, well, report problems back in a non-whiny way with the data necessary for MT to actually fix your problem. make sure you have a backup of your Know-Good config BEFORE you attempt an upgrade. And be ready to downgrade if you do run into trouble.
The problem is, not everything is in the change log. Like the changes to multi core support.
Even so, don't whine about it -- do something helpful.

I have absolutely no issues with my CCR's and high cpu usage with DNS like others are saying (so multi core support is just fine for me) If I did, I would submit a supout to support and let them debug the issue. That would help me, and it would help others with the same issue.

Simply whining doesn't solve anything.

Where was I whining?

I was telling people to test the new builds in a lab setup before deploying them to a production network. It's not a hard thing to do.

Petzl · Sun Nov 16, 2014 1:41 pm

Problems after upgrading to 6.22 with omnitik u5hnd

with my 3 test omnitiks the Wlan1 interface has changed to wlan2 , and configuration is gone.
Also had to add it back to the bridge interface ...

avantwireless · Sun Nov 16, 2014 5:13 pm

2shpn is still exhibiting the exact same failure mode in high noise environment. Every so on all clients are detached until reboot. Have to have a ping watchdog on most reliable client. That also prevents the watchdog on the ethernet port for other hangs...

ba7abak · Sun Nov 16, 2014 8:35 pm

What's new in 6.22 (2014-Nov-11 14:46):
*) new RouterBOOT firmware for Metal 2SHPn to improve wireless stability;
.

i have Metal 2SHPn after this update the CCQ 71/50 % before the upgrade 100/100 %
i see the note firmware improve wireless stability it's not make

IntrusDave · Sun Nov 16, 2014 9:04 pm

CCR series still have problems with randomly rebooting.

Which CCR? I have 4x CCR1009-8G-1S-1S+ and 2x CCR1016-12G, all running 6.22, none of them rebooting.

androns · Sun Nov 16, 2014 10:16 pm

951G-2HnD with 6.22

What the hell?

I inserted USB flash drive (8Gb), formatted it (FAT32) and got a mess in files.

Cannot delete any of those files (because they don't exist obviously)

Also I don't know how to walk throught the directory structure in webfig ...

mt622_usb.jpg

denisun · Sun Nov 16, 2014 11:25 pm

I have many disconnections from my pppoe-client (bridge mode) with 6.22.

I downgrade to 6.20.

Mon Nov 17, 2014 8:29 am

951G-2HnD with 6.22

What the hell?

I inserted USB flash drive (8Gb), formatted it (FAT32) and got a mess in files.

Cannot delete any of those files (because they don't exist obviously)

Also I don't know how to walk throught the directory structure in webfig ...

mt622_usb.jpg

did you try to format the disk? maybe the files do actually exist, but are marked as "deleted" by some other OS

Rudios · Mon Nov 17, 2014 8:41 am

951G-2HnD with 6.22

What the hell?

I inserted USB flash drive (8Gb), formatted it (FAT32) and got a mess in files.

Cannot delete any of those files (because they don't exist obviously)

Also I don't know how to walk throught the directory structure in webfig ...

mt622_usb.jpg

I noticed this too!.
When the USB disk is plugged in a windows machine, the files are there too!
After a format on Windows (NOT quick) the disk was empty.
Another thing I noticed is that the number of the disk keeps on counting. By using the same USB device, I'm already at disk5
Also, the file icons of all the disks remain, even when the device is unplugged. After reboot all are gone, and when re-inserting the device only the last used (disk5 in my case) will be shown again.

keema · Mon Nov 17, 2014 9:11 am

Why upgrade that critical router before testing by yourself on other non critical place ?
I first upgrade my home MT router everything working then update non critical part of network and after that update critical part of network. I know people using today 2.9.27 or 3.30 or 4.17 or 5.26 or 6.22 and there are happy with that version.

Don't upgrade before testing on other non critical place.
RouterBoard have option to make partition make two partition one for testing other with working system tested before is something wrong happens just switch back to tested working system.
http://wiki.mikrotik.com/wiki/Manual:Partitions

If is something very very important upgrade must me planed, tested, prepared with replaced device ready to replace.... upgrading critical part of network without precise planing is crazy. It is nice button upgrade just to try sorry but on some places I can afford that luxury.

This can be argued. Home routers usually don't have as complex settings as company routers do. And it is almost never the most commong router thing that is not working but somethung more specific but still very important.

androns · Mon Nov 17, 2014 10:31 am

951G-2HnD with 6.22

mt622_usb.jpg
did you try to format the disk? maybe the files do actually exist, but are marked as "deleted" by some other OS

Yes, I've tried to format several times it while plugged in the router. And it shows 100% ok and bunch of these files.
So maybe I will try to format ir (not quick format) on my windows machine and then check how it looks in router.

yep .. and that disk1 ... diskN keeps increasing and i cannot remove any of those disks.

Mon Nov 17, 2014 3:24 pm

I've ugraded a RB1200 in one side of a wireless link with moderate load and see increased und changing ping times to the direct attached ethernet interface of the wireless bridge

[admin@gw35] > ping 192.168.54.162
HOST SIZE TTL TIME STATUS
192.168.54.162 56 64 16ms
192.168.54.162 56 64 3ms
192.168.54.162 56 64 10ms
192.168.54.162 56 64 12ms
192.168.54.162 56 64 1ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 13ms
192.168.54.162 56 64 8ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 20ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 1ms
192.168.54.162 56 64 1ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 10ms
192.168.54.162 56 64 2ms
sent=18 received=18 packet-loss=0% min-rtt=0ms avg-rtt=5ms max-rtt=20ms

The RB2011 6.15 on the other side of the link does not show this problems:
[admin@gw43] > ping 192.168.54.162
HOST SIZE TTL TIME STATUS
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
192.168.54.162 56 64 0ms
sent=14 received=14 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms

Ethernet is 1000FDX and no error shown on the ethernet statistics of RB1200 and Wireless Bridge Ethernet.

Queues is only hardware queue and fastpath is allowed. CPU usage is low and link usage is low.

martinp · Mon Nov 17, 2014 8:34 pm

IPv6 is broken in this release. Configured address showed up as "invalid" in /ipv6 address. Downgraded to 6.19 again, everything works fine.

pants6000 · Tue Nov 18, 2014 8:05 am

FWIW, IPv6 seems to be working fine for me on 6.22.

zsteva · Tue Nov 18, 2014 12:47 pm

/toot torch dont show src-address

http://imgur.com/GuYk8Ds

its works just fine on 6.18.

Alfabi · Tue Nov 18, 2014 2:39 pm

I have problems in address-lists and dhcp from 6.19 and all higher versions later. I submitted a report of the problem (Ticket#2014110466000984) to the v6.21.1. I tested the new version 6.22 right now and surprise: nothing has changed.
I have heard people talk here in "BugOS" to refer to "RouterOS" and tend to agree with them, unfortunately.

im have same problem -(

noyo · Tue Nov 18, 2014 3:21 pm

What's New in 6.23rc1 ?
CHANGELOG is empty

iqt · Tue Nov 18, 2014 3:48 pm

/toot torch dont show src-address

http://imgur.com/GuYk8Ds

its works just fine on 6.18.

Confirmed, address display for /tool torch is somehow messy (src-address is 192.168.230.1, dst-address not shown). The display within Winbox is ok.

[admin@MikroTik] > /tool torch interface=WAN dst-address=0.0.0.0/0                      
MAC-PROTOCOL    SRC-ADDRESS                                      TX         RX TX-PACKETS RX-PACKETS
ip                                                          2.4kbps    1840bps          2          2
                                                            2.4kbps    1840bps          2          2

[admin@MikroTik] > /tool torch interface=WAN src-address=0.0.0.0/0                      
MAC-PROTOCOL            TX         RX TX-PACKETS RX-PACKETS
ip                 4.2kbps     920bps          2          1
                   4.2kbps     920bps          2          1


[admin@MikroTik] > /tool torch interface=WAN src-address=0.0.0.0/0 dst-address=0.0.0.0/0
MAC-PROTOCOL    SRC-ADDRESS                                      TX         RX TX-PACKETS RX-PACKETS
ip              192.168.230.1                               4.6kbps     920bps          2          1
                                                            4.6kbps     920bps          2          1

dcuk · Tue Nov 18, 2014 11:12 pm

In the interests of making Mikrotik aware of what is happening, with 6.22 I'm seeing the following issues with an RB450G:

MicroSD card has completely disappeared from system, no longer showing under disks or stores. This last appeared correctly in version 6.18

Ethernet stats are zero for all slave ports configured as hardware switchports (ether5-trunk is the master port) and extended information is missing:

/interface ethernet switch port> print stats
                      name:  ether2-skybox ether3-tv ether4-ap  ether5-trunk switch1-cpu
            driver-rx-byte:              0         0         0 1 359 887 146
          driver-rx-packet:              0         0         0     6 157 431
            driver-tx-byte:              0         0         0 7 683 300 763
          driver-tx-packet:              0         0         0     8 133 653
                  rx-bytes:              0         0         0             0
              rx-too-short:              0         0         0             0
                     rx-64:              0         0         0             0
                 rx-65-127:              0         0         0             0
                rx-128-255:              0         0         0             0
                rx-256-511:              0         0         0             0
               rx-512-1023:              0         0         0             0
              rx-1024-1518:              0         0         0             0
               rx-1519-max:              0         0         0             0
               rx-too-long:              0         0         0             0
              rx-broadcast:              0         0         0             0
                  rx-pause:              0         0         0             0
              rx-multicast:              0         0         0             0
              rx-fcs-error:              0         0         0             0
            rx-align-error:              0         0         0             0
               rx-fragment:              0         0         0             0
               rx-overflow:              0         0         0             0
                  tx-bytes:              0         0         0             0
                     tx-64:              0         0         0             0
                 tx-65-127:              0         0         0             0
                tx-128-255:              0         0         0             0
                tx-256-511:              0         0         0             0
               tx-512-1023:              0         0         0             0
              tx-1024-1518:              0         0         0             0
               tx-1519-max:              0         0         0             0
               tx-too-long:              0         0         0             0
              tx-broadcast:              0         0         0             0
                  tx-pause:              0         0         0             0
              tx-multicast:              0         0         0             0
               tx-underrun:              0         0         0             0
              tx-collision:              0         0         0             0
    tx-excessive-collision:              0         0         0             0
     tx-multiple-collision:              0         0         0             0
       tx-single-collision:              0         0         0             0
     tx-excessive-deferred:              0         0         0             0
               tx-deferred:              0         0         0             0
         tx-late-collision:              0         0         0             0

Similarly on the Ethernet interfaces directly:

/interface ethernet> print stats
                      name:  ether1-gateway ether2-skybox ether3-tv ether4-ap  ether5-trunk
            driver-rx-byte:   7 288 415 796             0         0         0 1 361 018 164
          driver-rx-packet:       8 072 759             0         0         0     6 165 323
            driver-tx-byte:     831 390 476             0         0         0 7 692 641 941
          driver-tx-packet:       5 676 361             0         0         0     8 143 470
                  rx-bytes:                             0         0         0             0
              rx-too-short:                             0         0         0             0
                     rx-64:                             0         0         0             0
                 rx-65-127:                             0         0         0             0
                rx-128-255:                             0         0         0             0
                rx-256-511:                             0         0         0             0
               rx-512-1023:                             0         0         0             0
              rx-1024-1518:                             0         0         0             0
               rx-1519-max:                             0         0         0             0
               rx-too-long:                             0         0         0             0
              rx-broadcast:                             0         0         0             0
                  rx-pause:                             0         0         0             0
              rx-multicast:                             0         0         0             0
              rx-fcs-error:                             0         0         0             0
            rx-align-error:                             0         0         0             0
               rx-fragment:                             0         0         0             0
               rx-overflow:                             0         0         0             0
                  tx-bytes:                             0         0         0             0
                     tx-64:                             0         0         0             0
                 tx-65-127:                             0         0         0             0
                tx-128-255:                             0         0         0             0
                tx-256-511:                             0         0         0             0
               tx-512-1023:                             0         0         0             0
              tx-1024-1518:                             0         0         0             0
               tx-1519-max:                             0         0         0             0
               tx-too-long:                             0         0         0             0
              tx-broadcast:                             0         0         0             0
                  tx-pause:                             0         0         0             0
              tx-multicast:                             0         0         0             0
               tx-underrun:                             0         0         0             0
              tx-collision:                             0         0         0             0
    tx-excessive-collision:                             0         0         0             0
     tx-multiple-collision:                             0         0         0             0
       tx-single-collision:                             0         0         0             0
     tx-excessive-deferred:                             0         0         0             0
               tx-deferred:                             0         0         0             0
         tx-late-collision:                             0         0         0             0

oscar198810 · Wed Nov 19, 2014 1:50 am

Currently I have a problem with a CCR1009 + S1S1 with version 6.22, the simple queues dynamic and Static do not have a good performance.

I have configured PPPoE + EOIP + OSPF.

Previously had a RB1000AHX2 With 6.5v and all was well .

try installing the v6.5 version but change the CCR1009 iD Software and lost the license for which I had to return to the probe and the 6.22 but 6.17 to 6.21.1 .

oscar198810 · Wed Nov 19, 2014 2:21 am

Currently I have a problem with a CCR1009 + S1S1 with version 6.22, the simplest dynamic queues do not have a good performance.

I have configured PPPoE + EOIP + OSPF.

Previously had a RB1000AHX2 With 6.5vy all was well .

try installing the v6.5 version but change the CCR1009 iD Software and lost the license for which I had to return to the probe and the 6.22 but 6.17 to 6.21.1 .

travisnj · Wed Nov 19, 2014 4:56 pm

Have 2SHPn as well.

All the sudden the past two versions and even RC23 are all causing SSID not to be broadcasted or allow attaching UNTIL REBOOT...

This is happening now very very very often... Had to ROLL BACK TO LAST V.5 to gain stability of SSID/RADIO broadcasting..

2SHPn IS NOT FIXED, STILL LOOSING SSID/RADIO (I do not have CPU 50/100 issue.., Clients just cannot connect and do not see SSID)

MKabar · Thu Nov 20, 2014 1:19 am

OK, that's it. I am quiting with this upgrade quick fix trash. Whole RouterOS is just pile of error after errors.
I just try 6.22 for a few minutes and now I am back on 6.18 and I will never try any new version again or buy a new MikroTik.
I bought 951G-2HnD in the spring. I want some really good WiFi AP for my IT workroom.
With original 5.26 (I think) USB 2,5" 250 GB HDD (small handy home made NAS) doesn't work on Android smartphone or tablet. Only some errors with lots of nonsence number.
With 6.xx it's start to work on Android, but on the Windows 7 (all my systems are Win7) it was really painfull, because it work only if you logged in Winbox and change some SMB file sharing settings (number of user etc). After clean star it was working for a while, but after Win7 hibernation, no way without login to Winbox.
FINALLY versin 6.17 fix that. but it was buggy and router died after couple shutoff (I disconned all electricity in all devices for the night).
So I managed to fix that through PXE boot.
With version 6.18 USB HDD was working almost fine like a NAS from computers and android devices.
But sometimes, it's show wrong amount of space left on HDD, but only sometimes. And manytimes all folders (except for web-proxy2 and lost+found) are suddenly gone and you have to wait for sometimes couple of minutes or log to the WInbox to get access for your folders and files back
I try 6.20 and it was working, little less folder disappearence, but show everytime only 9 MB space left, wchich was nonsence. But I was using 6.20 for the last two monthor something like that.
Today I try 6.22 and even 6.23 RC afterwards, but my HDD was gone, nothing worked, It didn't even show any HDD connected.
Seriously, do you think, that's normal? Why do you keep changing or corrupting something that worked OK?
You fix couple of error and make dozens new one. A milion versions but nothing stable and usable without problems.
Exacly the same think like Asus motherboards BIOS back in 2005-2007. Since 2008 I am using Gigabyte motherboars only and my
constant problems with BIOS (HW compatibility, unstability, error etc. etc.) are gone forever. No more Asus for me.
So no more MikroTik for me?
SMB and USB HDD NAS functionallity should work like a charm without any problems. Do it something wit it FINALLY!!! Thanks.

Thu Nov 20, 2014 1:16 pm

I am sorry that you had to experience this, yes, you are right, we are working on some changes for the HDD mounting software in RouterOS, and it seems, that all your issues are related to that.

We are aware of the remaining problems, and are attempting to fix them.

Mendesvel · Thu Nov 20, 2014 5:10 pm

"Normis",

It's not you... it's me...

And all the other problems and things that broke during all the other updates or that never really worked well...

CCR performance, multi threading, Memory Leaks, IPSEC issues, downgrade issues, upgrade issues, stability issues, queues, routing, firewalling, watchdog issues, kernel panics... i could definitely stay here for hours

I know that there are circumstances for all in life, but for me that work with more than 1K of your equipment's it's all getting to that point that i have to admit... I like Mikrotik very much and all the wireless paraphernalia is quite nice.

But i miss my other friends, those that have R&D and don't use the customer as a department (good move by the way less employees)
Those that are more expensive, but really have asics, application specific integrated circuits you know?
MKT is really cheap compared to my friends, but i'm tired of processed food.

Well all that and what will break on 6.23...

I know that the answer will be that all your are hardly working for a "better OS"

and you know what I'll probably do... flash them with something nice... something different... I'll think of something... don't worry..

steen · Thu Nov 20, 2014 6:47 pm

Hello Folks!

60% of our devices successfully updated to RoS6.22, rock solid for a week: rb333, rb411,rb433,rb600,rb750,crs and ccr. Remaining will be taken upcoming weekend.

kubik256 · Thu Nov 20, 2014 7:08 pm

Why upgrade that critical router before testing by yourself on other non critical place ?
I first upgrade my home MT router everything working then update non critical part of network and after that update critical part of network. I know people using today 2.9.27 or 3.30 or 4.17 or 5.26 or 6.22 and there are happy with that version.

Don't upgrade before testing on other non critical place.
RouterBoard have option to make partition make two partition one for testing other with working system tested before is something wrong happens just switch back to tested working system.
http://wiki.mikrotik.com/wiki/Manual:Partitions

If is something very very important upgrade must me planed, tested, prepared with replaced device ready to replace.... upgrading critical part of network without precise planing is crazy. It is nice button upgrade just to try sorry but on some places I can afford that luxury.

Very clever, but you really think that I didn't test new version before I upgrade a critical router?
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.

So next time please try to think before post some stupidity

jaykay2342 · Fri Nov 21, 2014 12:22 am

Very clever, but you really think that I didn't test new version before I upgrade a critical router?
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.

So next time please try to think before post some stupidity

Why do you the update of a critical router not during a maintenance windows? Even a tiny configuration change to a critical router i would only do during a maintenance windows having an implementation- and a rollback-plan. So if it is not working i roll back. For systems that are critical i have spare hardware. Those hardware is also be used for tests in the lab.

If i'm afraid something breaks i do a real test:
1. Export the config from the live system.
2. Replace the IPs with the ones from the test range. Just a search/replace with a text editor.
3. Import the new config into the test/spare device.
4. Do the planned change/upgrade on the test device.

Over all i agree that MT can improve the testing before they release a version. Some bugs are visible without a special config and should be found by doing basic tests.

visalink · Fri Nov 21, 2014 3:06 am

Hello Folks!

60% of our devices successfully updated to RoS6.22, rock solid for a week: rb333, rb411,rb433,rb600,rb750,crs and ccr. Remaining will be taken upcoming weekend.

Steen, you are a partner of Mikrotik?
Or you're a lucky guy.

visalink · Fri Nov 21, 2014 3:08 am

Why upgrade that critical router before testing by yourself on other non critical place ?
I first upgrade my home MT router everything working then update non critical part of network and after that update critical part of network. I know people using today 2.9.27 or 3.30 or 4.17 or 5.26 or 6.22 and there are happy with that version.

Don't upgrade before testing on other non critical place.
RouterBoard have option to make partition make two partition one for testing other with working system tested before is something wrong happens just switch back to tested working system.
http://wiki.mikrotik.com/wiki/Manual:Partitions

If is something very very important upgrade must me planed, tested, prepared with replaced device ready to replace.... upgrading critical part of network without precise planing is crazy. It is nice button upgrade just to try sorry but on some places I can afford that luxury.
Very clever, but you really think that I didn't test new version before I upgrade a critical router?
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.

So next time please try to think before post some stupidity

+1

npero · Fri Nov 21, 2014 9:01 am

Very clever, but you really think that I didn't test new version before I upgrade a critical router?
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.

So next time please try to think before post some stupidity

kubik256 and visalink maybe I am stupid but for now update dozen of router on 6.22 and all my routers working maybe because I am stupid and try to help you.
Also nice answer for anyone try to help you with this answer you can expect someone to help you

.

Also next time thing before write something like this for people on forum try to solve your problem.

Good lucky to kubik256 and visalink

Fri Nov 21, 2014 11:39 am

Have 2SHPn as well.

All the sudden the past two versions and even RC23 are all causing SSID not to be broadcasted or allow attaching UNTIL REBOOT...

This is happening now very very very often... Had to ROLL BACK TO LAST V.5 to gain stability of SSID/RADIO broadcasting..

2SHPn IS NOT FIXED, STILL LOOSING SSID/RADIO (I do not have CPU 50/100 issue.., Clients just cannot connect and do not see SSID)

Please upgrade the RouerBoard firmware to v3.19 and check if the situation gets better.

AlecM · Fri Nov 21, 2014 5:31 pm

I have the RB2011UiAS-2HnD, just bought it. I upgraded to v6.22 RouterOS, and now using the WebFig on Google Chrome, OSX Yosemite, initial configuration goes correctly but then in quick after configuring my wireless access point I'm seeing "no_country_set" and am unable to configure anything related to wireless. Winbox on my virtual machine works perfectly aside from crashing sometimes, shows all the configuration.

steen · Sat Nov 22, 2014 10:09 am

Hello Folks!

All out devices are now successfully upgraded to RoS6.22 and latest firmware for each device, thats say:
RB333,
RB411,
RB433,
RB600,
RB750,
RB751U-2HnD,
RN2011 UAS-2HnD,
SXT-5D,
SXT G-5HnD,
SEXTANT(RB711G-5HnD, RB711-5HnD),
CCR1016-12G,
CRS125-24G-1S.

All systems working normally as far we can see.

Patching/Upgrading was made in two rollouts, two different cities using "The Dude", on first a few, and then many at time, going back to them and upgrade firmware and so on.

xocolate · Sat Nov 22, 2014 10:01 pm

guyz,

my 951Ui-2HnD, updated to 6.22 from 6.20

start lose and high ping on wired connections.
also i can't update firmware to 6.19 from 6.18. router just accidentally rebooted right after i press update in inbox.

downgraded to 6.20. all fine.

whats wrong?

rftnon · Sun Nov 23, 2014 5:54 am

I have a problem after the update to 6.20 and 6.22

The problem in the PPPoE

Any Script Related Abute PPPoE Monitor IP change Not Work after the update to 6.20 and 6.22 as the connection Disconnected or downlink

this script working before the update to 6.20 and 6.22
this code send mail thin PPPoE Disconnected by another ISP by PCC Service

Code :

/system script add name="PPPoEmonitorIPchange" source={

:global currentIP1;
:global newIP1 [/ip address get [find interface="pppoe-ISP1"] address];

:if ($newIP1 != $currentIP1) do={
:put "ip address $currentIP1 changed to $newIP1";
:set currentIP1 $newIP1;
:if ([:pick $newIP1 0 8] = "192.168.") do={
/tool e-mail send to="mypersonalemail@gmail.com" subject=("Disconnected - ISP1") body=("$currentIP1")
} else={
/tool e-mail send to="mypersonalemail@gmail.com subject=([/ip address get [find where interface="pppoe-ISP1"] address] . " - ISP1") body=("$currentIP1")
}
}

/system scheduler add name=IPcheck interval=1m on-event=PPPoEmonitorIPchange

infused · Sun Nov 23, 2014 11:05 pm

Very clever, but you really think that I didn't test new version before I upgrade a critical router?
I have tested it on 3 other Routerboards... there is all ok, but on this very important router it ***** everything.

So next time please try to think before post some stupidity
Why do you the update of a critical router not during a maintenance windows? Even a tiny configuration change to a critical router i would only do during a maintenance windows having an implementation- and a rollback-plan. So if it is not working i roll back. For systems that are critical i have spare hardware. Those hardware is also be used for tests in the lab.

If i'm afraid something breaks i do a real test:
1. Export the config from the live system.
2. Replace the IPs with the ones from the test range. Just a search/replace with a text editor.
3. Import the new config into the test/spare device.
4. Do the planned change/upgrade on the test device.

Over all i agree that MT can improve the testing before they release a version. Some bugs are visible without a special config and should be found by doing basic tests.

Pretty much this. You need to duplicate the device. As much as a pain in the ass that is to do. We don't even make changes to our core routers during business hours, let alone any upgrade.

napismizpravu · Mon Nov 24, 2014 7:57 am

Work is underway to correct the errors of work with discs that have arisen since version 6.20?
latest functionality works with disks was in version 6.19

discovered another bug,
smb deleted files ... USB Flash 8GB free space 144 MB samba info > delete 1,2 GB dat > smb info free space 144 MB / info free space winbox disk list 1,3 GB free space
disk format table ext3 print RouterOS / Windows NTFS

http://forum.mikrotik.com/viewtopic.php ... vu#p449879
+ deleted error message in thread

<Google Translator>

raymonvdm · Mon Nov 24, 2014 6:06 pm

I also just upgrade from 6.19 to 6.22 and now my 6to4 tunnels are broken (SIXXS) the are running / not running

And the both have a IPv6 static route to keep the ping going bacause i don`t always use them since my provider sometimes gives me Native IPv6 when it is not broken

astefan · Tue Nov 25, 2014 12:17 am

What about this problem?
http://forum.mikrotik.com/viewtopic.php?f=2&t=86119

If you have packet loss in all versions, maybe there is some sort of hardware problem? if you have the chance, try another machine or at least other NIC
No, we have packet loss only on version 6.8-6.22.Versions 6.5-6.7 works stable. After 20-30 minutes MT start drops packet on all interfaces. In log file we see next message "105 (no buffer space available)". We try start VM on next servers:
1. Supermicro X8DTT 12CPUs x 2.4 GHz Processor Type Inter(R) Xeon(R) CPU E5645 @ 2.40GHZ
Intel Corporation 82576 Gigabit Network Connection

I have problem with Intel Corporation 82576 Gigabit Network card after upgrade to: 6.15, 6.19, 6.22 MT lost 2-5% packet on this interface. 5.26 works fine

mercury13 · Tue Nov 25, 2014 8:23 pm

Hi to All!

Please, give a torrent file for RoS6.20

napismizpravu · Tue Nov 25, 2014 10:57 pm

What's new in 6.23rc7 (2014-Nov-25 08:26):

*) files - allow to move files between different disks in winbox;
*) dhcpv4 server - fix adding address lists;
*) 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;

RB433UAH
6.20rcX -6.23rc7 persistent problem with USB Flash = not working proxy cache + free space 0 B + samba error (FTP access via FTP to disk is okay)

upgrade RouterOS ... correction error disk:
write name disk1 (default no name) > format USB FLASH - ext3 > disable proxy > enable proxy > reboot (if it fails, then repeat the process)

Version 6.19 errors with working with disks are not

rado3105 · Wed Nov 26, 2014 2:33 am

local tx, rx limits during bandwitch test dont limit test...

lunchboxrts · Wed Nov 26, 2014 5:32 am

Wireless clients randomly stop transmitting when connected to R11e-5HacD. Only fix is to disconnect and reconnect. Tested Yoga 3 Pro, iPad mini, Macbook pro, Apple tv, Netgear PTV3000, and Droid turbo. Also tried all the latest betas with the same results.
(the card is in a 912UAG-2HPnD)

raktim · Wed Nov 26, 2014 5:26 pm

I upgraded to 6.22 also firmware, but problem of Metal 2Shpn has not solved yet. I can't connect from 30 meters distance.

Jeanluck · Thu Nov 27, 2014 1:04 pm

Upgrading Omnitik from 5.24 to 6.13 works fine.
But after that, upgrade from 6.13 to 6.22 delete all my wlan1 configuration, exactly in the same way that 5.26 to 6.14.....

Thu Nov 27, 2014 1:09 pm

Upgrading Omnitik from 5.24 to 6.13 works fine.
But after that, upgrade from 6.13 to 6.22 delete all my wlan1 configuration, exactly in the same way that 5.26 to 6.14.....

What kind of configuration was deleted? Give a few examples what was lost

antwal · Thu Nov 27, 2014 5:39 pm

6to4 tunnel NO fixed !!!

Router OS 6.22
6.22.JPG
Router OS 6.19 (6to 4 work OK)
6.19.JPG

Hi miszak,

I have same problems; you can post the ipv6 configuration?

for me, working only with version 6.15; have some problems with 6.20.

Thanks.

raktim · Fri Nov 28, 2014 7:20 am

**Metal 2Shpn is not working in 2GHz-B/G/N mode . it works only in B/G mode.
**Smart Phones , wifi usb Dongles & ip cameras are not connected with Metal 2Shpn @ short or long distance.

Fri Nov 28, 2014 1:13 pm

6to4 tunnel NO fixed !!!

Router OS 6.22
6.22.JPG
Router OS 6.19 (6to 4 work OK)
6.19.JPG

Hi miszak,

I have same problems; you can post the ipv6 configuration?

for me, working only with version 6.15; have some problems with 6.20.

Thanks.

Please contact our support department. Send your supout.rif file/s from latest version. We have tested 6to4 and it works with correct configuration.

If there is something specific in your configuration what does not allow to create connection, then we would definitely like to fix it.

http://www.mikrotik.com/support.html

rado3105 · Fri Nov 28, 2014 5:24 pm

contrary to v6.19 much lower wirelles throughoutput (2 times less sometimes), bad wireless stability, bandwitch test not working correctly....

Sob · Sat Nov 29, 2014 9:05 pm

Upload 6to4bug.rsc with following content (change the addresses of course) to router:

ros code

/ip address
add address=AA.BB.CC.DD/24 interface=ether1
/ip route
add gateway=AA.BB.CC.GG
/interface 6to4
add local-address=AA.BB.CC.DD mtu=1480 name=6to4
/ipv6 address
add address=2002:AABB:CCDD::1/16 advertise=no interface=6to4
/ipv6 route
add distance=1 dst-address=2000::/3 gateway=::192.88.99.1%6to4

Reset config:

ros code

/system reset-configuration run-after-reset=6to4bug.rsc

And then try to ping some IPv6 address:

ros code

[admin@MikroTik] > /ping address=2002:ca0c:1dea::1 count=1 
HOST                                     SIZE TTL TIME  STATUS                   
2002:59b9:e186::1                         104  64 0ms   hop limit exceeded       
    sent=1 received=0 packet-loss=100% 

[admin@MikroTik] > /ping address=2a02:610:7501:1000::2 count=1
HOST                                     SIZE TTL TIME  STATUS                   
                                                        no route to host         
    sent=1 received=0 packet-loss=100%

This is how it looks on 6.22, pinging other 6to4 address fails with "hop limit exceeded", native one fails with "no route to host". It works fine on 6.19 and lower.

Petzl · Sun Nov 30, 2014 12:05 am

Upgrading Omnitik from 5.24 to 6.13 works fine.
But after that, upgrade from 6.13 to 6.22 delete all my wlan1 configuration, exactly in the same way that 5.26 to 6.14.....

Same problem i have, sometimes ....

it looks like it has found a new wlan adapter ... and lost the ols one

keema · Mon Dec 01, 2014 9:58 am

Hello Folks!

60% of our devices successfully updated to RoS6.22, rock solid for a week: rb333, rb411,rb433,rb600,rb750,crs and ccr. Remaining will be taken upcoming weekend.
Steen, you are a partner of Mikrotik?
Or you're a lucky guy.

My thoughts exactly.

Mon Dec 01, 2014 1:05 pm

kubik256, visalink

Are you able to provide us with support output file or remote access, when problem is present?

santa · Mon Dec 01, 2014 1:13 pm

Any details on this one?

*) dhcpv4 server - fix adding address lists from radius;

Mon Dec 01, 2014 4:26 pm

Wireless clients randomly stop transmitting when connected to R11e-5HacD. Only fix is to disconnect and reconnect. Tested Yoga 3 Pro, iPad mini, Macbook pro, Apple tv, Netgear PTV3000, and Droid turbo. Also tried all the latest betas with the same results.
(the card is in a 912UAG-2HPnD)

Please try to install RouterOS v6.23rc10 and test if the issue is fixed as we have fixed only issue regarding 802.11ac driver.

Mantic · Tue Dec 02, 2014 1:47 am

I deployed 2 new 750UP's on our network with v6.22. They are configured with OSPF between the two, then on one OSPF to another router. For some reason, the last leg in that chain never got a full OSPF route. I ended up downgrading both to 6.19 and they work fine now.

Configuration:

Router A: a 750UP v6.22 OSPF connected to:
Router B: a 750UP v6.22 OSPF connected to:
Router C: a 2011UiAS v6.12

OSPF between B and C worked as all routes were being shared from C to B. It failed between A and B as they would neighbor up just fine, but the only routes shared was the /29 shared between them. No other routes would get pushed to A. I tried rebooting both and even tried bridging them together, but nothing would work and I was short on time. Downgrading did the trick w/ the exact same configuration. :S Luckily these were new routers and had no users on them.

EDIT: I have 2 more 750UPs I could setup in a lab environment and see if I couldn't reproduce the issue. Anyone interested?

keema · Tue Dec 02, 2014 8:17 am

Wireless clients randomly stop transmitting when connected to R11e-5HacD. Only fix is to disconnect and reconnect. Tested Yoga 3 Pro, iPad mini, Macbook pro, Apple tv, Netgear PTV3000, and Droid turbo. Also tried all the latest betas with the same results.
(the card is in a 912UAG-2HPnD)
Please try to install RouterOS v6.23rc10 and test if the issue is fixed as we have fixed only issue regarding 802.11ac driver.

Try, test and report back! LOL

santa · Tue Dec 02, 2014 9:32 am

EDIT: I have 2 more 750UPs I could setup in a lab environment and see if I couldn't reproduce the issue. Anyone interested?

Everyone, I believe

.

wrobli · Tue Dec 02, 2014 10:21 am

Hi.
When I update link to 6.22 witch wirelessfp my link loss packet randomly downgrade to 6.12 no problem.

Tue Dec 02, 2014 1:20 pm

Hi.
When I update link to 6.22 witch wirelessfp my link loss packet randomly downgrade to 6.12 no problem.

Please provide more detailed info on this problem to support@mikrotik.com and include a support output file.

lunchboxrts · Tue Dec 02, 2014 5:29 pm

Wireless clients randomly stop transmitting when connected to R11e-5HacD. Only fix is to disconnect and reconnect. Tested Yoga 3 Pro, iPad mini, Macbook pro, Apple tv, Netgear PTV3000, and Droid turbo. Also tried all the latest betas with the same results.
(the card is in a 912UAG-2HPnD)
Please try to install RouterOS v6.23rc10 and test if the issue is fixed as we have fixed only issue regarding 802.11ac driver.

So far so good. No interface lockups but still to early to call it.

Bonz123 · Tue Dec 02, 2014 9:42 pm

Hi

I Have a small problem to configure queues for large quantity of IP's!

for 10 ore 20 ore 50 adreses it's ok to use simple queue, but if need to configure about 500 IP's (all of them is reserved to mac:) who i need to configure in different DHCP adress pools and download speeds + I need a time limits
I tell you- it's nightmare!
Try to use time shedule, but have a problem in weekends + i need about 8 shedules each working day. I have idea and hope it's will bee introduced.

Solution:
Maybe it's possible define adresses in ''Target'' ore ''Dst" from-to example: 192.168.7.48-192.168.7.254 in single queue?

Thanks!

antonu17 · Wed Dec 03, 2014 6:09 am

After upgrading to 6.22 I am getting warnings for "transmit loop detected, downing interface for 60 seconds" just as described in the logs. This is with a GRE tunnel that between two mikrotiks that was working before.

The tunnel is from one location with 2 internet providers to another location with a single internet provider. The first location has 2 tunnels setup with difference source addresses but the same destination address and the second location with the same source address but 2 different destination address. One of the tunnels works fine but the second is now useless. It was setup with a route to prefer our favored internet provider and to failover to the second if the primary's link failed.

What exactly is the loop detection supposed to do?

Hello!
I had the same problem, and found reason of problem. In my case transmit loop detection was triggered because i used route-mark for making routing decision. After i've made static routes for my gre destinations - problem disappeared.

Thu Dec 04, 2014 2:01 pm

After upgrading to 6.22 I am getting warnings for "transmit loop detected, downing interface for 60 seconds" just as described in the logs. This is with a GRE tunnel that between two mikrotiks that was working before.

The tunnel is from one location with 2 internet providers to another location with a single internet provider. The first location has 2 tunnels setup with difference source addresses but the same destination address and the second location with the same source address but 2 different destination address. One of the tunnels works fine but the second is now useless. It was setup with a route to prefer our favored internet provider and to failover to the second if the primary's link failed.

What exactly is the loop detection supposed to do?
Hello!
I had the same problem, and found reason of problem. In my case transmit loop detection was triggered because i used route-mark for making routing decision. After i've made static routes for my gre destinations - problem disappeared.

This problem should be fixed in version 6.23.

antwal · Thu Dec 04, 2014 7:06 pm

Sorry for the delay; This is the configuration as it has always worked up to version 6:15; then the new version no longer worked ...

This is my configuration:

/interface 6to4
add clamp-tcp-mss=no comment="Hurricane Electric IPv6" \
    local-address=<Static Public IPv4 Address> mtu=1280 name=sit1 remote-address=\
    <Server IPv4 Address>
/ip neighbor discovery
set sit1 comment="Hurricane Electric IPv6"
/ipv6 address
add address=<Client IPv6 Address> comment="IPv6 Gateway" interface=sit1
add address=<Routed /64> comment="IPv6 Network 1" interface=\
    ether2-master-local
add address=<Routed /64>1 comment="IPv6 Network 2" interface=\
    ether5-slave-local
/ipv6 firewall filter
add chain=input comment="Allow established connections" connection-state=\
    established
add chain=input comment="Allow related connections" connection-state=related
add chain=input comment="Router  Allow IPv6 ICMP" protocol=icmpv6
add chain=forward comment="Router  Allow IPv6 ICMP" protocol=icmpv6
add chain=input comment="Allow UDP" protocol=udp
add chain=forward comment="Allow HTTP" dst-address=\
    <server web>/128 dst-port=80 protocol=tcp
add action=log chain=input disabled=yes in-interface=sit1
add action=drop chain=input comment="Drop everything else"
add chain=forward comment="Allow any to internet" out-interface=sit1
add chain=forward comment="Allow established connections" connection-state=\
    established
add chain=forward comment="Allow related connections" connection-state=\
    related
add action=drop chain=forward
add action=log chain=output disabled=yes log-prefix="[DROP IPv6] " \
    out-interface=sit1
/ipv6 firewall mangle
add action=change-mss chain=forward in-interface=sit1 new-mss=1220 protocol=\
    tcp tcp-flags=syn tcp-mss=1221-65535
add action=change-mss chain=forward new-mss=1220 out-interface=sit1 protocol=\
    tcp tcp-flags=syn tcp-mss=1221-65535
/ipv6 nd
set [ find default=yes ] advertise-dns=yes hop-limit=64
/ipv6 route
add distance=1 gateway=<Server IPv6 Address>

Manual Route:

/ipv6 route 
add dst-address=::/0 gateway=<Server IPv6 Address>

Version 6.15:
- working

Versione 6.19:
- (reset all, and restore rsc) - Working

Version 6.20:
- bridge-local and ether2-master-local -> no route to host
- sit1 -> echo reply
- Clients -> get IPv6 but not working

Version 6.22:
- on IPv6 Address the ether2-master-local is always Invalid, the ether5-slave-local is valid
- sit1 working; others interfaces not.

Versione 6.23:
- same problems of 6.22

Solutions? I have sended always supout.rif.

Thanks.

Fri Dec 05, 2014 11:00 am

Thank you very much for your reports and help!
6.23 version is released!
viewtopic.php?f=2&t=91901