PPPoE Client and keepalive-timeout

jaykay2342 · Tue Sep 24, 2013 9:10 pm

Hi guys,

i currently investigating an outage. Main uplink line failed and failback to DSL ( PPPoE ) was not working. It looked like the PPPoE Session died. Disabling and re-enabling of the PPPoE client interface solved it. I found out that there was no keepalive-timeout configured. As i was not able to find any default value in the wiki i'm wondering: Is it possible that the device was not doing any kind of "keepalive checks"?

btw it's run ROS 6.4

jaykay

asaleh75 · Tue Sep 24, 2013 10:07 pm

Hi,
keepalive-timeout default value is 10

jaykay2342 · Tue Sep 24, 2013 10:19 pm

Hi,
keepalive-timeout default value is 10

where have you found that information ?

asaleh75 · Tue Sep 24, 2013 10:35 pm

Hi,
keepalive-timeout default value is 10
where have you found that information ?

Hi,
Please check this link http://wiki.mikrotik.com/wiki/Manual:Interface/PPPoE Look at PPPoE Server Setup. Here a Notes:
"The default keepalive-timeout value of 10 is OK in most cases. If you set it to 0, the router will not disconnect clients until they explicitly log out or the router is restarted. To resolve this problem, the one-session-per-host property can be used."

jaykay2342 · Tue Sep 24, 2013 11:31 pm

Hi,
keepalive-timeout default value is 10
where have you found that information ?
Hi,
Please check this link http://wiki.mikrotik.com/wiki/Manual:Interface/PPPoE Look at PPPoE Server Setup. Here a Notes:
"The default keepalive-timeout value of 10 is OK in most cases. If you set it to 0, the router will not disconnect clients until they explicitly log out or the router is restarted. To resolve this problem, the one-session-per-host property can be used."

This is for PPPoE Server i'm talking about the PPPoE Client.

asaleh75 · Wed Sep 25, 2013 7:42 am

Hi,
Yes, no information in the wiki. When i create PPPoE client RouterOS set keepalive-timeout=60.

[admin@M-S] > /interface pppoe-client print
Flags: X - disabled, R - running 
 0    name="pppoe-out1" max-mtu=1480 max-mru=1480 mrru=disabled interface=ether1 user="" password="" profile=default 
      keepalive-timeout=60 service-name="" ac-name="" add-default-route=yes default-route-distance=1 dial-on-demand=no 
      use-peer-dns=no allow=pap,chap,mschap1,mschap2

jaykay2342 · Wed Sep 25, 2013 12:19 pm

Thanks, thats a good way to find out the default value. I manual set a timeout and will monitor the pppoe link.

Decsus · Mon May 20, 2019 3:34 pm

Hell of a necro post, apologies for that, but this is exactly the place to ask my question.

I have a setup

RB2011-RM serving as a PPPOE server (Radius behind that)

40 CPE's connected to the RB2011-RM (Hap Lite's)

Each CPE has 2 PPPoE clients set up, 1 is for internet, 2nd is for management
What I have found is that if the RB2011-RM somehow loses power, the CPE's maintain their PPPoE session.
The RB2011-RM restarts and waits for new requests (All previous sessions being closed on the RB2011) but doesn't get any because the CPE still thinks it has an active working session (2 sessions per CPE).
In effect the CPE never closes its session and thus never tries to reconnect.

CPE PPPoE client settings
Keepalive timeout is blank (Default)
on the Profile
Session Timeout = blank (Default)
Idle Timeout = blank (Default)

RB2011 PPPoE Server settings
Keepalive timeout = 60
One Session per host = NO
Max Sessions = blank
on the Profile
Session Timeout = blank (Default)
Idle Timeout = 30 Minutes
Only One - NO

Would greatly appreciate your feedback.

VMX · Mon Feb 21, 2022 8:02 pm

Hell of a necro post, apologies for that, but this is exactly the place to ask my question.

I have a setup

RB2011-RM serving as a PPPOE server (Radius behind that)

40 CPE's connected to the RB2011-RM (Hap Lite's)

Each CPE has 2 PPPoE clients set up, 1 is for internet, 2nd is for management
What I have found is that if the RB2011-RM somehow loses power, the CPE's maintain their PPPoE session.
The RB2011-RM restarts and waits for new requests (All previous sessions being closed on the RB2011) but doesn't get any because the CPE still thinks it has an active working session (2 sessions per CPE).
In effect the CPE never closes its session and thus never tries to reconnect.

CPE PPPoE client settings
Keepalive timeout is blank (Default)
on the Profile
Session Timeout = blank (Default)
Idle Timeout = blank (Default)

RB2011 PPPoE Server settings
Keepalive timeout = 60
One Session per host = NO
Max Sessions = blank
on the Profile
Session Timeout = blank (Default)
Idle Timeout = 30 Minutes
Only One - NO

Would greatly appreciate your feedback.

Sorry for reviving your necro response to a necro post

I just happen to be troubleshooting a small issue with PPPoE disconnects too, and stumbled upon this post. Did you ever manage to solve this?

From what you tell in your post, what I gather is that it should be the clients that implement a keepalive in this situation, right? You had only implemented a keepalive on the server side (the RB2011), but that keepalive is never triggered because it's the RB2011 that actually loses power. On the CPE side, the tunnel is never closed either, because there's no keepalive. They don't care if the RB2011 goes down, they just keep the tunnel up.

Wouldn't this be solved by just setting a keepalive in the CPEs too? That way if the RB2011 doesn't respond for more than X seconds, the CPEs will consider the PPPoE tunnel dead and try to reconnect.

Hopefully this is how you solved it... as I'm going to do the same thing on my end

PPPoE Client and keepalive-timeout

PPPoE Client and keepalive-timeout

Re: PPPoE Client and keepalive-timeout

Re: PPPoE Client and keepalive-timeout

Re: PPPoE Client and keepalive-timeout

Re: PPPoE Client and keepalive-timeout

Re: PPPoE Client and keepalive-timeout

Re: PPPoE Client and keepalive-timeout

Re: PPPoE Client and keepalive-timeout

Re: PPPoE Client and keepalive-timeout