SD.75934 (Customer) asked a question.
I am using the ragent for both regular Radius application and also for the meraki radius integration. I configured the meraki radius integration to use port 1888, and I see that erquests are reahcing the server on that port and that the server is listening on that port. However in the logs I see this:
2024-07-23 03:03:52 UTC [vmokta-radius-agent-01, pool-2-thread-6, radiusRequestId=NpYeEoTDcI, user=X.X, requestType=eap] : INFO - received packet from /10.170.8.30:39599 on local address /0:0:0:0:0:0:0:0:1812. packet id: 1
2024-07-23 03:03:52 UTC [vmokta-radius-agent-01, pool-2-thread-6, radiusRequestId=NpYeEoTDcI, user=dan.shechter, requestType=eap] : INFO - Completed processing. packetId=1, totalProcessingTime=1ms, queueTime=0ms, oktaTime=0ms, httpCode=N/A, result=OK, remoteAddress=N/A
Why does it shows port 1812 and not port 1888 in the log? Also, shouldn't the log show some failure and not just totalProcessingTime of 1ms?
Thanks!
Hello @SD.75934 (Customer) Thank you for posting on our Community page!
This is expected behaviour as per our documentation "The Okta RADIUS Server agent: Delegates authentication to Okta using single-factor authentication (SFA) or multi-factor authentication (MFA). Communicates via UDP, over default port 1812, and supports multiple ports simultaneously."
https://help.okta.com/oie/en-us/content/topics/integrations/radius-best-pract-about.htm
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.