We all know that the RADIUS protocol (being based on UDP) can be unreliable, especially in the face of saturated or unreliable links from your POP to your radius server, so we wonder if this is a good idea: 1. Invent a simple way to encapsulate RADIUS requests on a TCP connection, and build a simple app that will receive UDP Radius, and proxy it out on a TCP connection. Modify Radiator so it can received these proxied requests by TCP 2. Run the simple app at your POP, connecting you your central radius server(s) back in the core The theory is that using TCP allows the apps to get a better handle on poor network connections or down/unreachable radius servers than the simple UDP protocol. Does that seem like a good idea to anyone? Thoughts, feedback, flames solicited. 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 === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
