Discussion:
Different databases with single freeradius
Emrah Yıldırım
2018-02-06 20:47:18 UTC
Permalink
Hi,

http://freeradius.1045715.n5.nabble.com/Reg-Different-databases-with-single-frerradius-td5713985.html

I'm asking for your help with the subject. Would you please provide more
open and more concrete information? I've separated the
databases. I present the same problem... The Radacct table is visible to
everyone. Please help.

Regards
-
List info/subscribe/unsubscribe? See http://www.freeradi
Alan DeKok
2018-02-06 20:57:34 UTC
Permalink
On Feb 6, 2018, at 3:47 PM, Emrah Yıldırım <***@gmail.com> wrote:
>
> http://freeradius.1045715.n5.nabble.com/Reg-Different-databases-with-single-frerradius-td5713985.html
>
> I'm asking for your help with the subject. Would you please provide more
> open and more concrete information? I've separated the
> databases. I present the same problem... The Radacct table is visible to
> everyone.

What does that mean?

If you want to control who can read a table in SQL, consult the documentation for your SQL server.

Alan DeKok.


-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users
Emrah Yıldırım
2018-02-07 04:56:59 UTC
Permalink
Are you sure
you're looking at Link? This topic is related to Freeradius... I have
separated databases with SQL instance. However, separate hosts in both NAS
tables
Although I do, I see the same data in the RADACCT table of both databases.
Please give me a solution


6 Şub 2018 23:57 tarihinde "Alan DeKok" <***@deployingradius.com> yazdı:

On Feb 6, 2018, at 3:47 PM, Emrah Yıldırım <***@gmail.com> wrote:
>
> http://freeradius.1045715.n5.nabble.com/Reg-Different-
databases-with-single-frerradius-td5713985.html
>
> I'm asking for your help with the subject. Would you please provide more
> open and more concrete information? I've separated the
> databases. I present the same problem... The Radacct table is visible to
> everyone.

What does that mean?

If you want to control who can read a table in SQL, consult the
documentation for your SQL server.

Alan DeKok.


-
List info/subscribe/unsubscribe? See http://www.freeradius.org/
list/users.html
-
List info/subscribe/unsubscribe? See http://ww
Nathan Ward
2018-02-07 08:42:02 UTC
Permalink
> On 7/02/2018, at 5:56 PM, Emrah Yıldırım <***@gmail.com> wrote:
>
> Are you sure
> you're looking at Link? This topic is related to Freeradius... I have
> separated databases with SQL instance. However, separate hosts in both NAS
> tables
> Although I do, I see the same data in the RADACCT table of both databases.
> Please give me a solution

Almost certainly, you are calling both instances of the SQL module rather than just one. If you want accounting in only one database, you need to call only one module instance, as described in the link you refer to.

Please read this page before going further, it will tell you how to ask for help in a way that someone here can help you: http://wiki.freeradius.org/guide/Users-Mailing-List <http://wiki.freeradius.org/guide/Users-Mailing-List>

Also, read http://wiki.freeradius.org/guide/radiusd-X <http://wiki.freeradius.org/guide/radiusd-X>, and see if you can see where the problem is - I suspect you will be able to.

--
Nathan Ward

-
List info/subscribe/un
Alan DeKok
2018-02-07 14:20:52 UTC
Permalink
On Feb 6, 2018, at 11:56 PM, Emrah Yıldırım <***@gmail.com> wrote:
>
> Are you sure
> you're looking at Link?

You need to learn how to ask good questions. Your first question, and the link, are vague and content-free.

If you ask a bad question, you will get a bad answer.


> This topic is related to Freeradius... I have
> separated databases with SQL instance.

Does this mean you have two SQL instances configured in FreeRADIUS?

> However, separate hosts in both NAS
> tables
> Although I do, I see the same data in the RADACCT table of both databases.

You've configured the server to use both SQL instances for all users. This is wrong.

You need to call the right instance for the right user:

if (user is from system A) {
sql1
}
else {
sql2
}

Of course, that won't work as-is. Because you have given *zero* information about the usernames, SQL instance names, etc

If you give more information, you get better answers.

Alan DeKok.


-
List info/subscribe/unsubscribe? See h
Sergio NNX
2018-02-07 20:09:25 UTC
Permalink
Ciao.

We are upgrading from FR 2.0.x to 3.0.16 slowly and gradually.
We use ODBC to connect M$SQL Server.
We are unsure about how to set it up in v3.0.x.

/etc/raddb/mods-enabled/sql file

sql {
# The sub-module to use to execute queries. This should match
# the database you're attempting to connect to.
#
# * rlm_sql_mysql
# * rlm_sql_mssql
# * rlm_sql_oracle
# * rlm_sql_postgresql
# * rlm_sql_sqlite
# * rlm_sql_null (log queries to disk)
#
driver = "rlm_sql_unixodbc"

...
...
...
# The dialect of SQL you want to use, this should usually match
# the driver you selected above.
#
# If you're using rlm_sql_null, then it should be the type of
# database the logged queries are going to be executed against.
dialect = "unixodbc"

# Connection info:
#
server = "MSSQLTestServer"
# port = 3306
login = "testsqluser"
password = "xxxxxxx"
...
...


Should the dialect be the same as the driver (as suggested in the config file) or ....?

Thanks in advance.


radiusd -X output:

FreeRADIUS Version 3.0.16
Copyright (C) 1999-2017 The FreeRADIUS server project and contributors
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE
You may redistribute copies of FreeRADIUS under the terms of the
GNU General Public License
For more information about these matters, see the file named COPYRIGHT
Starting - reading configuration files ...
including dictionary file \freeradius-server-3.0.16\share\freeradius/dictionary
including dictionary file \freeradius-server-3.0.16\share\freeradius/dictionary.dhcp
including dictionary file \freeradius-server-3.0.16\share\freeradius/dictionary.vqp
including configuration file \freeradius-server-3.0.16\etc\raddb/radiusd.conf
including configuration file \freeradius-server-3.0.16\etc\raddb/proxy.conf
including configuration file \freeradius-server-3.0.16\etc\raddb/clients.conf
including files in directory \freeradius-server-3.0.16\etc\raddb/mods-enabled/
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/always
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/attr_filter
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/chap
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/date
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/detail
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/digest
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/eap
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/echo
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/exec
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/expiration
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/expr
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/files
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/logintime
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/mschap
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/pap
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/preprocess
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/radutmp
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/realm
including configuration file \freeradius-server-3.0.16\etc\raddb/mods-enabled/sql
including configuration file \freeradius-server-3.0.16\etc/raddb/mods-config/sql/main/unixodbc/queries.conf
Unable to open file "\freeradius-server-3.0.16\etc/raddb/mods-config/sql/main/unixodbc/queries.conf": No such file or directory
Errors reading or parsing \freeradius-server-3.0.16\etc\raddb/radiusd.conf

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/l
Alan DeKok
2018-02-07 20:21:36 UTC
Permalink
On Feb 7, 2018, at 3:09 PM, Sergio NNX <***@hotmail.com> wrote:
> We are upgrading from FR 2.0.x to 3.0.16 slowly and gradually.
> We use ODBC to connect M$SQL Server.
> We are unsure about how to set it up in v3.0.x.

> Should the dialect be the same as the driver (as suggested in the config file) or ....?

Usually, yes.
>
> including configuration file \freeradius-server-3.0.16\etc/raddb/mods-config/sql/main/unixodbc/queries.conf
> Unable to open file "\freeradius-server-3.0.16\etc/raddb/mods-config/sql/main/unixodbc/queries.conf": No such file or directory
> Errors reading or parsing \freeradius-server-3.0.16\etc\raddb/radiusd.conf

In this case, you should use "dialect = mssql"

Alan DeKok.


-
List info/subscribe/u
Sergio NNX
2018-02-07 20:11:39 UTC
Permalink
Hi.

We have noticed a few sort of modules showing up in the debug log.
However, we are unable to locate them anywhere. They do not appear in any configuration file.
So the question is: are those modules external modules, intrinsic (or core) ones or ...... ?
Are they v3 specific?

- proto_auth
- proto_acct
- proto_status

Thanks in advance.


Debug output

Wed Feb 07 12:00:19 2018 : Debug: Server was built with:
Wed Feb 07 12:00:19 2018 : Debug: accounting : yes
Wed Feb 07 12:00:19 2018 : Debug: authentication : yes
Wed Feb 07 12:00:19 2018 : Debug: ascend-binary-attributes : yes
Wed Feb 07 12:00:19 2018 : Debug: coa : yes
Wed Feb 07 12:00:19 2018 : Debug: control-socket : no
Wed Feb 07 12:00:19 2018 : Debug: detail : yes
Wed Feb 07 12:00:19 2018 : Debug: dhcp : yes
Wed Feb 07 12:00:19 2018 : Debug: dynamic-clients : yes
Wed Feb 07 12:00:19 2018 : Debug: osfc2 : no
Wed Feb 07 12:00:19 2018 : Debug: proxy : yes
Wed Feb 07 12:00:19 2018 : Debug: regex-pcre : yes
Wed Feb 07 12:00:19 2018 : Debug: regex-posix : no
Wed Feb 07 12:00:19 2018 : Debug: regex-posix-extended : no
Wed Feb 07 12:00:19 2018 : Debug: session-management : yes
Wed Feb 07 12:00:19 2018 : Debug: stats : yes
Wed Feb 07 12:00:19 2018 : Debug: tcp : yes
Wed Feb 07 12:00:19 2018 : Debug: threads : yes
Wed Feb 07 12:00:19 2018 : Debug: tls : yes
Wed Feb 07 12:00:19 2018 : Debug: unlang : yes
Wed Feb 07 12:00:19 2018 : Debug: vmps : yes
Wed Feb 07 12:00:19 2018 : Debug: developer : no
Wed Feb 07 12:00:19 2018 : Debug: IPv6 : yes
Wed Feb 07 12:00:19 2018 : Debug: Server core libs:
Wed Feb 07 12:00:19 2018 : Debug: freeradius-server : 3.0.16
Wed Feb 07 12:00:19 2018 : Debug: talloc : 2.1.*
Wed Feb 07 12:00:19 2018 : Debug: ssl : 1.1.1 dev
Wed Feb 07 12:00:19 2018 : Debug: pcre : 8.40 2017-01-11
Wed Feb 07 12:00:19 2018 : Debug: pthreads : 2.10.0
Wed Feb 07 12:00:19 2018 : Debug: odbc : 2.3.4
Wed Feb 07 12:00:19 2018 : Debug: Endianness:
Wed Feb 07 12:00:19 2018 : Debug: little
Wed Feb 07 12:00:19 2018 : Debug: Compilation flags:
Wed Feb 07 12:00:19 2018 : Debug:
Wed Feb 07 12:00:19 2018 : Info: FreeRADIUS Version 3.0.16
Wed Feb 07 12:00:19 2018 : Info: Copyright (C) 1999-2017 The FreeRADIUS server project and contributors
Wed Feb 07 12:00:19 2018 : Info: There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
Wed Feb 07 12:00:19 2018 : Info: PARTICULAR PURPOSE
Wed Feb 07 12:00:19 2018 : Info: You may redistribute copies of FreeRADIUS under the terms of the
Wed Feb 07 12:00:19 2018 : Info: GNU General Public License
Wed Feb 07 12:00:19 2018 : Info: For more information about these matters, see the file named COPYRIGHT
Wed Feb 07 12:00:19 2018 : Info: Starting - reading configuration files ...

<snip>
<snip>

Wed Feb 07 12:00:20 2018 : Debug: } # server status
Wed Feb 07 12:00:20 2018 : Debug: radiusd: #### Opening IP addresses and Ports ####
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_auth with path: \freeradius-server-3.0.16/lib/proto_auth
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_auth failed: "\freeradius-server-3.0.16\lib\proto_auth": The specified module could not be found. - No such file or directory
Wed Feb 07 12:00:20 2018 : Debug: Loading library using linker search path(s)
Wed Feb 07 12:00:20 2018 : Debug: Defaults : \freeradius-server-3.0.16\lib
Wed Feb 07 12:00:20 2018 : Debug: Failed with error: "proto_auth": The specified module could not be found.
Wed Feb 07 12:00:20 2018 : Debug: listen {
Wed Feb 07 12:00:20 2018 : Debug: type = "auth"
Wed Feb 07 12:00:20 2018 : Debug: ipaddr = *
Wed Feb 07 12:00:20 2018 : Debug: port = 0
Wed Feb 07 12:00:20 2018 : Debug: limit {
Wed Feb 07 12:00:20 2018 : Debug: max_connections = 16
Wed Feb 07 12:00:20 2018 : Debug: lifetime = 0
Wed Feb 07 12:00:20 2018 : Debug: idle_timeout = 30
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_acct with path: \freeradius-server-3.0.16/lib/proto_acct
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_acct failed: "\freeradius-server-3.0.16\lib\proto_acct": The specified module could not be found. - No such file or directory
Wed Feb 07 12:00:20 2018 : Debug: Loading library using linker search path(s)
Wed Feb 07 12:00:20 2018 : Debug: Defaults : \freeradius-server-3.0.16\lib
Wed Feb 07 12:00:20 2018 : Debug: Failed with error: "proto_acct": The specified module could not be found.
Wed Feb 07 12:00:20 2018 : Debug: listen {
Wed Feb 07 12:00:20 2018 : Debug: type = "acct"
Wed Feb 07 12:00:20 2018 : Debug: ipaddr = *
Wed Feb 07 12:00:20 2018 : Debug: port = 0
Wed Feb 07 12:00:20 2018 : Debug: limit {
Wed Feb 07 12:00:20 2018 : Debug: max_connections = 16
Wed Feb 07 12:00:20 2018 : Debug: lifetime = 0
Wed Feb 07 12:00:20 2018 : Debug: idle_timeout = 30
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_auth with path: \freeradius-server-3.0.16/lib/proto_auth
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_auth failed: "\freeradius-server-3.0.16\lib\proto_auth": The specified module could not be found. - No such file or directory
Wed Feb 07 12:00:20 2018 : Debug: Loading library using linker search path(s)
Wed Feb 07 12:00:20 2018 : Debug: Defaults : \freeradius-server-3.0.16\lib
Wed Feb 07 12:00:20 2018 : Debug: Failed with error: "proto_auth": The specified module could not be found.
Wed Feb 07 12:00:20 2018 : Debug: listen {
Wed Feb 07 12:00:20 2018 : Debug: type = "auth"
Wed Feb 07 12:00:20 2018 : Debug: ipv6addr = ::
Wed Feb 07 12:00:20 2018 : Debug: port = 0
Wed Feb 07 12:00:20 2018 : Debug: limit {
Wed Feb 07 12:00:20 2018 : Debug: max_connections = 16
Wed Feb 07 12:00:20 2018 : Debug: lifetime = 0
Wed Feb 07 12:00:20 2018 : Debug: idle_timeout = 30
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_acct with path: \freeradius-server-3.0.16/lib/proto_acct
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_acct failed: "\freeradius-server-3.0.16\lib\proto_acct": The specified module could not be found. - No such file or directory
Wed Feb 07 12:00:20 2018 : Debug: Loading library using linker search path(s)
Wed Feb 07 12:00:20 2018 : Debug: Defaults : \freeradius-server-3.0.16\lib
Wed Feb 07 12:00:20 2018 : Debug: Failed with error: "proto_acct": The specified module could not be found.
Wed Feb 07 12:00:20 2018 : Debug: listen {
Wed Feb 07 12:00:20 2018 : Debug: type = "acct"
Wed Feb 07 12:00:20 2018 : Debug: ipv6addr = ::
Wed Feb 07 12:00:20 2018 : Debug: port = 0
Wed Feb 07 12:00:20 2018 : Debug: limit {
Wed Feb 07 12:00:20 2018 : Debug: max_connections = 16
Wed Feb 07 12:00:20 2018 : Debug: lifetime = 0
Wed Feb 07 12:00:20 2018 : Debug: idle_timeout = 30
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_auth with path: \freeradius-server-3.0.16/lib/proto_auth
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_auth failed: "\freeradius-server-3.0.16\lib\proto_auth": The specified module could not be found. - No such file or directory
Wed Feb 07 12:00:20 2018 : Debug: Loading library using linker search path(s)
Wed Feb 07 12:00:20 2018 : Debug: Defaults : \freeradius-server-3.0.16\lib
Wed Feb 07 12:00:20 2018 : Debug: Failed with error: "proto_auth": The specified module could not be found.
Wed Feb 07 12:00:20 2018 : Debug: listen {
Wed Feb 07 12:00:20 2018 : Debug: type = "auth"
Wed Feb 07 12:00:20 2018 : Debug: ipaddr = 192.168.1.4
Wed Feb 07 12:00:20 2018 : Debug: port = 1821
Wed Feb 07 12:00:20 2018 : Debug: client 192.0.2.9 {
Wed Feb 07 12:00:20 2018 : Debug: require_message_authenticator = no
Wed Feb 07 12:00:20 2018 : Debug: secret = "testing123"
Wed Feb 07 12:00:20 2018 : Debug: shortname = "example-client"
Wed Feb 07 12:00:20 2018 : Debug: limit {
Wed Feb 07 12:00:20 2018 : Debug: max_connections = 16
Wed Feb 07 12:00:20 2018 : Debug: lifetime = 0
Wed Feb 07 12:00:20 2018 : Debug: idle_timeout = 30
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Warning: No 'ipaddr' or 'ipv4addr' or 'ipv6addr' field found in client 192.0.2.9. Please fix your configuration
Wed Feb 07 12:00:20 2018 : Warning: Support for old-style clients will be removed in a future release
Wed Feb 07 12:00:20 2018 : Debug: Adding client 192.0.2.9/32 (192.0.2.9) to prefix tree 32
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_auth with path: \freeradius-server-3.0.16/lib/proto_auth
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_auth failed: "\freeradius-server-3.0.16\lib\proto_auth": The specified module could not be found. - No such file or directory
Wed Feb 07 12:00:20 2018 : Debug: Loading library using linker search path(s)
Wed Feb 07 12:00:20 2018 : Debug: Defaults : \freeradius-server-3.0.16\lib
Wed Feb 07 12:00:20 2018 : Debug: Failed with error: "proto_auth": The specified module could not be found.
Wed Feb 07 12:00:20 2018 : Debug: listen {
Wed Feb 07 12:00:20 2018 : Debug: type = "auth"
Wed Feb 07 12:00:20 2018 : Debug: ipaddr = 127.0.0.1
Wed Feb 07 12:00:20 2018 : Debug: port = 18120
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_status with path: \freeradius-server-3.0.16/lib/proto_status
Wed Feb 07 12:00:20 2018 : Debug: Loading proto_status failed: "\freeradius-server-3.0.16\lib\proto_status": The specified module could not be found. - No such file or directory
Wed Feb 07 12:00:20 2018 : Debug: Loading library using linker search path(s)
Wed Feb 07 12:00:20 2018 : Debug: Defaults : \freeradius-server-3.0.16\lib
Wed Feb 07 12:00:20 2018 : Debug: Failed with error: "proto_status": The specified module could not be found.
Wed Feb 07 12:00:20 2018 : Debug: listen {
Wed Feb 07 12:00:20 2018 : Debug: type = "status"
Wed Feb 07 12:00:20 2018 : Debug: ipaddr = 127.0.0.1
Wed Feb 07 12:00:20 2018 : Debug: port = 18121
Wed Feb 07 12:00:20 2018 : Debug: client admin {
Wed Feb 07 12:00:20 2018 : Debug: ipaddr = 127.0.0.1
Wed Feb 07 12:00:20 2018 : Debug: require_message_authenticator = no
Wed Feb 07 12:00:20 2018 : Debug: secret = "adminsecret"
Wed Feb 07 12:00:20 2018 : Debug: limit {
Wed Feb 07 12:00:20 2018 : Debug: max_connections = 16
Wed Feb 07 12:00:20 2018 : Debug: lifetime = 0
Wed Feb 07 12:00:20 2018 : Debug: idle_timeout = 30
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: Adding client 127.0.0.1/32 (127.0.0.1) to prefix tree 32
Wed Feb 07 12:00:20 2018 : Debug: }
Wed Feb 07 12:00:20 2018 : Debug: Listening on auth address * port 1812 bound to server default
Wed Feb 07 12:00:20 2018 : Debug: Listening on acct address * port 1813 bound to server default
Wed Feb 07 12:00:20 2018 : Debug: Listening on auth address :: port 1812 bound to server default
Wed Feb 07 12:00:20 2018 : Debug: Listening on acct address :: port 1813 bound to server default
Wed Feb 07 12:00:20 2018 : Debug: Listening on auth address 192.168.1.4 port 1821 bound to server example
Wed Feb 07 12:00:20 2018 : Debug: Listening on auth address 127.0.0.1 port 18120 bound to server inner-tunnel
Wed Feb 07 12:00:20 2018 : Debug: Listening on status address 127.0.0.1 port 18121 bound to server status
Wed Feb 07 12:00:20 2018 : Debug: Opened new proxy socket 'proxy address * port 64591'
Wed Feb 07 12:00:20 2018 : Debug: Listening on proxy address * port 64591
Wed Feb 07 12:00:20 2018 : Debug: Opened new proxy socket 'proxy address :: port 64592'
Wed Feb 07 12:00:20 2018 : Debug: Listening on proxy address :: port 64592
Wed Feb 07 12:00:20 2018 : Info: Ready to process requests

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.ht
Alan DeKok
2018-02-07 20:20:18 UTC
Permalink
On Feb 7, 2018, at 3:11 PM, Sergio NNX <***@hotmail.com> wrote:
>
>
> We have noticed a few sort of modules showing up in the debug log.
> However, we are unable to locate them anywhere. They do not appear in any configuration file.
> So the question is: are those modules external modules, intrinsic (or core) ones or ...... ?
> Are they v3 specific?

They're already in the server core. We started moving functionality out of the core and into modules. That work wasn't finished in the v3 branch.

It is finished in v4. So there, the server core no longer knows anything about RADIUS. Which makes a number of things much simpler.

Alan DeKok.


-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.h
Emrah Yıldırım
2018-02-07 21:06:01 UTC
Permalink
First of all, I'm sorry. I sent out the changes I made and the
Freeradius-X output. If I need to share other information, please tell me
to share.

>Of course, that won't work as-is. Because you have given *zero*
information about the usernames, SQL instance names, etc

>If you give more information, you get better