(RADIATOR) RE: Platypus, hex session ID

Steve Brown steve at neteze.com
Tue Apr 23 14:01:58 CDT 2002


My fault, spoke to soon. It appears that the Boardtown RadiusNT scripts
setup the calls table so NASPort is a primary key, and can not accept
duplicate values.
 
Is NAS-Port supposed to be a unique number every time?
 
Steve
 
 
-----Original Message-----
From: Steve Brown [mailto:steve at neteze.com] 
Sent: Tuesday, April 23, 2002 11:38 AM
To: 'radiator at open.com.au'
Subject: Platypus, hex session ID
 
Anyone using Platypus with a session ID of type INT as distributed by
Boardtown with there RadiusNT integration scripts?
 
Some of the terminal servers we use appear to report session-ID in hex,
thus causing inserts into the calls and serverports table to fail.
 
Any ideas?
 
Steve Brown
steve at neteze.com
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20020423/a6b02bb3/attachment.html>


More information about the radiator mailing list