matt Penner

Realized I posted on general discussion when this should instead be on the help forum: I have my radiusdesk setup using NAS subnets (i.e. westOffice 192.168.1.0/24) for login authentication. I have a few realms, with users delegated realms depending where they are. I would like it so that only users in westOffice can log in to the westOffice NAS entry, so what I did was instead of "all realms" I set the 192.168.1.0/24 NAS entry's realm to be "West Office" I have two users, "user1" has their realm...

Update on this, I am currently looking at using huntgroups rather than realms as I was not able to get that working, however I am also having issues with huntgroups. In the huntGroups file I added "mattTest NAS-IP-Address ==192.168.1.9" In radiusdesk in the users private attributes I set the free radius internal attribute Huntgroup-Name to match. the huntgroup file seems to indicate that if a name is specified then the huntgroup will be looked up in the file but that does not appear to be the case,...

I have my radiusdesk setup using NAS subnets (i.e. westOffice 192.168.1.0/24) for login authentication. I have a few realms, with users delegated realms depending where they are. I would like it so that only users in westOffice can log in to the westOffice NAS entry, so what I did was instead of "all realms" I set the 192.168.1.0/24 NAS entry's realm to be "West Office" I have two users, "user1" has their realm set to "West Office" and "user2" has their realm set to "East Office" How I would expect...

I can confirm I have the same issue with 2022-B. All of the functions and menu sections you had mentioned are missing from my GUI as well. Have no version number, and am also missing the settings in admin, as well as the missing icon in task bar.

Looks like I am missing all the same things as in your examples for 2022-B. Have no version number, and am also missing the settings in admin, as well as the missing icon in task bar.

Hey, this is now resolved! I feel quite silly but a restart fixed the issue, I guess freeradius does an initial read of the NAS entries on start without refreshing during changes. I was sure i had done a restart before but here we are. Thanks for your help here!

My NAS entry already had the appropriate realms included. Realms was not configured to add suffix but I tested with and without that and there is no difference, even when creating a new user to test. Log still states invalid user. Attached is screenshot showing it working when I had created a client but stopping once attempting to use NAS. Your help is much appreciated

I am being given the error that login is incorrect, however when I create the client for the IP bypassing the NAS, the same user and password works. In radacct/ I am not seeing the IP of the device I am attempting to login to. The NAS IP I have set in radius desk is currently X.X.X.0/24, and I am attempting to login on X.X.X.9, so it should be within the appropriate range to showup in the NAS I use the username mattp which works fine on a created client. Is it possibly a realm option that I need...