Alan - Thanks for such a rapid and definitive response And of course, now I know what I'm looking for - yes I've found the old config that achieved the same. Apologies for the unnecessary question. Regards Dean Smith -----Original Message----- From: Freeradius-Users <freeradius-users-bounces+dean=eatworms.org.uk@lists.freeradius.org> On Behalf Of Alan DeKok Sent: 22 August 2018 23:53 To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: Files merging with SQL On Aug 22, 2018, at 6:32 PM, Dean Smith <dean@eatworms.org.uk> wrote:
I have updated a Freeradius 2.x system to a fresh 3.0.16 build (new hardware/os from the ground up)
That's good.
On 3.0.16 I am seeing that a request that matches a DEFAULT entry within files (which accepts with assorted tunnel attributes) is also then using the sql module and merging the attributes rather than not processing the SQL if the files section matches.
The two modules are completely independent.
Have I missed a change in behaviour between 2.x and 3.0.x ?
No. v2 behaves the same as v3. I suspect that your configuration changed the default v2 behaviour to skip "sql" if the "files" module matched a user.
In the debug I can see the match in users.then it also calls sql.
Which is what it's supposed to do.
Wed Aug 22 23:22:30 2018 : Debug: (1) files: users: Matched entry DEFAULT at line 1366
Wed Aug 22 23:22:30 2018 : Debug: (1) modsingle[authorize]: returned from files (rlm_files)
Wed Aug 22 23:22:30 2018 : Debug: (1) [files] = ok
Wed Aug 22 23:22:30 2018 : Debug: (1) modsingle[authorize]: calling sql (rlm_sql)
If you don't want it to do that, do: files if (!ok) { sql } See "man unlang" for details. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html