3.41. <AuthBy PLATYPUS> Previous topic Parent topic Child topic Next topic

<AuthBy PLATYPUS> provides authentication and accounting using the popular Platypus ISP billing package from Platypus website Opens in new window. The combination of Radiator and Platypus provides a very powerful and easy to use ISP billing and user management system. You are able to add users to Platypus, and have them able to log in immediately. Deactivating a Platypus account or changing their password takes effect immediately, and all user logins are available as soon as they are completed: no need to import accounting files.
<AuthBy PLATYPUS> supports all the common SQL configuration parameters. For more information about the SQL configuration parameters, see Section 3.6. SQL configuration.
<AuthBy PLATYPUS> uses Microsoft SQL for its user database, so in order to make Radiator work with Platypus on Unix, you usually need to install an ODBC driver, plus the Perl DBD-ODBC module.
During authentication, Radiator checks the password in the Platypus customer table. It also checks the “Block User” state. If it is set to Y or G, Radiator checks the Platypus Time Left field, and will reject the login if the time left is negative. Otherwise, it accepts the login, and set Session-Timeout in the reply to the number of seconds of login time left. This allows you to prevent users overspending the prepaid time.
During accounting, Radiator logs call details from each Accounting Stop request to the Platypus radiusdat table.
There is an example Radiator configuration file for Platypus in goodies/platypus.cfg. Use this as the starting point for configuring Radiator to work with Platypus.
Tucows has an optional package that makes Platypus compatible with RadiusNT, an NT-only radius server. With this package installed, Platypus lets you set up per-user and per-service RADIUS reply attributes using Platypus editing screens in the menu Maintenance->RadiusNT Setup. Radiator can also work with this, but you must use <AuthBy EMERALD> instead of <AuthBy PLATYPUS>, and configure it as if for Emerald. For more information, see Section 3.39. <AuthBy EMERALD>.