Thanks for your answer. Few more doubts on your answer when freeradius run as client and proxying packet. AAA I refer to the server here. When port change happens at freeradius as client for the same AAA ? If freeradius client say suppose bind to 26001 and authentication happens, then why will it change to another port say suppose 26002 or any other port even though first port (26001) is open and serving. Is this because of high load or any thing as such ? Can all threads use the same AAA port when thousands of messages get served or multiple ports opened at the same time ? Thanks, Saurabha On Fri, Jun 16, 2023 at 7:22 PM Alan DeKok <aland@deployingradius.com> wrote:
On Jun 16, 2023, at 9:08 AM, saurabha badhai <saurabha.badhai@gmail.com> wrote:
I see freeradius bind to port 0, and then OS takes care of assigning
right
port, but why freeradius doesn't close the same port programmatically after finish the request?
FreeRADIUS never opens a socket to port 0. It opens a socket, and asks the OS to bind it to a port.
If the OS leaves port 0 open, then there's nothing that FreeRADIUS can do.
Few more questions, 1. Disable proxy ? How to do that, want to close socket fd w/o restarting freeradius ?
You can disable proxying by updating the configuration files. Look for "proxy" in radiusd.conf.
2. Observed sometimes freeradius running as a client, open 2 different proxy ports simultaneously to the same AAA ? When is this possible ?
It's always possible. It works automatically. You don't have to manually assign proxy ports.
That's why FreeRADIUS uses the special port 0. As I said in my previous message, it's a signal to the OS to pick a random unused port.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html