Latest Version & Release History
RADREP version 1.89hi. Release date: 15th December 2009

Features added in version 1.89hi (15th December 2009)

- Changed the layout of some reports.

- The 'Company Name' heading is now at the top of each report and can be customised.
To customise the report heading you need to manually modify the radrep.ini file (located in the c:/Program Files/RADREP folder by default) to include the configuration item 'ReportCoHeadingName' in the [Hidden Settings] section as shown below.
The contents of the 'ReportCoHeadingName' field will replace the 'Company Name Header' in each report with whatever HTML code you have configured. The following example also shows how to add a logo if desired.
[Hidden Settings]
ReportCoHeadingName=<H1>My New Company Name &nbsp&nbsp&nbsp&nbsp&nbsp&nbsp <img src="http://www.radiusreporting.com/images/SecBoy-Logo.gif"width="79"height="27"></H1>

- Added the ability to change the report output scale to one of Bytes, KiloBytes, MegaBytes and GigaBytes. Currently this is only for the Usage Summary report, with all other reports to follow soon. To enable this feature you need to edit the radrep.in configuration file and add one of the following lines (depending on scale required) in the [Config] section:

DISP_SCALE=0 (Bytes scale)
DISP_SCALE=1 (KiloBytes scale)
DISP_SCALE=2 (MegaBytes scale)
DISP_SCALE=3 (GigaBytes scale)

Example for Gigabytes scale:
[Config]
DISP_SCALE=3


Features added in version 1.89g (18th September 2009)

Bug Fix
- Fixed an issue where for some log formats such as FreeRadius the Bytes-Sent and Bytes-Recieved fields were being displayed the wrong way around in reports.

 

Features added in version 1.89f (16th March 2007)

- Fixed an issue with Acct_Session_Id and Juniper SSL VPN logs. Juniper constructs strange session id strings that RADREP was initially mishandling causing only 1 connect per user to be identified.

 

Features added in version 1.89e (5th December 2006)

- Added 2 User-Name retrieval filter options (found under the Advanced Settings screen):
    a) Strip the REALM name from the user-name field when importing user-names from a Juniper SSLVPN RADIUS log. E.g. user-name of rhansen(REALM NAME)[ROLE1][ROLE2].... becomes just 'rhansen' (no quotes) All characters after the first left rounded bracket '(' are removed from the user-name field.
    b) Strip the Fully Qualified Domain Name (FQDN) from the user-name field when importing user-names from a Aventail SSLVPN RADIUS log. Eg. (rhansen)@(Authentication Realm) or rhansen@radiusreporting.com.... becomes '(rhansen)' or 'rhansen' (no quotes) respectively.

-Added a configuration field called MAX_USERNAME_CHARS in the [Hidden Settings] sections of the radrep.ini configuration file that allows you to modify the maximum number of characters in the user-name field. The default is 40 characters. Increasing this value will allow the support of usernames that have very long REALM/ROLE or FQDN suffixes. In most cases a user-name field of more than 40 characters indicates that there is some sort of corruption or problem within the log file being processed.
radrep.ini section example:
[Hidden Settings]
MAX_USERNAME_CHARS=40


Version 1.89d (17th June 2006)

Bug Fix
- Fixed a navigation issue with the HTML billing reports. Not all billing reports were accessible from the main index page due to sub directory and file placement errors.

 

Version 1.89c (28th February 2006)

Bug Fix
- Fixed a sorting problem with the historical report index file (historical.html). Dates with 2006 would appear before 2005.

 

Version 1.89b (23rd September 2005)

Bug Fix
- Fixed a problem writing the historical report index file (historical.html). Some URL links were published as 'unknown'. This is now fixed.

 

Version 1.89a (2nd September 2005)

Bug Fixes
- Fixed a problem where URL reports for 'user1' were being overwritten by 'user1 ' (trailing space) reports. Now the output URLs have the space replaced with an underscore so they are different.

- Temp file write error fix. Fixed a problem where some temp file names were failing to be written due to having invalid file name characters in them.

 

Features added in version 1.89 (1st August 2005)

- Memory Usage Configuration.
Added a memory usage slider bar that allows you to set the maximum number of accounting records per user to store in physical memory before writing them out to a temp file. By tweaking this option to your reporting requirements it is now possible to process and generate reports for log files that are in the order of tens of gigabytes in size.

- Each report type is now written to its own unique sub-folder under the report output folder.
The following shows the folder names that are now created for each report type under the selected output folder:
IPusage - IP Address usage reports
NASPortTypeUsage - NAS Port Type usage reports
NASPortUsage - NAS Port Number usage reports
NASusage - NAS IP Address usage reports, including Maximum Concurrent Usage reached and Active User reports
TotalAvg - Totals and Averages report
UserBilling - User based billing reports
UserUsage - User based usage reports
IAS_AA_AD - Microsoft IAS, Access Accept/Deny report.

- An option was added under the 'Advanced Settings' dialogue box to 'Omit users with zero completed sessions' from the reports.
This will make sure that users that have not completed at least one session will not appear in the reports.
It will eliminate users with 0 connects from the reports.

- Added an option under the 'Configuration' dialogue to allow the entry of a 'Report Description'.
This is so a short (50 character max) report description can be entered for each report generated.
The 'Report Description' will appear as a column in the 'Historical Report' index (historical.html)
as well as at the top of each reports 'Home Page'.

- Each report 'Home Page' now also shows how long it took to generate the set of reports.
(i.e. The log processing and report generation time)

- An option was added under the 'Advanced Settings' dialogue to turn on/off the warning about "Unknown Log Formats".
If you are processing an entire sub-folder of logs and some are in a format that RADREP does not understand this option will
suppress the 'Unknown Log Type' pop-up warning that is displayed when attempting to process these logs.

- The User Usage Detailed report attribute selection dialogue was revised to allow up to 6 user defined attributes.
Some check-box selectable attributes that were not commonly used were replaced with more commonly used attributes.
The table below summarizes the changes made.

Attributes Removed Attributes Added
Ascend-Connect-Progress Acct-Session-Time
Ascend-Billing-Number Acct-Session-Id
LE-Advise-Of-Charge Custom-Attribute#3
LE-Terminate-Detail Custom-Attribute#4
Ascend-Modem-PortNo Custom-Attribute#5
Ascend-Modem-SlotNo Custom-Attribute#6


Bug Fixes
-Fixed 'Process Subdirs' option so that it also processes log files in the chosen 'top level' directory as well as all sub-directories under it.
-Fixed date format bug when Regional Settings 'short date format' was set to yyyy/MM/dd. (dates would not change)

Issues
-Documentation and Windows Help files have not been updated since version 1.87.
-Documentation for new and modified features will be included in the version 1.90 release.

 

Features added in version 1.88 (21st May 2005)

- Added basic support for processing 'TACACS+ Accounting' logs (Start/Stop records only).
CSV formatted TACACS+ Accounting logs produced by CISCO ACS are now supported.

RADREP maps TACACS+ attributes to equivalent RADIUS attributes for reporting purposes as shown in the table below.

RADIUS TACACS+
Date Date
Time Time
User-Name User-Name
Acct-Status-Type Acct-Flags
Acct-Session-Time elapsed_time
Acct-Input-Octets bytes_in
Acct-Output-Octets bytes_out
Acct-Session-Id task_id
Framed-IP-Address addr
Acct-Terminate-Cause disc-cause
NAS-IP-Address NAS-IP-Address
NAS-Port NAS-Portname, port

Note: As with RADIUS, the detailed user usage report can show other TACACS+ attributes such as 'cmd' by adding them as 'Custom Attributes'.

- Updated the 'Run Mode Configuration Utility' to auto select folder rotation and added a 'Previous Week' report period.
The 'Previous Week' report period starts 7 days prior the current day and ends one day prior the current day.
E.g.. Current day is Monday.
Previous week 'start date' is Monday 12am of the previous week. Previous week 'end date' is Sunday 11:59:59pm of the previous week.

- Firefox browser compatibility. Changed \ to / in web page URL pathing to make Firefox navigate correctly.
Note that the Firefox bottom status bar does not inform of progress when sorting report columns. This only works under Internet Explorer.

- Changed 'CSV File' to 'USERS.CSV File' in drop down list of user retrieval methods. Since this was confusing some users, it was changed to reflect the file that is used to read in additional user information. (USERS.CSV)

Features added in version 1.87 (13th January 2005)

-Added the ability to process accounting logs residing in all sub-directories under the specified 'log file(s) folder'. Previous versions of RADREP could only process all logs that resided in the same folder but not in sub-directories under this folder.

Features added in version 1.86 (2nd January 2005)

-Added TCCRadius (Talon Computer Consulting Radius) log file compatibility. TCCRadius uses a Livingston format log file but writes a non conformant date line and user-name (username) attribute. By using a text editor and manually adding two configuration entries to your 'radrep.ini' configuration file RADREP will process TCCRadius accounting log files.

TCCRadius Compatibility Details.

To enable TCCRadius accounting log file compatibility:
1. Run the RADREP application at least once and configure the location of your log files.
2. Exit the RADREP application.
3. Using Windows Explorer browse to the RADREP installation folder (usually c:\program files\RADREP\) where the 'radrep.exe' application is located. If you have performed step 1 you will now see a 'radrep.ini' configuration file.
4. Open the 'radrep.ini' configuration file with any text editor (Windows Notepad will do just fine) and add the following two lines to the [Hidden Settings] section which is located at the very end of the file:

[Hidden Settings] <----- This line will already exist. You need to add the next two lines.
TCCRADIUS=1
PRIMARY_KEY_ATTRIB=USERNAME

5. After making the above changes save the 'radrep.ini' configuration file and then run the RADREP application again to begin processing your TCCRadius log files.

Sample TCCRadius STOP record

The following is a typical TCCRadius stop record showing the non-conformant date line and 'USERNAME attribute.

The standards say that the date line should be 'Wed April 01 00:04:11 2004' and the 'USERNAME' should be called 'USER-NAME')

04/01/2004 00:04:11 202.141.54.71 711 STOP testuser@mycompany.com
EVENT-TIMESTAMP=1080806589
ACCT-SESSION-ID=296900920
ACCT-SESSION-TIME=891
ACCT-INPUT-PACKETS=1493
ACCT-OUTPUT-PACKETS=1878
FRAMED-PROTOCOL=PPP
FRAMED-IP-ADDRESS=202.141.54.71
NAS-PORT-TYPE=ASYNC
NAS-IP-ADDRESS=203.161.51.254
ACCT-STATUS-TYPE=STOP
CALLED-STATION-ID=98717834
ACCT-INPUT-OCTETS=131082
ACCT-OUTPUT-OCTETS=678107
CALLING-STATION-ID=987174631
USERNAME=testuser@mycompany.com
NAS-IDENTIFIER=nas91.mycompany.com

Note: To process other types of RADIUS server logs you will need to undo these changes as they enable processing features specific only to TCCRadius server logs that write their logs in Livingston format but use a non-conformant date line and user-name (username) accounting attribute.

Features added in version 1.85 (1st December 2004)

- Enabled 'out of the box' ability to process Microsoft RAS logs. Previous versions could process RAS logs as long as the IAS server's 'Service Name' was changed from RAS to IAS or RADREP was configured to look for a 'service name' of RAS instead of IAS.

- The IAS Access Accept / Deny Report was enhanced to show a column with the users First and Last name when using a users.csv file to import full user details.

- Under the Advanced Configuration section a checkbox was added to enable the processing of Interim accounting record data.
If Interim accounting records are being written to your log files, RADREP can now process them and give accurate usage statistics for a specific period of time, even if the user did not log out and create an accounting STOP record during the selected period.
As such, a new column called 'Record Types' has been added to the 'User Usage Detailed' report to show the accounting 'Record Types' used to calculate the usage for a user's session. This new column will have one of the following entries depending on when the user's session started and ended..
Stop --------------------> The user's session started prior to the current report period but ended within this report period. As such no START record was found in this period.
Start/Stop ---------------> The user's session started and stopped within the selected report period.
Start/Interim -------------> The user's session started in the current report period, but will finish sometime after the end of this report period.
Interim/Stop -------------> The user's session started prior to the current report period and ended during this report period. Interim records allow us to calculate the usage for just this period.
Interim/Interim -----------> The user's session did not start or stop during this period. It started before the selected report period start date/time and will end after the selected report period end date/time. Interim accounting data was used to calculate the user's usage for just this report period.

- Added a Checkbox under the 'Advanced Configuration' section to enable/disable the NAS-IP-Address filter to operate on the 'user-name' import from RADIUS logs.
Within the 'RADIUS Log File - User-Name Retrieval' area of the 'Advanced Configuration' screen, enabling the 'Filter on specific NAS-IP-Address' option can only be done by first enabling and configuring the 'Filter on NAS-IP-Address' option under the 'RADIUS Log File - Processing Options' section.
When both the 'Filter on NAS-IP-Address' and the 'Filter on specific NAS-IP-Address' options are both enabled, only user-names having activity on the specified NAS-IP-Address will show up in the SITE/GROUP/USER SELECTION window (and subsequent reports) when the 'Retrieve User List' button is clicked on.
If you require the ability to generate billing reports for all users in the log, but only want to gather usage information for those users who logged into a specific NAS-IP-Address then you should only enable the 'Filter on NAS-IP-Address' option under the 'RADIUS Log File - Processing Options' section. When selecting only this option, only users who used the Specific NAS-IP-Address will have usage data in their reports for the selected period. All other users will have no usage data in their reports but still have the ability to be billed a 'fixed service fee' for the period.

Features added in version 1.83 (9th August 2004)

-Added the ability to select which fields are displayed in the 'User Usage Summary' report. A new configuration button for this report allows you to enable/disable the display of the following fields: Site-Name, Group-Name, User's First and Last name, Connects, Session Time, Bytes Received, Bytes Sent.

-Added User-Name attribute sanity checking. The User-Name field is now checked for data values of a maximum length of 40 characters. This was added to reduce occurrences of reporting on corrupt user-name data or bogus user-name data.

-Changed all configurable cost values for the Billing Reports so they can contain up to 3 decimal places. All totals in the reports are still rounded to 2 decimal places, but now it is possible to have data volume, per connect and time based costs that contain up to 3 decimal places. E.g. 0.025 cents per MB transferred etc.

-Added a number of hidden settings that allow certain customization features to be enabled/disabled. By manually editing the relevant settings in the [Hidden Settings] section of the radrep.ini file the following features can be enabled/disabled:

[Hidden Settings]
-Added the ability to enable/disable the reading of the 'Group-Name' attribute in CISCO ACS CSV formatted logs so that auto grouping of users can occur when reading a log containing this attribute.
USE_GROUP_NAME_ATTRIBUTE=0/1 (Default: 0. 1=Read 'Group-Name' attribute for auto-grouping purposes)
Note: RADREP only produces 'Site and Group' based reports when using the users.csv (CSV File) or the 'ACE/Server Database' to read in user grouping information. So even though RADREP will read in the group information from your RADIUS CSV formatted log files you still need to write/dump this information to the 'users.csv' file (manipulate it if necessary) and then read/reload it into RADREP in order to generate Group based reports.
The process would be as follows:
1. Run and configure RADREP at least once to create the radrep.ini file located in the same directory as radrep.exe.
2. Edit the 'radrep.ini' file and make the USE_GROUP_NAME_ATTRIBUTE=1. (the default will be =0)
3. Start/Run RADREP again.
4. Click on the 'Configuration' Button and check/select the option that says "Dump user details to 'users.csv' file."
5. Select the 'Retrieve user list from:' method to be 'RADIUS Log file(s)'.
6. Press the 'Retrieve user list' button.
7. After RADREP has retrieved all the 'User-Name' fields and associated 'Group-Name' fields from the RADIUS logs it will write this information out to the 'users.csv' file, located in the 'Report Output Folder'.
8. You can now edit the 'users.csv' file that has been created and amend any necessary user or Grouping information.
9. Now change the 'Retrieve user list from:' method to be 'CSV File'.
10. Press the 'Retrieve user list' button again to read the 'User-Name' and grouping information from the 'users.csv' file.
11. After reading in this information from the 'users.csv' file you can now generate group based reports.
12. To generate group based reports set the 'Report Start/End Dates', select the reports you want and then press the 'Generate New Report(s)' button.
Another way to generate Group based reports from CISCO ACS CSV logs is to enable the USE_GROUP_NAME_ATTRIBUTE=1 setting and select one Group at a time from the SITE/GROUP/USER hierarchy and generate reports. The only drawback in doing it this way is that report output will be only for the Group you select so you will have to generate reports one group at a time.

-Added the ability to change the reporting primary key. Usually the 'user-name' is used as the primary key. By changing the following radrep.ini file configuration parameters it is possible to change the attribute which is used to represent the "User-Name" field. This was done for some users who wanted to report on H323 attribute fields (in particular the h323-remote-address) as the primary key. The following settings apply to making this change but will depend on which log file type you use as to which ones you need to change.
PRIMARY_KEY_ATTRIB= (Default: User-Name. Change to any unique attribute name seen in a user's accounting STOP record.)
IASSTD_PRIMARY_KEY_ATTRIB= (Default=0 which reads field 2 of an IAS Standard log as the 'User-Name'. Examples values are 4129 or another unique field in a user's accounting STOP record..
IASDB_PRIMARY_KEY_ATTRIB= (Default=6 which is the Field number of the IAS Database compatible log that contains the 'User-Name' attribute. To change the 'User-Name' field number enter the field number of a unique field in the IAS Database compatible log that you want to use instead of the default.)
CSV_PRIMARY_KEY_ATTRIB= (Default=0 which means to detect the field number in the CSV log header that contains the 'User-Name' attribute.

Bug Fix
-Fixed a bug in totaling the connects cost/charge in the CSV Billing summary report. The cost per connect was not being totaled correctly.

Features added in version 1.82 (3rd May 2004)

-Added the ability to select the report start and end time in addition to the start and end date. As in previous versions, only connects that started and finished during the selected start-end time period are shown in the reports. If the user did not end their session during the selected report period then their session information is carried over to the next period and not shown in the reports.

-Enhanced the ability to detect corrupted/bad log file data and skip over it. Some users reported that RADREP would stop reporting on their logs for some days of the month. It was found that for these users their logs contained bad data usually showing itself as BINARY instead of TEXT only characters in their log files. Previous versions of RADREP would stop processing a log at the point which binary data was encountered. Now this data is skipped over and log processing continues.

-When using the users.csv file to group users it would not allow a field to contain a comma. E.g."lastname, firstname". This version now allows fields to contain commas as long as they are enclosed in quotes.

-Added a Profile/Plan field as matching criteria in the billing templates. It is now possible to add a third field in the users.csv file called 'Profile'. This field is intended to be used to represent a user's billing profile/plan such as Gold, Silver, Bronze etc. The users.csv file can now include an optional last field called 'PROFILE'. The format of this file is shown below:
SITE,GROUP,FIRST & LAST NAME,DEFAULT LOGIN, PROFILE
The PROFILE can also be read in as an additional field from the RSA ACE/Server by using the 'User Extension Data' field defined in 'Advanced Settings'. If the 'PROFILE' field is used in ACE/Server as 'User Extension' data, it will be dumped to the users.csv file if this option is selected in RADREP.

-The profile field was added as part of each Billing Rate template output.

-Two hidden configuration settings were added to 'radrep.ini':
1. The ability to combine the group and profile,
2. The ability to convert the Site, Group and Profile fields in the users.csv file to lower case as they are read in. This was added to make it possible to eliminate duplicates that were due to CASE mismatches in the users.csv file.
To enable these abilities you must manually edit the radrep.ini settings file section and keywords as follows:
[Hidden Settings]
COMB_GROUP_PROFILE=1 (1 = group and profile are combined, 0 = not combined [default].)
SITE_GROUP_PROFILE_LOWER=1 (1 = convert the site, group and profile fields to lower case, 0 = leave the fields as they are [default].)

Added the Active Card Activpack RADIUS log converter 'activ2liv.exe'. For those using Activpack AAA RADIUS logs you can now use this utility to convert your logs into Livingston format so that RADREP can process them.

Features added in version 1.80 (6th February 2004)

New Usage Reports
Added four new Usage Reports and amended the layout and format of the Concurrency and Active users reports so that they are now done on a per NAS Server basis.
1. Usage per Framed-IP Address - Summary and Detailed view of which users logged in using a particular Framed-IP-Address

2. Usage Per NAS Server - Summary and Detailed view of which users logged into each NAS server. Includes Concurrency and Active User reports per NAS Server.

3. Usage per NAS-Port - Summary and Detailed view of which users logged in using a particular NAS-Port number. This report is produced on a per NAS Server basis.

4 Usage per NAS-Port-Type - Summary and Detailed view of which users logged in using a particular NAS-Port-Type. This report is produced on a per NAS Server basis and identifies what connection method the end user used. E.g. Async, Sync, ISDN , Wireless etc.

Added Log File order processing.
When processing multiple logs RadRep will now open each file and see what the first timestamp is in order to sort the logs from oldest to newest. This eliminates some of the problems with processing logs out of chronological order.

Reversed Bytes Sent/Received
Depending on whether a report is viewed from the NAS servers view point or the end user's perspective, the bytes sent and receive will oppose each other. Bytes Sent/Received have now been reversed in the User and Billing reports to reflect the user's view of the data. That is, the data sent and received is now viewed from the user's perspective rather than the NAS/RAS servers perspective which is how previous versions of RadRep reported it. You will also see that the NAS server reports show bytes sent/received to be opposite to that of the user based reports because the data sent/received is viewed from the NAS servers perspective.

- Added notification message for when the "users.csv" file is written.

- Updated the 'Run Mode Configuration Tool' so that you can open a 'radrep.ini' configuration file located in a directory other than the current directory.

Bug Fix
- Fixed a concurrency count problem when parsing logs that recorded inconsistent START/STOP record attributes for acct-session-id, multi-session-id and unique-session-id.

 

Features added in version 1.76 (16th November 2003)

Run Mode Configuration Tool.
Added a new GUI tool (autorun.exe) that allows you to change RADREP's mode of operation. This tool allows you to switch RADREP between Standard GUI mode, Auto Run Test Mode and Auto Run Quiet Mode. Previously if you were setting RADREP up in Auto-Run mode you would have to manually edit the appropriate settings in radrep.ini. Using this tool to switch between "Standard GUI mode" and "Auto Run mode" means you now no longer need to manually edit the radrep.ini to do this. (Note that radrep.ini must be in the same directory as this tool)

radrep.ini settings file location.
The radrep.ini settings file is now created in the same directory where radrep.exe is located. Previously it would be created in the <drive>:\windows directory or the users profile directory. If you are upgrading from a previous version of RADREP, you can copy your existing radrep.ini file to your installation location in order to maintain all your current settings.

Command Line INI file passing.
Now you can pass the 'radrep.ini' settings file to 'radrep.exe' as a command line argument.
e.g. radrep.exe d:\myreport\radrep.ini

ErrorLog Text file.
A file called 'ErrorLog.txt' is written to same directory where 'radrep.exe' is located if there are any problems parsing command line options or when generating reports in Auto Run Quiet Mode. Auto Run Quite Mode is used when running RADREP as a Windows Scheduler process.

 

Features added in version 1.75 (26th October 2003)

- Added a User-Name import filter option to the Advanced Settings area. This will allow you to specify a pattern of characters (including * wildcards) to use for filtering and importing select user-names from RADIUS accounting logs during the 'User Retrieval' process.
- Added check-box option for controlling the behavior of the Concurrency and Active User reports. You can now choose to generate these reports for all users found in the logs (giving true concurrency figures) or just those loaded in the site/group/user hierarchy.
- Amended the calendar start-end date picker so that it can handle 2 digit year formats when the Windows Regional Settings short-date format is set to using 2 digit years. When using 2-digits for the year, 30 to 99 is now treated as 1930 to 1999, 0 to 29 is treated as 2000 to 2029. Previously if you had your Windows Regional Date setting set for using two digit years, RADREP would not allow you to change the start-end dates.
- FreeRADIUS enhancements. A number of enhancements were made to handle the processing of logs with multi-session-id and event-timestamp attributes.
- Added user-name CASE sensitivity for Matching Criteria of Billing Templates. A USER NAME defined in a Billing Template as matching criteria is now also tied to using the user-name CASE sensitivity setting under the Advanced settings configuration screen.
- Amended the HTML sorting routine for sorting IP addresses so it could handle non numeric values if for some reason they appeared in the report tables.
- Rearranged the Advanced Options Layout. Those options most commonly used now appear from top to bottom.

Bug Fixes
- Fixed default billing template (template 0) problem which occurred when Data Volume Billing was selected. Now this defaults correctly to using the 'Volume Combined' option and updates the screen correctly.
- When Billing Detailed only reports were chosen a link to the Billing Summary page was presented at the end of this report when it should not have been.

 

Features added in version 1.74b (2nd October 2003)

Bug Fix
- Fixed a problem with processing and extracting fields from CSV & IAS logs which were empty and encapsulated by double quotes.
Fields that were empty but encapsulated by double quotes would cause RADREP to abort processing.
(e.g. "" )

 

Features added in version 1.74a (20th September 2003)

Bug Fix
- Fixed a bug in the Billing Detailed web report that would cause the Totals row to be formatted incorrectly when the TAX rate was set to 0.

 

Features added in version 1.74 (18th September 2003)

- Added AUTO_RUN_PERIOD options 6, 7 and 8 which allow you to run reports automatically for 7, 14 and 21 days prior to the current date.
- Added the ability to specify the SITE, GROUP, and USER to generate reports for when running in Auto-Run mode. Previously Auto-Run mode would generate reports for all users.

Bug Fixes
- Fixed a bug that would cause a user's total number of Bytes Sent and Bytes Received to be truncated when they exceeded 2GB.

 

Features added in version 1.73 (9th September 2003)

- Enhanced the Usage 'Summary Totals & Averages' web report to include the Average Online Time for all users and the Average Connection Duration.
- Added averages per connection and per day to the 'Detailed Usage' web report' for each user.
- Enabled the 'Dump user details to users.csv file' option for RADREP Lite users so that they can dump all user-names found in the logs to a flat CSV file.

Bug Fixes
- Fixed a bug in the Billing reports where specific user costs where not initializing correctly if the user had only one connection for the report period.
- Fixed a small HTML formatting problem that caused reports to have a right hand margin when they should not have had this.

 

Features added in version 1.72a (31st August 2003)

Bug Fix
Fixed a problem with building and displaying the 'Report Period' on the Historical Report Index page. Previously the first few characters of the report period date would be missing.

 

Features added in version 1.72 (26th August 2003)

Strip the DOMAIN name prefix from the User-Name
An additional option has now been added in the 'Advanced Configuration' dialogue, which when enabled will strip off the user's DOMAIN name and leave only the short name displayed in the RADREP hierarchy and all reports. Previously when processing logs, especially those from Microsoft IAS, the DOMAIN name followed by the User-Name would be presented as the user's Login ID.

Changing of IAS Service Name
Previously when using Microsoft IAS you had to leave the IAS 'Service Name' at its default value of 'IAS'. If you did not do this then RADREP would not be able to identify the log type as an IAS log. An additional configuration option has been added in the 'Advanced Configuration' dialogue which allows you to define an alternative service name other than the default of 'IAS'. This name should match what you have configured in your IAS Server Configuration under the 'Service' tab.

Bug Fix
Fixed a small problem with the CSV formatted Detailed Usage report. When the first users had 0 usage it would cause the Report headings to appear after the start of the report output instead of on the first line.

 

Features added in version 1.71 (5th August 2003)

Filtering Enhancement
The ability to filter reports based on a specific NAS-IP-Address was added to the 'Advanced Settings' section of RADREP. By enabling this feature and specifying the IP address of a NAS server it is now possible to produce NAS specific reports. Previous versions of RADREP required you to use the 'radfilter.exe' utility to pre-filter the logs on a specific NAS IP Address if you wanted to produce NAS specific reports.

 

Features added in version 1.70 (25th July 2003)

Historical Reports:
Added an option to automatically rotate the selected report output folder. This provides the ability to archive previously generated reports for future reference. When selecting the 'Report Output Folder' reports will now be created in a sub-directory under this folder. The sub-directory name will be dependent on the 'Historical log Rotation' method chosen and will automatically change periodically as selected by the user. The default is to overwrite prior reports with new reports that are generated and write them to a sub-directory called 'Overwritten_Reports'.

The following user selectable automatic output folder rotation options are available:
     1. No Rotation (i.e. Use the same output folder and overwrite existing reports)
     2. Every time reports are generated
     3. Daily
     4. Weekly
     5. Monthly

A new 'Historical Reports Index' page called 'historical.html' is now also built after each report generation run. The 'historical.html' file will reside in the top level directory you choose as your 'Report Output Folder'. For those customers hosting reports on a web server, you will now need to make your web server home page point to 'historical.html' instead of 'home.html'.

Data Volume Based Billing:
Added the ability to bill users on a per data volume transferred basis. This will be especially useful for billing users who connect via wireless infrastructure and are billed based on the data volume they transfer rather than the time they are connected. Previous versions of RADREP could only generate billing reports based on the duration a user was connected.

Start-End Date Changing:
When selecting the 'Start Date' if the the 'End Date' is before the 'Start Date' it will be set to the same as the 'Start Date'. This was done to make it easier to manually generate daily reports. Likewise when the 'End Date' is selected to be before the current value of the 'Start Date', the 'Start Date' is made to take on the same value as the 'End Date'.

IAS Log parsing (User-Name Retrieval):
When 'Retrieving the user list' from IAS RADIUS logs and the 'Process Access Accept or Deny' packets feature is enabled, RADREP will now only load user-name fields found in Access Request accounting records (IAS Packet type 1) and START/STOP accounting records (IAS Packet Type 4). Previously RADREP would display 'user-name' fields found in IAS Access Accept and/or Access Deny records. This change was made to minimize the chances of the IAS 'canonical user-name' being displayed in the SITE/GROUP/USER selection hierarchy due to the user's short name not being available in IAS Access Accept/Deny packets and RADREP reverting to displaying the 'canonical user-name'. As in previous versions the 'IAS Access Accept/Deny Report' will purposely show ALL access attempts and not just access attempts from those users loaded in the SITE/GROUP/USER hierarchy.

IAS Log parsing (Bug Fix):
Fixed a bug which caused RADREP to crash when processing an IAS Log file with only Access Accept/Deny Packets in it. In version 1.66 RADREP would crash at the stage of trying to write the Concurrency Report because there was no IAS concurrency data to report on due to no START/START accounting records being present in IAS logs. This bug was not an issue if you logged both START/STOP and Access Accept/Deny accounting data in your IAS logs.

Billing Reports - Cost Rounding enhancement:
When calculating a users respective usage costs all values are now rounded UP to 2 decimal places. This means for instance that a calculated data volume cost of $10.325 will become $10.33 and $10.324 will become $10.32.

 

Features added in version 1.66a (17th June 2003)

     Changed the way the Concurrency Duration is calculated. The Concurrency Report now shows the correct Maximum Concurrency Duration.

Features added in version 1.66 (16th June 2003)

     Updated the Concurrency Report to show a list of users that were:
     1. Logged in when the Maximum Concurrency count was recorded.
     2. Still logged in at the end of the report period. This list will show users who are currently logged in if the report end date is set to the current date.

Features added in version 1.65 (9th June 2003)

Added a feature in the 'Advanced Settings' configuration dialogue box to enable the user to select the format of the DATE field in their CSV or IAS formatted log files. (Livingston logs always use the same format for the DATE field so this is not a problem.)
- Previous versions of RADREP would assume that in CSV and IAS formatted logs that the format of the DATE field was 'Month/Day/Year'. Now you are able to select the format of the DATE field as seen in your IAS or CSV formatted RADIUS logs.

Bug Fix
- In CSV formatted log files (Funk and CISCO) RADREP would not not pick up the 'Acct-Terminate-Cause' attribute. This attribute is now picked up correctly and displayed in the reports if it exists in you accounting records.

Features added in version 1.64a (6th June 2003)

Bug Fix
Fixed a bug introduced with a new Microsoft IAS Access Accept/Deny Report where the Total Accept and Deny counter a the end of the report was one greater than it should have been. The Total shown for the number of Access Accepts and Denies is now correct.

Features added in version 1.64 (4th June 2003)

Bug Fix
Fixed a bug introduced with a new option in v1.63 which provided the ability enable/disable user-name CASE sensitivity.
-When CASE sensitivity was enabled user reports would be overwritten if two or more user-names were made up of the same characters (disregarding case). If you did not turn this option on in version 1.63 then you would not be exposed to this problem.

Features added in version 1.63 (3rd June 2003)

Added a Microsoft IAS RADIUS specific report that will show 'Access Accept' / 'Access Deny' accounting information.
- This report will show successful and/or failed login attempts. If there is a failure it will display the reason why a user was rejected access.

Bug Fixes
- Fixed a problem with the Error message handler which was causing the wrong error message to be displayed.
- Fixed a user-name CASE sensitivity matching problem. Now there is a checkbox in the 'Advanced Settings' section to turn on or off user-name case sensitivity.

Features added in version 1.60 (28th May 2003)

- Major enhancements to the billing rates configuration area. Features added include:
   *Ability to define up to 50 billing cost/rate templates.
   *Ability to define different usage time billing costs/rates for each Site, Group or specific User - including wildcard (*) name matching.
   *Ability to set the local currency sign to Dollars ($), Pounds (£), Euro (€), Yen (¥) etc.
- Revised the Web Reports Navigation Menus. Added Print, Home, Back, Forward to the bottom of all reports.
- Added a configuration option which adds the ability to view the CSV reports from the Web Reports Home page.
- Added a configuration option to enable HTML paging of large web reports.
- Added a 'View Existing Report(s)' button so if there are existing reports you can view them easily.


Bugs Fixes
- Fixed a Billing Heading Formatting error when TAX value was set to 0.
(Column headings did not match up with the appropriate column under certain conditions)
- Fixed a problem with reading CSV formatted RADIUS logs where the last field in the log entry would not be recognized.

Features added in version 1.50 (1st May 2003)

- Updated Windows Help file and PDF User Manual.
- Updated the Installer/setup engine.
- Fixed TAB key toggling when using the TAB key to navigate through each option in the RADREP dialogue.

Features added in version 1.49 (9th April 2003)

- Minor updates of information and error message popups. This was done to tidy up some of messages that get displayed when no SART/STOP record data is found in a log(s) or the report START and END dates selected do not correspond to the record dates in the log file(s) being processed. Previously this would lead to no generation of reports and error or information messages which where not entirely accurate in their error or problem descriptions.
- Added a check-box called 'Warn about bad date ranges' to the configuration screen. When enabled and the report start-end date range that is chosen does not co-inside with the record dates in the log file being processed, a Warning popup notifying the user of this will appear. This will happen for each log file that is processed if they also do not have record dates which lie within the chosen report start-end date range. If this check-box is turned off (cleared) then no date range warning messages will be displayed.

Features added in version 1.48 (6th April 2003)

- Updated RADREP PDF User Manual. This now has all the details on how to setup RADREP with the various log formats that it supports including in some detail Microsoft IAS logs.
- Improved Log detection engine for better compatibility and flexibility with Microsoft IAS logs.
- For those using Ascend instead of IETF attribute naming conventions, the following attributes are now seen to be of equivalent meaning for report generation purposes. This slight naming difference was bought to our attention by someone using Ascend modems and Radiator as their RADIUS server.
Framed-IP-Address (IETF) = Framed-Address (Ascend)
NAS-IP-Address (IETF) = NAS-Identifier (Ascend)

Features added in version 1.45 (20th March 2003)

- Ability to run RADREP in an unattended/scheduled mode so that it can be fully automated.
This enables it to be run via the Windows scheduler or via a batch file for automatic generation of reports.
For full details on how to enable 'auto run' mode see the RADREP FAQ.

Changes in version 1.42 (11th March 2003)

- Added a 'Cancel' button to the status window so that the user can abort the current operation at any time.
- Added the ability to minimize the RADREP dialogue window during log processing.
- Enhanced the speed of processing log files.

Bug fixes
- Fixed a problem with the way Windows message queues were processed. This was causing RADREP to slow down (almost to a halt) when it did not have focus or the mouse was not over the status window. This fix has actually boosted all round performance considerably.
- Fixed a bug with reading the TimeStamp attribute from Microsoft IAS logs. This was causing RADREP to show no data in the reports.

Changes in version 1.40 (9th March 2003)

- Added the ability to define up to 2 custom attributes to report on in the 'Detailed Usage Report'
- Added the ability to read Microsoft IAS RADIUS log files (Both 'Database compatible file format' & IAS native format). Prior versions of RADREP could only generate reports from IAS RADIUS logs by first converting the IAS log into Livingston accounting log format using the ias2liv.exe conversion utility).
- Added the ability to configure RADREP to process all accounting logs located in a single folder/directory which end in a specified suffix.
E.g. All logs ending in *.log or *.act (Previous versions could only specify the location of a primary and secondary RADIUS accounting log file)
-Improved the log type format detection so that Livingston, Microsoft IAS and Funk Steel Belted RADIUS log types are correctly detected and identified.
-Added NULL character checking option for log files that contain NULL characters smack in the middle of a log entry. Enabling this will slow down log processing slightly but will produce more concise reports from log files that are not exactly all that clean in their formatting of log data.

Bug fixes
- Fixed a bug in the 'Usage Summary' report where the Bytes Sent column reported the same total and average as the bytes Received column.
- Revised memory management. Some improvements have been made to the way RADREP allocates and revokes memory during 'user list retrieval' process as well as the log file analysis and report generation processes. These changes reduce the total amount of RAM used by RADREP.
-Fixed a major bug in the way RADREP detected and processed Funk Steel Belted RADIUS logs. This was actually causing older SBR logs to not be detected or processed at all.

Changes in version 1.30 (15th Feb 2003)

Major enhancements to the 'Detailed Usage Report'.
- Ability to easily view summarized session disconnect/terminate information. Disconnect/Terminate causes are grouped into 5 categories, each displayed with a unique icon and color. (Disconnect Categories are: Normal, User Requested / Initiated, Timeout, Failed Authentication OR Erroneous user input, and Other/Non-User).
- Ability to select (by clicking on a checkbox) which RADIUS accounting attributes get displayed in the 'Detailed Usage Report'.
The ability to selectively display the following additional attributes is now included:
NAS-IP-Address = 10.3.8.1
NAS-Port = 6911
NAS-Port-Type = 1
Connect-Info = "33600 V34+/LAPM"
Calling-Station-Id = "0396972558"
Called-Station-Id = "18389"
Ascend-Xmit-Rate = 33600
Ascend-Billing-Number = "L2"
Ascend-Connect-Progress = 60
Ascend-Modem-PortNo = 5
Ascend-Modem-SlotNo = "9"
Ascend-Connect-Progress = 60
LE-Terminate-Detail = "User Request - PPP Term Req"
LE-Advice-of-Charge = "69A30"

Bug Fixes
Fixed a bug where if a 'user-name' field had one of the following characters the report generation process would fail.
( \ / : * ? " < > | )

Changes in version 1.29 (31st Jan 2003)

- Added smart handling for duplicate accounting records in the logs. (Now ignores multiple sequential records with the same Acct-Status-Id).
- Improved the speed of the Web Reports column sorting.
- Changed the font size and type in the web reports to Helvetica 10point. (Improves readability and fits more users per page)
- Amended the 'Detailed Usage Report' for each user to include the Session 'Acct-Termination-Cause' or 'Ascend-Disconnect-Cause' if available.
- Amended the 'Detailed Usage Report' for each user to include the 'Ascend-Data-Rate' if it is available in the accounting log.
- Updated the RADIUS log filtering utility (radfilter.exe) so that it can filter RADIUS logs that are ill-formatted.
- For the evaluation version a pre-report generation dialog popup was added to tell you how many users you have in your radius logs.(This way you can work out what license level you will require if purchasing RADREP.)
- Added a new report to show the 'Overall Connection Concurrency' and some general RADIUS log statistics.
* The Concurrency report will not be NAS specific, but an overall concurrency figure. If you only have one RADIUS Client (NAS) then this will be fine. If you need a report that will show the maximum concurrency reached per NAS in a multi-NAS environment, then you will have to use the RADIUS LOG filter utility 'radfilter.exe'. This will allow you to filter the main log on a specified NAS IP-Address, and write out a new log containing only those accounting records that contain this NAS address. You can then use RADREP to produce reports from this new log (including the concurrency report) which will be NAS specific.

Changes in version 1.26 (17th Jan 2003)

- Revised log parsing code to handle ill-formatted RADIUS log files. (Thanks to Richard Nicol for reporting this.)
- Added progress information to the web browser status bar when performing column sorts on web reports.

Changes in version 1.25 (7th Jan 2003)

- Revised HTML output format.
- Added column sorting on HTML reports.
- Some minor bug fixes.

Version 1.20 (Nov 22nd 2002)

- Initial General Release.
- This is the first release suitable for general end user usage.

Version 1.0 (April 2002)

- Initial customer specific version of RADREP.

 

Copyright © SecurityBoy Consulting 2002-2009. All Rights Reserved.

If you have found this page via a search engine you might want to go to the RADREP Home Page.