Hi, Mikrotik Users
On my PPPOE server (ROS 3.13) continues PPPOE DIE,
So PPPOE connected, is working very well, but after some minutes it dies, no traffic is passing through it.
Such problem there was with PPPT on earlier versions, but on 3.13 this problem we can see just with PPPOE,
When this problem will be fixed?
Thanks With Regards
Karapet Aznavuryan
as i say before , this problem was exist even in 2.9 maybe you did not understand but after a lot of conversations with support and forum the answer is NOTHING.
after it die, create sup-out file and send it to support
I have already sent supout file to mikrotik team, but there is no news yet,
I hope they’ll fix that problem, as it is very important for Mikrotik Users.
Almost every Provider uses PPTP or PPPOE Servers to provide their services.
So we need it to work properly.
With Regards
Karapet Aznavuryan
i have same problem. When pppoe client request a big number of connections, pppoe freeze, but it not disconnect. Version is 3.13 … problem solved with downgrading?
it`s curious, when clients disconnect and reconnect, connectiviti problem was solved.
sorry for my bery bery bad english
I have this problem since first version of 2.9 but mikrotik team does not care about it . even one reply !!!
maybe it is a core FEATURE !! which makes it differ from other pppoe servers.
Hello people,
probably I have a problem similar to you.
After a while my PPPoE clients connections went down and then reconnect a lot of times.
In the log I can see PEER IS NOT RESPONDING message, wireless connection is ok ( tx/rx ccq 60/95 ) with no disconnections at all;
it seems that Mtik is loosing client replies; this problem is with all types of clients ( NS2, Straightcore etc. )
RB333 - 333Mhz - Ros 3.13, I am going to change wireless card (R52H) with a new one, second step is to change RB333 with RB433.
I already sent supout file to Mikrotik, they requested also a log at time of error, no solutions till now.
Regards
Alessandro
Actually the physical link is not the problem . i have tested it at the client side at the time of the problem ( time out ) . exactly when the pppoe dies and i got time out ( client side ) i could open winbox with the MAC not with ip ! and after some seconds of working with winbox over MAC the ping of the pppoe came back !!!
so client at the pppoe die time ( time out ) have 3 ways to bypass the time out
other friends which have this problem please try the second way and say result. if there is another way please say here.
sometimes this problem occurs over 100 times an hour and sometimes once a day
Hello,
I think should be fine if Mikrotik team inform us on progress of analysis of this problem.
It is urgent and we need to be informed if a solution will be released soon.
Thanks
Alessandro
I agree .
Estimated
As I could observe in my situation, it is not a MRU/MTU’s/MSS problem. Simply it is given occasionally, and I am starting suspecting in clients that they have a level of poor sign. The solutions that encontre: To enter for cap two with winbox or neighbor by means of mac-telnet To disconnect, and reconnect. In the terminus, to do a ping to some random page in order that routeros this obliged one to resolve. I did a script in order that every 5 seconds realizae a ping to http://www.google.com, nevertheless the problem is not solved. I emphasize that the pppoe is still active, there is not disconnected, only that it freezes. I am suspecting that is a problem of loss of routes, another thing does not happen to me.
Regards
compare your setups - do you have big PPPoE server with lots of users or small router over wireless - those are completely two different things. Do you use RADIUS, queues, MRRU??
Have you enabled pppoe,debug logging to remote place to actually see what was the last thing your pppoe concentrator did?
At this point we see only stand alone - independent incidents and in this case problem might be anywhere (pppoe clients, nework structure, wireless problems)
As soon as we will be able to find something common in several setups we will have ability to start fixing it
i have sent many supout till now . not enough ?!
i have strong x86 system and i tested with some other systems.
the routeros is level 6
i have external radius server and less than 30 queues
no mrru
logged pppoe,debug to external syslog but nothing useful
no wireless at all . no link problem also . i have tested with a lot of physical link types. and i have this problem since early versions of 2.9
actually i have a lot of research to find where this problem comes from but no success.
Hello, I think that a “common” problem to all of us is that PPPoE clients disconnect, we have radius, no MRRU no wireless disconnections and supout files already sent to you. please Normis a question to you: have you tried to read our supout? Mine is not a polemic question but my impression, and probably also for other peole here, is that you ( Mikrotik support ) have not yet taken this problem into appropriate level of urgency.
I know, probably this is not Mikrotik problem, but we need to you a little bit more help than just " this is not mtik problem".
I use your products and will continue to use them but sometimes support should jump into our field to see real customers 
With best regards
Alessandro
compare your setups - do you have big PPPoE server with lots of users or small router over wireless - those are completely two different things. Do you use RADIUS, queues, MRRU??
Have you enabled pppoe,debug logging to remote place to actually see what was the last thing your pppoe concentrator did?
At this point we see only stand alone - independent incidents and in this case problem might be anywhere (pppoe clients, nework structure, wireless problems)
As soon as we will be able to find something common in several setups we will have ability to start fixing it
Ive heard rumors somewhere that MT team would replace the current kernel and at this point I started to believe that it will not happens until a major version number change, perhaps. BUT I do believe that MT team knows that this freeze problem is something they need to rely on kernel developers to solve. Could this be something common? (unregistered_netdevice: … bla bla bla thing) That is what makes me feel a bit of calm facing the situation.
Now reading your last words I may change my mind. Didn’t said anything until now because MT was looking about that random queue missing thread. Anyway, I would like to help this out. What can I do? Well… Our problem here is only FREEZE of pppoe servers on wireless.
We have actually ONE device running ROS 3.13 freezing due to PPPOE server problem, so… If you want, we can give you full access to our router and also, we can set any LOGs you may need to a remote Syslog right inside MTs lab. Also, we recommend that MT keep monitoring this device with SNMP as it is the way we detect this freeze thing over the time. Otherwise you must learn yoga and sit watching the box til the freeze happens. Is there anything else we can do to aid MT team?
Thank you
Ozelo
Problem with PPPoE is in RouterOS version which is not RC (release candidate).
If you (I) use 3.0rc9 for example, on RB333/600, pppoe never freeze and everything works fine. Ok, try to upgrade it to 3.13 - pppoe die.
I tried to do same thing (put 3.0rc9) on RB433 but not working on this board, only 3.0 and up.
BUT…RB333 is end of life and now what ?!
Yeah, I think the same.Tomorrow I will go to replace the failing RB333 with an RB433 ROS 3.13, I think that the problem will disappear.
Another consideration for Normis: you have all our supout files so would be easy for you to check our configurations ( pppoe setup, mrru etc ), so why you said:
“compare your setups - do you have big PPPoE server with lots of users or small router over wireless - those are completely two different things. Do you use RADIUS, queues, MRRU??
Have you enabled pppoe,debug logging to remote place to actually see what was the last thing your pppoe concentrator did?”
You should know our configurations and compare them, is it thrue?
With best regards to all
Alessandro
Boys
As I could observe, the problem is given in some clients sporadically, nevertheless the pppoe server continues working well in the rest of the clients. The pppoe server always works, except that in some clients it(he,she) freezes.
Regards
that is my point - all your cases are completely different. “pppoe disconnects” is not one specific problem. it can be caused by anything
Ok Normis, I agree with you, I know what does mean " problem determination", but seems that after a lot of customers claiming a problem on PPPoE, no actions or a precise direction was taken. PPPoE problem are arised since ros 2.9 and my impression is that no actions to correct the problem or at least “some” problems were made, am I wrong? Today I will go to change RB333 with RB433, I will let you informed on results, obviously I will not change the clients; another info for you: yesterday I downgraded to version 3.0 rc14, the PPPoE login of clients was EXTREMELY fast compared to version 3.13 ( 5 seconds - 30 seconds ) and disconnections are decreased a lot, another strange think is that disconnections starts at around 10:00 local time ( 08:00 gmt ), it maybe that the temperature of RB333 increases and the problem arises? It maybe a solution to decrese the clock to 266Mhz?
Thanks and regards
Alessandro