1. VOP Radius Release Information and Patches
1.1. Version 4.1 Build 229
1.1.1. Known Issues and Patches for 4.1.229
 

April 23, 2007: Update2 for VOP Radius 4.1 Build 229 Released.

 
 

Special Note: This update requires a reboot. Not doing so could cause console errors.

 
 

Note 1: All Updates are cumulative. That is, UpdateX will contain all the fixes present in UpdateX-1, UpdateX-2, etc..

 

Note 2: The Update and Instructions are available for download at the bottom of this page.

 

 

 

VOP Radius - README File.

 

*** Important Note ***

--------------------------------------------------------------------------------

SQL database types support has been extended starting in version 4.0.228. Even though SQL is a standard, there are some particularities to every server (MS SQL, MySQL, etc...) The Vircom specific attributes Analog-Access and Digital-Access records were defined originally of type binary. Binary record type not being "universal" enough, their record type is changed to integer. Depending of your SQL database server, the latter attributes may work properly independently of their record type. However it is HIGHLY RECOMMENDED when upgrading to version 4.0.228 and above to modify the record type of the Analog-Access and Digital-Access attributes to Integer in your SQL database.

 

1. A zero value means FALSE.

2. A non-zero value means TRUE (1,2, etc.)

3. NULL data is allowed and it means "don't care".

 

 

*** Important Note ***

--------------------------------------------------------------------------------

Customers using VOP Radius MMC, must update both VOP Radius Server and MMC.

 

--------------------------------------------------------------------------------

 

VPRRS229.2.EXE

--------------------------------------------------------------------------------

   - Fixed a rare exception occuring while loading the users from the disk.

   - Fixed display in the console (Radius Server tab --> ODBC DataSource)

 

 

VPRRS229.1.EXE

--------------------------------------------------------------------------------

  • Fixed a problem with "Check password when UserName clash" within "Add. Database IDs"/ "ODBC" in the console. The VOP Radius server was ignoring the feature; the user was found only by the user name. Please note that the same feature, in the "Radius Server" tab, was already working.

 

 

VPRRS229.EXE

--------------------------------------------------------------------------------

   - Added support for Rodopi AAA Corba Interface

       - For authentication ("Radius Server" and "Add. Database IDs" tabs)

       - For accounting ("Accounting" tab)

       - For secondary/fallback solution ("Cache/Fallback" tab)

 

 

Contacting us

=============

If you need assistance or have suggestions concerning our products, do not hesitate to call or write us. Our offices are open from 9:30AM to 6:00PM Eastern time, weekdays.

 

E-mail:Technical support 

support@vircom.com

 

E-mail:Suggestion box    

suggest@vircom.com

 

Our support Web Page     

http://www.vircom.com

 

Our tech support line

(514) 845-8474, weekdays,

9:30AM to 6:00PM Eastern time.

1.1.2. Important document for customers upgrading from an older version
1.1.3. Release Information
1.1.4. Manuals

VOP Radius manuals can be downloaded below:

1.1.5. Rodopi AAA CORBA Interface

VOP Radius uses the Rodopi AAA CORBA Interface to interact with the Rodopi billing software. This interface provides more flexibility in the selection of attributes than using stored procedures.

 

Authentication details:

 

1.     The Rodopi billing software must return either a Password attribute or an Auth-Type attribute.  

2.     The Service-Type attribute must be returned. Its value must be either a valid integer (see RFC 2865) or a Service-Type string value, found in the VOP Radius dictionary (VPRDict.txt):

 

·        VALUE<tab>Service-Type<tab>Framed-User<tab>2

 

Note: <tab> is a tabulation character

 

For further details, see “Authentication Access” in the VOP Radius Application Help File.

 

Configuring the AAA CORBA Interface:

 

·        Rodopi Server

 

The Rodopi AAA Interface configuration information is stored in an XML file on the server where the Rodopi AAA Interface service is installed. Any configuration changes must be saved in this file:

 

<Rodopi Installation Folder>\Shared Services\Rodopi.Service.AAA.exe.config

 

·        VOP Radius Server

 

Whether the AAA Interface is used for authentication or accounting, the setup information required by VOP Radius is the same:

 

o       Host name / IP Address: This identifies the machine where the Rodopi AAA Interface service is installed; it may be either a host name or an IP address. The default host name is Localhost.

 

o       Port: In the Rodopi.Service.AAA.exe.config file, this is defined as:

 

/configuration/appSettings/parameter/value where the parameter/key attribute is RadiusInterface.Port.

 

The default port is 8087.

 

o       CORBA object name

 

In the Rodopi.Service.AAA.exe.config file, this is defined as:

 

/configuration/rodopiAppConfiguration/solution/instance/parameter where the parameter/key attribute is RadiusInterface.Name
 
The default CORBA object name is RodopiRadiusAAA.
1.2. Version 4.0 Build 228

 

1.2.1. Important document for customers upgrading from an older version
1.2.2. Release Information
Please see attached "Release.pdf" document.
1.2.3. Manuals

VOP Radius manuals can be downloaded below:

1.2.4. Known Issues and Patches for 4.0.228

September 26, 2005: Update38 for VOP Radius 4.0 228 Released.

Special Note: This update requires a reboot. Not doing so could cause console errors.

Note 1: All Updates are cumulative. That is, UpdateX will contain all the fixes present in UpdateX-1, UpdateX-2, etc..

Note 2: The Update and Instructions are available for download at the bottom of this page.

Update information

*** Important Note ***
--------------------------------------------------------------------------------
SQL database types support has been extended starting in version 4.0.228. Even
though SQL is a standard, there are some particularities to every server (MS SQL,
MySQL, etc...) The Vircom specific attributes Analog-Access and Digital-Access
records were defined originally of type binary. Binary record type not being
"universal" enough, their record type is changed to integer. Depending of your
SQL database server, the latter attributes may work properly independently of
their record type. However it is HIGHLY RECOMMENDED when upgrading to version
4.0.228 and above to modify the record type of the Analog-Access and Digital-
Access attributes to Integer in your SQL database.

1. A zero value means FALSE.
2. A non-zero value means TRUE (1,2, and above)
3. NULL data is allowed and it means "don't care".


*** Important Note ***
--------------------------------------------------------------------------------
Customers using VOP Radius MMC, must update both VOP Radius Server and MMC.

--------------------------------------------------------------------------------

VPRRS228.38.EXE
--------------------------------------------------------------------------------
   - VOP Radius now performing VoIP detection for CISCO or unknown type NAS only.

--------------------------------------------------------------------------------

VPRRS228.37.EXE
--------------------------------------------------------------------------------
   - VOP Radius now logs incoming NAS IP address and NAS port upon access
     denial caused by an invalid password.

   - VOP Radius now omits users with service type 8 (Authenticate-Only) and
     service type 99 (Authenticate-Vop) from active users count validation of
     maximum simultaneous users on-line. (As per VOP Radius license key)

--------------------------------------------------------------------------------

VPRRS228.36.EXE
--------------------------------------------------------------------------------
   - VOP Radius now logging SQL query time lapse.

--------------------------------------------------------------------------------

VPRRS228.35.EXE
--------------------------------------------------------------------------------
   - This update apply to the ODBC authentification method.

     The "Analog-Access" and "Digital-Access" fields are now bound as SQL_C_LONG
     instead of SQL_C_ULONG.

     If a row was having a negative value (e.g. -1) for "Analog-Access" and/or
     "Digital-Access", then this row was not returned by the SQL server to
     VOP Radius (a negative value is invalid for SQL_C_ULONG). The user was
     simply not found.

     Here is a table showing the SQL types that VOP Radius uses to bind the
     columns.

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  Field Name         |  RADIUS Attribute       |  Formerly     |  Update 35    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  UserName           |  User-Name (1)          |  SQL_C_CHAR   |  SQL_C_CHAR   |
|  Password           |  User-Password (2)      |  SQL_C_CHAR   |  SQL_C_CHAR   |
|  Service-Type       |  Service-Type (6)       |  SQL_C_CHAR   |  SQL_C_CHAR   |
|  Session-Limit      |  Session-Timeout (27)   |  SQL_C_LONG   |  SQL_C_LONG   |
|  Idle-Limit         |  Idle-Timeout (28)      |  SQL_C_ULONG  |  SQL_C_ULONG  |
|  Static-IP          |  Framed-IP-Address (8)  |  SQL_C_CHAR   |  SQL_C_CHAR   |
|  IP-Netmask         |  Framed-IP-Netmask (9)  |  SQL_C_CHAR   |  SQL_C_CHAR   |
|  TimeBank           |                         |  SQL_C_LONG   |  SQL_C_LONG   |
|  Framed-Route       |  Framed-Route (22)      |  SQL_C_CHAR   |  SQL_C_CHAR   |
|  Filter-ID          |  Filter-Id (11)         |  SQL_C_CHAR   |  SQL_C_CHAR   |
|  Analog-Access      |                         |  SQL_C_ULONG  |  SQL_C_LONG   |
|  Digital-Access     |                         |  SQL_C_ULONG  |  SQL_C_LONG   |
|  Port-Limit         |  Port-Limit (62)        |  SQL_C_ULONG  |  SQL_C_ULONG  |
|  Speed-Limit        |  Connect-Info (77)      |  SQL_C_ULONG  |  SQL_C_ULONG  |
|  Expiry-Date        |                         |  SQL_C_DATE   |  SQL_C_DATE   |
|  Radius ProfileID   |                         |  SQL_C_CHAR   |  SQL_C_CHAR   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

     Note:
     With VOP Radius 4.0.228, the Service-Type attribute may be absent from user
     definition attributes or absent from the profile attributes, but not both,
     except if the Framed-Protocol attribute was defined whereas the Service-Type
     of the incoming packet was "Framed-User", then in this case, only a warning
     message will be generated.

     For more information, a careful read of the "Authentication Access" page in
     the console help is strongly suggested.

--------------------------------------------------------------------------------

VPRRS228.34.EXE
--------------------------------------------------------------------------------
   - VOP Radius and VOPTest did not handle properly NAS port higher than
     0x7fffffff.

--------------------------------------------------------------------------------

VPRRS228.33.EXE
--------------------------------------------------------------------------------
   - Username and password check with NT SAM was not working using the Auth-Type
     attribute with the optional "\DomainName" used to identify a specific domain.

--------------------------------------------------------------------------------

VPRRS228.30.EXE
--------------------------------------------------------------------------------
   - VOP Radius would not accept CHAP challenges bigger than 16 bytes.

--------------------------------------------------------------------------------

VPRRS228.29.EXE
--------------------------------------------------------------------------------
   - Rodopi Accounting Stored Procedure Call Fixed.

     How the problem occured:
     1. The "Use ODBC for Accounting Logs" option is checked under the
        "Accounting" tab.
     2. In the ODBC Setup, the database type selected is "Rodopi".
     3. In the incoming accounting packet, the NAS-Port (5) attribute is
        omitted.

     Problem Description:
     When we called the stored procedure, we would put in the Stored Procedure
     call statement the NAS-Port (5) attribute with a value of NUL instead
     of NULL.

--------------------------------------------------------------------------------

VPRRS228.28.EXE
--------------------------------------------------------------------------------
   - Fixed VOPTest EAP testing feature broken in version 4.0 starting with
     update 16.

--------------------------------------------------------------------------------

VPRRS228.27.EXE
--------------------------------------------------------------------------------
   - Classified VOP Radius log tracking messages using only five categories.

--------------------------------------------------------------------------------

VPRRS228.26.EXE
--------------------------------------------------------------------------------
   - VOP Radius console and server able to read both old and new user log formats.

   - VOP Radius log message headers matched with log tracking console panel names.

   - VOP Radius calling station id concurrency option could not be used with
     verify port-limit upon server reply feature.

   - VOP Radius time banking feature only worked in version 4.0 if service type
     is defined in the profile.

--------------------------------------------------------------------------------

VPRRS228.25.EXE
--------------------------------------------------------------------------------
   - VOP Radius users online panel has new pause button preventing display to be
     refreshed. This is useful to scroll through the listing while searching for
     a specific user.

   - VOP Radius console can now display users with username containing spaces.

   - Fixed selection of default generic auto-mapping for ODBC authentication.
     (Custom Stored Procedure)

   - VOP Radius can now authenticate users with username containing apostrophes.

   - VOP Radius MMC can now use local rpc connections and named pipes for remote
     connections.

   - VOP Radius files panel now offers the possibility to change the path and
     the name of the client definition file (VPRTSDef.txt).

   - VOP Radius help file now documents use of client type in the radius client
     definition.

   - VOP Radius help file hyperlinks have been revised.

   - VOP Radius Max Authentication Timeout feature could cause server to lock
     up CPU resources. In the case where there is a fallback method configured
     else than the cache, and that both the primary data source and the fallback
     data source failed to answer, VOP Radius will not fallback to cache but
     rather falls in an endless loop. Unless the NAS sends another retry itself
     to unlock it. Hence it may happen in the case of double failure of the
     primary source and the fallback source when the latter is not configured
     to be the cache and that the NAS doesn't attempt the same request a few
     times.

--------------------------------------------------------------------------------

VPRRS228.24.EXE
--------------------------------------------------------------------------------
   - VOP Radius console is restored when re-opening the console once minimised.

   - Fixed selection of default generic auto-mapping for ODBC authentication.

--------------------------------------------------------------------------------

VPRRS228.23.EXE
--------------------------------------------------------------------------------
   - VOP Radius MMC did not allow sorting by calling station id.

--------------------------------------------------------------------------------

VPRRS228.22.EXE
--------------------------------------------------------------------------------
   - In version 4.0 starting with update 9, it may be possible that the chart
     under the Statistics Tab may not be displayed correctly occasionnally.

   - VOP Radius can use two different files to retrieve UNIX password and UNIX
     GID. This is helpful for those using a shadow file for the passwords.

   - VOP Radius processing time for text backup and ODBC backup cases has been
     reduced.

   - VOP Radius can attribute IP addresses to user requests with a service type
     else than "Framed-User". This is helpful for those willing to assign an IP
     address to outbound users.

--------------------------------------------------------------------------------

VPRRS228.21.EXE
--------------------------------------------------------------------------------
   - If an additionnal accounting attribute is of type String and the accounting
     packet can potentially contain many similar attributes, a string to look
     for can be provided to VOP Radius to find a match.  For example, this is
     useful to parse among vendor specific attribute-value pairs (AV-pairs).

   - Additional accounting attributes are allowed even if the packet is not a
     CISCO VoIP packet. However, a CISCO VoIP attribute value MAY NOT be added
     if your VOP Radius license does not support VoIP.

   - Implement use of Unix GID as profile name.

   - Optimised VOP Radius debugging performance, removed source IP debugging.

   - Special treatment provided to Ascend attributes without any vendor ID
     extended to Ascend attributes with Ascend vendor ID.

   - Fixed Help File for Users Online tab wrongly stating that "Limit" column
     units were seconds while in fact they are minutes.

--------------------------------------------------------------------------------

VPRRS228.20.EXE
--------------------------------------------------------------------------------
   - Starting in version 3.5.227.21, VoIP packet without any cisco H.323
     attribute absolutely needed NAS port type attribute to be present.

   - Starting in update 17, RODOPI accounting date format was wrongly modified.

--------------------------------------------------------------------------------

VPRRS228.19.EXE
--------------------------------------------------------------------------------
   - VOP Radius allows to assign an IP address to an outbound user whose
     outbound service type has been changed to framed user.

   - VOP Radius logs matched profile name.

   - VOP Radius sends both SESSION_LIMIT and ASCEND_SESSION_LIMIT to ASCEND
     units. (As well as both IDLE_TIMEOUT and ASCEND_IDLE_TIMEOUT)

   - VOP Radius avoids raising warning if the server can not open the client
     definition file when it is open by the console or the wizard.

   - VOP Radius provides option to turn off Windows Event Viewer Logging.

   - Renaming of "Authenticated" column within the console users online
     listing for "Authentication", as well as use of DONE and NONE rather
     than YES and NO to indicate whether user went through the authentication
     phase.

   - Update 17 prevented use of multi-login check on port zero.

--------------------------------------------------------------------------------

VPRRS228.18.EXE
--------------------------------------------------------------------------------
   - VOPCom does not unconditionnally insert anymore attribute 61 (NAS-Port-Type)
     with a value of 5 (Virtual) when opening a request with a NAS port value of
     zero. A NAS-Port-Type = Virtual will rather remove the NasPortID attribute
     from the packet.

   - Prevent multi-logins of user in version 4.0 only worked when remote server
     is down.

--------------------------------------------------------------------------------

VPRRS228.17.EXE
--------------------------------------------------------------------------------
   - Calling Station ID Concurrency feature implementation. If this option is
     checked, many users or a same user can be granted access to a same NAS port
     using different Calling Station IDs.  This option is useful for anyone using
     a wireless NAS which make use of Calling Station ID to store MAC address
     (e.g. Nomadix, etc.).
     If this option is checked, user port limit and NAS port limit are treated
     like connection limits no matter the type of the different connections being
     NAS ports and/or Calling Station IDs.
 
     In addition if this option is checked, VOP Radius considers Calling Station
     ID to be universally unique if the Calling Station ID is at least
     10-character long (The latter encompasses MAC address, E.163 and E.164
     format types).   Normally VOP Radius in order to prevent ghost connections
     when an access request comes in from a same NAS for a port VOP Radius has
     a user already connected to, the new connection is allowed to replace the
     ghost connection rather than being rejected. In case this option is checked,
     VOP Radius considers Calling Station ID to be a non-sharable resource too.
     In order to prevent ghost connections when an access request comes in for
     a Calling Station ID VOP Radius had a user already connected to, the new
     connection is allowed to replace the ghost connection rather than being
     rejected. Therefore this option is also useful for anyone using a carrier
     not providing any means to monitor their NAS activity (e.g. GlobalPOPs, etc.).

   - Additional accounting attributes for Rodopi data source are allowed even if
     the packet is not a CISCO VoIP packet. However, a CISCO VoIP attribute value
     MAY NOT be added in the SQL request if your VOP Radius license does not
     support VoIP (the value will be 'NULL' instead).

   - Any string attribute value may have one or more apostrophes.

--------------------------------------------------------------------------------

VPRRS228.16.EXE
--------------------------------------------------------------------------------
   - VOP Radius reflects RSA Security SecurID products renaming and re-branding.
     Effective October 2004, RSA ACE Server and Agent become RSA Authentication
     Manager and Agent. VOP Radius has been certified against RSA Authentication
     Manager version 6.0 dated September 2004.
   - VOPTest default timeout delay is adjusted to 3000 ms to better meet RSA
     SecurID authentication average latency.
   - VOPTest enhancements to test RSA Authentication consisting of multiple
     successive challenges.

--------------------------------------------------------------------------------

VPRRS228.15.EXE
--------------------------------------------------------------------------------
   - VOP Radius allows to assign an IP pool filter name to each NAS. Before
     sending back the reply to the NAS, VOP Radius verifies whether it has to
     assign an IP address to the user. First it looks whether the NAS has a
     filter name assigned to it. If not, in the case of roaming, it looks whether
     the remote server has a filter name assigned to it. Finally, it checks
     whether there is a Filter-ID attribute in the packet.
   - VOP Radius access check allows to check for exact connection speed using
     Connection-Spped-Limit in a profile. The  presence of the "@" character in
     front of the speed value forces exact connection speed check.

--------------------------------------------------------------------------------

VPRRS228.14.EXE
--------------------------------------------------------------------------------
  - VOP Radius access check allows to check for exact connection speed. The
    presence of the "@" character in front of the speed value forces exact
    speed check. Here are four valid examples for matching exact speed; either
    one of the four forms can be used:
 Connect-Info=@256
 Connect-Info="@256"
 Connect-Speed-Limit=@256
 Connect-Speed-Limit="@256"

  - Fixed exception fault occuring with very long username.

--------------------------------------------------------------------------------

VPRRS228.13.EXE
--------------------------------------------------------------------------------
  - Fixed exception fault when a user is provided with many profiles not using
    profile lists.

  - Added icon to VOP Radius Client title bar.

--------------------------------------------------------------------------------

VPRRS228.12.EXE
--------------------------------------------------------------------------------
  - Defining a client with a name format similar to an IP address
    ( xxx.xxx.xxx.xxx ) corrupted its own defintion.

--------------------------------------------------------------------------------

VPRRS228.11.EXE
--------------------------------------------------------------------------------
  - Connect-Info did not work properly as an access check item.

--------------------------------------------------------------------------------

VPRRS228.10.EXE
--------------------------------------------------------------------------------
  - Invalid password warning message is now providing invalid password value.
  - Fixed a bug inserted in 4.0.228.8 where only "Radius Server" could be used
    as fallback method.

---------------------------------------------------------------------------------

VPRRS228.9.EXE
--------------------------------------------------------------------------------
  - Maximum Authentication Timeout now by increments of 1 sec rather than 5 sec.

--------------------------------------------------------------------------------

VPRRS228.8.EXE
--------------------------------------------------------------------------------
  - Console layout tab order to navigate has been fixed.
  - Implementation of a fail-over server for each server meant for roaming users.
  - Implementation of a timeout to fail-over rather then relying on retries.
  - Roaming is searched for by suffix, then prefix and default roamer server now
    used as last resort.
  - Modify possible refresh rate of VOP Radius MMC from Hour:Minute to Minute:Second
  - Voptest now allows Client IP Address to differ from NAS IP Address.
  - Fixed the "Remove-Attributes" attribute. The list syntax was not working
    properly: only the first attribute of the list was removed.
  - Fixed an issue with the pdf documentation. Some rows were not showing properly.
  - Fixed an issue with the "Use ODBC Logs" option in the "Log Tracking" tab:
    The "Debug Informations: Level 2" error messages are now inserted in the
    database if the associated checkbox is marked. More messages are inserted
    as well if the associated "Error Log Information Level" is checked (very
    few may still only appear in the text file).

--------------------------------------------------------------------------------

VPRRS228.7.EXE
--------------------------------------------------------------------------------
  - Fixed SQL sample scripts to create Analog-Access and Digital-Access record
    as integer.
  - Fixed Microsoft Access sample database creating Analog-Access and Digital-
    Access record as integer.
  - Fixed VOP Radius help file to document Analog-Access and Digital-Access
    record as integer.

--------------------------------------------------------------------------------

VPRRS228.6.EXE
--------------------------------------------------------------------------------

  - Fixed SQL support for Analog-Access and Digital-Access special attributes.
       Some SQL server would return values else than 0 and 1.
  - Fixed VOP Radius MMC console.
       VOP Radius MMC console was not working using UDP.
       VOP Radius MMC console was not working properly with 4.0.228 server.
  - Fixed User List file format
       User list file format now friendly reader (stretched over 132 columns).
  - Fixed Time-Of-Day special attribute.
       A bug has been inserted in 4.0.228 which prevented use of Time-Of-Day.

--------------------------------------------------------------------------------

VPRRS228.5.EXE
--------------------------------------------------------------------------------

  - Fixed support for Windows 2003.
       On some Windows 2003 configurations, version verification during
       installation would caused the dll to be misplaced. Version verification
       has been replaced by date verification.
  - Fixed sample scripts to create SQL tables.
       Sample script was missing one line to create a field called "TimeBank".
  - Fixed a bug inserted in 4.0.228 where an Access Request with no NAS-Port-ID
       attribute would fail.
  - Fixed ODBC Fallback support.
       Four fields were greyed out under this option: Timebank, Port-Limit,
       SpeedLimit, and ExpirationDate.
--------------------------------------------------------------------------------

VPRRS228.4.EXE
--------------------------------------------------------------------------------

  - Fixed support for MySQL.
       Analog-Access and Digital-Access attributes could not be used with MySQL.
  - Fixed support for NULL String Vs NULL Data using SQL. (MS SQL does not
       necessarily return NULL DATA for NULL string.

--------------------------------------------------------------------------------

VPRRS228.3.EXE
--------------------------------------------------------------------------------

VPRRS.EXE (The VOPRadius server application itself)

  - Custom Stored Procedure Support
       With the VPRRS228.2.EXE update, the special attribute "Return-Code" had
       to be the first attribute returned. Now, this restriction has been
       removed.
  - The NAS-Port-Id attribute
       The NAS-Port-Id check was not working properly. The latter issue has been
       fixed.

--------------------------------------------------------------------------------

VPRRS228.2.EXE
--------------------------------------------------------------------------------

Main RADIUS Configuration console
VPRRS.EXE (The VOPRadius server application itself)

  - Custom Stored Procedure Support
       The "Custom Stored Procedure Support" feature can be used by customers
       with specific authentication needs.

       To have more info on that new feature:

       1. Open the Main RADIUS Configuration console.
       2. Select the "Radius Server" tab.
       3. Select the "ODBC DataSource" radiobutton.
       4. Click on the "Setup" button.
       5. Under "Database Type" combobox, select "Custom Stored Procedure".
       6. Click the "Yes" popup button and read the help associated to the
          "Custom Stored Procedure Support".

--------------------------------------------------------------------------------

VPRRS228.1.EXE
--------------------------------------------------------------------------------
 
Main RADIUS Configuration console

  - The current update number installed is now shown.
  - Added a title bar icon
  - Added the minimize functionality
  - Added an icon on the system tray to show the console if clicked

  * Users Online tab
    - Changed the values showed in the Service-Type column.
    - The remove button is now enabled only if it is available (interface
      improvement).
    - Added a comment saying that the remove button effect is not instantaneous.

  * Radius Server tab

    - For LDAP, when the "Bind with username" checkbox is checked, the password
      editbox is disabled under "mapping attribute names".  The reason for that
      is because the actual act of binding verifies the validity of the account.
      If you can't bind, the account's username & password are incorrect.  So no
      need to map the password field.

  * CONSOLE HELP

    - Revised the help related to the Users Online tab.
    - Revised the help for the Authentication Access.
 
VPRRS.EXE (The VOPRadius server application itself)

  - Fixed exception with LDAP authentication when the only attribute mapped was
    the Username.
  - The VOP Radius 4.0.228.0 release introduced some problems with the
    "Expiration" attribute. This is now fixed.
  - When an incoming packet Service-Type was Framed-User and no Service-Type was
    specified in the data source or in the user's profile, the normal behavior
    is to accept the connection as long as there's a Framed-Protocol present in
    the datasource or the profile. The code had a problem whereas even if the
    framed-protocol was NOT present, it was still acting as if it was present.
    This behavior is now fixed.

--------------------------------------------------------------------------------

----------------------------
Procedure to apply the patch
----------------------------

<DEVELOPER: Update the procedure below to the patch's requirements.>

1) Make sure version 4.0.228 is installed
2) Stop VOP Radius and close the console
3) Launch VPRRS228.x.EXE installation package.
4) Read the Readme.txt file.
5) Reboot computer
6) Start VOP Radius on startup (if service set to manual)
6) Confirm under NT Event Viewer --> Application Log that the service started ok