Re: (RADIATOR) Problems with SessionDatabase SQL
Hello Stephen - On Sat, 28 Oct 2000, Delanet Administration wrote: > I've made a few changes to my sessiondatabase section and radiator does > not seem to honor all of them. In paticular, the username seems to be > returned as the plain value returned by the NAS (%u) despite my having > changed it to %n. I have it declared as follows: > > > DBSource dbi:mysql:radius > DBUsername xxx > DBAuth xx > > AddQuery insert into RADONLINE (USERNAME, NASIDENTIFIER, NASPORT, > ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE, SERVICETYPE, > NASPortDNIS, CallerID, ConnectInfo) values ('%n', '%N', 0%{NAS-Port}, > '%{Acct-Session-Id}', %{Timestamp}, '%{Framed-IP-Address}', > '%{NAS-Port-Type}', > '%{Service-Type}','%{Called-Station-Id}','%{Calling-Station-Id}','%{Connect-Info}') > > > > I know it does see my changes as the addition of the caller source and > destination as well as connect-info does work. Only the username refuses > to change. I'm hoping this is not normal? And is there a way around this > as it is necessary for me to change. > > I'm using Radiator 2.16.3 on FreeBSD 4.1.0r with MySQL 3.23.26b. > Can you send me a trace 4 debug showing what is happening? Changing the AddQuery should do what you expect, but perhaps you could give me a bit more detail on exactly what your requirements are. thanks Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc. Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X. === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Problems with SessionDatabase SQL
I've made a few changes to my sessiondatabase section and radiator does not seem to honor all of them. In paticular, the username seems to be returned as the plain value returned by the NAS (%u) despite my having changed it to %n. I have it declared as follows: DBSource dbi:mysql:radius DBUsername xxx DBAuth xx AddQuery insert into RADONLINE (USERNAME, NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE, SERVICETYPE, NASPortDNIS, CallerID, ConnectInfo) values ('%n', '%N', 0%{NAS-Port}, '%{Acct-Session-Id}', %{Timestamp}, '%{Framed-IP-Address}', '%{NAS-Port-Type}', '%{Service-Type}','%{Called-Station-Id}','%{Calling-Station-Id}','%{Connect-Info}') I know it does see my changes as the addition of the caller source and destination as well as connect-info does work. Only the username refuses to change. I'm hoping this is not normal? And is there a way around this as it is necessary for me to change. I'm using Radiator 2.16.3 on FreeBSD 4.1.0r with MySQL 3.23.26b. Thanks in advance, -- Stephen Comoletti - Network Engineer / Systems Administrator Delanet Inc. http://www.delanet.com Frontline Communications Corp. http://www.fcc.net phone: (302) 326-5800 fax: (302) 326-5802 x312 262 Quigley Blvd, New Castle, DE 19720, USA === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Problems with SessionDatabase
Looks like it was a trailing backslash left over from the NT config. Removed it and it's working. Thanks! Shaun [EMAIL PROTECTED] > probably you have some sort of typo before this in your configuration file, > possible a missing clause terminator? Did you get any other errors > printed? > > Have a close look at your config file. > > On Jul 19, 11:51am, Shaun Lessman wrote: > > Subject: (RADIATOR) Problems with SessionDatabase > > I am working on moving Radiator from our NT servers over to UNIX boxes and > > am having a problem where the SessionDatabase directive doesn't seem to be > > understood on the UNIX boxes. The config file is virtually the same as on > > the NT servers, with the exception of the DBSource value. The reason the > > DBSource value is explicitly defined instead of being defined in the Sybase > > interfaces file is that I could never get lookups to work against that file > > using FreeTDS DBD, even with $SYBASE set correctly. Any help would be > > appreciated. === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Problems with SessionDatabase
Hi Shaun, probably you have some sort of typo before this in your configuration file, possible a missing clause terminator? Did you get any other errors printed? Have a close look at your config file. Cheers. On Jul 19, 11:51am, Shaun Lessman wrote: > Subject: (RADIATOR) Problems with SessionDatabase > I am working on moving Radiator from our NT servers over to UNIX boxes and > am having a problem where the SessionDatabase directive doesn't seem to be > understood on the UNIX boxes. The config file is virtually the same as on > the NT servers, with the exception of the DBSource value. The reason the > DBSource value is explicitly defined instead of being defined in the Sybase > interfaces file is that I could never get lookups to work against that file > using FreeTDS DBD, even with $SYBASE set correctly. Any help would be > appreciated. The debugging information is as follows: > > > Mon Jul 19 11:36:31 1999: ERR: Unknown object 'SessionDatabase' in > /usr/local/etc/radius.cfg line 103 > DBSourceDBI:FreeTDS:database=plat;host=*removed*;port=1433; > Mon Jul 19 11:36:31 1999: ERR: Unknown keyword 'DBSource' in > /usr/local/etc/radius.cfg line 104 > DBUsername *removed* > Mon Jul 19 11:36:31 1999: ERR: Unknown keyword 'DBUsername' in > /usr/local/etc/radius.cfg line 105 > DBAuth *removed* > Mon Jul 19 11:36:31 1999: ERR: Unknown keyword 'DBAuth' in > /usr/local/etc/radius.cfg line 106 > > Mon Jul 19 11:36:32 1999: INFO: Server started > > Please CC [EMAIL PROTECTED] when posting your response to the list. > > Thanks! > > Shaun > [EMAIL PROTECTED] > > > === > Archive at http://www.thesite.com.au/~radiator/ > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. >-- End of excerpt from Shaun Lessman -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Problems with SessionDatabase
I am working on moving Radiator from our NT servers over to UNIX boxes and am having a problem where the SessionDatabase directive doesn't seem to be understood on the UNIX boxes. The config file is virtually the same as on the NT servers, with the exception of the DBSource value. The reason the DBSource value is explicitly defined instead of being defined in the Sybase interfaces file is that I could never get lookups to work against that file using FreeTDS DBD, even with $SYBASE set correctly. Any help would be appreciated. The debugging information is as follows: Mon Jul 19 11:36:31 1999: ERR: Unknown object 'SessionDatabase' in /usr/local/etc/radius.cfg line 103 DBSourceDBI:FreeTDS:database=plat;host=*removed*;port=1433; Mon Jul 19 11:36:31 1999: ERR: Unknown keyword 'DBSource' in /usr/local/etc/radius.cfg line 104 DBUsername *removed* Mon Jul 19 11:36:31 1999: ERR: Unknown keyword 'DBUsername' in /usr/local/etc/radius.cfg line 105 DBAuth *removed* Mon Jul 19 11:36:31 1999: ERR: Unknown keyword 'DBAuth' in /usr/local/etc/radius.cfg line 106 Mon Jul 19 11:36:32 1999: INFO: Server started Please CC [EMAIL PROTECTED] when posting your response to the list. Thanks! Shaun [EMAIL PROTECTED] === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.