[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
why does dail-up or pppoe access always has session-timeout ?
- Subject: why does dail-up or pppoe access always has session-timeout ?
- From: freimer at freimer.org (Fred Reimer)
- Date: Thu, 30 May 2013 12:32:51 +0000
- In-reply-to: <[email protected]>
- References: <[email protected]>
Because PPPOE comes from PPP, which was designed for dialup. You typically don't want to leave a dialup connection up forever.
Sent from my Verizon Wireless 4G LTE smartphone
-------- Original message --------
From: Joe <sj_hznm at hotmail.com>
Date: 05/30/2013 5:11 AM (GMT-05:00)
To: NANOG <nanog at nanog.org>
Subject: why does dail-up or pppoe access always has session-timeout ?
a question obsessed me for a long time. "why my pppoe connection to internet has a max session time, even if every thing goes ok? "
In our DSL access network , max session timeout is set to 4 days, this parameter is sent to BAS by radius server after finishing authenticating procedure. As I know, beside us some other service providers also applied this parameter to pppoe session, the parameter varies from 48 hours to 96 hours. Reading documents of BAS, we found this is default value for session-time on BAS, that means even if radius server does not response BAS with session-timeout attribute BAS will cut pppoe session after sometime. so , why does those BAS designer or protocol designer set such a parameter for pppoe access ?
should anyone do me a favor on explaining this ?