Page 1 of 1

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 12:30 pm
by Chupaka
in Terminal, '/interface print detail'
I can not see any details regarding report last link up/down time and link down count when i try to go by terminal with /interface print.
Is there something else to do?
what exactly do you see? here's mine output:
[admin@router] > interface print detail where name=sfp1
Flags: D - dynamic, X - disabled, R - running, S - slave 
 0  R  name="sfp1" default-name="sfp1" type="ether" mtu=1500 actual-mtu=1500 
       l2mtu=1590 max-l2mtu=10226 mac-address=00:00:00:00:00:01 fast-path=yes 
       last-link-up-time=nov/05/2014 13:12:29 link-downs=0 
[admin@router] > 

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 1:01 pm
by aTan
After update OpenVPN clients can't connect to updated server. On server log says TCP connection established and then it timeouts on a client (OpenVPN native or ROS client). supout is sent to support. Ticket#2014110666000355

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 3:19 pm
by tomaskir
We are also seeing increased CPU usage after upgrading to 6.21.1

Previous avg usage: 0.3%
New avg usage: 4%

This might not seem much, but its a 10x (ten-times, ten-fold) increase in CPU usage on the same config/load.

Image

[Ticket#2014110566000599]

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 3:45 pm
by Noa
CCR1009-8G-1S-1S+
firmware 3.13

After uprade to 6.21.1 reboots several times during the day without any messeges in log`s

Great release guys. Are you even tried to test this befor releasing?

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 3:56 pm
by Chupaka
Also downgrading downgrading does not work. Device just reeboting but after still have ros 2.21.1
and what's in Log? what exactly you do to downgrade?

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 4:04 pm
by Noa
Also downgrading downgrading does not work. Device just reeboting but after still have ros 2.21.1
and what's in Log? what exactly you do to downgrade?
Sorry, it is my mistake. I used just reboot item, not system -> pakeges -> downgrade

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 7:19 pm
by Sob
*) fixed 6to4 tunnels having inactive routes;
Not true, I'm affraid. This config (I'd say it's the most basic one) worked fine for years:

ros code

/interface 6to4
add local-address=213.211.xx.xx mtu=1480 name=6to4
/ipv6 address
add address=2002:d5d3:xxxx::1/16 advertise=no interface=6to4
add address=2002:d5d3:xxxx:80::1 interface=internal
/ipv6 route
add distance=1 dst-address=2000::/3 gateway=::192.88.99.1%6to4
But after upgrade from 6.19 to 6.21.1, routes do not work, both 2000::/3 and 2002::/16 claim to be unreachable:

ros code

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

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

 2 ADC  dst-address=2002:d5d3:xxxx:80::/64 gateway=internal
        gateway-status=internal reachable distance=0 scope=10
So back to 6.19 and it works again.

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 9:37 pm
by lucky79
Still cannot go lower than 6dB TX Power on RB922UAGS-5HPacD so have to stay on 6.19 where it is possible to go to 0. Will you guys fix it? Or nobody else having the problem?
In older RouterOS version the the 6db tx-power offset was not taken into the account. This problem is now fixed in latest RouterOS releases where it uses the correct tx-power value. Since the offset is 6db you can't get lower as you can't specify in the cards eeprom lower value than 0.
So does that mean with 6dB tx power the real output is also 6dB? If yes the maximum antenna gain connected legally to this device could only be 24dB in my country where 1W EIRP (30dBm) is allowed? Or what does this offset really mean?

And is this valid only for AC boards or also older N boards?

Thanks

Re: v6.21.1 released

Posted: Thu Nov 06, 2014 11:02 pm
by steen
Hello Folks!

Upgraded some more devices from RoS6.20 + boot 3.18 -> RoS6.21.1 + boot 3.19, this time CRS125-24G-1S using vlan trunks and access ports. Everything went smoothly no visible problems observed, whole procedure was completed within 5 minutes.
.

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 12:59 am
by ditonet
ROS 6.21.1 / RouterBOOT 3.19 on RB951Ui-2HnD.
Profiler permanently shows 'DNS' CPU usage over 80% and DNS resolver stops resolving after few hours.
After downgrade to 6.20 problem disappeared.

Regards,

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 8:27 am
by docmarius
On my RB1100AHx2 I got 40-60% unclassified CPU usage after upgrade (in idle).
Downgrade to 6.20 brings it down to 0 - 0.2%.

On other single core Atheros based boards, everything seems fine (750GL, 951G, Omnitik, CRS-125).

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 10:36 am
by tomaskir
On my RB1100AHx2 I got 40-60% unclassified CPU usage after upgrade (in idle).
Downgrade to 6.20 brings it down to 0 - 0.2%.

On other single core Atheros based boards, everything seems fine (750GL, 951G, Omnitik, CRS-125).
Email support, seems like the same problem I linked in
http://forum.mikrotik.com/viewtopic.php ... 50#p455257

On that CCR 2 cores are constantly on 50% CPU usage.

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 12:45 pm
by ivimail
WARNING
CCR1009-8G-1S-1S+
firmware 3.13

After uprade to 6.21.1 reboots several times during the day without any messeges in log`s

Great release guys. Are you even tried to test this befor releasing?
Same problem with same router, but with firmware 3.19. rebooted randomly after few minutes/hours after update. I just downgraded to 6.19 same day and reported to mikrotik support. waiting for an answer... Also I never could use microsd cards with this router, sometimes is recognized, sometimes nto, sometimes I can format it, sometimes not. latest firmware doesn't repair this problem and I don't have any valid response from support. is my ccr defective? usb disks can be used without any problem

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 2:14 pm
by dada
So does that mean with 6dB tx power the real output is also 6dB? If yes the maximum antenna gain connected legally to this device could only be 24dB in my country where 1W EIRP (30dBm) is allowed? Or what does this offset really mean?

And is this valid only for AC boards or also older N boards?

Thanks
my measurement says that the real card output is about 2.0-2.5dBm on each connector when set to 6dBm (ROS 6.20). The offset is only for new wireless chipsets I think.

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 2:29 pm
by janisk
lucky79 6to4 will be resolved in 6.22, you can get testing build if you like.

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 2:42 pm
by normis
Profiler permanently shows 'DNS' CPU usage over 80% and DNS resolver stops resolving after few hours.
it is fixed in the new v6.22, please wait until we release it

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 3:45 pm
by uldis
So does that mean with 6dB tx power the real output is also 6dB? If yes the maximum antenna gain connected legally to this device could only be 24dB in my country where 1W EIRP (30dBm) is allowed? Or what does this offset really mean?

And is this valid only for AC boards or also older N boards?

Thanks
my measurement says that the real card output is about 2.0-2.5dBm on each connector when set to 6dBm (ROS 6.20). The offset is only for new wireless chipsets I think.
The offset isn't used on all the new chipset boards.
Usually we use that for the boards where the total output power is more than 30db.

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 6:24 pm
by pants6000
Using webfig on 6.20, I can't correctly add a new DHCP network in IP/dhcp server/networks. The only field that will stay populated is the address field, the rest are cleared when I press apply. Tried from two different browsers. CLI/winbox work fine.

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 11:34 pm
by LinFor
On my RB1100AHx2 I got 40-60% unclassified CPU usage after upgrade (in idle).
Downgrade to 6.20 brings it down to 0 - 0.2%.
I have same problem with 6.21.1 and RB2011UAS-2HnD.
After reboot all is ok, but after few hours unclassified CPU usage increases to 100% and performance of the router decreasing with packet loss.

Re: v6.21.1 released

Posted: Fri Nov 07, 2014 11:54 pm
by johnvam
I upgraded our CCR1016-12S-1s+ from 6.13 to 6.21.1 and it was rebooted with no reason several times in day...

Also Watchdog is not creating supout file in order to send you info!!!

Rolled back to 6.13 thanks to second partition!

Re: v6.21.1 released

Posted: Sat Nov 08, 2014 1:41 pm
by hanty
After upgrade RB1100AHx2 from 6.20 to 6.21.1 I lose all of my LAN connections. All WAN was work properly.
I downgrade to 6.20 - OK. Please test your firmware before release.

Re: v6.21.1 released

Posted: Sat Nov 08, 2014 9:03 pm
by mousa1983
userman don't work
after rebot roter i loss connection with router
Why so much bug in new version!!?

Re: v6.21.1 released

Posted: Sat Nov 08, 2014 10:06 pm
by FernandoSuperGG
The LCD doesn't refresh bandwidth stats with PPP interfaces on RB2011 series if the interface goes down then up again. Never worked for me.
The LCD freezes with "no link".
When not, it does not shows bandwidth stats again, until a reboot.

Re: v6.21.1 released

Posted: Sun Nov 09, 2014 7:59 am
by mousa1983
What's new in 6.21 (2014-Oct-30 12:34):

*) userman - fix ~Your session has been reset due to inactivity~ error;

:( Problem is still remains and new problems occur
I downgrade router to 6.18

Re: v6.21.1 released

Posted: Sun Nov 09, 2014 10:24 am
by estdata
Please fix the igmp proxy stream. I have the lagg when I watch TV
support ticket: [Ticket#2014110866000137]

Re: v6.21.1 released

Posted: Sun Nov 09, 2014 1:27 pm
by poizzon
please check firewall.
got same issue when forgot block DNS requests on WAN interface .


Warning!

I just upgrade RB2011UAS-2HnD to 6.21.1 from v6.19 and my router CPU used 100%.
and I turn off all ether Port(ether3 Port is Console) but, Nothing had changed.

I sent a rif file to the mikrotik support email and I waiting for a reply.
Please do sufficient test, before the release.

Re: v6.21.1 released

Posted: Mon Nov 10, 2014 10:30 am
by Quicksivler
I upgraded our routers (all either 6.19 or 6.20).. worked fine but 3/4 of our omnitiks lost their wireless card configuration. When booting the wlan1 is gone and wlan2 now apears (there's only 1 wireless card in an omnitik) but is disabled and set to defaults. I restored from backup's but this is the only glitch I've had in 5 years of upgrading routerboards. My advice is if you are upgrading an omnitik, backup your wireless config and check anywhere (routing, IP's, etc) where the interface is listed.

Re: v6.21.1 released

Posted: Mon Nov 10, 2014 3:22 pm
by Robox
RB951G-2HnD
upgrade 6.7 to 6.21.1 - ok (include Firmware 3.19 )
downgrade 6.21.1 to 6.7 - ok

Re: v6.21.1 released

Posted: Mon Nov 10, 2014 3:58 pm
by strods
I upgraded our routers (all either 6.19 or 6.20).. worked fine but 3/4 of our omnitiks lost their wireless card configuration. When booting the wlan1 is gone and wlan2 now apears (there's only 1 wireless card in an omnitik) but is disabled and set to defaults. I restored from backup's but this is the only glitch I've had in 5 years of upgrading routerboards. My advice is if you are upgrading an omnitik, backup your wireless config and check anywhere (routing, IP's, etc) where the interface is listed.
Could you please write to out support email with description of this problem? Simple upgrade seems to be working fine. Maybe problem is caused by your specific configuration or version from which you did upgrade these devices. Please send supout file together with configuration of wireless interface. Also mention versions from which you did upgrade these devices.

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

Re: v6.21.1 released

Posted: Mon Nov 10, 2014 7:30 pm
by imildar
When do you fix 'inactive routes' in 6to4 tunnel?
It is still not working in 6.22 rc

Gogo pls :] ipv6 must be working

Now i made downgrade to 6.19

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 8:48 am
by djdrastic
Upgraded a RB951-2Hnd from 6.18 to 6.21.1 . Router would refuse any winbox access ("This application has requested the Runtime to terminate it in unusual way.
Please contact the application's support team for more information").
SSH / HTTP access would just result in a spinning cursor until the connection times out.
Upgrade was done locally via directly connected CAT5 cable so unlikely to be bad connectivity resulting in bad image.


Had to netinstall back to 6.18 to get it back in action.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 8:58 am
by normis
This forum also has automatic translation, see the button in bottom right corner.
About the other features, not sure how they are useful. Browsers have integrated "tweet this" buttons, why overload the forum with social media links?

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 10:09 am
by Deac
OK, normis:
The most useful features for me:
- Personal Bookmarks
- 'Solution'-marked posts
- Quick search for 'Solution'-marked posts

P.S.
Not only forum now.
This is a fully functional community with blogs and feedback.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 11:03 am
by jarda
On my RB1100AHx2 I got 40-60% unclassified CPU usage after upgrade (in idle).
Downgrade to 6.20 brings it down to 0 - 0.2%.
I have same problem with 6.21.1 and RB2011UAS-2HnD.
After reboot all is ok, but after few hours unclassified CPU usage increases to 100% and performance of the router decreasing with packet loss.
I have the same on on Omnitik with 6.21.1.

Port 53 is blocked on input on all wans (it counts only few hits during 12 hours). I had to switch off SNMP, as it was not able to provide values due to big CPU load. Sometimes when restarted it keeps cpu iddle and after some time it takes 100% by unclassified, mostly it is on 100% load immediatelly after reboot. Running with approximatelly 6MB of free RAM. Throughput does not seem to be affected.

Sometimes it states some percentage of CPU time spent on IPSEC. But the ipsec is not used at all...

Should I downgrade to 6.20? Or maybe even to 6.18?

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 11:08 am
by bramfm
Since version 6.21.1 I get random reboots with my RB1100AHx2. Had to downgrade to 6.20 again.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 12:48 pm
by WirelessRudy
Hey guys, let's have a simple reality check for a moment.

If you download/upgrade any new ROS and deploy it...You essentially become the "Beta" tester, eh? :o

So far, I don't believe that MikroTik is requiring anyone to upgrade to a newer version of the software. So if the current version is working, then probably you should leave it alone.
If you want to experiment with newer versions, that's ok but then you do it at your own risk.
Since MikroTik doesn't charge for the software, you might conclude that it is worth ever penny you paid for it.. But there are other opinions that might differ at bit.

Rule of thumb should be, to only test new ROS software on a non-essential network and give it enough time to reveal any problems. If someone deploys it on a active network, well then, you have to accept the risks.

-tp
Well, that's all nicely said and basically true. But when you have automated update script or developed a habit to update directly from the MT servers you do get at times nasty surprises. I have been updating new client units (to prepare them, or just was thinking them to upgrade from an older version to what I considered to be the latest stable) and found to my surprise the version number was already higher again that what I'd expected. So far never had big problems because of that since usually I perform such act first on new to be configured CPE's only. But its sod's law, when a probably disaster is lurking around the corner, one day it will hit you.....

Hence I still never found the courage to use a very tempting automated upgrade script (that would safe me o so much work), too often the latest ROS comes with errors. Most of them won't have an effect on my specific usage, but in the past I have seen wireless disasters that I am really not waiting to see happening in my network.....
Picking a new ROS version is like electing your favorite politician.... After the election you never know if he is really doing what you'd expect him to do or just the opposite..... :o

Actually MT should only allow new releases with permanent version number ready in their download (for auto upgrade) section when they are approved by many clients and at least are around for a month or so. Any other version, no matter how good they think it is, should be not considered to be 'definite and final stable version' before its really proven in 99% of the cases it works.....

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 1:16 pm
by Deac
Actually MT should only allow new releases with permanent version number ready in their download (for auto upgrade) section when they are approved by many clients and at least are around for a month or so. Any other version, no matter how good they think it is, should be not considered to be 'definite and final stable version' before its really proven in 99% of the cases it works.....
The separate 'Beta Program' speaking differently.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 1:26 pm
by keema
Since version 6.21.1 I get random reboots with my RB1100AHx2. Had to downgrade to 6.20 again.
Same here. Mikrotik staff must be surprised again.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 1:29 pm
by normis
Since version 6.21.1 I get random reboots with my RB1100AHx2. Had to downgrade to 6.20 again.
Same here. Mikrotik staff must be surprised again.
Please send us supout.rif file from both these routers, keema and bramfm

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 1:30 pm
by indnti
Our RB 1100 AHX2 hangs completly after 4 or 5 days :evil:
Dont't install 6.21.1 :!:

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 1:38 pm
by jarda
Went back to 6.20 on omnitiks. Keeping 6.21.1 on other devices as they are without problems so far.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 2:44 pm
by visalink
Our RB 1100 AHX2 hangs completly after 4 or 5 days :evil:
Dont't install 6.21.1 :!:
With the x86 also hangs.

I do not understand why version v6.21.1 keeps the site, it is very unstable.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 2:58 pm
by normis
please, has at least one of you contacted support about this? we can't fix it, if we can't see the problem

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 3:18 pm
by Robox
This forum also has automatic translation, see the button in bottom right corner.
Только в одну сторону, а загружать вас мелкими проблемами нехотелось бы, да и диву дашь, когда видишь перевод написанного, технический язык - сложнее перевести автопереводчику, поэтому и предлагаю подфорумы языковые.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 3:22 pm
by normis
This forum also has automatic translation, see the button in bottom right corner.
Только в одну сторону, а загружать вас мелкими проблемами нехотелось бы, да и диву дашь, когда видишь перевод написанного, технический язык - сложнее перевести автопереводчику, поэтому и предлагаю подфорумы языковые.
Forum moderators that work in MikroTik don't speak all languages. This is an official forum, so we need to unserstand what is being discussed. You can make local forums for your country and host them yourself. Many countries have such forums. I believe that the Indonesian forum has more members than this one

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 3:30 pm
by Robox
Последнее предложение :)
1. Подается заявка на создание подфорума с таким-то языком.
2. Автор заявки должен принять кураторство этого подфорума, т.е. стать автоматически субмодератором и согласится автоматически на трансляцию проблемм в основные ветки на английском.
3. Т.е. человек, подавший заявку, должен быть здесь не новичком, владеть английским и быть приверженцем (активным в жизни) вашего железа и программного обеспечения.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 3:49 pm
by KBV
Who will read your discussion on the Russian?
This interesting presence admins and developers here.

PS как вы занимаетесь IT без Английского? Документацию Гуглом переводите? Сочувствую.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 3:58 pm
by voxframe
I realize this is off topic... But Normis, please hear my thoughts.

This is crazy with the bugs being introduced. I too am experiencing random reboots on 1100 hardware, as well as CCR. No "custom" scripting or complicated configurations. No userman, no hotspot, etc.

I don't have the time/ability to make supout files and send them and track progress etc.
-- I AM NOT A BETA TESTER --

There is a serious problem with your release methods for new firmware, and it needs to be addressed/organized better.

Right now it feels like your developers are guessing trying to patch bugs and release firmware in a hurry, and thus introducing more/bigger bugs. There needs to be a proper Alpha, Beta, Stable firmware flow, and right now there isn't.

My advice
====================
1) Introduce a PROPER firmware flow. ALPHA = v7 BETA = v6 STABLE =v5
2) Make ALPHA/BETA the same as Ubnt does. Only certain people who have accepted/approved can access the BETA files. Everyone else only sees STABLE.
3) NOTHING gets released to STABLE until completely cleared for at least a couple months.

This is a normal flow for any software company (That knows what they are doing anyway).
However Mikrotik has introduced one BIG FATAL mistake that breaks this...
-- You have produced hardware, that depends on BETA firmware!! -- (CCR, CRS, some 2011, etc that NEED v6)
THIS IS A BIG BIG BIG NO NO NO NO NO!!!!!!!!!!!!!

I don't want CCR in my hands when it can only run BETA firmware!
I don't want CRS in my hands when it can only run BETA firmware!

I want you to MARK your new firmware as BETA, so people understand the most recent is NOT THE BEST!
I want you to STOP producing new hardware that requires BETA firmware to operate! Make it work on the STABLE firmware first, or don't produce/release it!
This was your absolute biggest mistake. v5 was stable, and is stable, and works nearly flawlessly for what it promises, but I can't run it on everything, otherwise I WOULD!

This is very frustrating Normis, Mikrotik is the only company that does software development that I have ever seen work in such a backwards fashion. Again, even Ubnt can get this right. (And that is not a nice thing to say, because they can't get a lot of things right)

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 4:10 pm
by keema
I realize this is off topic... But Normis, please hear my thoughts.

This is crazy with the bugs being introduced. I too am experiencing random reboots on 1100 hardware, as well as CCR. No "custom" scripting or complicated configurations. No userman, no hotspot, etc.

I don't have the time/ability to make supout files and send them and track progress etc.
-- I AM NOT A BETA TESTER --

There is a serious problem with your release methods for new firmware, and it needs to be addressed/organized better.

Right now it feels like your developers are guessing trying to patch bugs and release firmware in a hurry, and thus introducing more/bigger bugs. There needs to be a proper Alpha, Beta, Stable firmware flow, and right now there isn't.

My advice
====================
1) Introduce a PROPER firmware flow. ALPHA = v7 BETA = v6 STABLE =v5
2) Make ALPHA/BETA the same as Ubnt does. Only certain people who have accepted/approved can access the BETA files. Everyone else only sees STABLE.
3) NOTHING gets released to STABLE until completely cleared for at least a couple months.

This is a normal flow for any software company (That knows what they are doing anyway).
However Mikrotik has introduced one BIG FATAL mistake that breaks this...
-- You have produced hardware, that depends on BETA firmware!! -- (CCR, CRS, some 2011, etc that NEED v6)
THIS IS A BIG BIG BIG NO NO NO NO NO!!!!!!!!!!!!!

I don't want CCR in my hands when it can only run BETA firmware!
I don't want CRS in my hands when it can only run BETA firmware!

I want you to MARK your new firmware as BETA, so people understand the most recent is NOT THE BEST!
I want you to STOP producing new hardware that requires BETA firmware to operate! Make it work on the STABLE firmware first, or don't produce/release it!
This was your absolute biggest mistake. v5 was stable, and is stable, and works nearly flawlessly for what it promises, but I can't run it on everything, otherwise I WOULD!

This is very frustrating Normis, Mikrotik is the only company that does software development that I have ever seen work in such a backwards fashion. Again, even Ubnt can get this right. (And that is not a nice thing to say, because they can't get a lot of things right)
Agreed 100%. Regarding supouts Normis. I cannot send it anymore as I have already downgraded my 1100AH2 to 6.20. Don't you have a piece on stock where your testers can try? They should have done it before. I have no special config of this router.

What I've also noticed is that sometimes firewall src-nat masquerade rule is displayed as invalid and it doesn't work. Disabling and enabling it a couple of times and it starts to work.... :S When invalid I get this message:

--- in/out interface matcher not possible when interface [pppoe-xxx-xxx] is slave - use master instead [eoip-xxx-xxx].

After a couple of disablings and enablings it stops being slave?!

http://forum.mikrotik.com/viewtopic.php?f=2&t=90998

br,

keema

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 4:18 pm
by normis
when you have such a situation, make supout.rif, then downgrade. shouldn't take more than 30 seconds to make the file.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 4:22 pm
by keema
when you have such a situation, make supout.rif, then downgrade. shouldn't take more than 30 seconds to make the file.
:)

It was kinda hard for me to think of that as I was under stress as this router is a main router for a whole building. It was my mistake anyway... I shouldn't have upraded the router but when I saw that after 6.21 immediatelly came 6.21.1 I thought maybe, just maybe after so many v6 version this is finally a stable one....

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 5:03 pm
by jarda
when you have such a situation, make supout.rif, then downgrade. shouldn't take more than 30 seconds to make the file.
I would like to. I tried several times but it had never finished.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 5:26 pm
by voxframe
Again, I have tried on a few occasions, sometimes they work, others they hang.

But what you are not understanding Normis, is that I should not have to be doing this in the first place!

This is all what a BETA tester should be doing. Not a customer using the most recent "stable" firmware. If someone wants to test firmware, and has the time to experiment, GREAT! But do not subject users to this on the "stable" branch.

Normis, please read what I said, and instead of addressing the most useless part of my entire post, stop and consider its overall meaning/impact.
Something needs to change with Mikrotik's firmware release policy/system/schedule!

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 8:28 pm
by visalink
please, has at least one of you contacted support about this? we can't fix it, if we can't see the problem
Normis,
I am not an employee of mikrotik, test you, stop using the purchasers of mikrotik as testers.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 8:32 pm
by visalink
I realize this is off topic... But Normis, please hear my thoughts.

This is crazy with the bugs being introduced. I too am experiencing random reboots on 1100 hardware, as well as CCR. No "custom" scripting or complicated configurations. No userman, no hotspot, etc.

I don't have the time/ability to make supout files and send them and track progress etc.
-- I AM NOT A BETA TESTER --

There is a serious problem with your release methods for new firmware, and it needs to be addressed/organized better.

Right now it feels like your developers are guessing trying to patch bugs and release firmware in a hurry, and thus introducing more/bigger bugs. There needs to be a proper Alpha, Beta, Stable firmware flow, and right now there isn't.

My advice
====================
1) Introduce a PROPER firmware flow. ALPHA = v7 BETA = v6 STABLE =v5
2) Make ALPHA/BETA the same as Ubnt does. Only certain people who have accepted/approved can access the BETA files. Everyone else only sees STABLE.
3) NOTHING gets released to STABLE until completely cleared for at least a couple months.

This is a normal flow for any software company (That knows what they are doing anyway).
However Mikrotik has introduced one BIG FATAL mistake that breaks this...
-- You have produced hardware, that depends on BETA firmware!! -- (CCR, CRS, some 2011, etc that NEED v6)
THIS IS A BIG BIG BIG NO NO NO NO NO!!!!!!!!!!!!!

I don't want CCR in my hands when it can only run BETA firmware!
I don't want CRS in my hands when it can only run BETA firmware!

I want you to MARK your new firmware as BETA, so people understand the most recent is NOT THE BEST!
I want you to STOP producing new hardware that requires BETA firmware to operate! Make it work on the STABLE firmware first, or don't produce/release it!
This was your absolute biggest mistake. v5 was stable, and is stable, and works nearly flawlessly for what it promises, but I can't run it on everything, otherwise I WOULD!

This is very frustrating Normis, Mikrotik is the only company that does software development that I have ever seen work in such a backwards fashion. Again, even Ubnt can get this right. (And that is not a nice thing to say, because they can't get a lot of things right)
+1
Agreed 100%.

Re: v6.21.1 released

Posted: Tue Nov 11, 2014 10:25 pm
by pbr3000
I realize this is off topic... But Normis, please hear my thoughts.

This is crazy with the bugs being introduced. I too am experiencing random reboots on 1100 hardware, as well as CCR. No "custom" scripting or complicated configurations. No userman, no hotspot, etc.

I don't have the time/ability to make supout files and send them and track progress etc.
-- I AM NOT A BETA TESTER --

There is a serious problem with your release methods for new firmware, and it needs to be addressed/organized better.

Right now it feels like your developers are guessing trying to patch bugs and release firmware in a hurry, and thus introducing more/bigger bugs. There needs to be a proper Alpha, Beta, Stable firmware flow, and right now there isn't.

My advice
====================
1) Introduce a PROPER firmware flow. ALPHA = v7 BETA = v6 STABLE =v5
2) Make ALPHA/BETA the same as Ubnt does. Only certain people who have accepted/approved can access the BETA files. Everyone else only sees STABLE.
3) NOTHING gets released to STABLE until completely cleared for at least a couple months.

This is a normal flow for any software company (That knows what they are doing anyway).
However Mikrotik has introduced one BIG FATAL mistake that breaks this...
-- You have produced hardware, that depends on BETA firmware!! -- (CCR, CRS, some 2011, etc that NEED v6)
THIS IS A BIG BIG BIG NO NO NO NO NO!!!!!!!!!!!!!

I don't want CCR in my hands when it can only run BETA firmware!
I don't want CRS in my hands when it can only run BETA firmware!

I want you to MARK your new firmware as BETA, so people understand the most recent is NOT THE BEST!
I want you to STOP producing new hardware that requires BETA firmware to operate! Make it work on the STABLE firmware first, or don't produce/release it!
This was your absolute biggest mistake. v5 was stable, and is stable, and works nearly flawlessly for what it promises, but I can't run it on everything, otherwise I WOULD!

This is very frustrating Normis, Mikrotik is the only company that does software development that I have ever seen work in such a backwards fashion. Again, even Ubnt can get this right. (And that is not a nice thing to say, because they can't get a lot of things right)
+1
Agreed 100%.
+1
Agreed 200%. Especially at the CCR topic.

Re: v6.21.1 released

Posted: Wed Nov 12, 2014 8:15 am
by DrDeft
yes +1

Re: v6.21.1 released

Posted: Wed Nov 12, 2014 4:38 pm
by voxframe
Normis?

Clearly you can see I'm not the only one who thinks this.

There is a real problem that needs to be solved with MT's methods of releasing firmware.

MT also needs to absolutely STOP releasing hardware that is dependent on BETA level firmware (v6 is BETA, don't even try calling it stable). This really screwed a lot of users! If I could run my CCR on v5, I would gladly do it.

People in our market need our products to WORK without stopping. Performance is "nice" but not the major issue. When the routers are rebooting and jamming etc... They are one thing = GARBAGE!

I have worked with many vendors, as well as software developers. I have *NEVER* seen such an unorganized disaster as Mikrotik's firmware methods. You guys need to clean up your procedures, and have proper ALPHA/BETA/STABLE groups. This way the people who want to play with BETA can do it and are aware of it, and the ones who want to use stable can stick with stable and not worry.

Right now you don't even have stable (6 is not stable, please never never call it stable, it is not stable. It is untested guessing.).

6 needs to be frozen feature-wise, and stabilized. Nothing else added or changed. Make your NV2 changes and improvements etc on v7 or something else.

Sorry I am just echoing the same thing I said before, but it is simple common sense, and I don't understand why Mikrotik can't see the current system is unacceptable.

Re: v6.21.1 released

Posted: Wed Nov 12, 2014 4:42 pm
by keema
Normis?

Clearly you can see I'm not the only one who thinks this.

There is a real problem that needs to be solved with MT's methods of releasing firmware.

MT also needs to absolutely STOP releasing hardware that is dependent on BETA level firmware (v6 is BETA, don't even try calling it stable). This really screwed a lot of users! If I could run my CCR on v5, I would gladly do it.

People in our market need our products to WORK without stopping. Performance is "nice" but not the major issue. When the routers are rebooting and jamming etc... They are one thing = GARBAGE!

I have worked with many vendors, as well as software developers. I have *NEVER* seen such an unorganized disaster as Mikrotik's firmware methods. You guys need to clean up your procedures, and have proper ALPHA/BETA/STABLE groups. This way the people who want to play with BETA can do it and are aware of it, and the ones who want to use stable can stick with stable and not worry.

Right now you don't even have stable (6 is not stable, please never never call it stable, it is not stable. It is untested guessing.).

6 needs to be frozen feature-wise, and stabilized. Nothing else added or changed. Make your NV2 changes and improvements etc on v7 or something else.

Sorry I am just echoing the same thing I said before, but it is simple common sense, and I don't understand why Mikrotik can't see the current system is unacceptable.
Don't apologize m8. It's Mikrotik who should be apologizing... but you wont live to see that. You didn't just say what was already said in this thread. The same thing has been posted in almost every thread announcing a new RoS release since v.5x. Nothing has changed and I doubt anything will.

Re: v6.21.1 released

Posted: Wed Nov 12, 2014 5:56 pm
by leonset
please, has at least one of you contacted support about this? we can't fix it, if we can't see the problem
With due respect, Mikrotik must implement the appropiate test suites to see the problem before clients face it. Full stop.

Specially if the bug breaks any current feature or makes the router unavailable (reboots, port flaps, high CPU usage...). Do it using different alpha/beta/stable branches, do it using separate packages (as with wireless-ng), or use whichever other way you see fit.

I've worked with lots of different manufacturers, OS'es and systems (storage, network, database, security...) and none of them have a "perfect" update procedure, but Mikrotik is among the worst. For me isn't the worst, at least Mikrotik have decent support and relatively fast response times to bugs...

An adecuate update policy is the feature that Mikrotik needs, ASAP please :)

Re: v6.21.1 released

Posted: Wed Nov 12, 2014 6:36 pm
by patrick7
+9999. The next few releases should ONLY contain bug fixes, no new features etc.

Re: v6.21.1 released

Posted: Wed Nov 12, 2014 6:51 pm
by k5nic
TO: MikroTik
FROM: User at large
RE: MikroTik products

As a relatively new user of MikroTik products, specifically routerboards and such, it saddens me to see such poor Quality Control on your software releases. I do not expect a reply on this email, but hear me out!

I have been in IT for over 20 years, I have used a great many products produced by companies such as Cisco, Microsoft, SonicWall, WebSense, etc. as well as a great many different Linux distros. The biggest complaint I personally have would be against Microsoft for their horrible patching system and the number of bugs they allow out the door when they release a new version is pitiful!

With your latest 6.21.1 release, it seems to me that you have now digressed to the extremely low level of Microsoft in terms of "get it out the door, we'll fix the bugs later!" kind of mentality. It disappoints me that such a great product 8 months ago when I started learning these heavily, now has deteriorated to such a low level.

I must concur with the several posts that it is time for MikroTik to get a formal alpha-beta-stable cycle and structure. This company has grown large enough that version control will do you in unless you get a handle on it NOW. It should have already been taken care of to avoid this type of screw-up. I, for one, will back off my pro-MikroTik stance and start using Cisco products a little more heavily again until this type of issue is corrected for future prevention, not just to get this 6.x.x.x.x whatever build out the door!

I have replaced a great many Cisco products in the last 6 months with MikroTik, and was getting ready to start some maintenance cycles to upgrade them, however, at this point I am unwilling to do so, and if a stable version 6.2x.x.x.x whatever doesn't come out shortly and stabilize this whole mess, I may have to start replacing the MikroTik systems with newer Cisco gear again, and move off the MikroTik product. At this point, I cannot, in good conscience recommend MikroTik as a stable, enterprise class alternative to Cisco.

Respectfully,
Jay Lytle, Senior Consultant/Owner
JSSM Consulting

Re: v6.21.1 released

Posted: Wed Nov 12, 2014 8:07 pm
by sergejs