Page 1 of 1

v5.2 released

Posted: Wed Apr 27, 2011 11:49 am
by normis

What's new in 5.2 (2011-Apr-26 16:09):

*) fixed webfig;
*) console - fixed problem with supout file generation and export that
appeared in version 5.1, it was causing console to enter busy loop
on some boards;
*) ssh client - added source address and remote command options;
*) user manager - added /tool usermanager profile;
*) route - fixed problem with missing connected routes;

Re: v5.2 released

Posted: Wed Apr 27, 2011 2:26 pm
by babbage
Hello
Plz explain more about:
"*) route - fixed problem with missing connected routes;"

Re: v5.2 released

Posted: Wed Apr 27, 2011 2:28 pm
by normis
Hello
Plz explain more about:
"*) route - fixed problem with missing connected routes;"
There was a problem, that some connected routes could suddenly disappear. This is fixed.

Re: v5.2 released

Posted: Wed Apr 27, 2011 2:59 pm
by doush
Hello
Plz explain more about:
"*) route - fixed problem with missing connected routes;"
When you disabled an IP address and enabled it, no connected routes were populating in the routing table.

Re: v5.2 released

Posted: Wed Apr 27, 2011 7:02 pm
by wirelesswaves
Well after a long chat with my pal Rudy last night, I was somewhat encouraged to give 5.1 a bash.

This morning, it was on MT site, this afternoon, it was replaced by ROS5.2... So biting hard down on a stick I fired it up.

Now please, what is this, some new frequency!!! 2429 Mhz... I hope that is not a pre-amble of what is to come.

Come on MT, I am scared enough to try any further ROS systems since 3.3 and 4.16, give me some confidence back!!!!!!!!!!

Re: v5.2 released

Posted: Wed Apr 27, 2011 8:07 pm
by napismizpravu
Does not support Alpha AWPCI085HU miniPCI 500mW (Atheros AR5414, 802.11 a/b/g) in the RouterOS 5.2 RB433UAH. Scan OK, connect log: "failed connect, on 2452, authentication timeout". AP encrypted and unencrypted (R52H connect OK). RouterOS 4.3 works.

Re: v5.2 released

Posted: Wed Apr 27, 2011 9:19 pm
by dssmiktik
Mikrotik,

Thanks for the SSH command capability, I've been wanting this for awhile now.

However, like most things in RouterOS, I would like to see the ability to capture the commands output to fully use this feature.
Example:
:local resource [/system ssh address=<router> command="/system resource print as-value"]
<Parse $resource to get remote router's resource>

Oh, and I guess another thing is maybe to have the ability to specify a password at the command line if we choose to. This way we can run SSH commands unattended. This would allow a script to run a command remotely on another router if we choose to.

Anyway, these are the two features I would like to see along with SSH command to be of much use to me.

Thanks.

Re: v5.2 released

Posted: Wed Apr 27, 2011 9:27 pm
by dssmiktik
File -> Download does not appear to work on v5.2 Webfig.

Re: v5.2 released

Posted: Wed Apr 27, 2011 10:09 pm
by ditonet
RB450G just upgraded to ROS 5.2, strange values in Queue Tree, column PCQ Queues:
pcq_bug.JPG
Queues with these values are RED-type not PCQ-type.
On RB433AH everthing is OK.

Regards,

Re: v5.2 released

Posted: Wed Apr 27, 2011 11:51 pm
by SQx
graphs - not working, on RouterBoard 750G v. 5.2

----------------------
Display only:

Traffic and system resource graphing

Re: v5.2 released

Posted: Thu Apr 28, 2011 12:59 am
by Basdno
graphs - not working, on RouterBoard 750G v. 5.2

----------------------
Display only:

Traffic and system resource graphing


Did you remember to enable/allow graphs from the IP you checked from? :)

Re: v5.2 released

Posted: Thu Apr 28, 2011 6:19 am
by petro25
:shock: It is not visible Russian font

Image
Image

Re: v5.2 released

Posted: Thu Apr 28, 2011 6:38 am
by petro25
Radio problems
Noise-97 sometimes in an operating time from for it interrupts communication
The similar occurs even indoors


Image
Image
Image

Re: v5.2 released

Posted: Thu Apr 28, 2011 8:34 am
by janisk
Mikrotik,

Thanks for the SSH command capability, I've been wanting this for awhile now.

However, like most things in RouterOS, I would like to see the ability to capture the commands output to fully use this feature.
Example:
:local resource [/system ssh address=<router> command="/system resource print as-value"]
<Parse $resource to get remote router's resource>

Oh, and I guess another thing is maybe to have the ability to specify a password at the command line if we choose to. This way we can run SSH commands unattended. This would allow a script to run a command remotely on another router if we choose to.

Anyway, these are the two features I would like to see along with SSH command to be of much use to me.

Thanks.
this is why you can use keys to authenticate from routeros client and it will work in same manner as paswordless key authentication from any other ssh client.
you have to add key to '/user ssh-keys private' private key on local router and '/user ssh-keys' to add public key and off you go.

Re: v5.2 released

Posted: Thu Apr 28, 2011 9:16 am
by BobcatGuy
Use caution on upgrade to 5.1 or 5.2, I cannot recall which one did this, BUT*****************************
Somehow through the upgrade process the Virtual AP's did not work, so I removed all of them. Had just he main AP which i called basement AP, whic I clearly recal setting up after the upgrade since I had to disable wireless package so that the 100 %CPU issue didnt come up, which I found to be when additional Virtual AP's are added thag is when the cpu goes to 100% When adding a Virtual AP, the MAC address is 00:00:00:00:00 where before when there was no problem, the MAC would fill in automatically with the MAC of that wireless card.

Save time, if it is all 0's it will set your board to 100% cpu, and all interfaces in list will not show up. ( yes a BUG) still in 5.2 verified, and drove 20 Km's with note book to fix that board again.

But this is NOT why I am pissed.. I had 5.1 running with the main AP set to basement AP, where before I had the main ap and 2 virtual ap's Ie My own Private AP, MainFloorAP and BasementAP.

Needless to say the basment and main were on seperate bridges, and my private ap was on my private bridge, even called PRIVATE. On the upgrade to 5.2 SOMEHOW that only AP that I set up, called basementAP SOMEHOW switched from the bridge I set it to, being Basment bridge, and after the upgrade it was on the Bridge called PRIVATE.....

so, needless to say, that wasnt what I wanted, my tenants roaming my network, which has alot of sensitive data, and has full access to other networks.

MT Fix these issues, how can you put 5.2 as a stable version on the download page if its been released this same day?

Fix the Virtual AP issues.

And for anyone wantign to test it, set up 3 ap's named " AirMatrix-SK " " BasementAP " and "MainFloorAP" put them on theier seperate bridges with 2 or 3 ehter ports, have DHCP on basement ap and main ap, but none on private bridge. is it because the names end with AP? I dont know, but it will put the board, in my case a 493, to 100% and then interfaces will not be listed. To fix, disable the wireless package, reboot, may require a site visit, some times it boots, sometimes it doesnt.

Grrrrrr

Re: v5.2 released

Posted: Thu Apr 28, 2011 9:33 am
by janisk
please send supout.rif to the support.

Re: v5.2 released

Posted: Thu Apr 28, 2011 12:19 pm
by mangust
RB750, V5.2.

Cant see the stat of the "slave" interfases:
WAN - out interface
LAN - is the Master Port, all other slaves.

Is it Ok ?

Re: v5.2 released

Posted: Thu Apr 28, 2011 12:33 pm
by kirshteins
RB750, V5.2.

Cant see the stat of the "slave" interfases:
WAN - out interface
LAN - is the Master Port, all other slaves.

Is it Ok ?
Yes, switched traffic is not going though the CPU.

Re: v5.2 released

Posted: Thu Apr 28, 2011 3:41 pm
by wirelesswaves
Nomis, please make 5.1 available on the web site again, for ROS, X86 and 100 series.. Rudy says its fine, but I wont install 5.2 to anymore clients having seen frequency 2429 appear.. (see above post)

Ps, what is this I read that NV2 doesnt work on X86, I am currently using NV2 on wrap2E, which is X86 based. (it seams to be working OK ( apart from usual dropouts similar to other RB variants))

Re: v5.2 released

Posted: Thu Apr 28, 2011 3:43 pm
by normis
Nomis, please make 5.1 available on the web site again, for ROS, X86 and 100 series.. Rudy says its fine, but I wont install 5.2 to anymore clients having seen frequency 2429 appear.. (see above post)

Ps, what is this I read that NV2 doesnt work on X86, I am currently using NV2 on wrap2E, which is X86 based. (it seams to be working OK ( apart from usual dropouts similar to other RB variants))
v5.1 contains many problems. v5.2 works fine. I don't know what rudy says.

Re: v5.2 released

Posted: Thu Apr 28, 2011 5:19 pm
by siprox
i try ros 5.2 with nv2 protocol this morning on rb433ah, ptp with other rb433 on 5ghz freq, work fine until this night with the same setting before, and unstable on version 5.0 & 5.1, the problem is control frame time out, im happy finally nv2 stable on my machine. tomorrow will try on other machine workk on 2,4ghz freq, hope this stable to. thanks MT.

Re: v5.2 released

Posted: Thu Apr 28, 2011 7:41 pm
by sobrado
Nomis, please make 5.1 available on the web site again, for ROS, X86 and 100 series.. Rudy says its fine, but I wont install 5.2 to anymore clients having seen frequency 2429 appear.. (see above post)
RouterOS 5.1 is available on the web site yet:

http://download.mikrotik.com/routeros-mipsle-5.1.npk (RB100 series)
http://download.mikrotik.com/mikrotik-5.1.iso (x86)

However, why do you want to downgrade to this release? Normis is right, there are many important bugs fixed on 5.2. I cannot fully understand your post about the 2429 MHz frequency. Have you sent a supout.rif file to Mikrotik support? Is it related with a frequency shift, right? You have another channel at 2464 MHz, again 2 MHz over the standard channel frequency but said nothing about it. It seems like upper channels are shifted, without more information it may be related even with a faulty wireless adapter.
$ ifconfig iwi0 chan 
iwi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:0e:35:a8:7e:79
        priority: 4
        groups: wlan egress
        media: IEEE802.11 autoselect (DS1)
        status: active
        ieee80211: nwid "WaveLAN Network" chan 3 bssid 00:60:1d:f0:07:4c 42dB 100dBm
                chan  freq      properties
                   1  2412 MHz  -
                   2  2417 MHz  -
                   3  2422 MHz  -
                   4  2427 MHz  -
                   5  2432 MHz  -
                   6  2437 MHz  -
                   7  2442 MHz  -
                   8  2447 MHz  -
                   9  2452 MHz  -
                  10  2457 MHz  -
                  11  2462 MHz  -
                  12  2467 MHz  -
                  13  2472 MHz  -
                  14  2484 MHz  -
        inet 156.35.97.196 netmask 0xffffff00 broadcast 156.35.97.255
My advice is using ROS 5.2 (as Normis suggests) or downgrading to RouterOS 4.17. It makes not a lot of sense moving to a ROS release that is known to have serious bugs. If you were happy with ROS 4.x, then 4.17 is a good choice for you.

Re: v5.2 released

Posted: Thu Apr 28, 2011 9:04 pm
by ToMikaa87
5.2 still has the througput issue.

Re: v5.2 released

Posted: Thu Apr 28, 2011 9:27 pm
by wirelesswaves
Nomis, and the other respondant.

Because 2429 is not even a valid channel!!! So why is it there!... The card is not that clever, its down to the person that did the coding, and if they have screwed up with channel spacings, then it makes me a little hesitant to go on an upgrade the network.

There have already been many situations where one of my cpe's has successfully logged on to an adjacent channel, some 20dB down on the real carrier frequency, so its a worry now with regards the integral code...

Offset, does not come into the equation, as far as I am concerned there is no reason for the card to report the same SSID on a frequency that is not a valid channel under any circumstances.

Nomis, what is the story relating to NV2 on X86 based products, I obviously missed the notification yet, it appears to be running on a wrap2e, so what goes?

Re: v5.2 released

Posted: Thu Apr 28, 2011 9:47 pm
by petro25
Noise-97 sometimes in an operating time from for it interrupts communication
After reboot noise level-116

http://petro25.sytes.net/out/supout.rif

Re: v5.2 released

Posted: Thu Apr 28, 2011 9:51 pm
by babbage
Nomis, please make 5.1 available on the web site again, for ROS, X86 and 100 series.. Rudy says its fine, but I wont install 5.2 to anymore clients having seen frequency 2429 appear.. (see above post)

Ps, what is this I read that NV2 doesnt work on X86, I am currently using NV2 on wrap2E, which is X86 based. (it seams to be working OK ( apart from usual dropouts similar to other RB variants))
v5.1 contains many problems. v5.2 works fine. I don't know what rudy says.

Normis, do you mean there are more problems fixed in v5.2 than what is mentioned in changelog? You have only 3 fixes mentioned!

Re: v5.2 released

Posted: Fri Apr 29, 2011 12:51 am
by margarine
Dear Mikrotik..
i recently upgraded my rb750 from v4.16 to 5.2
in usermanager there is big problem for me..
i've been using credit for my customer, but after upgraded to 5.2 i cant find credit from 4.16. where can i find it?
what should i do my credit in 4.16 can show up in 5.2...
i cant remember all the credit for my customer. but i've backup from my last 4.16
i hope that you can help me...

Re: v5.2 released

Posted: Fri Apr 29, 2011 1:39 am
by jero
What's new in 5.2 (2011-Apr-26 16:09):
*) fixed webfig;
*) console - fixed problem with supout file generation and export that
appeared in version 5.1, it was causing console to enter busy loop
on some boards;
My RB-750G is working now !!!! It was freezing several times a day.

Now, apparently, is ok.

[]s, Jero

Re: v5.2 released

Posted: Fri Apr 29, 2011 2:45 am
by WirelessRudy
Nomis, please make 5.1 available on the web site again, for ROS, X86 and 100 series.. Rudy says its fine, but I wont install 5.2 to anymore clients having seen frequency 2429 appear.. (see above post)

Ps, what is this I read that NV2 doesnt work on X86, I am currently using NV2 on wrap2E, which is X86 based. (it seams to be working OK ( apart from usual dropouts similar to other RB variants))
v5.1 contains many problems. v5.2 works fine. I don't know what rudy says.
Rudy says the v5.1 wireless part as far as 802.11a/n and nv2 is concerned works fine. Since 5.2 changelog is not showing any wireless related fixes but according this topic 5.2 has many new (or unsolved old ones) other issues reported Rudy says on a 802.11a/n network 5.1 is fine. I am not influenced by any of the issues mentioned on this 5.2 topic so Rudy is happy with 5.1 unless MT tell me that hidden wireless features not mentioned in changelog for 5.2 are performed.
And since Rudy also expects many more new ´stable´ versions to come Rudy just sits and wait to see what they will bring. For now 5.1 is fine for me. No doubt at the end of the year I will run 5.8 or so.... :shock:

Rudy upgraded rb122's, 133C's, 532(A)'s, 433(AH)'s, 411's, 333's, 1 rb600 and one 493AH all from several 4.x and 5.xrc versions to 5.1. Most upgrades done remotely over wireless. In total 220+ units....
First time ever not had one single issue! That's why Rudy is so happy with 5.1.. :D

Simon; http://download.mikrotik.com/all_packages-x86-5.1.zip
use same format for other packages.

Re: v5.2 released

Posted: Fri Apr 29, 2011 3:54 am
by tanjil
same problem occured on 5.2 version .. its not fixed yet

cant reboot the Os properly.. it takes 10 or 20 mins time ... after restart the router /sys log Kernel failure....
how to solve this...

Re: v5.2 released

Posted: Fri Apr 29, 2011 8:00 am
by petro25
Very much I want to see in the following version grathing for radio

1) Noise level
2) Signal level
3) Speed of connection
4) Quality of tx of rx

Re: v5.2 released

Posted: Fri Apr 29, 2011 8:42 am
by dssmiktik
this is why you can use keys to authenticate from routeros client and it will work in same manner as paswordless key authentication from any other ssh client.
you have to add key to '/user ssh-keys private' private key on local router and '/user ssh-keys' to add public key and off you go.
Thanks :) I just checked the Wiki and got myself educated on this new feature.

Re: v5.2 released

Posted: Fri Apr 29, 2011 6:58 pm
by dominicbatty
I think there may be still be routing issues in v5.2 associated with routing marks. I've only just noticed this and it might also be apparent in prior versions, I'll check next week but perhaps someone could clarify what is happening below.

If I mark all "OUTPUT" traffic from the router in the mangle rules with a new routing mark of "A"

We then have two routes ....

0.0.0.0/0 without a routing mark using interface "int1"
0.0.0.0/0 with routing mark "A" using interface "int2"

If I log all traffic leaving the router using a SRC-NAT logging rule matching to anything with routing mark "A". I then see entries in the log file stating in interface:(none), out interface: "int1".

I know the traffic is correctly marked with routing mark "A" as if it wasn't. the SRC-NAT logging rule would not trigger but it is selecting the route without a routing mark instead of the one marked with routing mark "A" so it appears something in the routing selection is not taking into account the routing mark.

Does this sound correct ... according to the packet flow a routing decision is made before the SRC-NAT as far as I can tell?

Cheers, Dominic

Re: v5.2 released

Posted: Fri Apr 29, 2011 7:17 pm
by fewi
What are the distances for your routes? The routing mark route should have a lower distance than the generic default route, otherwise it would be treated as ECMP.

Re: v5.2 released

Posted: Sat Apr 30, 2011 9:57 am
by dominicbatty
the distance for the routes, routing mark and non-routing mark are both 1. I thought that ECMP was done by having multiple gateways under a single route and then it selecting them in turn? I tried increasing the distance of the default route but this does not seem to have any effect.

spurious interfaces

Posted: Sat Apr 30, 2011 5:41 pm
by glucz
I reported a problem previously that interfaces disappear in winbox, but can be seen through the terminal
http://forum.mikrotik.com/viewtopic.php?f=1&t=50994

Now I noticed a few spurious interfaces that cannot be removed through the terminal and since the interfaces are missing in winbox, they are virtually invisible and unremovable.

I saw the missing interfaces starting in version 4.x, but these extra interfaces are new in 5.x

I tried to delete them in many different ways, and I show one in the attached screenshot. The one I'm trying to remove is l2tp-0 ... since all my server interfaces are dyamic, static ones are definitely there via some kind of bug.

... one more note: these interfaces will remain in the router after a reboot as well - which is not suprising since they are static.

GL

Re: v5.2 released

Posted: Sun May 01, 2011 1:29 am
by voxframe
Is anyone else noticing a SERIOUS CPU jump on routers that are in moderately well used (~100 clients) environments???

I use the 450G boards as PPPoE servers with RADIUS backend. And on 3.30 and 4.xx the CPU idles around 10% on heavy load. But after upgrading to any 5.x version the CPU is always 60-100%. Nothing else has changed except for the upgrade, and when I downgrade everything goes back to normal.

I have confirmed this on every single routerboard we have. (100+)
The CPU usage is MUCH higher, without any good reasoning behind it.

Re: v5.2 released

Posted: Mon May 02, 2011 11:06 am
by glucz
I had 3 high CPU usage related crashes on 5.2 within the past 2 days on 2 different x86 routers. I couldn't do a supout in the first 2 cases and forgot in the 3rd case, but I did make a profile screenshot. A reboot was required in all cases. There were about 30 users logged in with 3mbps traffic. Normal CPU usage in those cases is 5-8%.

Re: v5.2 released

Posted: Mon May 02, 2011 12:44 pm
by normis
Nomis, and the other respondant.

Because 2429 is not even a valid channel!!! So why is it there!..
There is no such thing as "valid channel" if you enable "Superchannel", which you have done. Set it back to manual-txpower and these other frequencies will be gone. Superchannel mode allows you to set any frequency you want, it doesn't list any "channels".

Re: v5.2 released

Posted: Mon May 02, 2011 3:25 pm
by benmikrotik
Is usermanager working on this release?

Re: v5.2 released

Posted: Mon May 02, 2011 3:27 pm
by normis
Is usermanager working on this release?
yes

Re: v5.2 released

Posted: Mon May 02, 2011 6:45 pm
by yogii
hi..

i have plan to buy ROS DOM, but i doubt about level, is there different of ROS level 4/5/6 about performace? or other?

thx a lot. :)

Re: v5.2 released

Posted: Mon May 02, 2011 11:28 pm
by dadaniel
5.2 still has the througput issue.
I am also having throughput issues with 5.2 on RB750G. I only get ~30Mbps of my 100Mbps connection. No problem with 4.17

Re: v5.2 released

Posted: Mon May 02, 2011 11:59 pm
by bwigham
Is usermanager working on this release?
yes
I don't think "yes" is correct.

I've found this software no were near stable enough to be used in a live environment.

I have had to re-install the software and re-entered all my users manually twice this week at 4am when there’s nobody online. Then I’ve got customers trying to create an account and purchase credit. I have lost a lot of customers because the account won’t create because of ‘primary key not unique’ errors. Then when they do create an account and purchase credit, it’s completely random whether or not the profile will get added. Since last weekend, I’ve been sitting waiting on emails coming in from PayPal and when they do, I have to check and make sure the account got the profile added ok. If it hasn’t, I then try and add the profile manually - though it doesn’t work most of the time, again with the ‘primary key’ error.
The only way I could get through this week was to create a load of accounts with profiles (did this the last time I rebuilt the database), delete the faulty account and setup one of the pre-made accounts with their details.

I’m not sure if the older versions work without these issues, but if they do I would advise anyone thinking of using this version for anything other than testing, to not do it..!

Re: v5.2 released

Posted: Tue May 03, 2011 3:08 am
by benmikrotik
Is usermanager working on this release?
yes
I'm gonna try it this weekend.

I've read that the "time start on first log on" was removed. Why? I am using voucher/prepaid accounts with this option enabled.

This option is very important so time only starts when user logs in.

Re: v5.2 released

Posted: Tue May 03, 2011 6:50 am
by siprox
Is usermanager working on this release?
yes
I'm gonna try it this weekend.

I've read that the "time start on first log on" was removed. Why? I am using voucher/prepaid accounts with this option enabled.

This option is very important so time only starts when user logs in.
yes, same question from me?, why this function removed?. we stuck on v.4.17 now.. im very glad v.5 userman, can breaking the voucher on to more than 3 voucher per paper, will saving the papers.

Re: v5.2 released

Posted: Tue May 03, 2011 8:50 am
by timberwolf
5.2 still has the througput issue.
I am also having throughput issues with 5.2 on RB750G. I only get ~30Mbps of my 100Mbps connection. No problem with 4.17
@dadaniel:
Could you please provide further information on your problems in a separate thread, including your setup?
Than someone might be able to help you, and you can always send a supout file to MT.
Please stop posting unspecific problem descriptions in various unrelated threads.
V5.x may have an effect on your setup, but that doesn't necessarily mean, that there isn't a configuration problem in your setup.

Re: v5.2 released

Posted: Tue May 03, 2011 9:26 am
by normis

yes, same question from me?, why this function removed?. we stuck on v.4.17 now.. im very glad v.5 userman, can breaking the voucher on to more than 3 voucher per paper, will saving the papers.
this function didn't work in any version before. including v4.17, that's why we removed it, until it can be fixed. so basically it doesn't matter for you if you use v5.2 or v4.17

Re: v5.2 released

Posted: Tue May 03, 2011 10:02 am
by rpingar
still bridge filter dosn't show any stats,
does it work and have only stats update problem or it doesn't work at all?

regards
Ros

Re: v5.2 released

Posted: Tue May 03, 2011 10:07 am
by normis
still bridge filter dosn't show any stats,
does it work and have only stats update problem or it doesn't work at all?

regards
Ros
did you report this before?

Re: v5.2 released

Posted: Tue May 03, 2011 10:14 am
by rpingar
still bridge filter dosn't show any stats,
does it work and have only stats update problem or it doesn't work at all?

regards
Ros
did you report this before?
no, but on the forum a lot of people reported bridge filter issue

Ros

Re: v5.2 released

Posted: Tue May 03, 2011 10:15 am
by normis
you know that unreported issues can't be fixed. not all issues are easy to find by ourselves, that's why we also rely on our customers to report problems that they find.

Re: v5.2 released

Posted: Tue May 03, 2011 11:28 am
by benmikrotik

yes, same question from me?, why this function removed?. we stuck on v.4.17 now.. im very glad v.5 userman, can breaking the voucher on to more than 3 voucher per paper, will saving the papers.
this function didn't work in any version before. including v4.17, that's why we removed it, until it can be fixed. so basically it doesn't matter for you if you use v5.2 or v4.17

I hope you can prioritize fixing it. I need this feature for my wifi hotspot.

Thanks in advance.

Re: v5.2 released

Posted: Tue May 03, 2011 11:33 am
by Michel
Is usermanager working on this release?
yes
No, I have still a problem with the Logs under 5.2 - see here for 5.1

http://forum.mikrotik.com/viewtopic.php?f=1&t=50732

Re: v5.2 released

Posted: Tue May 03, 2011 8:37 pm
by BlackbirdSDH
I found some serious bug rebooting the devices. If you try to reboot by using winbox under System/Reboot, sometimes the router will shutdown instead of rebooting the device.
That happend about 6 times on different RB (450G,493G,1100 and x86). This is not happening erverytime but to often. Rebooting using terminal does not show this effect (so far).

Greetings from germany.

Re: v5.2 released

Posted: Wed May 04, 2011 8:45 am
by pbr3000
you know that unreported issues can't be fixed. not all issues are easy to find by ourselves, that's why we also rely on our customers to report problems that they find.
The no working bridge filter was already reported from me to support. The open ticket is 2011041266000166. Already sent supout from v4.17 with working filters and v5.1 and v5.2 with filters don't working.

Re: v5.2 released

Posted: Wed May 04, 2011 8:53 am
by rpingar
you know that unreported issues can't be fixed. not all issues are easy to find by ourselves, that's why we also rely on our customers to report problems that they find.
The no working bridge filter was already reported from me to support. The open ticket is 2011041266000166. Already sent supout from v4.17 with working filters and v5.1 and v5.2 with filters don't working.

I openede a new thicket yesterday: #2011050366000191

hope to get some feedback about it soon.

regards
Ros

Re: v5.2 released

Posted: Wed May 04, 2011 1:55 pm
by Alfabi

What's new in 5.2 (2011-Apr-26 16:09):

*) fixed webfig;
*) console - fixed problem with supout file generation and export that
appeared in version 5.1, it was causing console to enter busy loop
on some boards;
*) ssh client - added source address and remote command options;
*) user manager - added /tool usermanager profile;
*) route - fixed problem with missing connected routes;
Dear Normis, where im can get information about changelog on bootload firmware? im see on Our RB750 present 2.34 present 2.26 ???

Re: v5.2 released

Posted: Wed May 04, 2011 2:03 pm
by Beccara

Re: v5.2 released

Posted: Wed May 04, 2011 7:15 pm
by webasdf
Anybody else having issues with 5.2 and PPTP losing connection? We have 2 remote sites connected into a main site via pptp. The PPTP connections from the remote sites seem to drop off randomly. To get connection back, we need to restart the pptp client at the remote sites. I've set up netwatch at the remote sites to do this automatically, but the remote sites have voip phones connected to the main site via eoip tunnels over the pptp link. When pptp goes out, so do the voip phones. So, the netwatch solution is a poor band aid.

We also had the router at the main site lock up this morning and had to reboot it manually.

Already sent supout.rif to support, just wondering if anybody else has seen similar behavior?

Re: v5.2 released

Posted: Wed May 04, 2011 7:28 pm
by honzam
Wiki is a again OUTDATED. Where is 2.34?

Re: v5.2 released

Posted: Wed May 04, 2011 7:53 pm
by mgutz2
i cant upgrade from my 5.orc11 to 5.2.

Re: v5.2 released

Posted: Thu May 05, 2011 12:33 am
by Trezona
Anybody else having issues with 5.2 and PPTP losing connection? We have 2 remote sites connected into a main site via pptp. The PPTP connections from the remote sites seem to drop off randomly. To get connection back, we need to restart the pptp client at the remote sites. I've set up netwatch at the remote sites to do this automatically, but the remote sites have voip phones connected to the main site via eoip tunnels over the pptp link. When pptp goes out, so do the voip phones. So, the netwatch solution is a poor band aid.

We also had the router at the main site lock up this morning and had to reboot it manually.

Already sent supout.rif to support, just wondering if anybody else has seen similar behavior?
Yes i have the same problem, but with 2 pppoe connections. The 2 pppoe connections disappear at random times.
The only way i can restore them is by rebooting the x86 pc...

I too have sent my supout.rif file to support.

Re: v5.2 released

Posted: Thu May 05, 2011 5:05 am
by wa4zlw
I don't think this is a 5.2 issue per se, but I am seeing dynamic PPTP sessions disappearing. My static PPTP is staying up. My dynamic ones are coming in over 3G wireless (from Verizon in my case) and it seems to drop quite often and no this is not with any calls coming in to kill the data stream.

Leon

Re: v5.2 released

Posted: Thu May 05, 2011 9:42 am
by kirshteins
I found some serious bug rebooting the devices. If you try to reboot by using winbox under System/Reboot, sometimes the router will shutdown instead of rebooting the device.
That happend about 6 times on different RB (450G,493G,1100 and x86). This is not happening erverytime but to often. Rebooting using terminal does not show this effect (so far).

Greetings from germany.
Is there any serial console output, when reboot fails? What packages are you using on those routers? Is there any watchdog configuration? Was this issue present before v5.2?

Re: v5.2 released

Posted: Thu May 05, 2011 11:19 am
by Chupaka
i cant upgrade from my 5.orc11 to 5.2.
"/log print" after reboot

Re: v5.2 released

Posted: Thu May 05, 2011 11:38 am
by alexspils
1. RB532, system routerboard settings are unavalaible in winbox, cli works fine
2. Telnet from registration table does not work
telnet: inet_pton failed for 00:00:00:00:00:00/telnet: Success
Trying 00:00:00:00:00:00...

Re: v5.2 released

Posted: Thu May 05, 2011 8:40 pm
by yogii
hello, why ping direct from my rb750 ROS 5.2 many packet-loss,

Image

but it different from my ROS 5.2 from virtual box.

Image

what make it different? is there something wrong from my RB's ethernet?

Re: v5.2 released

Posted: Thu May 05, 2011 8:42 pm
by yogii
hello, why ping direct from my rb750 ROS 5.2 many packet-loss,

Image

but it different from my ROS 5.2 from virtual box.

Image

what make it different? is there something wrong from my RB's ethernet?

Re: v5.2 released

Posted: Fri May 06, 2011 8:18 am
by glucz
I have a somewhat similar situation on 5.2. Can you check
ip route cache print
Maybe your route cache is full? That's what is happening to me.

GL

Re: v5.2 released

Posted: Fri May 06, 2011 10:53 am
by asus
I upgraded my x86 MT from 5.rc4 to 5.1. After using net for few mins some of My PPPoE users won't able to ping server or browse net & if they try to disconnect pppoe dialer it take too much time to disconnect or may b sometimes they need to reboot pc. I thought this would be a network issue or something else but this same thing happening with my diffrent network.

Please Check....
Thanks
:)

Re: v5.2 released

Posted: Fri May 06, 2011 11:01 am
by asus
i cant upgrade from my 5.orc11 to 5.2.
everyone has this problem do net install.
But net install will clear your configurations even if you click save old settings so dnt foget to take backup 1st :D

I too faced this issue in 3 of my x86MT while upgrading from 5.rc4 to 5.1 & also from 5.1 to 5.2.

Re: v5.2 released

Posted: Fri May 06, 2011 11:15 am
by Ivoshiee
Both ends running v5.2, in case of NV2 protocol in use the "P Throughput" field of connected client is empty in Winbox. It does have numbers when using some other protocol.

Re: v5.2 released

Posted: Fri May 06, 2011 4:53 pm
by siprox
I found some serious bug rebooting the devices. If you try to reboot by using winbox under System/Reboot, sometimes the router will shutdown instead of rebooting the device.
That happend about 6 times on different RB (450G,493G,1100 and x86). This is not happening erverytime but to often. Rebooting using terminal does not show this effect (so far).

Greetings from germany.
Is there any serial console output, when reboot fails? What packages are you using on those routers? Is there any watchdog configuration? Was this issue present before v5.2?
hello, i also facing the same problems with ROS 4.17 on my rb450, my configuration as hotspot usermanager, i set scheduler reboot in 1d 05:00:00 always, sometimes rb450 not responding/hangs, when scheduler running, if the problem occur i replug the adaptors power and then rb will reboot, i saw in the log router normally reboot, not showing "router was rebooted without proper shutdown (cause1)" with critical error, i not set watchdog, i leave it as default.

Re: v5.2 released

Posted: Fri May 06, 2011 5:44 pm
by ekkas
I had today that RB493AH got 100% CPU and Internet stopped working, or was super-slow.
Luckily could issue a reboot from Winbox and after about 2 minutes it finally rebooted and working correctly again.
Also had this on 5.1 as well. (Memory leak?)

The router made an autosupout which I sent to support. #2011050666000407

Ekkas

Re: v5.2 released

Posted: Sat May 07, 2011 1:05 am
by dominicbatty
Interesting comment about the lock up on the 493. My 493G has been having problems since moving from 5.0 to 5.2 with CPU peaking really high and giving me quite serious packet loss for short periods of time. I just noticed I've also got an autosupout today as well. I downgraded to 5.1 but looking at the ISP logs tonight I am still seeing hourly pascket loss on the lines over all three lines.

Re: v5.2 released

Posted: Sat May 07, 2011 11:05 am
by babbage
All who have problem with interface disconnecting after a random period of time, cpu load spikes, packet losts, ... which require you to reboot the router:

please check:
/ip route cache
print

see if you have a leak here and if your route cache usage is increasing. It seems to be serious bug in MK v5 that route cache memory becomes full due to a memory leak.

Post back with your feedbacks.

Re: v5.2 released

Posted: Sat May 07, 2011 12:51 pm
by asus
cache-size: 9253
max-cache-size: 1048576

also it takes too much time to stop services while rebooting...

Re: v5.2 released

Posted: Sat May 07, 2011 1:32 pm
by ekkas
Cache is constantly growing.
If I do a print every second, it is more and more everytime.

[admin@TRUEROUTER] /ip route cache> pr
cache-size: 5569
max-cache-size: 16384
[admin@TRUEROUTER] /ip route cache> pr
cache-size: 5571
max-cache-size: 16384
[admin@TRUEROUTER] /ip route cache> pr
cache-size: 5581
max-cache-size: 16384
[admin@TRUEROUTER] /ip route cache> pr
cache-size: 5609
max-cache-size: 16384
[admin@TRUEROUTER] /ip route cache> pr
cache-size: 5610
max-cache-size: 16384
[admin@TRUEROUTER] /ip route cache> pr
cache-size: 5618
max-cache-size: 16384
[admin@TRUEROUTER] /ip route cache> pr
cache-size: 5627
max-cache-size: 16384
[admin@TRUEROUTER] /ip route cache>


EDIT: Came back after a few hours and it's back to 5300 again. So it does not seem to just keep growing after all.

Re: v5.2 released

Posted: Sat May 07, 2011 2:24 pm
by arsadeghi
Since I upgraded many of my x86 routers to 5.2 sometimes my PPPOE users can't send and receive anything and I have to reboot the routers. It happens every day at a specific time but on different routers. Also there's a problem with Graphs. Everybody can make a http connection to my router and can see each connected user's queue and you cannot limit it to some specific IP addresses.

Arash Sadeghi

Re: v5.2 released

Posted: Sun May 08, 2011 3:36 pm
by voxframe
RB450G boards, constantly locking up on 5.2

Before they were either on 3.30 or 4.16

Since upgrading them the CPU has gone from idling at 5-10% to idling at 50%+.
This is 5 times now I've had boards lock up for no reason, with no log entries. All different locations, all different configs, all different power and physical setup.

Before I had 200+ day uptimes on the boards, now I am lucky if I can hit 30 without any issues.

I will be reverting to 4.17 until you guys can figure this out. Sorry I can't be more help, but there's very obviously still problems, but I have nothing to give you as the boards don't give me any data to indicate the problem.

I knew upgrading was a mistake. I tell people never do it, and of course I stupidly do it.

Re: v5.2 released

Posted: Sun May 08, 2011 6:33 pm
by arsadeghi
I have some other issues on as much as I have active PPPOE users on my routers. Sometimes I get more than 10 packet losses continusely. It happens like every 5-10 minutes. Even when I'm pinging the router from another router on a same switch. I'm thinking of downgrading all NASes to 4.17.
Also sometimes routers wont send and receive anything to PPPOE clients and I have to reboot them.

Arash Sadeghi

Re: v5.2 released

Posted: Sun May 08, 2011 9:07 pm
by ekkas
I mirror the above 2 posts.
MT guys have you identified the problem and working on a fix, or is it still unknown causes?
I'd like to know if I can hang on for another few days as downgrading everything will be a major problem , especially on hotspot/usermanager boards.

I.o.w. is there a fix on the way soon, or not?

Ekkas

Re: v5.2 released

Posted: Sun May 08, 2011 9:20 pm
by arsadeghi
Dear Friends,

I confirm that by downgrading my x86 routers to 4.17 all above problems had been solved. For your information all my routers where using multicore CPU's.
I experienced more problems on more utilized routers.

Arash Sadeghi

Re: v5.2 released

Posted: Mon May 09, 2011 9:31 am
by kirshteins
hello, i also facing the same problems with ROS 4.17 on my rb450, my configuration as hotspot usermanager, i set scheduler reboot in 1d 05:00:00 always, sometimes rb450 not responding/hangs, when scheduler running, if the problem occur i replug the adaptors power and then rb will reboot, i saw in the log router normally reboot, not showing "router was rebooted without proper shutdown (cause1)" with critical error, i not set watchdog, i leave it as default.

Problem you are experiencing is fixed in v5.0. BlackbirdSDH is having a problem after initiating rebooting from Winbox using v5.2.

Re: v5.2 released

Posted: Mon May 09, 2011 10:05 am
by Beccara
We're seeing CPU spikes that cause router instability, Took us 20min to get the reboot command to register. Supports so far saying its a "led" crash. This is on AP's which would run fine for a number of days then all PPPoE sessions would either drop or not pass traffic, VLan's that were bridged would continue to pass traffic but winbox showed 100% CPU usage and you can't mac-telnet in. Happened on 2 different AP's one running 5.0 and the other 5.2

Have rolled back to 4.16 and things are fine (The AP's had previously on 4.16 been running fine for months)

Re: v5.2 released

Posted: Mon May 09, 2011 10:14 am
by normis
anyone having issues in v5.2, please generate supout.rif file at the moment of the problem, write a description, make a screenshot, and send it all to support.

Re: v5.2 released

Posted: Mon May 09, 2011 10:15 am
by Beccara
Already done :) 2011050966000018

Re: v5.2 released

Posted: Mon May 09, 2011 10:17 am
by normis
Already done :) 2011050966000018
yes, you already posted in the other topic, and I can see that Janis M. is working on it.

Re: v5.2 released

Posted: Mon May 09, 2011 11:41 am
by dominicbatty
Came in this morning after monitoring v5.2 all weekend with no obvious problems to find as soon as the users started routing traffic through it, it started jumping up and around >95% CPU load and started dropping packets.

I've dropped back to v5.0 to see if I can establish if it is a configuration change or the firmware change to 5.2 that has had the effect as we have a few mods over the past couple of weeks that might possibly be causing the issues.

I'll run with v5.0 through today and post some information later.

Re: v5.2 released

Posted: Mon May 09, 2011 11:41 am
by normis
Came in this morning after monitoring v5.2 all weekend with no obvious problems to find as soon as the users started routing traffic through it, it started jumping up and around >95% CPU load and started dropping packets.

I've dropped back to v5.0 to see if I can establish if it is a configuration change or the firmware change to 5.2 that has had the effect as we have a few mods over the past couple of weeks that might possibly be causing the issues.

I'll run with v5.0 through today and post some information later.
do you use dynamic routing? OSPF?

Re: v5.2 released

Posted: Mon May 09, 2011 12:28 pm
by dominicbatty
No, we don't use OSPF .... we also seem to be having the same issues in v5.0 as well this morning.

Re: v5.2 released

Posted: Mon May 09, 2011 12:40 pm
by dominicbatty
We do use a number of mangle rules doing route marking for outbound traffic?

Re: v5.2 released

Posted: Mon May 09, 2011 10:41 pm
by voxframe
See this is good!

We use OSPF on our networks.
PPPoE for all clients.
Average of 100 clients per 450G board
RADIUS controlled.
RADIUS inserts simple queues for each client

No big firewall rules, no NAT, no tunnels.

That is basically all the functionality.

Re: v5.2 released

Posted: Mon May 09, 2011 11:21 pm
by mdminfo
Usermanager and Paypal
======================


Hi,

If a user cancels his payment or if there is a timeout, the credit is although put into the account. Is there any possibility to stop this? I am loosing a lot of money every day!


mdminfo

Re: v5.2 released

Posted: Tue May 10, 2011 1:38 am
by Beccara
So it seems that ROS 5.x has a memory leak:

Router 1:
ROS 5.2
OSPF, BGP x 1 instance, MPLS,BGP Signalled VPLS
Contrack on, No NAT/Mangle/Filter rules
Bridge Ethernet to bridge containing BGPVPLS.
Low traffic
Memory usage: Stable
Image

Router 2:
ROS 5.2
BGP x 1 instance, PPPoE server x 2, 7 PPPoE sessions
Contrack on, No NAT/Filter rules, 7 mangle rules doing mark packet/connection, 14 changle MSS rules, Wireless WDS with WDS’s bridged for PPPoE
Low Traffic
Memory usage: Increasing slowly
Image

Router 3:
ROS 5.0
BGP x 1 instance, PPPoE server x 6, 29 PPPoE sessions
Contrack on, , No NAT/Filter rules, 7 mangle rules doing mark packet/connection, 58 changle MSS rules, Wireless WDS with WDS’s bridged for PPPoE
Medium High traffic
Memory usage: Increasing rapidly, Has locked up when usage hits 90%+
Image


Router 4:
ROS 4.16
BGP x 1 instance, PPPoE server x 7, 26 PPPoE sessions
Contrack on, , No NAT/Filter rules, 7 mangle rules doing mark packet/connection, 52 changle MSS rules, Wireless WDS with WDS’s bridged for PPPoE
High traffic
Memory usage: Stable
Image

Router 5:
ROS 4.10
OSPF, BGP x 2 instance, MPLS,BGP Signalled VPLS, PPPoE server x 3, 89 PPPoE sessions
Contrack on No NAT/Filter rules, 7 mangle rules doing mark packet/connection, 178 changle MSS rules, Wireless WDS with WDS’s bridged for PPPoE
Very High Traffic
Memory usage: Stable
Image


I think anyone with ½ a brain can see that there is a memory leak that depends on traffic levels in ROS 5.x, ROS 4 devices under heavier load suffer no such memory problems where as 2 routers running ROS 5.x have become unstable with CPU’s stuck at 100%.

Re: v5.2 released

Posted: Tue May 10, 2011 1:57 pm
by macgaiver
It look like it is time for you to send "2 supout.rif file" mail (one without a leak, other with obvious leak without any restarts in between them) to support@mikrotik.com it is only way how they can narrow it down. From what i can understand about memory leaks, all the leaked memory is full of rubbish data, so they need to exclude all normal data and what ever remains will be the problem - in other words there are no big sign " Memory Leak here"

Re: v5.2 released

Posted: Tue May 10, 2011 5:06 pm
by mihaimikrotik
I also confirm the memory leak. Also, there are other problems that need attending.

The current system we're testing v5.2 is Intel quad core with 2 GB of ram. We're running bgp, with 3 peers providing full bgp table and also 3 bgp peers providing partial routes and 1 IGP peer. There are some issues:

1. The system stops responding from time to time giving about 30 seconds of timeout. We're also using bridges with rstp active, so I suspect that might be the cause. Still, this does not happen on v4.16/v4.17. It should be investigated.

2. If hardware multi-cpu is set then there are even bigger issues. The same timeout applies and also, Winbox locks up the core used for system processes. So, if I am running with 3 interfaces active, 3 cores will go to those interfaces and the last one will be used for the rest of the stuff. That core will go up to 100% randomly and even if Winbox disconnects it will stay at 100% untill the router is rebooted. I have not yet found a way to determine what exactly is keeping it at 100%. With multi-cpu no, this does not happen.

3. CPU load is still high compared to v4.16. Ok, I understand that no matter what we do it will be higher when using bgp, but it is way to high. It cannot be used on PC arhitecture unless running really fast systems (like I7), which is turning v5 in a slow OS compared to the previous versions.

Points 1) and 2) are really a problem, as this effectively makes v5 unusable in production environments.

Re: v5.2 released

Posted: Tue May 10, 2011 5:18 pm
by Ozelo
Routing filters problems when upgrading from 4.16 to 5.2

This was the code I was using before the upgrade:
/routing filter add action=accept bgp-communities=65530:65530 chain=alpha-out disabled=no invert-match=no protocol=bgp
/routing filter add action=discard chain=alpha-out disabled=no invert-match=no
But I MUST do the following to get it working again on version 5.2:
/routing filter add action=accept bgp-communities=65530:65530 chain=alpha-out disabled=no invert-match=no prefix=0.0.0.0/0 prefix-length=0-32 protocol=bgp
/routing filter add action=discard chain=alpha-out disabled=no invert-match=no

Anyone else could confirm this? These chains are on OSPF output to redistribute BGP routes marked with that community.

Re: v5.2 released

Posted: Tue May 10, 2011 6:13 pm
by mihaimikrotik
I also confirm the default route filter problem and I have also disabled rstp on one of the bridge interfaces. The disconnects have stopped meaning rstp is not working properly anymore (compared to 4.16).

Edit: new problem.

If you have winbox connected to v5.2 and you hit refresh on an IGP peer then you will get 50-100 Mbps between THAT ROUTER and WINBOX IP. Which makes no sense, but that is what happens. That traffic should be perhaps between the two peers refreshing the routes, but it does not happen that way. The interface torch shows the Winbox IP sending data at high rate towards the v5.2 router.\

Image

Re: v5.2 released

Posted: Wed May 11, 2011 12:57 am
by mars
why is it that system health works in ros 4.17 but not in ros 5
was something removed?

Re: v5.2 released

Posted: Wed May 11, 2011 8:21 am
by normis
which routerboard model? do you have the routerboard package installed?

Re: v5.2 released

Posted: Wed May 11, 2011 11:34 am
by mars
forgot to say x86

Re: v5.2 released

Posted: Wed May 11, 2011 12:20 pm
by normis
There are many different motherboards, it's hard to keep an eye on all of them. Probably a kernel driver was changed for your model.

Re: v5.2 released

Posted: Wed May 11, 2011 1:26 pm
by mars
would that change be on the linux side or on mikrotik side

Re: v5.2 released

Posted: Wed May 11, 2011 1:35 pm
by normis
kernel is on the linux side. it's hard so say why it stopped working for you, mayb try sending a supout.rif file to support@mikrotik.com

Re: v5.2 released

Posted: Wed May 11, 2011 2:09 pm
by babbage
Came in this morning after monitoring v5.2 all weekend with no obvious problems to find as soon as the users started routing traffic through it, it started jumping up and around >95% CPU load and started dropping packets.

I've dropped back to v5.0 to see if I can establish if it is a configuration change or the firmware change to 5.2 that has had the effect as we have a few mods over the past couple of weeks that might possibly be causing the issues.

I'll run with v5.0 through today and post some information later.
do you use dynamic routing? OSPF?

Goto /ip route cache
and print the output. See if your used memory is almost full during having high cpu load and packet losts.

Re: v5.2 released

Posted: Wed May 11, 2011 2:17 pm
by babbage
anyone having issues in v5.2, please generate supout.rif file at the moment of the problem, write a description, make a screenshot, and send it all to support.
Yes its a month I have submitted many files but yet no answer!

#2011041066000044 and
#2011032666000151


This memory leak in /ip route cache, has been present since 5. I remember having the issue even with RCs but don no which RC.

Re: v5.2 released

Posted: Wed May 11, 2011 2:25 pm
by normis
anyone having issues in v5.2, please generate supout.rif file at the moment of the problem, write a description, make a screenshot, and send it all to support.
Yes its a month I have submitted many files but yet no answer!

#2011041066000044 and
#2011032666000151


This memory leak in /ip route cache, has been present since 5. I remember having the issue even with RCs but don no which RC.
you were instructed to adjust your EoIP configuration because it caused a loop. You didn't respond about that.

Re: v5.2 released

Posted: Wed May 11, 2011 2:37 pm
by babbage
I disabled them! Cleared them!
It didn't fix the issue

I then downgraded to v4 cause I couldn't reboot my router twice a day. It started with 7 days, 2 days and 1 , then twice a day...
....................
But I still have 2 of my routers on this version. One of them has 2 EOIPs which gets problem every 2 days.
The other 1 EOIP (even I disabled it but no fix) which runs into problem every 7 days.

Thank GOD there is a good counter! I check /ip route cache. When the usage reaches max ram size, it's time to reboot the router. If I do not reboot, the router CPU load gets into more than 70%, packet lost apears with "No buffer available" in ping command in winbox. All router functionality starts fainting untill router fully hangs.

I have reported all of these with corresponding supout file. These are long tickets. But I have not received any update recently.

Re: v5.2 released

Posted: Wed May 11, 2011 3:00 pm
by babbage
you were instructed to adjust your EoIP configuration because it caused a loop. You didn't respond about that.
In addition, the EOIP disconnection was a symptom of router mulfunction and not the root cause! When router stops normal functionality, everything bad happens. EOIP interfaces disconnect/connect... bridges won't work. Ping times out... packet forwarding decreases.... pppoe interfaces disconnect...

As I said, there is something with route memory cache. Why should it increase until getting full? Why should it increase at a fixed rate and during a fixed period of time? have you seen my RAM usage graphs? Isn't having a pattern for a problem occurance unsuall?

Re: v5.2 released

Posted: Wed May 11, 2011 3:03 pm
by normis
so why didn't you respond to the support ticket? if there is no response, support engineer assumes the suggestion fixed the problem. there is no use to complain here, email support

Re: v5.2 released

Posted: Wed May 11, 2011 3:41 pm
by glucz
Normis ... and when you said that you were looking into my ticket which is about this same issue a few days ago, and forgot about it ... ? Even when others asked about the status - we received no answer.

I don't see what the added value is in disregarding a serious problem in ROS 5.X . Not talking about it will not make us just forget and stop bringing it up.

This problem is not just an inconvenience. It truly effects ROS features and stability and questions its usefulness in real life situations.

Ticket#2011041766000095

... after a day I have half my cache full (no P2P and no DDOS)

[admin@MikroTik] > system resource print
uptime: 1d2h24m17s
version: "5.2"
free-memory: 232320KiB
total-memory: 270224KiB
cpu: "Intel(R)"
cpu-count: 1
cpu-frequency: 3024MHz
cpu-load: 40%
free-hdd-space: 218790KiB
total-hdd-space: 253803KiB
write-sect-since-reboot: 5596
write-sect-total: 5596
architecture-name: "x86"
board-name: "x86"
platform: "MikroTik"
[admin@MikroTik] > ip route cache print
cache-size: 29487
max-cache-size: 65536


The router will stop responding in another 16-20 hours ... should it not lock up until then.



Here is another one after just 1 day 15 hours

[admin@MikroTik] > system resource print
uptime: 1d15h17m24s
version: "5.2"
free-memory: 219892KiB
total-memory: 256280KiB
cpu: "Intel(R)"
cpu-count: 1
cpu-frequency: 2394MHz
cpu-load: 0%
free-hdd-space: 30781468KiB
total-hdd-space: 30945632KiB
write-sect-since-reboot: 9777
write-sect-total: 9777
architecture-name: "x86"
board-name: "x86"
platform: "MikroTik"
[admin@MikroTik] > ip route cache print
cache-size: 32767
max-cache-size: 32768
[admin@MikroTik] >

Re: v5.2 released

Posted: Thu May 12, 2011 8:19 am
by normis
I already said above, instead of complaining here, email this information to support, where our support engineer will look at it. Other people on this forum have no benefit if you just complain and don't inform MikroTik

Re: v5.2 released

Posted: Thu May 12, 2011 8:30 am
by jcremin
Other people on this forum have no benefit if you just complain and don't inform MikroTik
In the same way that nobody benefits by you complaining about a customer complaining about bug in your software. Sometimes it seems you spend more time insulting people for the way they asked a question than actually trying to help them solve it. It is pretty obvious that things can't be communicated nearly as easily through the "support" system, so why not just offer a little official support on the forums.

I'm not trying to be rude here, but the easier you make it for your customers to communicate with you and help troubleshoot problems like these, the easier it will be to solve them and the happier everyone will be.

Re: v5.2 released

Posted: Thu May 12, 2011 8:33 am
by normis
glucz here is complaining that he didn't receive an answer to his ticket. In fact, the latest mail in the ticket was a question to him, which he didn't answer. That's why there is no progress on the issue in his specific case. I am only talking about him and his ticket right now.

Re: v5.2 released

Posted: Thu May 12, 2011 8:39 am
by jcremin
I understand.. I wasn't necessarily speaking about his ticket specifically, but just an observation over the last few years I have been on this forum. It is obvious that quite a few people are having similar issues with 5.x leaking memory or something like that, so it surprises me that you aren't doing more to reach out to troubleshoot with them. I understand the importance of being able to track issues, but there's got to be an easier way to support 10 people in the forum having the same problem by getting them to work together, rather than simply having all 10 work separately with MT support.

Sorry, don't mean to be dragging this off topic. That was my 2 cents... I'll be quiet now. :)

Re: v5.2 released

Posted: Thu May 12, 2011 8:46 am
by normis
It is too often that people post angry messages like "when is this going to be fixed" because they assumed somebody reported this somewhere, but actually all of them are just waiting, and nothing is posted to the forum or to support. I am simply encouraging everyone to make those supout.rif files and participate to get problems fixed.

Re: v5.2 released

Posted: Thu May 12, 2011 8:54 am
by babbage
glucz here is complaining that he didn't receive an answer to his ticket. In fact, the latest mail in the ticket was a question to him, which he didn't answer. That's why there is no progress on the issue in his specific case. I am only talking about him and his ticket right now.
normis, we all do agree we should not complain here.
As I said, I have updated ticket and since didn't get reply, I posted to forum too. I am glad to see I am not alone on this. Also, new people get familiar with possible problems when upgrading.
........................................
Now, I appreciate if you provide me with your email address or contact my profile email so I send you bounch of ticket replies that I sent and didn't get answer back. May be you have not received them. Or you may ask your tech co-workers to simply update the ticket and ask me what they need to know se we together help to solve the problem.

Re: v5.2 released

Posted: Thu May 12, 2011 8:55 am
by normis
please list the ticket numbers in question, and I will make sure you get an answer

Re: v5.2 released

Posted: Thu May 12, 2011 9:43 am
by glucz
Hm. It seems like that my previous post got deleted. I hope it was because of the size and not the content ... so I will just phrase it simply:

Please send me the question you refer to, because I received no questions from support.

Thank you
GL

Re: v5.2 released

Posted: Thu May 12, 2011 10:00 am
by mangust
...
[admin@MikroTik] > system resource print
uptime: 1d2h24m17s
version: "5.2"
free-memory: 232320KiB
total-memory: 270224KiB
architecture-name: "x86"
board-name: "x86"
platform: "MikroTik"
[admin@MikroTik] > ip route cache print
cache-size: 29487
max-cache-size: 65536

...
Here is another one after just 1 day 15 hours
[admin@MikroTik] > system resource print
uptime: 1d15h17m24s
version: "5.2"
free-memory: 219892KiB
total-memory: 256280KiB
architecture-name: "x86"
board-name: "x86"
platform: "MikroTik"
[admin@MikroTik] > ip route cache print
cache-size: 32767
max-cache-size: 32768
[admin@MikroTik] >
I'm just interested Is there a way to increase "max-cache-size" ?
Is there any dependency between RAM/model and max-cache-size?

Re: v5.2 released

Posted: Thu May 12, 2011 10:11 am
by glucz
It seems like that the max cache size depends on the RAM in the router.

The minimum size seems to be 16384
If you have over 128M RAM, the size is 32768
If you have over 256M RAM, the size is 65535
etc ...

The point is that it will fill up regardless of the cache size. The added bonus is that 5.2 is not stable enough (at least for me) to give enough time to fill up 65535. It would lock up with 100% CPU. I made a post in the forum about that with different screenshots.

GL


ps: I just received the question from support. The question really is not technical in nature and requires no true answer. I answered it however to speed up the process.

Re: v5.2 released

Posted: Thu May 12, 2011 10:15 am
by normis
the last email from us says "thank you for the report, we are investigating this issue".

Re: v5.2 released

Posted: Thu May 12, 2011 12:35 pm
by mangust
It seems like that the max cache size depends on the RAM in the router.
..
As I understand you have the same RAM size on both routers , but max-cache-size for routers is different.

Re: v5.2 released

Posted: Thu May 12, 2011 12:41 pm
by glucz
No. They are all different. Whatever was available at the time.

Whoever else is also having route cache problems: Are you using tarpit actions in firewall rules?
I picked 2 MT750's off the shelf and am tring to build the minimum required rules and services to replicate the problem.

Thanks
GL

Re: v5.2 released

Posted: Thu May 12, 2011 4:47 pm
by babbage
No. They are all different. Whatever was available at the time.

Whoever else is also having route cache problems: Are you using tarpit actions in firewall rules?
I picked 2 MT750's off the shelf and am tring to build the minimum required rules and services to replicate the problem.

Thanks
GL
I have currently 4 routers running v5 which 2 of them have this route cache memory problem.
I confirm the two having problem, have TARPIT rule in firewall while the other 2 which are working fine do not have any tarpit rule. For test, I am going to disable tarpit rule in one problem routers.

But I know another company utilizing MK with the same problem and no tarpit rule.

Re: v5.2 released

Posted: Thu May 12, 2011 5:32 pm
by mangust
No. They are all different.
GL
I' realy sorry ( :oops: ), but what is the difference between
total-memory: 270224KiB and total-memory: 256280KiB ???
Looks like both routers has 256Mb RAM.

Re: v5.2 released

Posted: Thu May 12, 2011 6:57 pm
by glucz
This is total RAM-shared video ram, so the RAM available might be slighly different for each configuration.

GL

Re: v5.2 released

Posted: Thu May 12, 2011 7:58 pm
by Alfabi
ospf+nbma+mpls - bug in nbma mode -not send hello packet
im have around 1K routes distributed by OSPF nbma method, neighbor stil active but MPLS is lost. in Debug mode in not freeze router im dont see any hello packet to lost node. After reboot freeze router all working done day or two. When im going on freeze rb and change network type ptmp all is standing up without reboot.

Re: v5.2 released

Posted: Thu May 12, 2011 9:21 pm
by fabsoft
i've upgaraded from 4.13 to 5.1 and then to 5.2 on a x86 system;
now i can't access via ssh with admin privilege using password but using ssh-key still works ok.
i tryed by creating other users and i've no problem to login with passwords.

Re: v5.2 released

Posted: Thu May 12, 2011 9:39 pm
by xezen
its got bugs 5.2 has route problems

ask support for 5.3 test

it works well for me
much better then 5.2

Re: v5.2 released

Posted: Thu May 12, 2011 11:45 pm
by Beccara
Care to explain the "route bugs"

Re: v5.2 released

Posted: Fri May 13, 2011 7:50 am
by tchus
5.2 is without doubt the best of the rest.
Still problems with Usermanager, but definitely the most stable IMHO.
I am not using any of the wireless functions of the RouterOS.
Simply a hotspot/router/authenticator with UBNT radios.

Re: v5.2 released

Posted: Fri May 13, 2011 8:15 am
by babbage
No. They are all different.
GL
I' realy sorry ( :oops: ), but what is the difference between
total-memory: 270224KiB and total-memory: 256280KiB ???
Looks like both routers has 256Mb RAM.
Glucz,
It seems my route cache momory ram has stopped increasing when I disabled tarpit rules... It's now 14 hours since I did it. I will keep posting if it's fixed.
Of course I have slight total memory usage icrease but route cache memory increase has stopped.

Re: v5.2 released

Posted: Fri May 13, 2011 8:30 am
by glucz
Yes. I can too confirm after 16 hours that route cache is now stable. So tarpit seems to leak into route cache.

GL

Re: v5.2 released

Posted: Fri May 13, 2011 8:57 am
by xezen
i have a eoip tunnel network setup over ospf routes with bridge on radius

keeps crashing over 5-6M of data over bridge

Re: v5.2 released

Posted: Fri May 13, 2011 9:00 am
by babbage
Yes. I can too confirm after 16 hours that route cache is now stable. So tarpit seems to leak into route cache.

GL
My memory usage graph always showed slight memory increase. Even on the routers without this tarpit rule and of course these routers were stable in functionality.
But from this tarpit rule experience and also day to day monitoring of graph I can coclude that root cause for all memory leaks is that, MK does not release used memories. Another example is when I "make supout file". Just when I click, about 5 mbytes of memory is used up instantly and at once and never get released. Of course I have provided all evidences to Janis Megis who is working great with me to follow up the issue in ticket #2011041066000044.

Attached you can see the memory graph I am talking about. See spikes in weekly section. Spikes happened when I tried to generate supout file. Slight increase is also notable.
capture.PNG
....................
We noticed Tarpit rule problem cause it was using up route cache mem which is small and very vital to day to day fine operation of router. In contrast, total memory consumption with slight pace may be noticed in 2 or 3 month based on the total memory you install on the router. For most we have to install new releases so we never hit this long period of uptime ;)
I have a RB1000 box running 3.28 with 100mbit/s of traffic. Its sooooooooo stable and even if memory is used more for a few hours, you have it free too when not needed.

Re: v5.2 released

Posted: Fri May 13, 2011 9:05 am
by xezen
what all you running through your box as i dont even use half of that you use


do you use proxy on your server?

Re: v5.2 released

Posted: Fri May 13, 2011 9:21 am
by babbage
no proxy... but your graph also shows memory usage increases... I beleive that should not happen unless you have increase of traffic or load on the router or puting new configuration that require more ram. For me, everything is the same during a month but still memory usage increases...

Re: v5.2 released

Posted: Fri May 13, 2011 12:37 pm
by xezen
this is correct it also the firewall setup example i found that

user one uses internet the hole month for facebook http traffic 512k
then next month user finds out about torrents then download a hole month of p2p also at 512k

but the p2p has more rules in the firewall so it uses more load on the server even if its the same amount of data

Re: v5.2 released

Posted: Fri May 13, 2011 8:21 pm
by WirelessRudy
It seems some of you on this topic are familiar with memory leaking:

I have this rb1000 with rosv4.11 that is doing simple queus for all my clients and some basic firewall filtereing.
The routing it performs is no more than a general route back into my network (next unit) and some policy routing with src addr list classifier in the mangle for the two gateway with failover.

My memory usage goes sligthy up for some weeks and then when it comes near 50% it ´hangs´. Meaning the internet ports stop functioning. This is going on for more then a year now, sometimes worse, sometimes better.
I see no relation in the total traffic running over this router nor do I see it with the amount of client in the simple queus. (approx. 225)

Normally, after the crash, we have to power cycle the unit to bring it back and all works fine than for another xx weeks.
Yesterday I saw the memory usage graph near a level to where the rb crashed 2 weeks ago and decided just to reboot it in the middle of the night. As you can see in the graph, the memory usage goes down considerably after the reboot.

Any ideas?

Re: v5.2 released

Posted: Fri May 13, 2011 8:30 pm
by WirelessRudy
Forgot to say, I have ROS 5.2 now implemented on my whole network to satisfaction (routers and AP`s and CPE`s) but this main gateway of my network not yet. I am a bit afraid to do so because if this router goes down my network is down. So first I wanted to know if my problem (which seems to me a sort of a ´memory leakage´) is solved in ros5.x

Hence my previous post.

Re: v5.2 released

Posted: Sun May 15, 2011 8:29 am
by Belyivulk
We saw ROS 5.x deployed for a few weeks before crashes. If you have it on busy AP's i suggest downgrading to 4.16 before you have issues...

Re: v5.2 released

Posted: Sun May 15, 2011 7:23 pm
by babbage
I installed 5.2 on a pppoe (bras) mk router.

Till now I see a bug. in PPP, active connection you can see new connecting pppoe client uptime starts from 39seconds and starts decreasing till reaching 0, then starts increasing! So funny :)

So it's user "yyy" connect. you can see it's alive for 39, 38, 37, 36, .... , 0 , 1, 2 ,.... uptime!

It seems it's like starting timer from -40seconds

Re: v5.2 released

Posted: Sun May 15, 2011 11:39 pm
by dssmiktik
It is too often that people post angry messages like "when is this going to be fixed" because they assumed somebody reported this somewhere, but actually all of them are just waiting, and nothing is posted to the forum or to support. I am simply encouraging everyone to make those supout.rif files and participate to get problems fixed.
So I mention this again, what about a public facing bug-tracker? This would solve all these problems mentioned. We (the paying customers) will be able to keep track of bugs / features on our own time, and always have a place to reference when we ask a question about a bug/feature. This would solve the endless forum postings about 'ticket xyz, what is status?'.

Also my 2 cents. I know RouterOS is a complex software, and I feel we (the paying / prospective customers) could benefit greatly from such as system as mentioned above.

Re: v5.2 released

Posted: Sun May 15, 2011 11:57 pm
by NetworkPro
Can you give an example public bug tracking system for a commercial closed software product?

Re: v5.2 released

Posted: Mon May 16, 2011 12:06 am
by fewi
Both Cisco and Juniper have bug trackers that are open for customers with appropriate credentials

Re: v5.2 released

Posted: Mon May 16, 2011 12:44 am
by Beccara
Cisco, Juniper, Microsoft, Novell just to name a few, Admittedly you need to sign NDA's for most access but as I said to MT at MUM AU 11 the larger consumers of ROS will sign this in a heart beat to be able to see issue's and history of fix's because as we all know the current MT changlog is only useful for toilet paper.

The fact is even a NDA backed bug tracker would be incredibly useful to medium to big WISP's, At the moment it takes 4-8 weeks for us to vet a new release simply because we can't trust MT to release accurate changelog's or MT support to provide current known issues

Re: v5.2 released

Posted: Mon May 16, 2011 9:28 am
by dssmiktik
It can start simple, nothing too complex, just a way for 'trusted' users to submit/modify features / bugs / fixes, maybe this forum could be used as a starting point for vetting the users' allowed to 'post' data to the bugtracker. Then maybe read-only access for general users.

All I would like to see really is just a central place specifically for bugs/features/fixes (or temp workarounds).

Re: v5.2 released

Posted: Mon May 16, 2011 10:31 am
by babbage
Another issue with v5.2 running OSPF. After some time of uptime, my single instance of OSPF resets to default config like router id becomes 0.0.0.0 and other parameters becomes default.

Re: v5.2 released

Posted: Mon May 16, 2011 1:22 pm
by kirshteins
I installed 5.2 on a pppoe (bras) mk router.

Till now I see a bug. in PPP, active connection you can see new connecting pppoe client uptime starts from 39seconds and starts decreasing till reaching 0, then starts increasing! So funny :)

So it's user "yyy" connect. you can see it's alive for 39, 38, 37, 36, .... , 0 , 1, 2 ,.... uptime!

It seems it's like starting timer from -40seconds
I was not able to repeat it. What architecture is the PPPoE server and client? Any specific configuration?

Re: v5.2 released

Posted: Tue May 17, 2011 12:37 am
by Beccara
Support confirmed our memory leak is caused by SNMP, just an FYI for anyone out there suffering from the same

Re: v5.2 released

Posted: Tue May 17, 2011 12:56 am
by glucz
I installed 5.2 on a pppoe (bras) mk router.

Till now I see a bug. in PPP, active connection you can see new connecting pppoe client uptime starts from 39seconds and starts decreasing till reaching 0, then starts increasing! So funny :)

So it's user "yyy" connect. you can see it's alive for 39, 38, 37, 36, .... , 0 , 1, 2 ,.... uptime!

It seems it's like starting timer from -40seconds
I was not able to repeat it. What architecture is the PPPoE server and client? Any specific configuration?


I have seen a similar thing with OVPN uptime. I was able to make a screenshot and send it to support with supout. The issue is that the counter doesn't start from 0, but instead it will count from the current uptime value of ROS ... So In my case it said that the uptime was 19hrs ... I guess if the uptime value is large enough and the counter's underlying variable is unsigned, I can see this causing a backward count, but the initial value would be something random.

Re: v5.2 released

Posted: Tue May 17, 2011 7:41 am
by asus
There is some serious issue with pppoe connectivity in 5.2 & 4.17.

I downgraded to 5.0rc4 all issue solved but rc4 UM is not stable :(

Re: v5.2 released

Posted: Tue May 17, 2011 8:11 am
by kirshteins
There is some serious issue with pppoe connectivity in 5.2 & 4.17.

I downgraded to 5.0rc4 all issue solved but rc4 UM is not stable :(
Please describe this problem in more details.

Re: v5.2 released

Posted: Tue May 17, 2011 9:47 pm
by gustkiller
anyone running 5.2 is getting stuck bgp routes after peer down?

i have a two main bgp routers and thei are interconected via ibgp. on the first router i just lost a peer to an exchange point. so a lost about 5k routes from them. but the lost routes are stuck in both routers, the routing table didnt got updated with the lost routes.

Anyone with that problem too?

v5.3 released

Posted: Wed May 18, 2011 11:34 pm
by napismizpravu
bad blocks 4.x,5.2> 0% ........ install RouterOS 5.3 (distib. 17.05.) bad blocks 4,2% ... RB433UAH

Re: v5.2 released

Posted: Fri May 20, 2011 1:58 pm
by mramos
bad blocks 4.x,5.2> 0% ........ install RouterOS 5.3 (distib. 17.05.) bad blocks 4,2% ... RB433UAH
BTW, I netinstalled 5.2 on a RB433 and at two RB450 because they had 0.3 ... 0.5% badblocks with the built in ROS (4.11 I guess). Even formatted NAND from boot menu (via RS232 console) to "zero" this readings.

But they still there.

Regards;

Re: v5.2 released

Posted: Mon May 23, 2011 5:45 am
by babbage
I installed 5.2 on a pppoe (bras) mk router.

Till now I see a bug. in PPP, active connection you can see new connecting pppoe client uptime starts from 39seconds and starts decreasing till reaching 0, then starts increasing! So funny :)

So it's user "yyy" connect. you can see it's alive for 39, 38, 37, 36, .... , 0 , 1, 2 ,.... uptime!

It seems it's like starting timer from -40seconds
I was not able to repeat it. What architecture is the PPPoE server and client? Any specific configuration?


I have seen a similar thing with OVPN uptime. I was able to make a screenshot and send it to support with supout. The issue is that the counter doesn't start from 0, but instead it will count from the current uptime value of ROS ... So In my case it said that the uptime was 19hrs ... I guess if the uptime value is large enough and the counter's underlying variable is unsigned, I can see this causing a backward count, but the initial value would be something random.
You are absolutely correct. When the router reached a higher uptime no more of this issue.

Re: v5.2 released

Posted: Tue May 24, 2011 9:06 pm
by isawyer
I have tried ROS 5.2 on multiple boards: RB800, RB600, RB433, RB433AH. In each case I am no longer able to right click a registered client and use telnet. The terminal window opens and displays the following:

telnet: inet_pton failed for 00:00:00:00:00:00/telnet: Success
Trying 00:00:00:00:00:00...
Connected to 00:00:00:00:00:00.
Escape character is '^]'.

MikroTik v5.2
Login:


The login prompt is for the AP itself vs the remote client. I am able to telnet if I use the Telnet applet under tools.

Re: v5.2 released

Posted: Thu May 26, 2011 2:44 pm
by makstex
Loses its default gateway through pptp provider after 5 minutes at full load - 98%. Only helps to reboot. Downgrade to version 4.17 solved the problem.
ps: 450G and 750G