Most likely those ports are opened to communicate with the other RADIUS and/or SQL servers that you are proxying to. Do a netstat to see what addresses that they are connected to. You will probably see that it is the other servers. RADIUS RECEIVES Authentication and Accounting requests on 1645 and 1646 (Or whatever ports you configure in your cfg file), but for it to proxy the info, it will have to open up another connection on another port to connect to the other RADIUS servers. You will probably see that they are connecting to another address on port 1645 or 1646.
-Ronan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jim Liebgott Sent: Thursday, 07 March, 2002 13:21 To: [EMAIL PROTECTED] Subject: (RADIATOR) unknown ports I use Radiator 2.18.3. I noticed that the server binds to three UDP ports that aren't listed in my configuration, and appear to have random port numbers (all greater than 1024). I am using both the authentication and accounting features, and I use <AuthBy RADIUS> to proxy authentication requests. In the current incarnation of the daemon, it is bound to 1645 and 1646 (which is expected because I use those for authentication and accounting) and also 2837, 2789, and 1443. It seems that there are always three ports, but the port numbers change over time (it takes perhaps a day to notice a change). Is this a normal part of a radius server and/or a normal part of Radiator? It seems a bit strange to me that the server is bound to ports that don't appear to be in use. === 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.