I seem to have a couple of problems with the reports in packetfence 4.5.0.

The registered nodes report doesn't seem to be showing historic information.  
If I look at "New Nodes" all the data is there and similarly if I look at 
"Wireless Connections" I can see a graph of devices that have connected.  But 
if I look at "registered nodes" I get the message "There's not enough data to 
generate this graph. Is PacketFence in production?"  However, if I register a 
node, it shows that one node as being registered, until I unregister the node 
and it goes back to having no information.

Also at the moment I'm in the process of trying to sort out Radius Accounting 
to get bandwidth information.  At the moment the data isn't being sent from my 
wireless controller (hp msm720, I'm in the process of contacting HP about 
this,) so that may be the reason for my issues.  However if I select the "Top 
25 Bandwidth Consumers" report I get the message "Error! Can't fetch data from 
database for report nodebandwidth."  And when I look at the tables there's no 
nodebandwidth table.  I've noticed there's the radacct_log table (which as 
you'd expect) shows all rows to have acctinputoctets and acctoutputoctets to be 
'0'  If I update some of these values using sql, I can't see any of that 
information elsewhere in packetfence.

Also, while I'm asking, how difficult is it to create custom reports and where 
should I start to look?

Thanks
John

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to