Re: re[2]: (RADIATOR) Radiator freezing intermitantly
Hello Matt, Hello Brian - It is usually very easy to see this in a trace 4 debug, as you will have the timestamps on all the DEBUG messages. regards Hugh On Friday, Jun 27, 2003, at 20:10 Australia/Melbourne, Matt Taylor wrote: We are running into the same problem on a machine where we are using the primary ip address of the system for radiator. A user will dial in and our equipment will run the radius request, at which I can see radius authenticating the user in authlog, but the dialup equip isn't getting it cause it tries 5 times to auth (the set value) and tells users their username and password is invalid. We are using 3com (now utstarcom) hiperarc running TCS 4.2 and the newest version of radiator. Attached is my conf file. I have radius stable on a system now, but when I tried to move it to this new system it worked. The problem is intermitent. I've seen this kind of problem when any log files you have get too large. Radiator struggles to respond before the NAS times out and sends another request, as a result of the load induced from appending to a large log file each time an authentication takes place. Regards Matthew Taylor Senior Network Engineer - Cisco CCNA, Citrix CCA, Watchguard WCSP, WCSPV Techcel Computer Services Pty Ltd Phone (02) 4960 1139 Fax (02) 4960 2639 === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening? -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator freezing intermitantly
Hello Brian - Thanks for letting me know. regards Hugh On Friday, Jun 27, 2003, at 23:12 Australia/Melbourne, Brian Fisk wrote: Well after fooling around with it, I found that the problem was not an ip issue, but with accounting. The message I was getting from my RAS was AUTH: client/server failure which I found usually meant a secret mismatch. I turned on monitoring for auth and accounting on the ras, and I saw I was getting the error message in my RAS syslog ever time it sent an accounting request. I turned off Accounting on my ras and the problem went away and users could authenticate. So I redid my accounting statements in my radius.cfg to be a bit more simple and only logg what I need. I also cleared the mysql accounting table which had around 20k entries in it. It is a slower machine and maybe from what Matt said, it could have been too much. But it seams to be holding steady. Brian - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Brian Fisk" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, June 26, 2003 8:07 PM Subject: Re: (RADIATOR) Radiator freezing intermitantly Hello Brian - If the machine running Radiator only has a single interface and a single IP address, then the only reason that the NAS will not receive a reply and send a retransmission must be due to packets being dropped on the return path, either because of filters or firewalls or misconfigured interfaces. By definition, if Radiator is receiving the request, processing it and sending back a reply, then Radiator is operating correctly. As mentioned in my previous mail, this sort of problem usually requires debugging with a packet sniffer to ascertain exactly what is going on. regards Hugh On Thursday, Jun 26, 2003, at 23:27 Australia/Melbourne, Brian Fisk wrote: Update: We are running into the same problem on a machine where we are using the primary ip address of the system for radiator. A user will dial in and our equipment will run the radius request, at which I can see radius authenticating the user in authlog, but the dialup equip isn't getting it cause it tries 5 times to auth (the set value) and tells users their username and password is invalid. We are using 3com (now utstarcom) hiperarc running TCS 4.2 and the newest version of radiator. Attached is my conf file. I have radius stable on a system now, but when I tried to move it to this new system it worked. The problem is intermitent. # radius.cfg -JJGracia - Jan2003 # #Foreground #LogStdout # Use a low trace level in production systems. Increase # it to 4 or 5 for debugging, or use the -trace flag to radiusd PidFile /var/run/radiusd.pid AuthPort1645 AcctPort1646 #BindAddress 199.234.153.42,199.234.153.3 #NasTypeTotalControlSNMP #trace 3 DbDir /etc/radiator DictionaryFile %D/dictionary.usr LogDir /var/log/radius #LogFile%L/%Y%m.log #Trace 3 Filename %L/%Y%m.log Trace 3 #LogFormat %0:%1:%2 LogMicroseconds Identifier myauthlogger Filename %L/authlog LogSuccess 1 LogFailure 1 SuccessFormat %l:%U:%P:OK FailureFormat %l:%U:%P:FAIL Identifier mystatslogger Filename %L/statslog # Format %0:%1:%2:%23 Secret tempest DupInterval 0 Secret tempest DupInterval 0 #NasType TotalControl SNMPCommunity private DBSourcedbi:mysql:radius:localhost DBUsername blue DBAuth green DBSourcedbi:mysql:radius DBUsername blue DBAuth green RewriteUsername s/^([EMAIL PROTECTED]).*/$1/ RewriteUsername tr/[A-Z]/[a-z]/ RewriteUsername s/\s+//g #RewriteUsername tr/A-Za-z0-9_@//cd # AcctLogFileName %L/detail # WtmpFileName%L/wtmp DBSourcedbi:mysql:radius:localhost DBUsername blue DBAuth green AuthSelect select PASSWORD,CHECKATTR,REPLYATTR from SUBSCRIBERS where USERNAME='%n' AccountingTable ACCOUNTING AcctColumnDef USERNAME,User-Name AcctColumnDef TIME_STAMP,Timestamp,integer AcctColumnDef ACCTSTATUSTYPE,Acct-Status-Type AcctColumnDef ACCTDELAYTIME,Acct-Delay-Time,integer AcctColumnDef ACCTINPUTOCTETS,Acct-Input-Octets,integer AcctColumnDef ACCTOUTPUTOCTETS,Acct-Output-Octets,integer AcctColumnDef ACCTSESSIONID,Acct-Session-Id AcctColumnDef ACCTSESSIONTIME,Acct-Session-Time,integer AcctColumnDef ACCTTERMINATECAUSE,Acct_Terminate-Cause AcctColumnDef NASIDENTIFIER,NAS-IP-Address AcctColumnDef NASIPADDRESS,NAS-Identifier AcctColumnDef NASPORT,NAS-Port,integer
Re: (RADIATOR) Radiator freezing intermitantly
Well after fooling around with it, I found that the problem was not an ip issue, but with accounting. The message I was getting from my RAS was AUTH: client/server failure which I found usually meant a secret mismatch. I turned on monitoring for auth and accounting on the ras, and I saw I was getting the error message in my RAS syslog ever time it sent an accounting request. I turned off Accounting on my ras and the problem went away and users could authenticate. So I redid my accounting statements in my radius.cfg to be a bit more simple and only logg what I need. I also cleared the mysql accounting table which had around 20k entries in it. It is a slower machine and maybe from what Matt said, it could have been too much. But it seams to be holding steady. Brian - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Brian Fisk" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, June 26, 2003 8:07 PM Subject: Re: (RADIATOR) Radiator freezing intermitantly > > Hello Brian - > > If the machine running Radiator only has a single interface and a > single IP address, then the only reason that the NAS will not receive a > reply and send a retransmission must be due to packets being dropped on > the return path, either because of filters or firewalls or > misconfigured interfaces. > > By definition, if Radiator is receiving the request, processing it and > sending back a reply, then Radiator is operating correctly. > > As mentioned in my previous mail, this sort of problem usually requires > debugging with a packet sniffer to ascertain exactly what is going on. > > regards > > Hugh > > > On Thursday, Jun 26, 2003, at 23:27 Australia/Melbourne, Brian Fisk > wrote: > > > Update: > > > > We are running into the same problem on a machine where we are using > > the > > primary ip address of the system for radiator. A user will dial in > > and our > > equipment will run the radius request, at which I can see radius > > authenticating the user in authlog, but the dialup equip isn't getting > > it > > cause it tries 5 times to auth (the set value) and tells users their > > username and password is invalid. We are using 3com (now utstarcom) > > hiperarc running TCS 4.2 and the newest version of radiator. > > Attached is > > my conf file. I have radius stable on a system now, but when I tried > > to > > move it to this new system it worked. The problem is intermitent. > > > > > > # radius.cfg -JJGracia - Jan2003 > > # > > #Foreground > > #LogStdout > > > > # Use a low trace level in production systems. Increase > > # it to 4 or 5 for debugging, or use the -trace flag to radiusd > > > > > > PidFile /var/run/radiusd.pid > > AuthPort1645 > > AcctPort1646 > > #BindAddress 199.234.153.42,199.234.153.3 > > #NasTypeTotalControlSNMP > > #trace 3 > > > > DbDir /etc/radiator > > DictionaryFile %D/dictionary.usr > > > > LogDir /var/log/radius > > #LogFile%L/%Y%m.log > > #Trace 3 > > > > > > Filename %L/%Y%m.log > > Trace 3 > > #LogFormat %0:%1:%2 > > LogMicroseconds > > > > > > > > Identifier myauthlogger > > Filename %L/authlog > > LogSuccess 1 > > LogFailure 1 > > SuccessFormat %l:%U:%P:OK > > FailureFormat %l:%U:%P:FAIL > > > > > > > > Identifier mystatslogger > > Filename %L/statslog > > # Format %0:%1:%2:%23 > > > > > > > > Secret tempest > > DupInterval 0 > > > > > > > > Secret tempest > > DupInterval 0 > > #NasType TotalControl > > SNMPCommunity private > > > > > > > > DBSourcedbi:mysql:radius:localhost > > DBUsername blue > > DBAuth green > > > > > > > > DBSourcedbi:mysql:radius > > DBUsername blue > > DBAuth green > > > > > > > > > > > >RewriteUsername s/^([EMAIL PROTECTED]).*/$1/ > >RewriteUsername tr/[A-Z]/[a-z]/ > >RewriteUsername s/\s+//g > > #RewriteUsername tr/A-Za-z0-9_@//cd > > # AcctLogFileName %L/detail > > # WtmpFileName%L/wtmp > > > > > > > > DBSourcedbi:mysql:radius:localhost > > DBUsername blue >
re[2]: (RADIATOR) Radiator freezing intermitantly
> We are running into the same problem on a machine where we are using the > primary ip address of the system for radiator. A user will dial in and our > equipment will run the radius request, at which I can see radius > authenticating the user in authlog, but the dialup equip isn't getting it > cause it tries 5 times to auth (the set value) and tells users their > username and password is invalid. We are using 3com (now utstarcom) > hiperarc running TCS 4.2 and the newest version of radiator. Attached is > my conf file. I have radius stable on a system now, but when I tried to > move it to this new system it worked. The problem is intermitent. I've seen this kind of problem when any log files you have get too large. Radiator struggles to respond before the NAS times out and sends another request, as a result of the load induced from appending to a large log file each time an authentication takes place. Regards Matthew Taylor Senior Network Engineer - Cisco CCNA, Citrix CCA, Watchguard WCSP, WCSPV Techcel Computer Services Pty Ltd Phone (02) 4960 1139 Fax (02) 4960 2639 === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator freezing intermitantly
IL PROTECTED]> Sent: Friday, June 20, 2003 7:41 PM Subject: Re: (RADIATOR) Radiator freezing intermitantly Hello Brian - On machines with multiple interfaces, this is usually due to the radius response being sent back to the client from a different IP address to that from which the request was received (ie the response was sent via a different interface). Using a sniffer to check the packet flow is usually very helpful (snoop, tcpdump, ethereal, ...). regards Hugh On Friday, Jun 20, 2003, at 23:12 Australia/Melbourne, Brian Fisk wrote: We had more troubles yesterday and the problem that is happening is when we have radiator setup to bind on a secondary ip of the machine. When I took out the bind address statement, which should make radiator listen on all ip's, it still wouldn't work. I had to set our dialup equipment to use the base ip of the machine and then it started working. When a user tried to dial up, they would authenticate, as I could see in my authlog, but the dialup equipment kept authenticating them for around 3-4 times before it hung up on them. The dialup equipment (total control) was giving me error messages that according to the total control website, said that the secret key was a mismatch. I think it's an ip issue with the machine but we will find out more from testing on monday. Brian Fisk - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Brian Fisk" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, June 19, 2003 8:03 PM Subject: Re: (RADIATOR) Radiator freezing intermitantly Hello Brian - I will need to see a copy of the configuration file (no secrets) together with a trace 4 debug from Radiator showing what is happening. There is also a FAQ item regarding Redhat 8 here: http://www.open.com.au/radiator/faq.html#127 regards Hugh On Friday, Jun 20, 2003, at 02:20 Australia/Melbourne, Brian Fisk wrote: I have been running radiator on the same server for the last 3 years and it worked perfect. I am now setting up radiator 3.6 on another server using the old config file which was version 2.18.1 I am noticing that radiator will just freeze up for a period of 5 minutes or so. Is there any incompatabilities between the versions for the config file, or can someone suggest a way of logging to diagnose the problem? I am running Redhat 8.0 Linux server1 2.4.18-24.8.0smp #1 SMP Fri Jan 31 06:03:47 EST 2003 i686 i686 i386 GNU/Linux) === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening? -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening? -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening? -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator freezing intermitantly
Update: We are running into the same problem on a machine where we are using the primary ip address of the system for radiator. A user will dial in and our equipment will run the radius request, at which I can see radius authenticating the user in authlog, but the dialup equip isn't getting it cause it tries 5 times to auth (the set value) and tells users their username and password is invalid. We are using 3com (now utstarcom) hiperarc running TCS 4.2 and the newest version of radiator. Attached is my conf file. I have radius stable on a system now, but when I tried to move it to this new system it worked. The problem is intermitent. # radius.cfg -JJGracia - Jan2003 # #Foreground #LogStdout # Use a low trace level in production systems. Increase # it to 4 or 5 for debugging, or use the -trace flag to radiusd PidFile /var/run/radiusd.pid AuthPort1645 AcctPort1646 #BindAddress 199.234.153.42,199.234.153.3 #NasTypeTotalControlSNMP #trace 3 DbDir /etc/radiator DictionaryFile %D/dictionary.usr LogDir /var/log/radius #LogFile%L/%Y%m.log #Trace 3 Filename %L/%Y%m.log Trace 3 #LogFormat %0:%1:%2 LogMicroseconds Identifier myauthlogger Filename %L/authlog LogSuccess 1 LogFailure 1 SuccessFormat %l:%U:%P:OK FailureFormat %l:%U:%P:FAIL Identifier mystatslogger Filename %L/statslog # Format %0:%1:%2:%23 Secret tempest DupInterval 0 Secret tempest DupInterval 0 #NasType TotalControl SNMPCommunity private DBSourcedbi:mysql:radius:localhost DBUsername blue DBAuth green DBSourcedbi:mysql:radius DBUsername blue DBAuth green RewriteUsername s/^([EMAIL PROTECTED]).*/$1/ RewriteUsername tr/[A-Z]/[a-z]/ RewriteUsername s/\s+//g #RewriteUsername tr/A-Za-z0-9_@//cd # AcctLogFileName %L/detail # WtmpFileName%L/wtmp DBSourcedbi:mysql:radius:localhost DBUsername blue DBAuth green AuthSelect select PASSWORD,CHECKATTR,REPLYATTR from SUBSCRIBERS where USERNAME='%n' AccountingTable ACCOUNTING AcctColumnDef USERNAME,User-Name AcctColumnDef TIME_STAMP,Timestamp,integer AcctColumnDef ACCTSTATUSTYPE,Acct-Status-Type AcctColumnDef ACCTDELAYTIME,Acct-Delay-Time,integer AcctColumnDef ACCTINPUTOCTETS,Acct-Input-Octets,integer AcctColumnDef ACCTOUTPUTOCTETS,Acct-Output-Octets,integer AcctColumnDef ACCTSESSIONID,Acct-Session-Id AcctColumnDef ACCTSESSIONTIME,Acct-Session-Time,integer AcctColumnDef ACCTTERMINATECAUSE,Acct_Terminate-Cause AcctColumnDef NASIDENTIFIER,NAS-IP-Address AcctColumnDef NASIPADDRESS,NAS-Identifier AcctColumnDef NASPORT,NAS-Port,integer AcctColumnDef ACCTFRAMEDIP,Framed-IP-Address AcctColumnDef ACCTFRAMEDNETMASK,Framed-Netmask AcctColumnDef ACCTCALLERID,Calling-Station-Id AcctColumnDef ACCTCALLEDID,Called-Station-Id AcctColumnDef MODEMTRAININGTIME,Modem-Training-Time,integer AcctColumnDef CHASISCALLSLOT,Chassis-Call-Slot,integer AcctColumnDef CHASISCALLSPAN,Chassis-Call-Span,integer AcctColumnDef CHASISCALLCHAN,Chassis-Call-Channel,integer AcctColumnDef MODULATIONTYPE,Modulation-Type AcctColumnDef ERRORCNTL,Error-Control AcctColumnDef COMPRESSTYPE,Compression-Type AcctColumnDef INTICONNECTRATE,Initial-Connect-Rate AcctColumnDef FRAMEDPROTOCOL,Framed-Protocol AcctColumnDef SPEEDOFCONNECT, Speed-Of-Connection # AcctFailedLogFileName %D/missedaccounting AuthLog myauthlogger #StatsLog mystatslogger - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Brian Fisk" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, June 20, 2003 7:41 PM Subject: Re: (RADIATOR) Radiator freezing intermitantly > > Hello Brian - > > On machines with multiple interfaces, this is usually due to the radius > response being sent back to the client from a different IP address to > that from which the request was received (ie the response was sent via > a different interface). > > Using a sniffer to check the packet flow is usually very helpful > (snoop, tcpdump, ethereal, ...). > > regards > > Hugh > > > On Friday, Jun 20, 2003, at 23:12 Australia/Melbourne, Brian Fisk wrote: > > > We had more troubles yesterday
Re: (RADIATOR) Radiator freezing intermitantly
Hello Brian - On machines with multiple interfaces, this is usually due to the radius response being sent back to the client from a different IP address to that from which the request was received (ie the response was sent via a different interface). Using a sniffer to check the packet flow is usually very helpful (snoop, tcpdump, ethereal, ...). regards Hugh On Friday, Jun 20, 2003, at 23:12 Australia/Melbourne, Brian Fisk wrote: We had more troubles yesterday and the problem that is happening is when we have radiator setup to bind on a secondary ip of the machine. When I took out the bind address statement, which should make radiator listen on all ip's, it still wouldn't work. I had to set our dialup equipment to use the base ip of the machine and then it started working. When a user tried to dial up, they would authenticate, as I could see in my authlog, but the dialup equipment kept authenticating them for around 3-4 times before it hung up on them. The dialup equipment (total control) was giving me error messages that according to the total control website, said that the secret key was a mismatch. I think it's an ip issue with the machine but we will find out more from testing on monday. Brian Fisk - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Brian Fisk" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, June 19, 2003 8:03 PM Subject: Re: (RADIATOR) Radiator freezing intermitantly Hello Brian - I will need to see a copy of the configuration file (no secrets) together with a trace 4 debug from Radiator showing what is happening. There is also a FAQ item regarding Redhat 8 here: http://www.open.com.au/radiator/faq.html#127 regards Hugh On Friday, Jun 20, 2003, at 02:20 Australia/Melbourne, Brian Fisk wrote: I have been running radiator on the same server for the last 3 years and it worked perfect. I am now setting up radiator 3.6 on another server using the old config file which was version 2.18.1 I am noticing that radiator will just freeze up for a period of 5 minutes or so. Is there any incompatabilities between the versions for the config file, or can someone suggest a way of logging to diagnose the problem? I am running Redhat 8.0 Linux server1 2.4.18-24.8.0smp #1 SMP Fri Jan 31 06:03:47 EST 2003 i686 i686 i386 GNU/Linux) === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening? -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening? -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator freezing intermitantly
We had more troubles yesterday and the problem that is happening is when we have radiator setup to bind on a secondary ip of the machine. When I took out the bind address statement, which should make radiator listen on all ip's, it still wouldn't work. I had to set our dialup equipment to use the base ip of the machine and then it started working. When a user tried to dial up, they would authenticate, as I could see in my authlog, but the dialup equipment kept authenticating them for around 3-4 times before it hung up on them. The dialup equipment (total control) was giving me error messages that according to the total control website, said that the secret key was a mismatch. I think it's an ip issue with the machine but we will find out more from testing on monday. Brian Fisk - Original Message - From: "Hugh Irvine" <[EMAIL PROTECTED]> To: "Brian Fisk" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, June 19, 2003 8:03 PM Subject: Re: (RADIATOR) Radiator freezing intermitantly > > Hello Brian - > > I will need to see a copy of the configuration file (no secrets) > together with a trace 4 debug from Radiator showing what is happening. > > There is also a FAQ item regarding Redhat 8 here: > > http://www.open.com.au/radiator/faq.html#127 > > regards > > Hugh > > > On Friday, Jun 20, 2003, at 02:20 Australia/Melbourne, Brian Fisk wrote: > > > I have been running radiator on the same server for the last 3 years > > and it > > worked perfect. I am now setting up radiator 3.6 on another server > > using > > the old config file which was version 2.18.1 > > > > I am noticing that radiator will just freeze up for a period of 5 > > minutes or > > so. Is there any incompatabilities between the versions for the config > > file, or can someone suggest a way of logging to diagnose the problem? > > > > I am running Redhat 8.0 Linux server1 2.4.18-24.8.0smp #1 SMP Fri Jan > > 31 > > 06:03:47 EST 2003 i686 i686 i386 GNU/Linux) > > > > > > === > > Archive at http://www.open.com.au/archives/radiator/ > > Announcements on [EMAIL PROTECTED] > > To unsubscribe, email '[EMAIL PROTECTED]' with > > 'unsubscribe radiator' in the body of the message. > > > > > > NB: have you included a copy of your configuration file (no secrets), > together with a trace 4 debug showing what is happening? > > -- > Radiator: the most portable, flexible and configurable RADIUS server > anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. > - > Nets: internetwork inventory and management - graphical, extensible, > flexible with hardware, software, platform and database independence. > > === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator freezing intermitantly
Hello Brian - I will need to see a copy of the configuration file (no secrets) together with a trace 4 debug from Radiator showing what is happening. There is also a FAQ item regarding Redhat 8 here: http://www.open.com.au/radiator/faq.html#127 regards Hugh On Friday, Jun 20, 2003, at 02:20 Australia/Melbourne, Brian Fisk wrote: I have been running radiator on the same server for the last 3 years and it worked perfect. I am now setting up radiator 3.6 on another server using the old config file which was version 2.18.1 I am noticing that radiator will just freeze up for a period of 5 minutes or so. Is there any incompatabilities between the versions for the config file, or can someone suggest a way of logging to diagnose the problem? I am running Redhat 8.0 Linux server1 2.4.18-24.8.0smp #1 SMP Fri Jan 31 06:03:47 EST 2003 i686 i686 i386 GNU/Linux) === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening? -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Radiator freezing intermitantly
I have been running radiator on the same server for the last 3 years and it worked perfect. I am now setting up radiator 3.6 on another server using the old config file which was version 2.18.1 I am noticing that radiator will just freeze up for a period of 5 minutes or so. Is there any incompatabilities between the versions for the config file, or can someone suggest a way of logging to diagnose the problem? I am running Redhat 8.0 Linux server1 2.4.18-24.8.0smp #1 SMP Fri Jan 31 06:03:47 EST 2003 i686 i686 i386 GNU/Linux) === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator Freezing
Hello Chris - For your first question, you should run Radiator with a "Trace 4" in the configuration file so you get the debug output in the log file. You will then be able to see what is going on and if you have any further questions you can send me a copy (with your configuration file). For your second question, there is an example configuration file and example SQL table definitions in the "goodies" directory of the Radiator distribution. There is also an excellent source of historical discussion on the archive site that you will find here: www.open.com.au/archives/radiator regards Hugh On Sat, 13 Jul 2002 03:07, Chris Painter wrote: > I am brand new to the site and I have 2 questions first, I am running > radiator on a windows 2k server and I have been getting screen freeze ups > over the past couple of days. When this happens no users cannot > authenticate. Second I want to put radiator on a FreeBSD machine and have > it authenticate against a sql db any advice would be appreciated. > > Thanks, > > Chris Painter > Global Systems Inc. > Systems Administrator/Distance Learning Project Manager > Work: 910.296.2001 x410 > Cell: 910.290.3699 > Fax: 910.296.2005 > E-mail: [EMAIL PROTECTED] > > > > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Radiator Freezing
I am brand new to the site and I have 2 questions first, I am running radiator on a windows 2k server and I have been getting screen freeze ups over the past couple of days. When this happens no users cannot authenticate. Second I want to put radiator on a FreeBSD machine and have it authenticate against a sql db any advice would be appreciated. Thanks, Chris Painter Global Systems Inc. Systems Administrator/Distance Learning Project Manager Work: 910.296.2001 x410 Cell: 910.290.3699 Fax: 910.296.2005 E-mail: [EMAIL PROTECTED] === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) radiator freezing on perl 5.005_03
Hello All - As Alexey says, we will need to see a copy of the configuration file (no secrets) together with a trace 4 debug from Radiator to see what is happening. We will also need to know what hardware/software platform you are using and any other relevant information that you have to hand. regards Hugh On Sunday 22 July 2001 15:47, Alexey Korchagin wrote: > Hello Roger and all. > > > RM> Has any one heard of radiator freezing on 5.005_03? > RM> Any ideas? > > I use many version of Radiator (from demo-version to 2.18.2) on RH > 6.1 with 5.005_03 and don't have any problems... > > I think that problem into other components. Look at trace level 4 and > may be you can see - what's happen wirh Radiator. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) radiator freezing on perl 5.005_03
Hello Roger and all. RM> Has any one heard of radiator freezing on 5.005_03? RM> Any ideas? I use many version of Radiator (from demo-version to 2.18.2) on RH 6.1 with 5.005_03 and don't have any problems... I think that problem into other components. Look at trace level 4 and may be you can see - what's happen wirh Radiator. -- Best regards, Alexey Korchagin mailto:[EMAIL PROTECTED] === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) radiator freezing on perl 5.005_03
Hi list, Has any one heard of radiator freezing on 5.005_03? it seems that after a few hours, radiator freezes (it is still running). it accepts requests but does not forward the request onto other servers. A killall -HUP fixes this problem. Any ideas? TIA Roger === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Radiator Freezing
Hello Aaron - On Tue, 18 Jan 2000, Aaron Liu wrote: > Hi Hugh, > > > > > You should try using AuthBy LDAP2 and the corresponding Net::LDAP module. > > Please have a look at section 6.30 in the Radiator 2.14.1 reference manual > for > > a discussion of the various LDAP options. > > > > Could you also let us know what LDAP server you are using? > > > > Note that there is a recent patch for Radiator 2.14.1: > > > > 7/1/00 Fixed a problem with AuthBy LDAP2, where recent versions > >of Net::LDAP do not support ldap_error_message. > >Download a new AuthLDAP2.pm from here. > > > > Thank you for your reply. We have tried the modification yesterday > evening and it seemed that the situation became worse. What we have done > were: > > 1. Installed perl-ldap-0.13.tar.gz >(perl Makefile.PL; make; make test; no error-> make install) > 2. Upgraded the AuthLDAP2.pm in perl lib directory. > 3. Changed radius.cfg so it used instead of . > 4. Restarted the server. > > Afterwards we observed the log and the requests and response kept coming > in, so we thought the change was okay. However, upon further testing with > radpwtst we found that we got "No Reply" with all three types of requests. > When we did actual dialup testing, the client timed out even though the log > said Radiator has sent back both access-accept and accounting-response (our > NAS here at the local telco was set to grant permission only after receiving > accounting-reponse). > Investigation from telco told us our radius service did not respond from > time to time. So finally we reverted the configuration to use old LDAP > service and it started working again (for the time being). > > We are using openldap-1.2.7-2 rpm for redhat6.1 for providing LDAP > service. > > Thank you very much for your advice in this issue again, in particular I > would like to know whether we have skipped any steps in changing to the > LDAP2 module, and why the radpwtst stopped working with the new > configuration. We have had numerous reports of problems with openldap. You might try either University of Michigan LDAP or Netscape's LDAP server, both of which we know to work quite reliably. >From your description above, I do not understand how Radiator could be sending both Access-Accept and Accounting-Accept, and still have your telco NAS not proceeding with the connection. I would like to see a trace 4 debug of both AuthBy LDAP and LDAP2 showing the differences. BTW - it is very useful to have both your configuration file (no secrets) and the trace 4 debug output discussed above when you submit a problem. It makes it much, much easier to help! Meanwhile, I will be doing some LDAP testing here shortly (on a Redhat 6.1 system), so I will have some good test results on both openldap and Umich LDAP. I'll let you know how I get on. regards 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.
Re: (RADIATOR) Radiator Freezing
Hi Hugh, > > You should try using AuthBy LDAP2 and the corresponding Net::LDAP module. > Please have a look at section 6.30 in the Radiator 2.14.1 reference manual for > a discussion of the various LDAP options. > > Could you also let us know what LDAP server you are using? > > Note that there is a recent patch for Radiator 2.14.1: > > 7/1/00 Fixed a problem with AuthBy LDAP2, where recent versions >of Net::LDAP do not support ldap_error_message. >Download a new AuthLDAP2.pm from here. > Thank you for your reply. We have tried the modification yesterday evening and it seemed that the situation became worse. What we have done were: 1. Installed perl-ldap-0.13.tar.gz (perl Makefile.PL; make; make test; no error-> make install) 2. Upgraded the AuthLDAP2.pm in perl lib directory. 3. Changed radius.cfg so it used instead of . 4. Restarted the server. Afterwards we observed the log and the requests and response kept coming in, so we thought the change was okay. However, upon further testing with radpwtst we found that we got "No Reply" with all three types of requests. When we did actual dialup testing, the client timed out even though the log said Radiator has sent back both access-accept and accounting-response (our NAS here at the local telco was set to grant permission only after receiving accounting-reponse). Investigation from telco told us our radius service did not respond from time to time. So finally we reverted the configuration to use old LDAP service and it started working again (for the time being). We are using openldap-1.2.7-2 rpm for redhat6.1 for providing LDAP service. Thank you very much for your advice in this issue again, in particular I would like to know whether we have skipped any steps in changing to the LDAP2 module, and why the radpwtst stopped working with the new configuration. -- Aaron Liu === 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 Freezing
Hello Aaron - On Fri, 14 Jan 2000, Aaron Liu wrote: > Dear all, > > We got a frozen radiator which refused access-requests. Here is the > debug log (at trace level 5) at that particular moment: > > Wed Jan 12 00:50:01 2000: DEBUG: Handling request with Handler > 'Realm=DEFAULT' > Wed Jan 12 00:50:01 2000: DEBUG: Deleting session for 4021, > 202.4.197.65, 97 > Wed Jan 12 00:50:01 2000: DEBUG: Handling with Radius::AuthLDAP > Wed Jan 12 00:50:01 2000: DEBUG: Connecting to 202.4.192.196, port 389 > Wed Jan 12 12:00:27 2000: INFO: Server started > Wed Jan 12 12:00:30 2000: DEBUG: Packet dump: > > Note that the server stopped responding at 00:50, when it was trying to > connect to our LDAP server. We verified the unavailability by using radpwtst > locally and got a 'No reply'. We restarted at 12:00 with a kill -HUP and it > promptly accepted connection from the auth port again. Below is our > configuration file: > > > Foreground > LogStdout > LogDir /var/log/radius > LogFile %L/%Y/%m/%d/log > DictionaryFile /usr/local/etc/dictionary > PidFile /var/run/radiusd.pid > DbDir /var/log/radius > Trace 5 > AuthPort1645 > AcctPort1646 > > > Secret > DupInterval 0 > > > > > # Tell Radiator how to talk to the LDAP server > Host202.4.192.196 > AuthDN X > BaseDN X > AuthPasswordX > UsernameAttraccessID > PasswordAttraccessPassword > CheckAttr accessCheckAttr > ReplyAttr accessReplyAttr > > AddToReply Framed-Protocol = PPP,\ > Service-Type = 2,\ > Framed-Routing = None,\ > Framed-MTU = 1500,\ > Framed-Compression = Van-Jacobson-TCP-IP > > AcctLogFileName %L/%Y/%m/%d/%H > You should try using AuthBy LDAP2 and the corresponding Net::LDAP module. Please have a look at section 6.30 in the Radiator 2.14.1 reference manual for a discussion of the various LDAP options. Could you also let us know what LDAP server you are using? Note that there is a recent patch for Radiator 2.14.1: 7/1/00 Fixed a problem with AuthBy LDAP2, where recent versions of Net::LDAP do not support ldap_error_message. Download a new AuthLDAP2.pm from here. hth 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.
(RADIATOR) Radiator Freezing
Dear all, We got a frozen radiator which refused access-requests. Here is the debug log (at trace level 5) at that particular moment: Wed Jan 12 00:50:01 2000: DEBUG: Handling request with Handler 'Realm=DEFAULT' Wed Jan 12 00:50:01 2000: DEBUG: Deleting session for 4021, 202.4.197.65, 97 Wed Jan 12 00:50:01 2000: DEBUG: Handling with Radius::AuthLDAP Wed Jan 12 00:50:01 2000: DEBUG: Connecting to 202.4.192.196, port 389 Wed Jan 12 12:00:27 2000: INFO: Server started Wed Jan 12 12:00:30 2000: DEBUG: Packet dump: Note that the server stopped responding at 00:50, when it was trying to connect to our LDAP server. We verified the unavailability by using radpwtst locally and got a 'No reply'. We restarted at 12:00 with a kill -HUP and it promptly accepted connection from the auth port again. Below is our configuration file: Foreground LogStdout LogDir /var/log/radius LogFile %L/%Y/%m/%d/log DictionaryFile /usr/local/etc/dictionary PidFile /var/run/radiusd.pid DbDir /var/log/radius Trace 5 AuthPort1645 AcctPort1646 Secret DupInterval 0 # Tell Radiator how to talk to the LDAP server Host202.4.192.196 AuthDN X BaseDN X AuthPasswordX UsernameAttraccessID PasswordAttraccessPassword CheckAttr accessCheckAttr ReplyAttr accessReplyAttr AddToReply Framed-Protocol = PPP,\ Service-Type = 2,\ Framed-Routing = None,\ Framed-MTU = 1500,\ Framed-Compression = Van-Jacobson-TCP-IP AcctLogFileName %L/%Y/%m/%d/%H We are running Redhat 6.1 on a dual PIII 550 Compaq Proliant box with 512MB of RAM. perl -V Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=linux, osvers=2.2.5-22smp, archname=i386-linux uname='linux porky.devel.redhat.com 2.2.5-22smp #1 smp wed jun 2 09:11:51 edt 1999 i686 unknown ' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='-O2', gccversion=egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) cppflags='-Dbool=char -DHAS_BOOL -I/usr/local/include' ccflags ='-Dbool=char -DHAS_BOOL -I/usr/local/include' stdchar='char', d_stdstdio=undef, usevfork=false intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib libs=-lnsl -ldl -lm -lc -lposix -lcrypt libc=, so=so, useshrplib=false, libperl=libperl.a Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic' cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib' Characteristics of this binary (from libperl): Built under linux Compiled at Aug 30 1999 23:09:51 @INC: /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005 . Thanks for any information that anyone can share with us. -- Aaron Liu === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) freezing
On Fri, Jan 07, 2000 at 02:19:24PM +0100, Robin Gruyters wrote:
> Hi here is a trace (from the second config):
>
> Fri Jan 7 14:13:44 2000: DEBUG: Handling request with Handler 'Realm=DEFAULT'
> Fri Jan 7 14:13:44 2000: DEBUG: Deleting session for
> ¦
> ^£#÷!M|ůÏãÀ·ÒQ¯Oeèÿ}²õ÷Pu;ÅYB¤ÆÎY¶ÈN&k´Ó?4N¾($!yIð1>eÔ´úùQæ¼]àÑ¿ómÞÄvüÞ&ÚÄ<ñÅg?¯ùv
> *·ì ñåÝfòÑZ:'
> rü{&=Ô¹Ô¼û(x/ê,t2&Ðxsݦ¢K[b¡3$£ë×6Öú¦&úß
> 0IMöj(Û?]"¯fGÌ`yzÉ
> $=ßfò¹ÑJ¾«dÊ/älÝ, 195.7.137.175, 18
> Fri Jan 7 14:13:44 2000: DEBUG: Handling with Radius::AuthLDAP2
> Fri Jan 7 14:13:44 2000: DEBUG: Connecting to ldap1.inside.servers, port 389
>
> It only freezes on de normal radius server(s) not on the proxy one
>
You probably don't want to be sending garbage to LDAP servers. If they
are like the ones I have to interface with, they are delicate flowers
and the slightest harsh word causes them to fail.
[EMAIL PROTECTED]
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) freezing
Hi here is a trace (from the second config):
Fri Jan 7 14:13:44 2000: DEBUG: Handling request with Handler 'Realm=DEFAULT'
Fri Jan 7 14:13:44 2000: DEBUG: Deleting session for
¦
^£#÷!M|ůÏãÀ·ÒQ¯Oeèÿ}²õ÷Pu;ÅYB¤ÆÎY¶ÈN&k´Ó?4N¾($!yIð1>eÔ´úùQæ¼]àÑ¿ómÞÄvüÞ&ÚÄ<ñÅg?¯ùv
*·ì ñåÝfòÑZ:'
rü{&=Ô¹Ô¼û(x/ê,t2&Ðxsݦ¢K[b¡3$£ë×6Öú¦&úß
0IMöj(Û?]"¯fGÌ`yzÉ
$=ßfò¹ÑJ¾«dÊ/älÝ, 195.7.137.175, 18
Fri Jan 7 14:13:44 2000: DEBUG: Handling with Radius::AuthLDAP2
Fri Jan 7 14:13:44 2000: DEBUG: Connecting to ldap1.inside.servers, port 389
It only freezes on de normal radius server(s) not on the proxy one
On Fri, Jan 07, 2000 at 10:17:13AM +1100, Hugh Irvine wrote:
>
> Hello Robin -
>
> On Thu, 06 Jan 2000, Robin Gruyters wrote:
> > Hi,
> >
> > I've got some problems with Radiator v2.14.1. It just freezes (most of the time
> > in the evening). I'm using Authby RADIUS and Authby LDAP2 with perl v5.00503 on
> > a FreeBSD system. below you find my config file(s).
> >
>
> Could you please send a trace 4 debug showing where Radiator is stopping? Also
> what LDAP server are you running? And which of the two copies of Radiator is
> the one that stops? If both stop is it because the LDAP request doesn't get
> answered?
>
> > BTW, is it possible to include more dictionaries??!
>
> It is only possible to specify a single dictionary at this time, however it is
> very easy to add definitions to it as the dictionary is only a text file.
>
> hth
>
> 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.
--
Regards,
Robin Gruyters - SYS/B.O.F.H. - [EMAIL PROTECTED] - http://www.phear.nl
RIPE nic-hdl: RG3771-RIPE http://www.ripe.net/cgi-bin/whois?AS9133
WISH Worldwide Websites B.V. PGP key ID DEB8C991
Tel: +31(0)413242500 - Fax: +31(0)413332281 - http://www.wish.net/
-- System Manager / Web Designer / B.O.F.H. ---
"Where do you wanna frag today?"
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) freezing
Hello Robin - On Thu, 06 Jan 2000, Robin Gruyters wrote: > Hi, > > I've got some problems with Radiator v2.14.1. It just freezes (most of the time > in the evening). I'm using Authby RADIUS and Authby LDAP2 with perl v5.00503 on > a FreeBSD system. below you find my config file(s). > Could you please send a trace 4 debug showing where Radiator is stopping? Also what LDAP server are you running? And which of the two copies of Radiator is the one that stops? If both stop is it because the LDAP request doesn't get answered? > BTW, is it possible to include more dictionaries??! It is only possible to specify a single dictionary at this time, however it is very easy to add definitions to it as the dictionary is only a text file. hth 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.
(RADIATOR) freezing
Hi,
I've got some problems with Radiator v2.14.1. It just freezes (most of the time
in the evening). I'm using Authby RADIUS and Authby LDAP2 with perl v5.00503 on
a FreeBSD system. below you find my config file(s).
Radiusproxy:
AuthPort 1812
AcctPort 1813
LogDir /radius/log
DbDir /etc/raddb
LogFile %L/%d%m%Y-e-tel.log
PidFile %L/e-tel.pid
Trace 3
Realm DEFAULT>
Host10.1.0.11
Host10.1.0.10
AuthPort1812
AcctPort1813
Secret
AcctLogFileName %L/details_e-tel-%d%m%Y
AcctLogFileFormat %l %{Acct-Status-Type} \
%{User-Name} %{Framed-IP-Address} %{Calling-Station-Id}
END
Radius config:
AuthPort 1812
AcctPort 1813
LogDir /radius/log
DbDir /etc/raddb
LogFile %L/%d%m%Y-e-tel.log
DictionaryFile %D/dictionary.usr
PidFile %L/e-tel.pid
Trace 3
# Tell Radiator how to talk to the LDAP server
Hostldap4.inside.servers
AuthDN cn=radius,o=WISH, c=NL
BaseDN o=WISH, c=NL
AuthPassword
UsernameAttruid
PasswordAttruserPassword
AddToReply Service-Type = Framed-User,\
Framed-Protocol = PPP,\
Framed-IP-Address = 255.255.255.254,\
Framed-MTU = 1500,\
Primary_DNS_Server= 212.123.129.68, \
Secondary_DNS_Server= 212.123.128.16
-END
BTW, is it possible to include more dictionaries??!
--
Regards,
Robin Gruyters - SYS/B.O.F.H. - [EMAIL PROTECTED] - http://www.phear.nl
RIPE nic-hdl: RG3771-RIPE http://www.ripe.net/cgi-bin/whois?AS9133
WISH Worldwide Websites B.V. PGP key ID DEB8C991
-- System Manager / Web Designer / B.O.F.H. ---
"Where do you wanna frag today?"
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
