Re: (RADIATOR) Warning: prerequisite MD5 0 not found
On Thu, 25 Nov 1999, dave wrote: Thanks very much for the reply. I did, indeed, follow the steps perl Makefile.PL make make test make install originally for MD5. However, it appears now that I may have had a permissions problem. Although the "make test" succeeded, the unpacked files of MD5 had obscure file ownerships left over from the tar archive. So when I redid the steps per your suggestion I set all the ownerships to "root" first, and this time Radiator compiled fine. Thanks very much. Sometimes you just need a sanity check. A word of advice for all: When installing Perl modules, make sure you do the first five steps: gunzip blah.tar.gz tar -xf blah.tar perl Makefile.PL make make test *NOT* as root. This will keep malicious programmers from sending bum modules that wipe out half your filesystem, and will also avoid the permission problems you were having. Only change to root when you are at the final step: make install. Hope this helps! -- Dave Lloyd === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) logging turned on
See: http://www.open.com.au/radiator/install.html It says: "Run radiator with perl radiusd -config_file goodies/simple.cfg. This runs Radiator with logging turned on (so you can see whats happening), and authenticates all requests from the file users. You will see some messages, followed by INFO: Server started. Radiator is now waiting for requests to arrive." However, I get *no* messages at all either to the console or the local terminal. - I'm using the stock "simple.cfg", which has "LogStdout" - All "make test" tests passed "ok" - The authentication test succeeds regardless: web# perl radpwtst -user fred -password fred sending Access-Request... OK sending Accounting-Request Start... OK sending Accounting-Request Stop... OK - "detail" contains accounting records But I don't have the logging information described. What do I need to do to get the logging information to appear? I've tried various things, such as: perl radiusd -config_file goodies/simple.cfg -foreground -log_stdout but I'm just guessing. Thanks in advance for your help! Dave === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Microsoft SQL 7 and Linux
Has anyone successfully connected their Radiator running on a Linux box to Microsoft SQL 7. If you have would you mind sharing the details. We are running SQL 6.5 and have no problems with the Sybase drivers but we are thinking of upgrading to 7. Greg Kornatowsky ZooLink === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Microsoft SQL 7 and Linux
On Mon, Nov 29, 1999 at 02:36:55PM -0800, Greg Kornatowsky wrote: Has anyone successfully connected their Radiator running on a Linux box to Microsoft SQL 7. If you have would you mind sharing the details. We are running SQL 6.5 and have no problems with the Sybase drivers but we are thinking of upgrading to 7. 6.5-7 breaks the Sybase libraries. Microsoft has recognised this as a bug (ie lost sales) and issue a patch to make it work again. SYBASE CT-Library Clients Cannot Connect to SQL Server --- The information in this article applies to: - Microsoft SQL Server version 7.0 --- BUG #: 55964 (SQLBUG_70) SYMPTOMS SYBASE clients using CT-Library based on Tabular Data Stream (TDS) 5.0 (including Open Client 10.0.4 and 11.1.1) cannot connect to Microsoft SQL Server 7.0. These clients may encounter one of the following SYBASE CT-Library errors reported by SYBASE ISQL.EXE: CT-LIBRARY error: ct_connect(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect CT-LIBRARY error: ct_connect(): protocol specific layer: internal Client Library error: There is a tds state machine error. An illegal tds token sequence was received. The Microsoft SQL Server 7.0 errorlog reports the following error: ods Error: 17832, Severity: 18, State: 7 ods Connection opened but invalid login packet(s) sent. Connection closed.. RESOLUTION == A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.asp The English version of this fix should have the following file attributes or later: Version File name Platform - 7.00.723 s70723i.exe Intel s70723a.exe Alpha NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files. STATUS == Microsoft has confirmed this to be a problem in SQL Server version 7.0. MORE INFORMATION Microsoft SQL Server 6.5 and 7.0 are designed for backward compatibility to support TDS 4.2 clients, including TDS 4.2 clients from SYBASE. However, some of Microsoft's customers have traditionally been able to connect their SYBASE TDS 5.0 clients and perform basic queries against a Microsoft SQL 6.5 server. This configuration is not supported by Microsoft, although some customers have been using it. Some changes were made in SQL 7.0 to provide more TDS protocol checks that prevented these SYBASE TDS 5.0 clients from making the same connection as in SQL 6.5. Therefore, a change has been introduced in SQL 7.0 that allows SYBASE TDS 5.0 clients to connect. However, this does not mean the configuration is officially supported by Microsoft. TDS 4.2 is the only level of compatibility that is supported for SYBASE TDS based clients. TDS 5.0 is a SYBASE specification and it is not supported by Microsoft. NOTE: Microsoft will not include these changes in future versions of Microsoft SQL Server. These changes will remain during the lifetime of the 7.0 product, including service packs. Limited testing has been performed by Microsoft regarding the functionality of SYBASE TDS 5.0 clients with this change. Only basic connectivity is ensured. Anyone requiring this functionality should seek a different solution for connecting SYBASE clients to Microsoft SQL Server such as using an ODBC driver or OLE-DB provider. Keywords : kbSQLServ700bug Version : winnt:7.0 Platform : winnt Issue type: kbbug Solution Type : kbfix THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL
(RADIATOR) Getting logon failures
Hi all, Is there a way to capture logon failures in Radiator? We are using AuthBy Emerald and have the log going to radlog table. I have tried setting trace values but none seem to trap logon failures. Is this possible? Thanks Ray Carpenter === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Startup
Hello Christopher - On Mon, 29 Nov 1999, Christopher Andersson wrote: %_Good morning! When I start radiusd, it takes over the terminal window. It sort of locks up, even though it works just fine when given requests from an other window. This happens both on NT4 and RedHat Linux. This has the effect that I cannot start it using the restartWrapper from my rc.local file. (The Linux box simply halts in the boot) My config-file contains nothing strange, and this happens when I use goodies/simple.cfg as well. Does anyone know how to solve this? I need to start Radiator at boot time, and I would like to use restartWrapper to make it restart in case anything goes wrong. This sounds most peculiar - can you send us a copy of your configuration file (no secrets) together with a copy of the logfile? 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.
Re: (RADIATOR) Getting logon failures
Hello Ray - On Tue, 30 Nov 1999, Ray Carpenter wrote: Hi all, Is there a way to capture logon failures in Radiator? We are using AuthBy Emerald and have the log going to radlog table. I have tried setting trace values but none seem to trap logon failures. Is this possible? You can use PasswordLogFileName. See section 6.13.7, 6.13.8 and 15.6 in the Radiator 2.14.1 reference manual. This has also been discussed on the list and I seem to remember there were some useful comments made - you might check the mailist archive site: http://www.thesite.com.au/~radiator/ 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.
Re: (RADIATOR) logging turned on
Hello Dave - On Tue, 30 Nov 1999, Dave Kitabjian wrote: See: http://www.open.com.au/radiator/install.html It says: "Run radiator with perl radiusd -config_file goodies/simple.cfg. This runs Radiator with logging turned on (so you can see whats happening), and authenticates all requests from the file users. You will see some messages, followed by INFO: Server started. Radiator is now waiting for requests to arrive." However, I get *no* messages at all either to the console or the local terminal. - I'm using the stock "simple.cfg", which has "LogStdout" - All "make test" tests passed "ok" - The authentication test succeeds regardless: web# perl radpwtst -user fred -password fred sending Access-Request... OK sending Accounting-Request Start... OK sending Accounting-Request Stop... OK - "detail" contains accounting records Could you tell me what platform you are running on? and which version of Radiator? 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.
SV: (RADIATOR) Startup
I'm sending a copy of a configuration file that produces this "lock up". It doesn't matter, however, which one I use; there's allways the same result. The logfile (also enclosed) doesn't give me any clues. Anyway, here they are. Thanks /chris Original Message - From: Hugh Irvine [EMAIL PROTECTED] To: Christopher Andersson [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, November 29, 1999 11:20 PM Subject: Re: (RADIATOR) Startup Hello Christopher - On Mon, 29 Nov 1999, Christopher Andersson wrote: %_Good morning! When I start radiusd, it takes over the terminal window. It sort of locks up, even though it works just fine when given requests from an other window. This happens both on NT4 and RedHat Linux. This has the effect that I cannot start it using the restartWrapper from my rc.local file. (The Linux box simply halts in the boot) My config-file contains nothing strange, and this happens when I use goodies/simple.cfg as well. Does anyone know how to solve this? I need to start Radiator at boot time, and I would like to use restartWrapper to make it restart in case anything goes wrong. This sounds most peculiar - can you send us a copy of your configuration file (no secrets) together with a copy of the logfile? 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 simple.cfg logfile
