On Thu, 26 May 2011 18:54:49 +0200 Marek Michalkiewicz wrote: > > This issue has nothing to do with RADIUS. There is still 4GB rollover > in byte counts logged to local log files, and passed to ip-down > scripts on the local machine running pppd. The long counters are > also not used in the MAXOCTETS feature, so the limit must be <4GB or > disabled. > > I'm looking into ways to implement monthly traffic limits (lower speed > above the limit), without terminating PPPoE connections every 24 hours > like phone companies do. Customers get static IP addresses that don't > change on reconnect, but some routers may lose their NAT state, etc. > > Thanks, > Marek
Hi, I read more carefully you message, and I realized we are talking about 2 different issues. This bug was submitted to report the missing of 2 radius extensions in the radius plugins of the ppp. Namely they are Acct-Input-Gigawords and Acct-Output-Gigawords as defined by rfc2869. On the other hand, there is the issue you reported about Bytes_Send, Bytes_Rcvd which also wrap at 4GB. Theese 2 issues also seem to have different solving approach. For the radius plugin problem, the solution is to implement a new set of counters. For the Bytes_Sent, Bytes_Rcvd problem, the existing counters need to be increased over the existing 32bit size to accomodate more data. Because there are 2 different issues with 2 different solutions i doubt they belong to the same bugreport. [offtopic] As for your wish to implement bandwidth limiting based on traffic volume, this should be easier to accomplish using radius as opposed to Bytes_Sent, Bytes_Rcvd passed to ip_down. Radius has traffic information available without the need to disconnect the ppp session, while it seems the Bytes_Sent, Bytes_RCVD are only transmitted upon ppp disconnect. I might be wrong though :) [/offtopic] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
