From owner-freebsd-net@FreeBSD.ORG Wed Mar 9 05:51:33 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAC9016A4CE; Wed, 9 Mar 2005 05:51:33 +0000 (GMT) Received: from smtp1.skyinet.net (smtp1.skyinet.net [202.78.97.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 160BD43D2D; Wed, 9 Mar 2005 05:51:33 +0000 (GMT) (envelope-from fooler@skyinet.net) Received: from fooler (fooler.ilo.skyinet.net [202.78.118.66]) by smtp1.skyinet.net (Postfix) with SMTP id F36BD583C0; Wed, 9 Mar 2005 13:51:30 +0800 (PHT) Message-ID: <01d001c5246c$0b9ddc50$42764eca@ilo.skyinet.net> From: "fooler" To: "Bikrant Neupane" , References: <002a01c523ef$bc5af280$eb2d4fca@HOME> Date: Wed, 9 Mar 2005 13:51:31 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: freebsd-net@freebsd.org Subject: Re: Session Timeout issue in pppoed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 05:51:33 -0000 ----- Original Message ----- From: "Bikrant Neupane" To: Cc: Sent: Tuesday, March 08, 2005 11:01 PM Subject: Session Timeout issue in pppoed > Hi, > I have a pppoe server on FreeBSD 4.10. > I have configured my Radius Server ( radiator) to set Session-Timeout > parameter so that the clients who are using prepaid hour based service get > disconnected when their time is over. In the ppp.log file I see the the > Sessio-Timeout being accepted by the server. In the mean time the same > connection has another Session-Timeout parameter set whose value is 0!! As a > result the clients do not get dsconnected at the specified time. > I guess this is configuration issue/problem with ppp rather than pppoed. > > this is a portion of my ppp.log file. > > ppp[18466]: Phase: PPP Started (direct mode). > ppp[18466]: Phase: bundle: Establish > ppp[18466]: Phase: deflink: closed -> opening > ppp[18466]: Phase: deflink: Link is a netgraph node > ppp[18466]: Phase: deflink: Connected! > ppp[18466]: Phase: deflink: opening -> carrier > ppp[18466]: Phase: deflink: carrier -> lcp > ppp[18466]: Phase: bundle: Authenticate > ppp[18466]: Phase: deflink: his = none, mine = PAP > ppp[18466]: Phase: Pap Input: REQUEST (gomez5) > ppp[18466]: Phase: Radius: Request sent > ppp[18466]: Phase: Radius(auth): ACCEPT received > ppp[18466]: Phase: MTU 768 > ppp[18466]: Phase: VJ enabled > ppp[18466]: Phase: Session-Timeout 29218 <<<<< > ppp[18466]: Phase: Session-Timeout 0 <<<<< > ppp[18466]: Phase: Pap Output: SUCCESS > ppp[18466]: Phase: deflink: lcp -> open > ppp[18466]: Phase: bundle: Network > ppp[18466]: Phase: Radius(acct): Accounting response received > > Here is my ppp.conf file > default: > allow users > enable pap > allow mode direct > set mru 1492 > set mtu 1492 > set speed sync > set timeout 172800 #2 days: 48hrs > enable lqr > set ifaddr 202.79.xx.xx 202.79.xx.xx-202.79.xx.xx > load server > set radius /etc/radius.conf > accept dns > > > Any idea why this is happening?? Please suggest. pppoed is just a daemon processing the pppoe frames while (user) ppp is the one handling the session-timeout radius attribute once configured to use the radius service... the way i look at it, your radius server (radiator) is sending two session-timeout attributes which the user ppp accepted the two attributes and set the last value which is 0 (unlimited time)... try a tcpdump or your radiator utility if indeed your radius server is sending two session-timeout attributes... fooler.