Suppose I have a user who is billed based on usage (or traffic) per month. If we're using RADIUS accounting to keep track of bytes|octets in/out, the accounting stop packets hold all that information. Suppose this user has a dedicated service and never logs off. If this user is online before their billing period starts and stays online until after their billing period stops, they could conceivably not get billed until they disconnects for the first time.
That poses a problem, obviously. If a user doesn't log off (or reboot their router as the case would be) for 3 months, they could get a pretty lofty bill which would not bode well. If a stop packet is forged at the end of a billing cycle without the user disconnecting, what are the ramifications? When the user finally does log off, a stop packet is sent with the same sequence number as the forged one. What happens? How does one get around this, or is there even a way? -- Regards, Jason A. Lixfeld Fastvibe Corporation Senior IP Network Engineer 220-156 Front St. W [EMAIL PROTECTED] Toronto, ON M5V-2L6 ------------------------------------------------------------- tel://416.341.0099:223 fax://416.341.0088 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
