MSSQL, bugs and a "patch"
s3b0 at gmx.de
Tue Feb 10 11:58:20 CET 2009
i try to work with a mssql-database. The connection to the database works fine, but there are some things missing and wrong in the schema and the dialup.conf.
I added the following part to the schema.sql to make sure, that there is a radpostauth-table in the mssql-database:
CREATE TABLE radpostauth (
[id] [int] IDENTITY (1, 1) NOT NULL,
[UserName] [varchar] (64) NOT NULL,
[pass] [varchar] (64) NOT NULL,
[reply] [varchar] (32) NOT NULL,
[authdate] [datetime] NOT NULL,
) on [PRIMARY]
ALTER TABLE [radpostauth] WITH NOCHECK ADD
CONSTRAINT [DF_radpostauth_UserName] DEFAULT ('') FOR [UserName],
CONSTRAINT [DF_radpostauth_pass] DEFAULT ('') FOR [pass],
CONSTRAINT [DF_radpostauth_reply] DEFAULT ('') FOR [reply],
CONSTRAINT [DF_radpostauth_authdate] DEFAULT ('1900-01-01 00:00:00') FOR [authdate],
CONSTRAINT [PK_radpostauth] PRIMARY KEY NONCLUSTERED
) ON [PRIMARY];
Maybe someone can verify this, if it is correct and maybe it is even worth to be supplied as a patch to the current version of the server.
In the next days, i will try to correct some other issues about the mssql-configuration and i will try to convert the missing dialup.conf from mysql to mssql.
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
More information about the Freeradius-Users