PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001604PacketFencecorepublic2012-11-13 09:432015-02-18 10:59
Reportermaikel 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version3.6.0 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0001604: bandwith accounting per HOUR
DescriptionAlso mentioned in the maillist.
With interim updates on accounting data, its a good feature to have an HOUR of even minute feature in the accounting maintenance loop. If the main pf.conf has information that the switches have interim updates, these code stubs can be enabled. Hope this can make it in the 3.6 train fixups
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-11-13 09:43maikelNew Issue
2012-11-14 10:11maikelNote Added: 0003279
2012-11-16 12:11maikelNote Added: 0003280
2015-02-18 10:59lmunroNote Added: 0003922
2015-02-18 10:59lmunroStatusnew => closed

Notes
(0003279)
maikel   
2012-11-14 10:11   
Also not the PacketFence Network Devices Configuration Guide needs to add somewhat more info about accounting to the samples

aaa accounting suppress null-username
!to supress shell logins etc
aaa accounting dot1x default start-stop group packetfence
! send start stop records

So far i am not using interim updates as it seems pf is not able to handle the data correctly.
i will work tomorrow on replicating this issue. IOS 15.0 seems to be also quite strange with sending negative accounting data.
(0003280)
maikel   
2012-11-16 12:11   
Good not here is. Cisco seems to have issues with the gigawords on later ios. A 2960 for example works good with gigawords till:
122-55.SE6

Loading 122-58.SE2 or even ios15 cause the gigawords attribute not to get send to the radius server
(0003922)
lmunro   
2015-02-18 10:59   
Obsolete bug tracker entries.
PF 4 introduced changes that either make these irrelevant or impossible to reproduce.

New issues are moving to github issues.