Hi,
We have 2 problems with the Ros6.1 release.

importing rsc scripts has changed the calling structure and also the maximum characters per router script has been changed in Ros 6.1

The first problem is fixable with some work on rewriting the structure of the scripts, aka where we had to \\\ a " or $ it has to change to only 1x \.

The second problem we can also sort by breaking the scripts up into smaller scripts being called.


I do not see these changes in the change log, and wondered who else has experienced this problem?

We have advised our clients not to upgrade to Ros6.1 for the moment as we first need to rewrite our scripts and test it on the new version, as it currently breaks (fails) on importing the rsc script file.

Is this an error on Mikrotik's side or will things stay this way forward?

Any info welcome please.

Thanks

This is turning into a spectacular problem for us too, and we've advised against 6.1 too. MikroTik, could you please be more careful with changing your scripting API? Some people have constructed elaborate management systems around it and have to also try accommodate multiple ROS versions across hundreds of routers. Changes like these really hamper the stability of the ROS platform.

So my first question, why does /import have to print script lines by default? Can you rather add a "debug=yes" or "verbose=yes" option to the import command, please? Reason being, we have scripts that are already perfectly verbose ala :put, so having ROS automatically print line numbers and commands creates an utter mess of the terminal output.

Secondly, please could you (MikroTik) explain exactly what other limitations have been imposed now, that Russian has observed? Right now all I see is scripts failing all over the network, and researching a fix will be much easier with an in-depth understanding of the changes you've made.

Thanks.

Windows 7 <- L2TP/IPSEC -> Mikrotik 6.1 stopped working.
Passing over L2TP and when at IPSEC it compains in logging about payload and triming.
Worked fine before upgrading

Mikrotik 6.1 <- L2TP/IPSEC -> Mikrotik 6.1 works fine.

Please fix urgently since affecting IPSEC like this is unpleasant.

I also upgraded the firmware based on this new release. Can I downgrade to 6.0, or my firmware won't allow it?

Thanks!

Hi,

Just to keep you informed...

Downgraded back to v6.0rc14.
Upgraded firmware to v3.07
Upgraded to v6.0
Keeping firmware at v3.07 (even if it asks to upgrade to v3.02 (not sure what kind of upgrade is this))

L2TP/IPSEC works fine now.

Best regards,
the_prism

running OSPF and wds-mesh, after upgrade to 6.1 then cpu always 100%

Ggraphs did not save interface graphing data after reboot
http://forum.mikrotik.com/viewtopic.php ... 83#p373130

I just duplicate the answer here:

Linux Kernel supports upto 252 additional routing tables, so MikroTik cannot break that limit

Thanks，you are right!
It is limited by Linux.

Hi,

Just to keep you informed...

Downgraded back to v6.0rc14.
Upgraded firmware to v3.07
Upgraded to v6.0
Keeping firmware at v3.07 (even if it asks to upgrade to v3.02 (not sure what kind of upgrade is this))

L2TP/IPSEC works fine now.

Best regards,
the_prism

So it is clear now that v6.1 has issues with IPSEC that were not there in v6.0 and v5.25... has anyone received any feedback from Mikrotik about this problem?

Normis, Janisk?

Edit: Sorry to bother, but IPSEC connectivity is quite an important feature for me, since no other implemented vpn solution is not yet production ready (openvpn not fully implemented, sstp still not stable enough).

JF

so what about the [Ticket#2013061366000906] ?

Today version of 6.2 rc1 on 951G.. when on winbox clicking DHCP Server option >>> the winbox is crashing.. on rc1 from 17/06/13 its ok..

I have upgraded from 5.25 to 6.1.
After upgrade I cannot login using web interface using Chrome 27.0.1453.110(Linux).

I got the message "ERROR: Internal Server Error"

I can connect to web interface using firefox, and I can connect using ssh.

Had the same problem, just clear your browser cache and it should start working.

Hi Normis,

UM v6.1 has a bug, please check the link below

http://forum.mikrotik.com/viewtopic.php?f=10&t=73813

Thanks

Hello,

Since I reverted back to v6.0, IPSEC works fine but I discovered a new bug, as follows:
If to disable the pppoe-out1 connection (ADSL) and to bring it back up, it will never connect and will rotate with this in logs:
23:19:26 pppoe,ppp pppoe-out1: initializing...
23:19:26 pppoe,ppp pppoe-out1: dialing...
23:19:27 pppoe,ppp pppoe-out1: terminating... - failed to authenticate ourselves to peer
23:19:27 pppoe,ppp pppoe-out1: disconnected
23:19:37 pppoe,ppp pppoe-out1: initializing...
23:19:37 pppoe,ppp pppoe-out1: dialing...
23:19:37 pppoe,ppp pppoe-out1: terminating... - failed to authenticate ourselves to peer
23:19:37 pppoe,ppp pppoe-out1: disconnected

Only reboot helps.

I don't recall to have such issues in 6.0rc14 and I'm not sure if they're present in 6.1.
If not - good, if yes - please fix in the next release.

Thank you,
the_prism

What happening with cpu load in 6.0-6.1? here is cpu graph and bridge graph. Why the cpu load is so high if there is no traffic? In firewall i have only two dest nat rules, and only two scripts,one for dyndns and second for vpn connectivity check.
rb751U-2Hnd, 6.1.

alexanders check what "tool profile" menu shows. you will see which process takes it.

alexanders check what "tool profile" menu shows. you will see which process takes it.

Have checked, dns showing from 90 to 40-30-20-0. what can be wrong with dns ?

you have "allow remote requests". have you made firewall rules to protect your router from DNS queries by unknown hosts? maybe your router is being abused from outside. create firewall in the input chain

normis
thanks, this help.

On RC13, 60 days uptime in production. Do you recommend upgrading to 6.1?

On RC13, 60 days uptime in production. Do you recommend upgrading to 6.1?

Don't fix what ain't broken. If you are happy and nothing is missing, stay with what you have.

Don't fix what ain't broken. If you are happy and nothing is missing, stay with what you have.

That's one of the lessons you learn the hard way

Anyways - for me, 6.0rc13 on CCR is quite rock-solid at the moment. No problems so far, but in every newer version (6.0rc14-6.1) I've got a strange issue, does anyone else here suffer from that?

Few minutes after upgrade, everything is fine. Then, the items in Winbox (Interface list, BGP peer list or OSPF neigbour lists for example) start to take a few seconds to load. 2-3 Minutes later, Winbox loses it's connection. Logging in even per ssh or telnet is not possible anymore. The device still responds to pings, but after a few more minutes (also 2-3) it loses connectivity completely. Luckily, I've got a remote serial connection to it, because login on serial is still possible. A reboot command there takes about 5 Minutes until the router reboots itself. I've tried to generate a supout.rif when it got stuck, but even that didn't work.

It's running as a BGP RR with 4 IPv4 and 3 IPv6 peers (full feed), OSPFv2 and v3, MPLS PE (LDP, 4 VRFs, VPLS & L3VPN) and has 3 bonded interfaces (2xGE each) with about 5-6 VLANs per interface.

I'm happy with 6.0rc13 until now, so for me this is not a critical issue so far. But I'm interested if somebody else has observed this behaviour and if it's known at Mikrotik.

Hello Folks!

I am bit comfused here regarding RoS versions.

Is RoS 6.X considered to be the stable production version series ?
We would never ever consider using and Release Candidates or betas in our production environment.

We have upgraded to RoS6.1 on some none important routers only and standard wifi internal networks, that ha been working without problems since start.
But I read here about IPSEC and instable wireless networks.

I have some questions:

1. Is the NV2 wireless network stable in RoS6.1 and RoS6.0 ?
2. Does IPSEC work between RoS <-> RoS devices, we need rock solid IPSEC links.
Currently we run RoS5.24 and RoS5.10 rock solid both in NV2 and IPSEC, is it safe for us to upgrade to RoS6.1 ?

We can not take any outages and breakdowns in our networks due to buggy RoS versions.

What do you say ?

I've also been having issues with 6.1 on my RB450G - PPPoE hangs, also issues with random reboots.

Grepping syslog for June:

grep "router was rebooted without proper shutdown" */*
12/messages:Jun 12 19:04:21 fw1 system,error,critical router was rebooted without proper shutdown
13/messages:Jun 13 03:54:21 fw1 system,error,critical router was rebooted without proper shutdown by watchdog timer
14/messages:Jun 14 01:54:26 fw1 system,error,critical router was rebooted without proper shutdown by watchdog timer
14/messages:Jun 14 08:57:55 fw1 system,error,critical router was rebooted without proper shutdown
15/messages:Jun 15 04:51:31 fw1 system,error,critical router was rebooted without proper shutdown
15/messages:Jun 15 17:33:20 fw1 system,error,critical router was rebooted without proper shutdown
17/messages:Jun 17 07:04:57 fw1 system,error,critical router was rebooted without proper shutdown
17/messages:Jun 17 16:03:30 fw1 system,error,critical router was rebooted without proper shutdown
17/messages:Jun 17 18:39:15 fw1 system,error,critical router was rebooted without proper shutdown
18/messages:Jun 18 14:04:46 fw1 system,error,critical router was rebooted without proper shutdown
18/messages:Jun 18 17:25:23 fw1 system,error,critical router was rebooted without proper shutdown
18/messages:Jun 18 22:00:42 fw1 system,error,critical router was rebooted without proper shutdown
19/messages:Jun 19 12:59:19 fw1 system,error,critical router was rebooted without proper shutdown
21/messages:Jun 21 08:43:46 fw1 system,error,critical router was rebooted without proper shutdown

I've rolled back to 6.0 this morning and so far no issues.

I'm using it and its fine.

From the looks of the forum there may be some small issue with Ipsec in 6.1 but looks like its very stable release overall.

On RC13, 60 days uptime in production. Do you recommend upgrading to 6.1?

Don't fix what ain't broken. If you are happy and nothing is missing, stay with what you have.

Thank you

Out of all the releases for CCR, RC13 looks like the most stable.

With 6.1 is very often disconnect. It is used NV2. When client have 5.24 (5.25), then is uptime a lot of days. But after upgrade to 6.1 is uptime several minutes.
[Ticket#2013062166000392]

upgrade from 6.0 to 6.1 broke all IPSEC VPN connections on RB1100ahx2... downgrade back to 6.0 resolved issue. Thought 6.1 would fix IPSEC VPN issue of random VPN disconnects and inability to pass traffic to CISCO end points.

issue with link aggregation speeds 802.3ad as well - inconsistent balancing

btest is setting only SEND. Watch torch.

Very bad performance of PPPoE server after upgrading to 6.1 form 5.25 .
in first day it works fine but after that the number of pppoe clients decreases .

I took 2 CCR's and put them side by side with 6.1 installed. Ran a cable between 2 of the ports.. .and set up IPSEC.

EPIC FAIL !

Submitted a ticket and got back "We have a known IPSEC problem in 6.1"

Really?? At this stage in the game.??

I still can't put my CCR's in production on my Gig fiber link... too many issue from the very start.

On RB750 the high DNS usage , about 90-100% , downgrading to 5.25 with the same IP address on WAN and the same config solves the problem .

Thanks.

Regarding IPSec, a temporary solution is to use v6.1 on both ends and put the peers on port 62465 with rsa key as authentication method instead of PSK. This is the only way it works for me.

If 6.1 is on one end and 5.25 on other, then the above workaround does not work. Still searching for a solution.


MikroTik any ETA on a fix for IPSec?

Hello,

I have 2 issues: CCR1016-12G keeps locking up every 2 weeks. X86 version still has packet loss of over 30% on ANY Intel interfaces. VRRP is unusable. Both routers are running v6.1

Just pointing out the fact that I have mentioned this in previous posts and there is no fix even after so much time. This issue is rendering the routers useless.

Regards,
Mihai

Please give me a link to ROS 6.2 RC1. And also, the current list of changes.
Thanks

Please give me a link to ROS 6.2 RC1. And also, the current list of changes.
Thanks

6.2 RC1 has not been released to the public yet, and there is no changelog at all for 6.2 yet. You should wait for 6.2 to be released and then they will have a changelog for it.

Please give me a link to ROS 6.2 RC1. And also, the current list of changes.
Thanks

6.2 RC1 has not been released to the public yet, and there is no changelog at all for 6.2 yet. You should wait for 6.2 to be released and then they will have a changelog for it.

How can someone get access to the beta/RC builds for testing/feedback before they get released to the public?

No changelog and questionable stability...Why do you need it?
http://www.mikrotik.com/download/share/ ... 6.2rc1.zip

I don't need it at the moment (unless it includes a fix for IPSec ). I was just curious if there is a process (register somewhere?) for users to try beta versions for feedback etc.

I don't need it at the moment (unless it includes a fix for IPSec ). I was just curious if there is a process (register somewhere?) for users to try beta versions for feedback etc.

Write to support and ask for access to beta releases.

I can also confirm issues with 6.1 and IPSEC with PSK.

IT seemed to be chipset based. All routers on 6.1
MIPS-BE <-> MIPS-BE = YES
MIPS-BE <-> PowerPC = NO
MIPS-BE <-> x86 = NO
POWERPC <-> x86 = YES

POWERPC <-> POWERPC = unknown
X86 <-> x86 = unknown

Downgrading to 6.0 on all routers resolved the issue immediately

Andrew

need more details, IPSec did not receive any changes that would brake that.

try to enable debug logs on RouterOS and see what is happening.

I am debugging a site with mutiple IPSEC tunnels on ROS 6.1 currently.

Enabling ipsec in system logging creates multiple entries but it is very difficult to identify which log entry belongs to which ipsec tunnel. Is there an easy way to filter the log so I see entries relating to just one endpoint please ?

Also, it seems it only negotiates SA's when the "secret" is identical for all tunnels. Changing one tunnel to a different secret breaks all tunnels (eventually) when their lifetime is up and they renegotiate.......

The best way to manage logs in Mikrotik - and frankly just about anything - is to export them via Syslog to a Dude server. You can then filter/sort/export them to your hearts content.

Go one step further an deploy SIEM if you wish to do correlation etc... http://communities.alienvault.com/

I havent seen what you describe about secrets though. We are running about 70 Ipsec tunnels on 5.25 and beginning to test with 6.1.

Hmmm, reading above is a bit worrying about ipsec. Has anybody tried mikrotik -> Cisco Ipsec? v6.1?

Alex

I am trying to upgrade a Mikrotik installation (5.25) on a XENServer 6.1 Virtual Machine to Mikrotik v6.1.

Doing the automatic upgrade by downloading the upgrade package to mikrotik, leaves me with a kernel panic after reboot.

Also sometimes while rebooting prior to upgrade the package verification fails with an error about licensing which doesn't make sense since the installation has a proper license.


Trying to boot from the installation ISO just gets stuck forever right before the package selection screen.

From a search on the forums it looks like this issue has been going on since at least 6.0RC7
http://forum.mikrotik.com/viewtopic.php ... er#p353213
http://forum.mikrotik.com/viewtopic.php ... er#p355551


I also tried to create a supout.rif while on v 5.25 and it never completes.

Does MikroTik v6.x not support XENServer?

It works like a charm on VMware ESXi 5.1

I also just tried v6.2rc1 with the same results.

Here is a screenshot of the VM Console when kernel panic occurs.

Just started another thread on the XenServer Issue, I have been trying since 6.RC10 to get this working..

The best way to manage logs in Mikrotik - and frankly just about anything - is to export them via Syslog to a Dude server. You can then filter/sort/export them to your hearts content.

Go one step further an deploy SIEM if you wish to do correlation etc... http://communities.alienvault.com/

I havent seen what you describe about secrets though. We are running about 70 Ipsec tunnels on 5.25 and beginning to test with 6.1.

Hmmm, reading above is a bit worrying about ipsec. Has anybody tried mikrotik -> Cisco Ipsec? v6.1?

Alex

Hi Alex,

Thanks for the syslog suggestion. I'll redirect these logs to The Dude and see if that helps.

IPSEC is troubling me on ROS6.x.

We have had several sites upgrade from working IPSEC VPN to ROS6.x and they have each experienced some disruption.

In one case we only had to change one tunnel's encryption algorithm to get it working to this latest site where we had to set every password the same **.

We suspect, but have not yet proven, that special characters may also be an issue if used in the secret. As it is a live site once we got it going we have had to leave it alone

These tunnels are a mix of Mikrotik to Mikrotik and Mikrotik to 3rd Party routers.

** Now confirmed issue on two sites using RoS 6.1. Change password on one peer so that it is different to the others and it breaks all tunnels. Change it back and all tunnels are again connected within a few minutes.

** Also, disabling one peer in the group also caused tunnels to start dropping. Re-enabling the disabled peer corrected the issue.

This is like the peers are somehow inter-connected ?

Hi,
We have 2 problems with the Ros6.1 release.

importing rsc scripts has changed the calling structure and also the maximum characters per router script has been changed in Ros 6.1

The first problem is fixable with some work on rewriting the structure of the scripts, aka where we had to \\\ a " or $ it has to change to only 1x \.

The second problem we can also sort by breaking the scripts up into smaller scripts being called.


I do not see these changes in the change log, and wondered who else has experienced this problem?

We have advised our clients not to upgrade to Ros6.1 for the moment as we first need to rewrite our scripts and test it on the new version, as it currently breaks (fails) on importing the rsc script file.

Is this an error on Mikrotik's side or will things stay this way forward?

Any info welcome please.

Thanks

This is turning into a spectacular problem for us too, and we've advised against 6.1 too. MikroTik, could you please be more careful with changing your scripting API? Some people have constructed elaborate management systems around it and have to also try accommodate multiple ROS versions across hundreds of routers. Changes like these really hamper the stability of the ROS platform.

So my first question, why does /import have to print script lines by default? Can you rather add a "debug=yes" or "verbose=yes" option to the import command, please? Reason being, we have scripts that are already perfectly verbose ala :put, so having ROS automatically print line numbers and commands creates an utter mess of the terminal output.

Secondly, please could you (MikroTik) explain exactly what other limitations have been imposed now, that Russian has observed? Right now all I see is scripts failing all over the network, and researching a fix will be much easier with an in-depth understanding of the changes you've made.

Thanks.

We are also seeing a substantial difference on how scripts are processed between 6.1 and 6.0. Mikrotik, could you comment on whether these changes were purposely done and scripts will need to be changed, or whether this is the result of an inadvertent side effect of some other change and will be fixed in (perhaps) 6.2. See for additional reports of the same issue:

See http://forum.mikrotik.com/viewtopic.php?f=1&t=73772 and
http://forum.mikrotik.com/viewtopic.php ... 3&start=74
http://forum.mikrotik.com/viewtopic.php ... 35#p374835

thanks in advance.

For those who need version 6.0 use this magnet link:
magnet:?xt=urn:btih:DFD38099181BA8AE7DD29E7F72288C556C93EF35&dn=routeros-6.0&tr=http%3a%2f%2ftracker.mikrotik.com%2f

Hello MIKROTIK Support.
Try to ask one more time:
When can we change DTIM interval of 802.11 wireless interface network?
When can we change Beacon SSID interval of 802.11 wireless interface network?
When can we change time slot (short, long or both) on wireless interface?

Web-proxy disable and still using the cpu.
What is happening, v6.1 has many problems.
Ticket#2013062666000025

one issue i have encountered is that if you are not "local" to the MikroTik trying to log into the box fails on everything, winbox, ssh, telnet even the webfig!

i upgraded a box to it (v6.1), then found i couldn't get to it any more, same thing happened to my box at home, dad couldn't log into it from the outside the network

any clues?

Kev

My RB750UP keeps blowing its little mind, randomly rebooting.

"System, error, Critical - router was rebooted without proper shutdown by watchdog timer"

It's operating in stock NAS mode, no modifications to system outside of shutting down all IP services, save for winbox, API-SSL and SSH.

I got half a mind to roll back to 5.x - what version is recommended to get a stable platform?

Memory Leak not solved !!

running 6.1 on CCR1016 .. after some pppoe connections... memory use are growing... then, routerboard reboot.. (i have sent it to support).

running 6.2rc1 .. same problem... HOLLY CRAP !!!!!!!!!

When one 'stable' version will be release ? one version that i can use all of my CCR ?s ??

shit softwware !!!!!!!! GRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR !!!!

Lost my VPN with Cisco ASA 5510.
Downgrade to 5.25 - all is ok!

invalid length of payload

I can confirm the problem with IPSec and ROS v6. Now back to 5.25, all fine! Please fix this bug soon, want to use my CCR again ...

There is more to this than just IPSec issues. The router, running 6.1, was very sluggish in response to commands, as if it was stuck in a loop, the terminal window taking upwards to 30 seconds to get to a command prompt in comparison to the normal 3-5 seconds.

Package rolled back to 5.25 immediately showed a clear difference in overall system performance. And this is nothing fancy running, just a stock RB on a cable connection with DHCP/NAT operating, and barely too, since I locked almost all my hardware in to the RB with static IP's.

6.1 is FUBAR, seriously.

The best way to manage logs in Mikrotik - and frankly just about anything - is to export them via Syslog to a Dude server. You can then filter/sort/export them to your hearts content.

Go one step further an deploy SIEM if you wish to do correlation etc... http://communities.alienvault.com/

I havent seen what you describe about secrets though. We are running about 70 Ipsec tunnels on 5.25 and beginning to test with 6.1.

Hmmm, reading above is a bit worrying about ipsec. Has anybody tried mikrotik -> Cisco Ipsec? v6.1?

Alex

Hi Alex,

Thanks for the syslog suggestion. I'll redirect these logs to The Dude and see if that helps.

IPSEC is troubling me on ROS6.x.

We have had several sites upgrade from working IPSEC VPN to ROS6.x and they have each experienced some disruption.

In one case we only had to change one tunnel's encryption algorithm to get it working to this latest site where we had to set every password the same **.

We suspect, but have not yet proven, that special characters may also be an issue if used in the secret. As it is a live site once we got it going we have had to leave it alone

These tunnels are a mix of Mikrotik to Mikrotik and Mikrotik to 3rd Party routers.

** Now confirmed issue on two sites using RoS 6.1. Change password on one peer so that it is different to the others and it breaks all tunnels. Change it back and all tunnels are again connected within a few minutes.

** Also, disabling one peer in the group also caused tunnels to start dropping. Re-enabling the disabled peer corrected the issue.

This is like the peers are somehow inter-connected ?

We rolled the worst site back to RoS6.0 and it's IPSEC tunnels have been stable for 3-4 days now. I have not been game to try RoS 6.2RC1 as this is a live customer site......

There is more to this than just IPSec issues. The router, running 6.1, was very sluggish in response to commands, as if it was stuck in a loop, the terminal window taking upwards to 30 seconds to get to a command prompt in comparison to the normal 3-5 seconds.

I haven't had this or any other problems running 6.1 in a dual-WAN configuration. I don't use IPSEC or VPN.

The best way to manage logs in Mikrotik - and frankly just about anything - is to export them via Syslog to a Dude server. You can then filter/sort/export them to your hearts content.

Go one step further an deploy SIEM if you wish to do correlation etc... http://communities.alienvault.com/

I havent seen what you describe about secrets though. We are running about 70 Ipsec tunnels on 5.25 and beginning to test with 6.1.

Hmmm, reading above is a bit worrying about ipsec. Has anybody tried mikrotik -> Cisco Ipsec? v6.1?

Alex

Hi Alex,

Thanks for the syslog suggestion. I'll redirect these logs to The Dude and see if that helps.

IPSEC is troubling me on ROS6.x.

We have had several sites upgrade from working IPSEC VPN to ROS6.x and they have each experienced some disruption.

In one case we only had to change one tunnel's encryption algorithm to get it working to this latest site where we had to set every password the same **.

We suspect, but have not yet proven, that special characters may also be an issue if used in the secret. As it is a live site once we got it going we have had to leave it alone

These tunnels are a mix of Mikrotik to Mikrotik and Mikrotik to 3rd Party routers.

** Now confirmed issue on two sites using RoS 6.1. Change password on one peer so that it is different to the others and it breaks all tunnels. Change it back and all tunnels are again connected within a few minutes.

** Also, disabling one peer in the group also caused tunnels to start dropping. Re-enabling the disabled peer corrected the issue.

This is like the peers are somehow inter-connected ?

We rolled the worst site back to RoS6.0 and it's IPSEC tunnels have been stable for 3-4 days now. I have not been game to try RoS 6.2RC1 as this is a live customer site......

Already tested, but same result. On 6.2RC1 we also have problems with IPSec. Such as "kernel panic" and reboot ....

FWIW I have two connections at home. My 10m connection is for my VOIP and my 50m connection is for data. When I went to 6.x after awhile my VOIP router would have very high latency due to all sorts of connections being made. This only happens on the VOIP router. I've regressed back to 5.25 after a few days on 6.0 and it happened again there. My data router is currently on 6.0. I am running OSPF v2 amongst my network as well. I am also using VPNs which also endpoint on the VOIP router. So this is all related.

Thanks.

Leon D. Zetekoff, NCE, MTCE
BackWoods Wireless

one issue i have encountered is that if you are not "local" to the MikroTik trying to log into the box fails on everything, winbox, ssh, telnet even the webfig!

i upgraded a box to it (v6.1), then found i couldn't get to it any more, same thing happened to my box at home, dad couldn't log into it from the outside the network

any clues?

Kev

You obviously have either a firewall rule blocking you, or an "Allowed Address" set on your username preventing your from logging in from a non-local address.

ipsec from 6.1 to 5.25 - no connection

ipsec from 5.25 to 6.1 - packet rejected

I'm seeing the exact same problem trying to connect an IPSec connection from a recently upgraded AH1100 V6.1 to an AH1100 V5.24. Not an issue connection to antoher AH1200 with V6.0rc13.

On the V5.24 side I see errors such as "malformed cookie" and "invalid payload length".

I'm a bit weary of upgrading the V5.24 router as it is in our headoffice and always in use, and when upgrading the other two units to V6.0rc13 it didn't apply the IP settings to the correct ports or not at all and requiring me to do the configuraiton from scratch on both the other routers.

another BUG on both 6.0 and 6.1

seems you can not change the serial port to anything BUT AUTO. Why is this? We can not make any connections with the serial ports.

Leon

welcome to bugOS world !!!

Hello MT support.
Have a bug on CCR in connection with RB951G+RB751G
I have 2 EoIP tunnels in Each of up selected devices with each other. I think you know.
If i downloading/uploading data from 951 to 751 - the traffic goes trough CCR.
I think it must go direct EoIP tunnel from 951 to 751.
Please correct this in 6.2

MIKROTIK 6.2

http://vicnezbuh.cz/soubory/routeros/all_files_6.2.zip

MIKROTIK 6.2

http://vicnezbuh.cz/soubory/routeros/ro ... be_6.2.npk

http://vicnezbuh.cz/soubory/routeros/ro ... le_6.2.npk

http://vicnezbuh.cz/soubory/routeros/ro ... pc_6.2.npk

http://vicnezbuh.cz/soubory/routeros/ro ... 86_6.2.npk

Do we dare after the ordeal 6.1 put us through??

Do we dare after the ordeal 6.1 put us through??

I don't recommend downloading files from unknown sources. Those are not MikroTik domains.

Do we dare after the ordeal 6.1 put us through??

I don't recommend downloading files from unknown sources. Those are not MikroTik domains.

When will be available for download 6.2?

When all known issues will be fixed.

When all known issues will be fixed.

And while this.... we live on Bug World.....

BR

When all known issues will be fixed.

issue with IGMP PROXY is "known issues"?

It's pretty well understood that things are kinda rocky in transitioning to ROS 6. Can we all please submit as many tickets to Mikrotik so that successive versions can get better? It does us no good to just complain frivolously.

I think Mikrotik is trying to do what they do as best as they can. Lets give them as much ammunition as we can to fix all these problems and help them succeed.

It's pretty well understood that things are kinda rocky in transitioning to ROS 6. Can we all please submit as many tickets to Mikrotik so that successive versions can get better? It does us no good to just complain frivolously.

I think Mikrotik is trying to do what they do as best as they can. Lets give them as much ammunition as we can to fix all these problems and help them succeed.

+1

Mikrotik are working really hard to resolve the reported issues.

On the V5.24 side I see errors such as "malformed cookie" and "invalid payload length".

I'm a bit weary of upgrading the V5.24 router as it is in our headoffice and always in use, and when upgrading the other two units to V6.0rc13 it didn't apply the IP settings to the correct ports or not at all and requiring me to do the configuraiton from scratch on both the other routers.

We saw the same errors connecting to a Sophos/Aastaro UTM and to a Sonicwall TZ170. Downgraded to 6.0 and the problem went away. Did not matter what Phase 1 settings were, it simply would not complete Phase 1.

Hard to believe this was missed.

CCR1036-12G-4S on v6.1

lost ping to CCR after winbox attempt. any help?

Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.

It's pretty well understood that things are kinda rocky in transitioning to ROS 6. Can we all please submit as many tickets to Mikrotik so that successive versions can get better? It does us no good to just complain frivolously.

I think Mikrotik is trying to do what they do as best as they can. Lets give them as much ammunition as we can to fix all these problems and help them succeed.

+1

Mikrotik are working really hard to resolve the reported issues.

Two years for a reported bug that still has not been resolved is "working really hard"??
They're wasting time on nonsense and unnecessary things while serious bugs are still unresolved.

Two years for a reported bug that still has not been resolved is "working really hard"??
They're wasting time on nonsense and unnecessary things while serious bugs are still unresolved.

Please tell me the ticket number of this issue, and I will check the progress.

October 03, 2011 12:08 PM
Ticket#2011092966000591

I upgraded from 5.21 to 6.1 (x86 Machine)

Server "stop networking" a few seconds after connect to L2TP Server (MikroTik) from Windows 7 client (no ipsec).

Under the "Stop networking" I mean = no ping to Mikrotik IP-Address from inside (real terminal) and from outside (over LAN).
For "start networking" again - helps reboot Machine 1-2 times

October 03, 2011 12:08 PM
Ticket#2011092966000591

Wow, that IS old! What is the issue in that ticket?

CCR1036-12G-4S on v6.1

lost ping to CCR after winbox attempt. any help?

Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Reply from 192.168.10.252: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.

2yrs minus 2 days and counting...

October 03, 2011 12:08 PM
Ticket#2011092966000591

Wow, that IS old! What is the issue in that ticket?

http://forum.mikrotik.com/viewtopic.php ... hilit=igmp

Hi All

in the 6.0 rc14 I have found that, exporting and importing backup on another hardware, backup also imports the mac address.
Once imported you can not change it in winbox and if change manualy in the .backup file don't effect.

I remeber this problem was present in versions 2.xx but solved in the next.

The problem has been fixed in 6.1? I have no way to test it at the moment.

thanks
Senzatempo

Hi All

in the 6.0 rc14 I have found that, exporting and importing backup on another hardware, backup also imports the mac address.
Once imported you can not change it in winbox and if change manualy in the .backup file don't effect.

I remeber this problem was present in versions 2.xx but solved in the next.

The problem has been fixed in 6.1? I have no way to test it at the moment.

thanks
Senzatempo

This is well known and documented. Backup is only for restoring on the same machine. Use Export/Import files to move config. This is not a bug.

Hello,MikroTik team!
It will be great,if you can fix problem with (3g/4g) ppp disconnection,and add ndis driver for popular 4g modems.
PPP disconnects after 1 minute or 40 minutes,and then try reconnects every second.

3G Network signal quality is from -74dbm to -83dbm.
I tested RoS version from 5.22 to 6.2rc1.
All versions have this problems.
My record was 1:40 minutes without disconnection.
(RoS 6.2rc1;RouterBoot 3.5)
Also I noticed that problem occurs frequently,if you didn't add NAT masquerade rule,or disable it.
This problem is very old.

Some forum themes about it:
http://forum.mikrotik.com/viewtopic.php?f=3&t=71031
http://forum.mikrotik.com/viewtopic.php?f=9&t=56463


Thanks.

This is well known and documented. Backup is only for restoring on the same machine. Use Export/Import files to move config. This is not a bug.

ok backup is for the same hardware, but in previous versions (5,x) worked well on different hardware.

Please to want to consider how to implement inquiry, working with similar configurations on the same model of rb, it is very convenient to use it instead of having to use export / import

to be able to import a configuration with import takes several steps, with the backup function only 1 click.

THS all
Senzatempo

Kick a ticket open, start a paper trail, that's the only way you can spur them to even look into the issue.

Hello,MikroTik team!
It will be great,if you can fix problem with (3g/4g) ppp disconnection,and add ndis driver for popular 4g modems.
PPP disconnects after 1 minute or 40 minutes,and then try reconnects every second.

3G Network signal quality is from -74dbm to -83dbm.
I tested RoS version from 5.22 to 6.2rc1.
All versions have this problems.
My record was 1:40 minutes without disconnection.
(RoS 6.2rc1;RouterBoot 3.5)
Also I noticed that problem occurs frequently,if you didn't add NAT masquerade rule,or disable it.
This problem is very old.

Some forum themes about it:
http://forum.mikrotik.com/viewtopic.php?f=3&t=71031
http://forum.mikrotik.com/viewtopic.php?f=9&t=56463


Thanks.

Two years for a reported bug that still has not been resolved is "working really hard"??
They're wasting time on nonsense and unnecessary things while serious bugs are still unresolved.

Please tell me the ticket number of this issue, and I will check the progress.

Hi Normis, did you check progres of ticket #2011092966000591?

Is there a change with ARP-Cache?

Seems it has a longer TTL now. Replaced a Router and the only BOX I needed to clear the arp-cache was a CCR with V6.

Hello everyone,

when it expects the new version mt 6.2 ?

thanks

It's definitively time for ROS v6.2 except if this is holiday period there

We don't have any holidays now. Work work work and fixing bugs

We don't have any holidays now. Work work work and fixing bugs

You can tell which bugs are fixed in version 6.2?

We don't have any holidays now. Work work work and fixing bugs

You can tell which bugs are fixed in version 6.2?

See changelog.

We don't have any holidays now. Work work work and fixing bugs

You can tell which bugs are fixed in version 6.2?

See changelog.

Excuse me, but where to get a new list of changes. There is only 6.1.

Excuse me, but where to get a new list of changes. There is only 6.1.

here: http://forum.mikrotik.com/viewtopic.php ... 34#p377724
And you can get the v6.2 from here: http://www.mikrotik.com/download/share/ ... es_6.2.zip

Thanks, Stillhard.
I have read the changelog.
Normis, please tell me, any planned improvements in the performance of CCR?

what about OSPF -nssa stability ? is that fixed?

what about OSPF -nssa stability ? is that fixed?

One known nssa problem was fixed several versions ago, so please be more specific on problem description.

what about OSPF -nssa stability ? is that fixed?

One known nssa problem was fixed several versions ago, so please be more specific on problem description.

connected network on nssa (redistribute connected on) become unreachable, default route on nssa present, translator always on but dont know where is nssa connected network, reboot tranlator fix this bug... to next time

sounds like already fixed problem,

This is well known and documented. Backup is only for restoring on the same machine. Use Export/Import files to move config. This is not a bug.

ok backup is for the same hardware, but in previous versions (5,x) worked well on different hardware.

Please to want to consider how to implement inquiry, working with similar configurations on the same model of rb, it is very convenient to use it instead of having to use export / import

to be able to import a configuration with import takes several steps, with the backup function only 1 click.

THS all
Senzatempo

I wouldn't recommend using Backup to move config from one Routerboard to another, since it f.ex. brings along MAC adresses. This can under some circumstances give u some serious headaches. Also Backup doesnt bring along any Wireless settings.

Regards

CCR1016-12G with 3.04 firmware v.6.1 works
When updating the firmware to 3.09 does not work.
backup partition booted.

All Partition work on same firmware.
but on the other partition I have v6.rc11 and allowed me to download the firmware and boot from the root partition.
Now install v6.2 and firmware version 3.09
Now it works fine.

we are running 6.2 about JUL 08 and still experiencing random not active PPPoE interface.
attached there is a screen shot

NORMIS, when it will be fixed???
thanks

we are running 6.2 about JUL 08 and still experiencing random not active PPPoE interface.
attached there is a screen shot

NORMIS, when it will be fixed???
thanks

Did you contact support ? Let me know your ticket number, I will check status

It has been posted arounf for a while......

I am going to open a ticket.....

regards
Ros

we are running 6.2 about JUL 08 and still experiencing random not active PPPoE interface.
attached there is a screen shot

NORMIS, when it will be fixed???
thanks

Did you contact support ? Let me know your ticket number, I will check status

[Ticket#2013072566000383]

regards
Ros

[Ticket#2013072566000383]

regards
Ros

what should Normis see in a fresh ticket? wait for an answer from support first

Hi guys, my ethernet chip atheros AR8151 b not recognized with ros 6.1 ,any idea why this happen ?

Hi guys, my ethernet chip atheros AR8151 b not recognized with ros 6.1 ,any idea why this happen ?

In which RouterOS version did it work? What device is this ?

Hi guys, my ethernet chip atheros AR8151 b not recognized with ros 6.1 ,any idea why this happen ?

In which RouterOS version did it work? What device is this ?

this is the gigabyte ga-g41 m-combo onboard lan chipset .The motherboard is brand new and i use it for first time with ros 6.1

If it never worked before, there is nothing we can do. Apparently linux kernel doesn't support it yet.

[quote="MiKeDaDoC"]Hi Folks,

Problem was that only on IPSec Peer would establish correct SAs, randomly, that means it doesn't matter if it was the netgear or a RB2011xx. Analysing the problem showed that one had to deactivate all but one peer, this peer would come up perfectly. Then activate the next peer, wait until it would come up after nearly one minute. And so on.[/quote]

Same Problem here. Only one IPSEC connection can be established. It seems something is broken in 6.1 regarding IPSEC.

If it never worked before, there is nothing we can do. Apparently linux kernel doesn't support it yet.

thank you

Hi Folks,

Problem was that only on IPSec Peer would establish correct SAs, randomly, that means it doesn't matter if it was the netgear or a RB2011xx. Analysing the problem showed that one had to deactivate all but one peer, this peer would come up perfectly. Then activate the next peer, wait until it would come up after nearly one minute. And so on.

Same Problem here. Only one IPSEC connection can be established. It seems something is broken in 6.1 regarding IPSEC.

Yes, IPSEC is broken in 6.1. It should be fixed in 6.2, look back a few posts for the pre-release link to it.

....
Yes, IPSEC is broken in 6.1. It should be fixed in 6.2, look back a few posts for the pre-release link to it.

It's still broken for me in unreleased ROS6.2. Very strange issue (2x RB2011), ping and small packets are passing fine, but larger packets are not reaching it's destination. I'm checking what can cause this and there is a support ticket open, but I had no much luck until now.

....
Yes, IPSEC is broken in 6.1. It should be fixed in 6.2, look back a few posts for the pre-release link to it.

It's still broken for me in unreleased ROS6.2. Very strange issue (2x RB2011), ping and small packets are passing fine, but larger packets are not reaching it's destination. I'm checking what can cause this and there is a support ticket open, but I had no much luck until now.

Yeap, on 6.2 pre-release IPSec is still broken.

I know that the proper way to report this is via supout.rif files but as these are on live running networks it's not easy to do so and frankly I don't want to *have* to break my networks everytime Mikrotik decides to change something that was otherwise working perfectly fine.

Mikrotik should do more tests before changing stuff that break important functionalities. It's not our job as end clients to do beta testing for them by providing supout.rif files each time they break something...
It's one thing to discover an unknown bug and another to find that the latest release has some functionality completely broken.
In the case of the latter it's obvious that whatever Mikrotik changed since the last known good release, that caused the problem. So why the hassle with the support.rif files and tickets?

Maybe they could form a beta testing community to allow to it access to night builds and have a larger set of installations to do tests before public releases. Some incentive for those people trying to help would be nice (some free routeros licenses maybe?)

This thing where on each release you don't know what will be broken needs to stop.
Mikrotik you cannot enter the high end market you are hoping for with CCR with this kind on inconsistency on your routeros releases. Think about it, what serious business will wanna use a software that unpredictable on each release?

Maybe they could form a beta testing community to allow to it access to night builds and have a larger set of installations to do tests before public releases.

write to support@, they can give you access to pre-release builds with (sometimes) changelogs via your MikroTik.com account

And what about the [Ticket # 2013070166000356] ?

Yeap, on 6.2 pre-release IPSec is still broken.

Has anyone tested this in production using 6.2 final release? changelog says its fixed........

Sorry - should have checked the 6.2 thread http://forum.mikrotik.com/viewtopic.php?f=2&t=75392 some people still having issues

Out of all the releases for CCR, RC13 looks like the most stable.

I second this. I was so stupid to upgrade a CCR router from beta "release candidate" to the "stable/release" version 6.2 and now it totally crashed after two weeks of uptime. It's a very very basic setup with 10 VLANs and a VPN (PPTP) access (and "no" traffic compared to what a CCR is supposed to handle!).

I have to downgrade to 6.0rc13 and maybe leave it there forever.
I cannot afford playing guinea pig for MikroTik since it's a production environment.

[EDIT] Seems CCR wasn't the core culprit in this case, but the DSL router hung.
But with all this reports of memory leaks etc. in ROS 6.x I certainly do not feel well (and the DSL box was stable for years).

I tried a few times to use 6.7, then 6.1 but both have issues using MLPPP which I almost exclusively use the Mikrotiks for. Normally on 750GL's or 493AH's depending on the number of lines in the bond.

5.26 is listed on the Mikrotik site as stable and has no issues as far as I can tell. Will not touch 6.anything until its in the stable spot for ANY production environment.

I tried a few times to use 6.7, then 6.1 but both have issues using MLPPP which I almost exclusively use the Mikrotiks for. Normally on 750GL's or 493AH's depending on the number of lines in the bond.

does anybody know about those issues? have you written to support@?