> From: Sepp Rudel
> Sent: Friday, 13 June 2003 12:21 AM
> it seems that both MySQL and PostgreSQL default schema
> define NAS-Port-Id as integer/numeric although RFC and
> FreeRADIUS dictionary says it's string. How come? I
> haven't tested, but I would expect that SQL query will
> fail if non-numeric NAS-Port-Id is received..
NAS-Port-Id is the non-numeric alternative to the NAS-Port
attribute, as far as I can tell from the RFCs.
mssql.conf stores NAS-Port-Id
oracelsql.conf stores NAS-Port-Id
postgresql.conf stores NAS-Port
sql.conf (mysql) stores NAS-Port
db_mysql.sql declares an INT(12)
db_oracle.sql declares a NUMERIC(12)
db_postgresql.sql delcares a NUMERIC(12)
No mssql rlm_sql driver module, and the ODBC drivers do
not supply database definition files.
So there's an inconsistency, but not in MySQL and postgresQL.
(PostgresQL's postgresql.conf has a note that NAS-Port-Id was
changed to NAS-Port since that what the author's cisco NAS
was returning.)
So far, only Oracle's got a coded inconsistency. I think it
would be a good idea to change those NAS-Port-Id's to NAS-Port's
instead...
However, this might need some thought... Do we just discard
NAS-Port-ID like we do now, or should it maybe be stored
as a fall-back from NAS-Port. If so, how should the DB schema
be changed? New column? VARCHAR-ise the NUMERICs? Leave it to
the local admin to deal with?
--
=========================================================
Paul "TBBle" Hampson
Bubblesworth Pty Ltd (ABN: 51 095 284 361)
[EMAIL PROTECTED]
The Creation of the Universe was made
possible by a grant from Texas Instruments.
-- PBS
---------------------------------------------------------
Random signature generator 3.0 by Paul "TBBle" Hampson
=========================================================
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
