Hi.
sometimes (about 1 or 2 in a day) the winbox freezes and when i
disconnect it and again connect every windows of winbox is empty without
any data.
I tried ssh or telnet also . in the ssh or telnet print commands or any
command like that (which output some data) does not work and sometimes
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
this problem will be solved with a reboot
one time i wait to see what happen if i don’t reboot . after about 1
hour the problem automatically solved ! but at that 1 hour any new user
could not connect with pppoe pptp etc .
Again problem occured about 10 hour ago. now i pluged monitor to it and see this message in all of the screen
unregister_netdevice: waiting for ppp61 to become free. Usage count = 51
i have contacted the support with the supout and they answer this nothing more
Unfortunately supout does not contain any information about crash. Disable all
unused packages like mpls-test, wireless, stpbridge-legacy etc. Write this
command in console:
/system hardware multi-cpu=no
and reboot router, it will load regular linux kernel.
If it is possible connect monitor and next time when router will crash it will
output info on a screen.
This is exactly what I mean FREEZE while using pppoe server with versions of ROS 3.5 and above. ROS 3.4 and below this is ok for nothing more than 100 simultaneous users and you may need ROS 2.9.45 if you think about nothing more than 750 users. But unfortunately, they said the same to us. We are still researching to know what exactly is happening and so far seems to be a random problem of instability envolving pppoe server only.
the support team have sent a new answer to me . just to share it with community i will write it here
Currently it looks like linux kernel bug, we will check it and inform you.
as i searched before the “unregister_netdevice: waiting for ppp61 to become free. Usage count = 51” is not the mikrotik problem and this problem have seen in other linux distros .
Hi . i found something about this problem and thought it is better to say.
i have radius server.
i disabled my radius server about 2 hours for some maintenance and about 100 pppoe users tried to connect via pppoe in mikrotik and mikrotik worked fine. i was waiting to see if mikrotik crashes i make a supout but mikrotik worked without any problem.
BUT exactly when i enabled my radius server after 5 or 10 seconds some users connected and then mikrotik again said
unregister_netdevice: waiting for ppp53 to become free. Usage count = 51
now i am sure that is problem occures when radius server answers to mikrotik and lot of ( approximately 15 ) pppoe users trying to connect at the same time.
We have the same problem view the topic http://forum.mikrotik.com/t/3-13-crashing-on-x86/23155/1
But I use freeradius server. I do not think the problem is attached with radius server as yesterday I disabled it and my users where authenticated via local, but the router continues to crash no difference.
Currently it looks like linux kernel bug, we will check it and inform you.
Regards,
Maris
Hello,
Well, this error message is coming directly from the Linux Kernel and that
makes things complicated - we need to relay on Linux Kernel developers for the
fix.
I suggest to play with SMP setting try to enable/disable it. Also a faster
RADIUS server might solve the problem
can you explain more please . i mean the reason of your advice . it is nearly impossible to reconfigure all of configuration manually AGAIN from first step. all of users will disconnected until config finish .
hey mikrotik guys . I see in another post that you said the 3.14 will be released in next week . does this problem solved completely in 3.14 ? please say details also . thanks
Well all of us are looking to solve the same problem.
I tried everything that you say and nothing. Change hardware, reconfigured, change version of RouterOS, and the same.
As you said, I’m using a FreeRadius Server
Well we hope that its problem will be resolved in v 3.14
Good Luck MKT Team
Rafael Lore
It is difficult to be trying with clients working, but in turn it is the best way of having betatester forced jeje. Honestly not from when the problem is generated, but I suspect that it is from v3.0. I hope that in the close V3.14. the problem is solved. We all lean the team mt, but these they must give priority to the topic, in my case I am a Latin-American client with mas of 100 licenses you pay. We all expect anxious and desperate.
We are still researching to know what exactly is happening and so far seems to be a random problem of instability envolving pppoe server only.
