Anonymous | Login | 2024-10-04 01:08 EDT |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||
0001475 | PacketFence | core | public | 2012-06-21 10:46 | 2012-07-19 11:09 | |||
Reporter | fgaudreault | |||||||
Assigned To | fgaudreault | |||||||
Priority | low | Severity | tweak | Reproducibility | N/A | |||
Status | resolved | Resolution | fixed | |||||
Platform | OS | OS Version | ||||||
Product Version | devel | |||||||
Target Version | Fixed in Version | |||||||
Summary | 0001475: Refactor the Bandwidth accounting violation process | |||||||
Description | Instead of using sliding window, we should be more precise in the way we calculate the time interval for the bandwidth usage. Example. If I define a violation to trap user that are doing more than 20GB/month of bandwidth transfer. Say I hit that limit after 3 days. It should block the user until day 1 of next month if auto-enable if disabled or if auto-enable is enabled, it should start the bandwidth calculation from the violation release date instead of the beginning of the month for the next violation. | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
Relationships | |||||||||||
|
Notes | |
(0002846) fgaudreault (viewer) 2012-07-19 11:09 |
Fixed in acct_violations branch. Will be merged shortly. |
Copyright © 2000 - 2012 MantisBT Group |