Discussion:
problem (bug?) logging to SQL
(too old to reply)
rodolfor
2008-07-11 09:30:08 UTC
Permalink
Hi all.
I use NPS linked to a sql database to log all radius requests.
The NAS is a mikrotik hotspot (RouterOS 3.11).
When a user try to login, the mikrotik radius client send a frame containing:
- AttributeNasPort: 2161115139
Type: NAS Port, 5(0x5)
Length: 6 (0x6)
NasPort: 2161115139 (0x80D00003)

The problem is that the radius server, generate an xml (to log in sql
server) that consider this field as "integer" and when it try to insert the
log row in the table it generate an overflow error (the Nas Port 2161115139
is too high), the row is not logged: THE USER IS NOT ENABLED TO LOGIN.

The error is apresent also if int he sql table I set the NasPort field as
bigint or other.

Is possible to modify the xml used by radius ?

thanks
rodolfor
2008-07-12 08:42:01 UTC
Permalink
As in this document:
http://www.microsoft.com/Downloads/details.aspx?FamilyID=6e4357f7-4070-4902-95f1-3ad411d963b2&displaylang=en

IAS use a stored procedure to update the database.
You could simply modify this SP to avoid the problem.
Post by rodolfor
Hi all.
I use NPS linked to a sql database to log all radius requests.
The NAS is a mikrotik hotspot (RouterOS 3.11).
- AttributeNasPort: 2161115139
Type: NAS Port, 5(0x5)
Length: 6 (0x6)
NasPort: 2161115139 (0x80D00003)
The problem is that the radius server, generate an xml (to log in sql
server) that consider this field as "integer" and when it try to insert the
log row in the table it generate an overflow error (the Nas Port 2161115139
is too high), the row is not logged: THE USER IS NOT ENABLED TO LOGIN.
The error is apresent also if int he sql table I set the NasPort field as
bigint or other.
Is possible to modify the xml used by radius ?
thanks
Loading...