Right so I would be just editing some sql query files.. The reason I’m asking is because I would not just edit them right away as I might break something. I would be editing this file right? —> /etc/freeradius/sql/mysql/dialup.conf
Thought to be honest, it's probably best to just put those remote IDs into an SQL table, and just use a SELECT to match it.
Good idea. Met vriendelijke groet \ With kind regards, Marijn van Gool NOC Network Engineer noc@comsave.com <mailto:noc@comave.com> +31 88 999 5555 marijn.vangool@comsave.com <mailto:marijn.vangool@comsave.com> www.comsave.nl <http://www.comsave.nl/>
On 11 Apr 2018, at 17:08, Alan DeKok <aland@deployingradius.com> wrote:
On Apr 11, 2018, at 10:53 AM, Marijn van Gool <marijn.vangool@comsave.com> wrote:
We’ve been using freeradius for a couple of years now and have expanded to connectiong users via PPPoE. Currently we give our customers a username and password whether they are authorized to connect. We want to change this to ADSL-Agent-Remote-Id, an attribute we see in the Access-Request packet.
That should be simple...
if (ADSL-Agent-Remote-Id == ...) { update control { Auth-Type := Accept } }
Thought to be honest, it's probably best to just put those remote IDs into an SQL table, and just use a SELECT to match it.
if ("%{sql:SELECT agent_remote_id FROM table WHERE agent_remote_id = %{ADSL-Agent-Remote-Id}}" != "") { update control { Auth-Type := Accept } }
You'll have to edit the SQL query, of course.
We are using this version of freeradius:
root@server1:~# freeradius -v freeradius: FreeRADIUS Version 2.1.12, for host x86_64-pc-linux-gnu, built on Aug 26 2015 at 14:47:03
We will upgrade to a version beyond 3.x.x soon.
You should be able to upgrade to 2.2.10 without any configuration changes. That version has many, many, fixes over 2.1.12.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html