We are currently implementing a couple of Radiator servers in our NOC and we will be using MSSQL stored proceedures to do both authentication lookups and the storing of accounting information.
According to the Radiator FAQ, FreeTDS is not the recommended choice for obveious reasons. I'm curious as to how many people may be using MSSQL for their backend but using Unix (in my case FreeBSD 4.4) as the RADIUS server platform. Right now my choices seem to be limited to DBI proxy or FreeTDS. I have FreeTDS working for web applications via PERL, etc. Just wondering how stable FreeTDS would perform in a very active RADIUS server environment. The one quirk I've always noticed is that if the connection breaks between FreeTDS and your MSSQL server, FreeTDS mod seems to bomb out the whole PERL script running. Any work arounds or suggestions? -- Robert Blayzor, BOFH INOC, LLC [EMAIL PROTECTED] "It only makes sense that every facet of our daily lives should depend upon the position of celestial bodies hundreds of millions of miles away." - Calvin and Hobbes === 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.