Community discussions

MikroTik App
 
marlowbg
newbie
Topic Author
Posts: 33
Joined: Wed Oct 06, 2010 4:23 pm

Stale (dead) PPPoE connections

Wed Mar 09, 2016 1:22 pm

Using Router OS on x86 platform v6.34.2

I'm observing that after running for some time (few days let's say) I'm having more than 2000 PPPoE connections, 648 of them are running=no which for me is Dead/Stale.

Anyone having same issue and how they can be removed besides Manual removal?

What is the reason for getting such big amount of these Stale connections?

Attached screenshot for clarity
Screen Shot 2016-03-09 at 16.47.42.png
I can manually "Remove" them, but the IP address assigned remains.
You do not have the required permissions to view the files attached to this post.
Last edited by marlowbg on Tue Mar 15, 2016 3:28 am, edited 1 time in total.
 
marlowbg
newbie
Topic Author
Posts: 33
Joined: Wed Oct 06, 2010 4:23 pm

Re: Stale (dead) PPPoE connections

Tue Mar 15, 2016 3:20 am

Anyone having the same issue?

It's still persists in 6.34.3
 
ethernet
just joined
Posts: 22
Joined: Tue Aug 25, 2009 1:44 am

Re: Stale (dead) PPPoE connections

Sat Mar 19, 2016 11:27 am

Have you tried 6.35r33 ?

What's new in 6.35rc33 (2016-Mar-18 11:12):

*) ppp - fixed crash when ppp interface gets disconnected and user gets authenticated at the same time (most probable with slow RADIUS server);
*) ppp - fixed memory leak high number of pppoe clients to the same server;
*) pppoe - make fast path receive work on tile, arm and x86;
*) pppoe-client - implemented fastpath support;
*) ppp - do not crash when received multiple CBCP packets;
*) pppoe - added rfc4679 support;
*) pppoe-server - added pado-delay option;
*) ppp - close connection if peer wants to re-authenticate;
*) radius - warn radius client if incorrect secret is being used;
 
marlowbg
newbie
Topic Author
Posts: 33
Joined: Wed Oct 06, 2010 4:23 pm

Re: Stale (dead) PPPoE connections

Sat Mar 19, 2016 11:54 am

Hi,

I have deployed 6.35rc29 few days back as advised by Mikrotik Support team and I can now confirm that it solved the issue.

Hope to see this fixes soon in the Current branch as I don't feel very comfortable running few thousand of users on a RC version :)

Who is online

Users browsing this forum: araqiel, freemannnn, GoogleOther [Bot], synchro, vbkp and 111 guests