Yes customer deployed load balancer based on the source port map to specific AAA server, Observed source port change for an ongoing authentication session, access-request is initiated from a different port after few access-challenges causing the load balancer to send the request to a different AAA and then get rejected. Is this behavior proper and expected, source port change for an ongoing authentication session ? On Fri, Jun 16, 2023 at 9:58 PM Alan DeKok <aland@deployingradius.com> wrote:
On Jun 16, 2023, at 12:08 PM, Saurabh <saurabh24sbp@gmail.com> wrote:
We deployed freeradius as client which receives radius message from UE/AP and proxy that to external AAA for auth and acct. You think it's 100 messages per second.
That's fine.
Facing one customer issue where even though udp socket is open and serving request to a AAA on a source port, observed a new port is open to same AAA.
Is that causing a problem?
My doubt is why a new socket with a new port to same AAA even if there is a one already. This behavior seen sometime not always.
Why not just say that at the start, instead of asking a bunch of unrelated questions?
This is how RADIUS works. It's fine.
i.e. If it's working, don't waste your time worrying about it.
Do the log messages contain an error?
No? Then it's fine. Why worry when there's no error?
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html