Hi Alan, I have confirmed from the team and there's nothing blocking freeradius to reach the WLC. The WLC is open to everything in the organisation. The packets are reaching freeradius as I can see an "Access-Request" on FreeRadius (from radsniff and tcpdump). Attaching a screenshot for reference. [image: image.png] However, freeradius -X is still here: [image: image.png] Here's the client.conf [image: image.png] Also, could the certificate cause any issues? Thanks for your help. Regards, Deepansha Gaur On Thu, Nov 30, 2023 at 10:16 AM Alan DeKok <aland@deployingradius.com> wrote:
On Nov 30, 2023, at 12:10 PM, Deepansha Gaur <dgaur@ualberta.ca> wrote:
"freeradius -X" and "/var/log/freeradius/radius.log" show nothing. Thanks.
Then the packets aren't reaching FreeRADIUS.
This isn't a FreeRADIUS problem. Either the routing is broken and the packets aren't reaching the server, or there's a firewall in place which blocks the packets, or there's something like selinux which is blocking the packet.
You can only do FreeRADIUS debugging if FreeRADIUS sees packets. If it doesn't see packets, it is (by definition) not an issue with FreeRADIUS.
Fix the network / firewall / whatever so that the packets reach FreeRADIUS.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
