Hi everyone, Thanks for the tip about libkqueue. I built and installed the latest version of that library and then was able to compile, install, and run the master branch with freeradius -Xf. However, I am still having difficulty with the configuration for eap-sim. For some reason the eapol_test client says that it can't process a packet? I have attached logs. Thanks, Shane ________________________________ From: Freeradius-Users <freeradius-users-bounces+shaneguan=microsoft.com@lists.freeradius.org> on behalf of Arran Cudbard-Bell <a.cudbardb@freeradius.org> Sent: Wednesday, February 9, 2022 7:08 AM To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Cc: Davut Karabay <davutk@microsoft.com>; Corbin Phipps <corbinphipps@microsoft.com>; Paul Irwin <Irwin.Paul@microsoft.com> Subject: Re: [EXTERNAL] Help in Configuring EAP-SIM [You don't often get email from a.cudbardb@freeradius.org. Learn why this is important at http://aka.ms/LearnAboutSenderIdentification.]
On Feb 9, 2022, at 10:05 AM, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
Signed PGP part
On Feb 9, 2022, at 8:53 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Feb 8, 2022, at 7:36 PM, Shane Guan via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Thanks for your responses. I switched over to master branch but I am unable to start the server. I have attached logs when I invoke "sudo freeradius -Xf" What would be the cause for this?
Error : Network - Failed adding new socket to network event loop: Failed inserting filters for FD 16: EFAULT: Bad address Error : /etc/freeradius/sites-enabled/default[209]: Opening radius I/O interface failed
Hmm... I don't recall seeing that.
My guess is that you're using an older libkqueue? We've put a lot of fixes into the upstream libkqueue repository, but those fixes haven't all made it into the Linux distributions.
I don't remember that issue though, are you sure you're binding to a valid address? Just try wildcard '*'.
Ah, looks like you are. strace would be the next step then if you wanted to figure out why it's happening. I haven't seen this in CI, in our local docker images, or at the sites we have v4 deployed, so it's something specific about your environment.... -Arran