(RADIATOR) Different SQL statements per START and STOP requests
Title: Different SQL statements per START and STOP requests Hi, Is it possible to run seperate AcctSQLstatement per START and STOP accounting requests? I would like to run a specific SQL statement when Acct START request received and STOP request received. Thanks, Ferhat
RE: (RADIATOR) Accounting
Title: RE: (RADIATOR) Accounting Ferdi, You should install perl modules DBI and DBD:Oracle Then configure in radius.cfg the SessionDatabase SQL (Manual page 22) It works great. Regards, Ferhat -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ferdi Tasik Sent: Wednesday, December 15, 1999 3:18 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: (RADIATOR) Accounting Hi, Mike I want to ask about accounting radiator : 1. How to connect from accounting to oracle database? Is there any script? 2. Can Oracle connect directly from accounting? Regards, Ferdi Tasik __ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Session Timeout Until xx:xx
Title: RE: (RADIATOR) Session Timeout Until xx:xx Hi, For double checking: Here is my users file and the cfg file. And Session-Timeout works this way very well. I will try the same functionality live with SQL database today. fred User-Password = x, Time = Al0800-1800 User-Service = Framed-User, Framed-Protocol = PPP, Framed-Netmask = 255.255.255.0, Framed-Routing = None, Framed-MTU = 1500, Framed-Compression = Van-Jacobson-TCP-IP # radius.cfg Foreground LogStdout LogDir /var/radius DbDir /usr/local/etc LogFile %L/logfile DictionaryFile %D/dictionary.ascend Trace 4 Client DEFAULT Secret xxx DupInterval 300 IgnoreAcctSignature /Client Realm DEFAULT AuthBy FILE Filename %D/users AddToReply Session-Timeout = until 1800 /AuthBy # Log accounting to the detail file in LogDir AcctLogFileName %L/detail /Realm -Original Message- From: Hugh Irvine [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 08, 1999 12:56 AM To: Ferhat DILMAN; Mike McCauley; [EMAIL PROTECTED]; Ferhat DILMAN; [EMAIL PROTECTED] Cc: tom minchin Subject: RE: (RADIATOR) Session Timeout Until xx:xx Hello Ferhat - On Tue, 07 Dec 1999, Ferhat DILMAN wrote: %_Thanks for it. It is now working. By the way, in the documentation, it says Session-Timeout = until 1800. It did not work with quotes. It worked without Curious - it works with here. Could you send us more details, including your configuration file (w/o secrets) so we can see what is happening? thanks Hugh -- 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
RE: (RADIATOR) Session Timeout Until xx:xx
Title: RE: (RADIATOR) Session Timeout Until xx:xx Thanks for it. It is now working. By the way, in the documentation, it says Session-Timeout = until 1800. It did not work with quotes. It worked without Thanks, cool functionality :) Ferhat -Original Message- From: Mike McCauley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 07, 1999 7:49 PM To: [EMAIL PROTECTED]; Ferhat DILMAN; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; tom minchin Subject: Re: (RADIATOR) Session Timeout Until xx:xx Hello Ferhat, On Dec 7, 11:41am, Hugh Irvine wrote: Subject: RE: (RADIATOR) Session Timeout Until xx:xx Hello Ferhat - On Tue, 07 Dec 1999, Ferhat DILMAN wrote: %_Hi, I have tested Session-Timeout=until 1800 parameter and does not work. Thanks for pointing this out - as it happens, a user reply item of Session-Timeout=until 1800 does in fact work. However, due to an oversight, it doesn't work in an AddToReply. Our apologies for this and Mike will post a fix shortly. Hugh is right. The special handling of Session-Timeout for until was not being done if it was in a DefaultReply and AddToReply. I have uploaded a fixed version of AuthGeneric.pm Thanks for reporting this. Cheers. -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. Ltd Unix, 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
(RADIATOR) Session Timeout Until xx:xx
Title: Session Timeout Until xx:xx Hi, The module AuthGeneric in 2.1.14 patch area states that: 28/9/99 New version of AuthGeneric supports a new format for Session-Timeout reply items:. If you have for example: Session-Timeout=until 1800 Then the Session-Timeout in the reply will be calculated as the number of seconds up until the time of day specified However, I am puzzled since I don't understand how to use this extra string in AuthBy SQL module. Is it possible to use a parameter in AuthGeneric inside AuthSQL ? Regards, Ferhat
(RADIATOR) ClearNasQuery
Title: ClearNasQuery Hi, I remember we had once discussed the same issue long time ago but could not find it in the archive logs. What I need is when the Leased Line between POP and the location where radiator resides is down, users are still on RADONLINE and also there are no STOP records arrived into the accounting table so that they still seem to be online. This is not a problem if their account is unlimited-time-account. However, if they only have xx hours per month, then it is a problem and we have to clear-nas. I can handle this using a SQL statement manually. Is there anyone done this automatically? Since the leased line is down, radiator will not receive clearnasquery request from the NAS. MRTG sending the request to radiator when the line is down? anybody tried? Another idea would be, periodically check the NAS within radiator and when it does not receive response, issue a clearnasquery? Regards, Ferhat
Re: (RADIATOR) Password Expiration
Hi, Not just AuthBy SYSTEM. We are using SQL database for example. Assume that we have set the field EXPIRE=15 and WARN=3. That means every 15 days, the user must change his/her password and probably will receive warning messages 3 days before. S/he may change his/her password either last day thru the black terminal script screen or in a way in the web server (this is easy part) My solution would be: 1- Password is set. 15 days left for changing. 3 days for warning. EXPIRE=15, WARN=3 2- Every day a backend stored procedure runs for every user and will change/remove password which is PASSWORD_CREATED+EXPIRESYSDATE (PASSWORD_CREATED (date format, is the date password created) 2- User will receive warning automatically in both black screen to change his password, and will also receive e-mail. 3- user changes his password using a web interface. and set (EXPIRE=SYSDATE+15) 4- user forgets to change his password and the final day arrives. his password expired. when he tries to re-connect he will receive "Password Expired, please use guest/guestpassword account to change password" message. User may connect to ONLY password-change page which is secure. After password changed, user may connect regularly using all services. This is my solution without (or minimal) change in radiator. What if this functionality is default in radius.cfg configuration items? (The minimal change would be to add request denied - password expired message into perl scripts and additional select statements for SQL database) And I will have to add guest/guestpassword account with IP-filter into password-change page ONLY. My 2 cents. Best Regards, Ferhat - Original Message - From: "Hugh Irvine" [EMAIL PROTECTED] To: "Ferhat DILMAN" [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: "Lutfi YUNUSOGLU" [EMAIL PROTECTED] Sent: 20 Kasm 1999 Cumartesi 04:23 Subject: Re: (RADIATOR) Password Expiration Hello Ferhat - On Thu, 18 Nov 1999, Ferhat DILMAN wrote: %_Hi, Is there a workaround/solution for password expiration in radiator? What we basically would like to do is to enable password changing in the black terminal script screen or another way just after user gets the authentication. Well, we can certainly extend the use of getspnam to return some additional information, but I'm not sure how you would go about letting the user change his password? Can you be more specific? thanks Hugh -- 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. === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Password Expiration
I was wrong. In 3. it must be: set PASSWORD_CREATED=SYSDATE (EXPIRE is still 15. :)) - Original Message - From: "Ferhat Dilman" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: "Lutfi YUNUSOGLU" [EMAIL PROTECTED] Sent: 21 Kasm 1999 Pazar 03:21 Subject: Re: (RADIATOR) Password Expiration Hi, Not just AuthBy SYSTEM. We are using SQL database for example. Assume that we have set the field EXPIRE=15 and WARN=3. That means every 15 days, the user must change his/her password and probably will receive warning messages 3 days before. S/he may change his/her password either last day thru the black terminal script screen or in a way in the web server (this is easy part) My solution would be: 1- Password is set. 15 days left for changing. 3 days for warning. EXPIRE=15, WARN=3 2- Every day a backend stored procedure runs for every user and will change/remove password which is PASSWORD_CREATED+EXPIRESYSDATE (PASSWORD_CREATED (date format, is the date password created) 2- User will receive warning automatically in both black screen to change his password, and will also receive e-mail. 3- user changes his password using a web interface. and set (EXPIRE=SYSDATE+15) 4- user forgets to change his password and the final day arrives. his password expired. when he tries to re-connect he will receive "Password Expired, please use guest/guestpassword account to change password" message. User may connect to ONLY password-change page which is secure. After password changed, user may connect regularly using all services. This is my solution without (or minimal) change in radiator. What if this functionality is default in radius.cfg configuration items? (The minimal change would be to add request denied - password expired message into perl scripts and additional select statements for SQL database) And I will have to add guest/guestpassword account with IP-filter into password-change page ONLY. My 2 cents. Best Regards, Ferhat - Original Message - From: "Hugh Irvine" [EMAIL PROTECTED] To: "Ferhat DILMAN" [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: "Lutfi YUNUSOGLU" [EMAIL PROTECTED] Sent: 20 Kasm 1999 Cumartesi 04:23 Subject: Re: (RADIATOR) Password Expiration Hello Ferhat - On Thu, 18 Nov 1999, Ferhat DILMAN wrote: %_Hi, Is there a workaround/solution for password expiration in radiator? What we basically would like to do is to enable password changing in the black terminal script screen or another way just after user gets the authentication. Well, we can certainly extend the use of getspnam to return some additional information, but I'm not sure how you would go about letting the user change his password? Can you be more specific? thanks Hugh -- 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. === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) GRIC Setting
Hi, In radiator configuration manual, the GRIC setting part, it assumes that all local users are connecting using a REALM something (in the manual: open.com.au) and the rest is ASSUMED to be GRIC user. However in our case we don't use a REALM at all. How will I define GRIC since all GRIC users use different foreign realms. The only solution came to my mind is to use multiple AUTH BY clauses in REALM DEFAULT using AUTHBY GROUP. However this will cause a very long delayed rejection messages to our local users since they will first try the local server, then will try GRIC server. Not acceptable I suppose. GRIC will also receive many wrong user authentication requests. Any solution or idea? Thanks, Ferhat === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) finger problem
Hi, We are using Radiator 2.13.1 on Solaris with Oracle v8. There are several POP's and we use finger for ghost sessions. We use Ascend TNTs. Radiator is in location Istanbul for example, and one of the POP's are in other city e.g. Ankara. When the line goes down between Istanbul-Ankara, and the user tries to logon in Istanbul, since the user information still on RADONLINE, it tries to check it thru finger and since the line is down, finger WAITS! a longtime thus Radiator does not respond other requests till the finger request is finished (single process that is). Then eventually finger timeouts and the session is deleted from RADONLINE and user is permitted. However this has two problems: 1- User may be still online in Ankara (thus simultanous sessions) 2- finger waits too long and no user auth is accepted till timeout of finger Any solutions to finger problem when the line is down? How can we automatically cancel finger requests if the line is down between POP and Radiator-Host location? Thanks very much, Ferhat === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) finger problem
Hi, NasType Ascend and the log: Wed Jun 9 01:13:20 1999: ERR: The internal finger client failed with: Can't con nect to 195.x.x.x: Connection timed out Wed Jun 9 01:13:20 1999: NOTICE: Session for xx at 195.x.x.x:90 has gone away (I have deleted user information and NAS identifier IP address) Thanks, Ferhat -Original Message- From: Mike McCauley [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 12, 1999 1:51 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: 'Tuncay Margilic'; 'Lutfi Yunusoglu' Subject: Re: (RADIATOR) finger problem Hello Ferhat. What NasType are you using, and what does your finger say when it times out? Try running it by hand, to see. With that information, we might be able add a patch that will detect a timeout and not delete the user. Cheers. On Jun 11, 10:30am, Ferhat Dilman wrote: Subject: (RADIATOR) finger problem Hi, We are using Radiator 2.13.1 on Solaris with Oracle v8. There are several POP's and we use finger for ghost sessions. We use Ascend TNTs. Radiator is in location Istanbul for example, and one of the POP's are in other city e.g. Ankara. When the line goes down between Istanbul-Ankara, and the user tries to logon in Istanbul, since the user information still on RADONLINE, it tries to check it thru finger and since the line is down, finger WAITS! a longtime thus Radiator does not respond other requests till the finger request is finished (single process that is). Then eventually finger timeouts and the session is deleted from RADONLINE and user is permitted. However this has two problems: 1- User may be still online in Ankara (thus simultanous sessions) 2- finger waits too long and no user auth is accepted till timeout of finger Any solutions to finger problem when the line is down? How can we automatically cancel finger requests if the line is down between POP and Radiator-Host location? Thanks very much, Ferhat === 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 Ferhat Dilman -- 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.
RE: (RADIATOR) Radiator with SecurID
Hi, SecurID works with Radiator well. You should however setup Proxy radius to SecurityDynamics AccessManager (Radius Server of theirs). Extra money but does not work otherwise. That is: Radiator = ACE Access Manager (Radius) = ACEProxy = ACEserver We are running this. Radiator in Solaris. Rest of three ACE software run on same NT server. Perfect. Some accounting problems but will be fixed. We are also testing SecuRemote VPN. Good Luck, Ferhat -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dennis Feijen Sent: Friday, May 07, 1999 3:37 PM To: '[EMAIL PROTECTED]' Subject: (RADIATOR) Radiator with SecurID Hello, Does anyone has experience with setting up a Radiator server with authentication done by a ACE/Server (SecurID) and doing i.e. CLI and accounting by the Radiator server? How can I configure this in my configuration file of the Radiator server. So, I guess, Radiator needs some ACE/Agent code in the server software of Radiator. Please, let me know. Dennis Feijen __ RADIX Connectivity Security Specialisten Dennis Feijen Zekeringstraat 17 tel +31 (0)20 6 870 870 System Engineer 1014 BM Amsterdam fax +31 (0)20 6 870 842 [EMAIL PROTECTED] http://www.radix.nl email alg: [EMAIL PROTECTED] __ === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) MD5 Problem
Hi, Did you do make install in MD5 installation steps? It is not documented in README. However even though you do that (it works fine in Solaris), it gives the error you have faced in Debian Linux, too. When you do MD5 make install (or make test, i don't remember well now), it gives two commands: 1 is to remove old files the 2 is to remove intermediate files. I don't recall which is which but I ran the first command and it cleans the files. Then Radiator is happy. :) Good Luck, Ferhat P.S. Solaris installation is just fine for MD5. Linux only problem is I guess. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dialup USA Sales Dept Sent: Friday, April 09, 1999 11:50 AM To: [EMAIL PROTECTED] Subject: (RADIATOR) MD5 Problem When trying to do the "make test" command or "perl Makefile.PL" command and installing radius im getting the following error message. Any ideas as to what I need to do to make this work properly. I had perl 5 installed on my FreeBSD system and installed the module 5 version 1.7 today. I got these errors so I upgraded the to the MD 5 version 2.06 , however I am still getting the same errors so now Im thinking it might not be the modules but instead the perl 5 that im running. Any thoughts? Anyone know what I should do? su-2.03# perl Makefile.PL Warning: prerequisite MD5 0 not found at (eval 1) line 221. Writing Makefile for Radius su-2.03# Then as I do the "make test" I get about 10 of these errors Can't load module Digest::MD5, dynamic loading not available in this perl. (You may need to build a new perl executable which either supports dynamic loading or has the Digest::MD5 module statically linked into it.) at /usr/local/lib/perl5/site_perl/MD5.pm line 8 === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) radpwtst error
Hi, I am trying to install Radiator 2.13 into Debian Linux. I have installed Perl and MD5 and then Radiator. Everything fine. Except when I test the radpwtst. It gives this error: By the way, in the installation guide from the web page, it says goodies/simple.cfg that does not exist. I try with radius2.cfg in radiator directory. I forgot to mention it before. albatros:/home/dilman/Radiator-2.13# perl radpwtst -user mike -password fredsending Access-Request...Can't call method identifier on an undefined value at radpwtst line 485. Radiator started well. Thanks, Ferhat
Re: (RADIATOR) LDAP and SHA'd password
I would check the Directory Manager password and EncryptedPassword fields. And the BaseDN. Are you sure you have to use Directory Manager account? I don't remember but I guess I had used admin username . My memory gone away. Regards, Ferhat -Original Message- From: Ingvar Berg (ERA) [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: 01 Nisan 1999 Perembe 02:22 Subject: (RADIATOR) LDAP and SHA'd password Hi, I just moved from testing with flat user file to LDAP with SHA-1 hashed passwords. And gets stuck without a clue... Can anyone see the reason for not accepting the password? /Ingvar === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) SQL help
I guess tables should be created before it starts recording. We do monthly recording of accounting information and I had to create tables before it started logging. By the way, a daily working tables really work? 31 tables in SQL every month? Daily tables are more reasonable since it is 11st of March and it is around 400,000 records already in the database. Ferhat -Original Message- From: Richard Hawley [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: 11 Mart 1999 Perembe 20:24 Subject: (RADIATOR) SQL help How would I go about having separate Radius Accounting logs for say, each day of the month, using an SQL database? I know I can do the following, but what I'm not sure about is if Radiator can create the tables or if the tables for each day have to be created already? AccountingTable ACCT%m%d Thanks. ..Rich -- Richard W. Hawley - Network Engineer CyberZone Internet Services http://www.cyberzone.net [EMAIL PROTECTED] === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) AuthBy SQL
Hi, I have some questions regarding AuthBy SQL after I had ugraded into 2.1.3: I have only one AuthBySQL and auth/acct goes into Oracle. Here is the sample log: Fri Mar 5 09:28:46 1999: DEBUG: Handling request with Handler 'Realm=DEFAULT' Fri Mar 5 09:28:46 1999: DEBUG: Rewrote user name to 54722 Fri Mar 5 09:28:46 1999: DEBUG: Query is: select NASIDENTIFIER, NASPORT, ACCTSE SSIONID from RADONLINE where USERNAME='54722' Fri Mar 5 09:28:46 1999: DEBUG: Handling with Radius::AuthSQL Fri Mar 5 09:28:46 1999: DEBUG: Handling with Radius::AuthSQL Fri Mar 5 09:28:46 1999: DEBUG: Query is: select PASSWORD,CHECKATTR,REPLYATTR f rom SUBSCRIBERS where USERNAME = '54722' and (expiredate sysdate or totaldays = 0) Fri Mar 5 09:28:46 1999: DEBUG: Radius::AuthSQL looks for match with 54722 Fri Mar 5 09:28:46 1999: DEBUG: Radius::AuthSQL ACCEPT: Fri Mar 5 09:28:46 1999: DEBUG: Access accepted for 54722 Fri Mar 5 09:28:46 1999: DEBUG: Packet dump: *** Sending to 195.174.219.2 port 1767 Code: Access-Accept Why are there TWO "Handling with Radius::AuthSQL statements in the log file? And here is: Fri Mar 5 09:28:49 1999: DEBUG: Handling request with Handler 'Realm=DEFAULT' Fri Mar 5 09:28:49 1999: DEBUG: Rewrote user name to 1623282 Fri Mar 5 09:28:49 1999: DEBUG: Query is: select NASIDENTIFIER, NASPORT, ACCTSE SSIONID from RADONLINE where USERNAME='1623282' Fri Mar 5 09:28:49 1999: DEBUG: Handling with Radius::AuthSQL Fri Mar 5 09:28:49 1999: DEBUG: Handling with Radius::AuthSQL Fri Mar 5 09:28:49 1999: DEBUG: Query is: select PASSWORD,CHECKATTR,REPLYATTR f rom SUBSCRIBERS where USERNAME = '1623282' and (expiredate sysdate or totalday s = 0) Fri Mar 5 09:28:49 1999: DEBUG: Radius::AuthSQL looks for match with 1623282 Fri Mar 5 09:28:49 1999: DEBUG: Radius::AuthSQL REJECT: Bad Password Fri Mar 5 09:28:49 1999: DEBUG: Query is: select PASSWORD,CHECKATTR,REPLYATTR f rom SUBSCRIBERS where USERNAME = 'DEFAULT' and (expiredate sysdate or totalday s = 0) Fri Mar 5 09:28:49 1999: INFO: Access rejected for 1623282: Bad Password Why does Radiator go to USERNAME='DEFAULT' check Any ideas? Thanks, Ferhat === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Urgent: MaxSessions Exceeded
Hi, After we upgraded into 2.1.3 radiator started giving messages "Request Denied" if it is MaxSessions Exceeded. In the previous version it was saying Maximum Sessions Exceeded in the script window. Now it says opposite and user thinks that it is password or user problem. Any solution? Regards, Ferhat === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Password Expiration
Title: Password Expiration Hi, Is there a workaround/solution for password expiration in radiator? What we basically would like to do is to enable password changing in the black terminal script screen or another way just after user gets the authentication. Thanks, Ferhat
