I also didn't have 17 and 18 in the table.
Regards,
Graeme
---Graeme Slogrove, BSc (Eng) Elec (Wits)Director, Systems Development & Value Added ServicesNetActive InternetTel: 011-719-0333 Fax: 011-719-0444Support: 011-719-0300
-----Original Message-----From: Dale E. Reed Jr. [mailto:daler@iea-software.com]Sent: 19 September 1999 07:20To: radiusnt@iea-software.comSubject: Re: [RadiusNT] INSERT conflict with RadiusNT and checkattribute
Graeme Slogrove wrote:> > What is the radlogmsgid for check-attribute errors ? When I enable> check-attribute, the following comes up under the log file.
The RadlogMsgs table is a lookup table for the RadLogs table. I didnotice in the RadiusNT.sql script, four entries are missing:
INSERT RadLogMsgs(RadLogMsgID, Description, Severity) VALUES(16, 'PortNot Allowed', 2)INSERT RadLogMsgs(RadLogMsgID, Description, Severity) VALUES(17, 'RejectAttribute', 2)INSERT RadLogMsgs(RadLogMsgID, Description, Severity) VALUES(18, 'CheckAttribute', 2)INSERT RadLogMsgs(RadLogMsgID, Description, Severity) VALUES(54, 'Badusername', 3)
You need #18, and since its missing, RadiusNT can't insert the RadLogrecord.
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart