Date: Fri, 11 Mar 2005 10:13:30 +0545 From: Bikrant Neupane <bikrant_ml@wlink.com.np> To: freebsd-net@freebsd.org Cc: fooler <fooler@skyinet.net> Subject: Re: Session Timeout issue in pppoed Message-ID: <200503111013.30287.bikrant_ml@wlink.com.np> In-Reply-To: <01d001c5246c$0b9ddc50$42764eca@ilo.skyinet.net> References: <002a01c523ef$bc5af280$eb2d4fca@HOME> <01d001c5246c$0b9ddc50$42764eca@ilo.skyinet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Exactly!!! There was a bug in our radius code :D thanks again, Bikrant On Wednesday 09 March 2005 11:36, fooler wrote: > ----- Original Message ----- > From: "Bikrant Neupane" <bikrant_ml@wlink.com.np> > To: <freebsd-isp@freebsd.org> > Cc: <freebsd-net@freebsd.org> > 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. > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503111013.30287.bikrant_ml>