After upgrade from 2.9.31 to 2.9.32 on PPPoE server with high load (up to 600-800 PPPoE Active connections), CPU hangs on 100% and PPPoE is not answering to responses. I must restart the computer, but after short time, CPU hangs on 100% CPU again. I was not able to find conditions when it hangs, it hanged with 96 Active connections too ! I downgraded to 2.9.31 and it works without 100%CPU hangs. I have another two PPPoE servers upgraded to 2.9.32 but with less PPPoE users ant they are working fine.
I sent supout to MT already awaiting for help.
My new observation: It seems that that the problem occurs when there is very high number of requests for PPPoE session.
From pppoe they problems are already from over 200 active users, from some time.
- ghost inteface.
- users cannot login when it is more than 200 active, after reboot.
It in my case helps (on point 2), if switch off interface on which PPPoE is Server, reboot Mikrotik, and I after reboot will include this interface again, customers log in correctly, and cpu utilization is OK.
I sended already some time this and all necessary data, to support, and I wait on improvement ( she had to be in version 2.9.32, and in extra pppoe package)
- users cannot login when it is more than 200 active, after reboot.
Did you check the level of license will allow you more then 200 pppoe connections?
Did you check the level of license will allow you more then 200 pppoe connections?
Yes, I have L6, and this is no problem witch license.
If little active customers are about 100-200 this after reboot has no problem.
Problem begins if it is about 250 or more, after reboot mikrotik, customers can not login and after several minutes cpu has 100%.
Mikrotik support knows this problem, he had to be solved in version 2.9.32, but it is not unfortunately.
Tried 2.9.32 this weekend. Couldn’t authenticate a single user. Had roughly 30 (of 1100) half logged in users with 100% cpu load on the pppoe server.
I guess they missed something during the bughunt. 2.9.26 through 2.9.31 was riddled with ghost interfaces that could only be removed from winbox (and not console)
I get this issue with 95 users.
If to many try to connect simultaniously it locks up the PPPoE Stuff.
I downgrade to 2.9.30 and the problem goes away
The problem I have with 2.9.30 (I’ve had it since 2.9.18) is that some times for no known reason the router will show the 95 users on in /ppp active print and /interface pppoe-server print and won’t allow any more on stating that it’s over the 200 sessions I’m licensed for.
95 != 200.
The first time I reported this I was told to do a net-install on the router and that it was probably a local fault on the router. It’s now happening at two sites even after doing a net-instal
Hi,
2Ghz and 256Mb are too little for 350 PPPoE Client. Because if not all online are runs there with 2.9.30 completely well. But with the 2.9.31 or also 2.9.32 that cannot be done in the long term.
dingsingo
it looks like everything is fine in 2.9.34…
But it looks in such a way, as if it would really go into 2.9.34.