Configure Freeradius Server on a Synology NAS to Authenticate Cisco RV340 Users
vladlevin at geo-logic.com
Wed Sep 4 03:22:19 CEST 2019
1. I was unable to find any vendor documention that would explain how to make it work. Both, Synology and Cisco, development level technical support couldn't help either and referred me to Freeradius or "other online sources".
2. I am not familiar with RADIUS server environment nor am I a programmer, so even after reading the documentation I am still not sure which file(s) to input the code into or what the correct code should be.
3. I am not looking for a lecture (though, if that's what gets you off, I am happy to provide the opportunity) nor for other people to do my work for me (I've spent many hours trying to get it to work with nothing to show for it), but was rather hoping that someone has already solved that problem and was willing to share the solution.
4. The group names are stored in the local user database of the Synology NAS; its RADIUS server, which is essentially Freeradius, is configured via GUI to use that database.
5. If I knew what additional information is needed, I'd be glad to provide it, if I can.
From: Freeradius-Users [mailto:freeradius-users-bounces+vladlevin=geo-logic.com at lists.freeradius.org] On Behalf Of Alan DeKok
Sent: Tuesday, September 03, 2019 1:49 PM
To: FreeRadius users mailing list
Subject: ++++SPAM++++ Re: Configure Freeradius Server on a Synology NAS to Authenticate Cisco RV340 Users
On Sep 3, 2019, at 4:39 PM, Levin, Vladimir <vladlevin at geo-logic.com> wrote:
> Could anyone provide instructions on how to configure Freeradius server on a Synology NAS to authenticate Cisco RV340 users? Specifically, I need to configure the server to send radius attribute class 25 with user group name back to the client (RV340).
We don't have documentation for commercial vendors here. Please read *their* documentation to see what they accept.
If you want to send a Class attribute back to the NAS, read "man unlang". It contains complete descriptions of how to send attributes. Plus, read sites-available/default. There are lots of examples there.
i.e. *read* the documentation instead of asking other people to do your work for you. If you can't be bothered to read the documentation and follow it, we can't be bothered, too.
And *where* is the group name stored? FreeRADIUS isn't a database. We don't store groups. So it has to come from somewhere.
How can we help you if you ask vague questions, and don't give us enough information?
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
More information about the Freeradius-Users