Hello all, It seems that the $INCLUDE <filename> command is ignored by freeradius during authentication. I have three groups of users in three different files and those three files are added to the main users file in raddb directory using $INCLUDE users.group1 $INCLUDE users.group2 $INCLUDE users.group3 but for some reason during authentication freeradius just looks up the main users file and ignores the $INCLUDE command which results in REJECT being sent. I think that i simply missed a configuration step as this setup was working before i did the upgade to the MASTER version from git. Thanks in advance Kris http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
Ok, please dont mind this email. freeradius is not ignoring anything:-) It was my mistake. Kris On 20/08/12 18:08, Krzysztof Grobelak wrote:
Hello all,
It seems that the $INCLUDE <filename> command is ignored by freeradius during authentication.
I have three groups of users in three different files and those three files are added to the main users file in raddb directory using
$INCLUDE users.group1 $INCLUDE users.group2 $INCLUDE users.group3
but for some reason during authentication freeradius just looks up the main users file and ignores the $INCLUDE command which results in REJECT being sent.
I think that i simply missed a configuration step as this setup was working before i did the upgade to the MASTER version from git.
Thanks in advance Kris
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
Hello, I thought that I sorted the problem but i did not. the include directive in the users file does not seem to be working. Users will be authenticated if their profile is present in the users file but when i place the profile in external file users.group1 and then add $INCLUDE users.group1 to the main users file the authentication fails as it never finds a match in users file. Could you please advice. Regards, Kris On 20/08/12 19:01, Krzysztof Grobelak wrote:
Ok, please dont mind this email. freeradius is not ignoring anything:-) It was my mistake.
Kris
On 20/08/12 18:08, Krzysztof Grobelak wrote:
Hello all,
It seems that the $INCLUDE <filename> command is ignored by freeradius during authentication.
I have three groups of users in three different files and those three files are added to the main users file in raddb directory using
$INCLUDE users.group1 $INCLUDE users.group2 $INCLUDE users.group3
but for some reason during authentication freeradius just looks up the main users file and ignores the $INCLUDE command which results in REJECT being sent.
I think that i simply missed a configuration step as this setup was working before i did the upgade to the MASTER version from git.
Thanks in advance Kris
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
On 22 Aug 2012, at 11:13, Krzysztof Grobelak <kgrobelak@airspeed.ie> wrote:
Hello,
I thought that I sorted the problem but i did not.
the include directive in the users file does not seem to be working.
Users will be authenticated if their profile is present in the users file but when i place the profile in external file users.group1 and then add $INCLUDE users.group1 to the main users file the authentication fails as it never finds a match in users file.
Could you please advice.
The users file is NOT part of the FreeRADIUS configuration, and is not processed by the conf parser, so includes will not work. The users file is used by rlm_files, rlm_files has no support for the $INCLUDE directive. -Arran
On 22 Aug 2012, at 11:25, Alan DeKok <aland@deployingradius.com> wrote:
Arran Cudbard-Bell wrote:
The users file is used by rlm_files, rlm_files has no support for the $INCLUDE directive.
Yes, it does. See the comments at the top of the "users" file.
Ah sorry, you're right, it's calling core functions to do the file parsing. -Arran
Krzysztof Grobelak wrote:
Users will be authenticated if their profile is present in the users file but when i place the profile in external file users.group1 and then add $INCLUDE users.group1 to the main users file the authentication fails as it never finds a match in users file.
What do you mean "it doesn't work" ? See the FAQ for "it doesn't work". What do you expect to see happening? What actually happens? The $INCLUDE is just a short-cut for "cat": # -- users file $INCLUDE users1 $INCLUDE users2 #-- Results in *exactly* the same behavior as: $ cat users1 users2 > users Alan DeKok.
Hello, What I expect to happen is that the INCLUDE command will "include" the users.group1 file in to the main users file and that the user will be found. What actually happens is that the users file is parsed and the only matched entry is the DEFAULT entry at the bottom of the main users file and the include directive is ignored. I had similar setup on another freeradius server where it was working as expected that is the reason why I am confused. I used diff to confirm that the config files are exactly the same on both servers. I will provide radiusd -X logs as soon as i get the chance. Thanks, Kris On 22/08/12 11:28, Alan DeKok wrote:
Krzysztof Grobelak wrote:
Users will be authenticated if their profile is present in the users file but when i place the profile in external file users.group1 and then add $INCLUDE users.group1 to the main users file the authentication fails as it never finds a match in users file. What do you mean "it doesn't work" ?
See the FAQ for "it doesn't work".
What do you expect to see happening? What actually happens?
The $INCLUDE is just a short-cut for "cat":
# -- users file $INCLUDE users1 $INCLUDE users2 #--
Results in *exactly* the same behavior as:
$ cat users1 users2 > users
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
Krzysztof Grobelak wrote:
What I expect to happen is that the INCLUDE command will "include" the users.group1 file in to the main users file and that the user will be found.
The behavior of the "users" file is documented. There's no need to say "I expect this to happen". The exact behavior is documented.
What actually happens is that the users file is parsed and the only matched entry is the DEFAULT entry at the bottom of the main users file and the include directive is ignored.
No, that doesn't happen. If the include directive is ignored, that's because either it's not being seen, or the included file is empty. Read the debug log to see. It *prints out* the file it's including. It's not hard to see this.
I had similar setup on another freeradius server where it was working as expected that is the reason why I am confused.
Well, it works the way it's documented.
I used diff to confirm that the config files are exactly the same on both servers.
I will provide radiusd -X logs as soon as i get the chance.
And read them before posting. Please. Odds are that the problem is trivially solvable by reading the logs. Alan DeKok/
Hello, I looked at the log output I see what is wrong but dont understand why. The user gets rejected because no password was found. It was not found because the $INCLUDE directive did not include the users.group1 into the users file. Alan you said that the include directive is ignored if its not being seen or the included file is empty. It's not empty so assuming that the directive is not being seen what would be reason for that?? Thanks, Kris Below is the log file. rad_recv: Access-Request packet from host xxx.xxx.xxx.xxx port 1645, id=129, length=153 Debug: Waking up in 0.3 seconds. Debug: Thread 3 got semaphore Debug: Thread 3 handling request 7, (2 handled so far) Framed-Protocol = PPP User-Name = "0123456789@dsl.test.ie" CHAP-Password = 0xac52fc9fec42d669c546add53f9e516ffb Calling-Station-Id = "CWT26 atm 1/1/12/03:8.35#" Connect-Info = "1000000000" NAS-Port-Type = ISDN NAS-Port = 20396 NAS-Port-Id = "Uniq-Sess-ID396" Service-Type = Framed-User NAS-IP-Address = xxx.xxx.xxx.xxx Info: (7) <thread> : # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default Info: (7) <thread> : group authorize { Info: (7) <thread> : - entering group authorize {...} Info: (7) [preprocess] = ok Info: (7) auth_log : expand: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/auth-detail-20120822 Info: (7) auth_log : /usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/auth-detail-20120822 Info: (7) auth_log : expand: %t -> Wed Aug 22 13:53:41 2012 Info: (7) [auth_log] = ok Info: (7) chap : Setting 'Auth-Type := CHAP' Info: (7) [chap] = ok Info: (7) [mschap] = noop Info: (7) [digest] = noop Info: (7) suffix : Looking up realm "dsl.test.ie" for User-Name = "0123456789@dsl.test.ie" Info: (7) suffix : Found realm "dsl.test.ie" Info: (7) suffix : Adding Realm = "dsl.test.ie" Info: (7) suffix : Authentication realm is LOCAL. Info: (7) [suffix] = ok Info: (7) eap : No EAP-Message, not doing EAP Info: (7) [eap] = noop Info: (7) [files] = noop Info: (7) sql : expand: %{Stripped-User-Name} -> Info: (7) sql : ... expanding second conditional Info: (7) sql : expand: %{User-Name} -> 0123456789@dsl.test.ie Info: (7) sql : expand: %{%{User-Name}:-DEFAULT} -> 0123456789@dsl.test.ie Info: (7) sql : expand: %{%{Stripped-User-Name}:-%{%{User-Name}:-DEFAULT}} -> 0123456789@dsl.test.ie Info: (7) sql : sql_set_user escaped user --> '0123456789@dsl.test.ie' Debug: rlm_sql (sql): Closing idle connection (6) Debug: No trigger subsection: ignoring trigger modules.sql.close Debug: rlm_sql (sql): Closing idle connection (5) Debug: No trigger subsection: ignoring trigger modules.sql.close Debug: rlm_sql (sql): Opening additional connection (7) Info: rlm_sql_mysql: Starting connect to MySQL server Debug: No trigger subsection: ignoring trigger modules.sql.open Debug: rlm_sql (sql): Reserved connection (7) Info: (7) sql : expand: SELECT id, username, attribute, value, op FROM radcheck WHERE username = '%{SQL-User-Name}' ORDER BY id -> SELECT id, username, attribute, value, op FROM radcheck WHERE username = '0123456789@dsl.test.ie' ORDER BY id Info: (7) sql : expand: SELECT groupname FROM radusergroup WHERE username = '%{SQL-User-Name}' ORDER BY priority -> SELECT groupname FROM radusergroup WHERE username = '0123456789@dsl.test.ie' ORDER BY priority Debug: rlm_sql (sql): Released connection (7) Debug: rlm_sql (sql): Opening additional connection (8) Info: rlm_sql_mysql: Starting connect to MySQL server Debug: No trigger subsection: ignoring trigger modules.sql.open Info: (7) sql : User 0123456789@dsl.test.ie not found Info: (7) [sql] = notfound Info: (7) [expiration] = noop Info: (7) [logintime] = noop Info: (7) pap : WARNING! No "known good" password found for the user. Authentication may fail because of this. Info: (7) [pap] = noop Info: (7) Found Auth-Type = CHAP Info: (7) # Executing group from file /usr/local/etc/raddb/sites-enabled/default Info: (7) group CHAP { Info: (7) - entering group CHAP {...} Info: (7) chap : login attempt by "0123456789@dsl.test.ie" with CHAP password Info: (7) chap : Cleartext-Password is required for authentication Info: (7) [chap] = invalid Info: (7) Failed to authenticate the user. Auth: (7) Login incorrect (rlm_chap: Clear text password not available): [0123456789@dsl.test.ie/<CHAP-Password>] (from client 4050.services.v2.A port 20396 cli CWT26 atm 1/1/12/03:8.35#) Info: (7) Using Post-Auth-Type Reject Info: (7) # Executing group from file /usr/local/etc/raddb/sites-enabled/default Info: (7) group REJECT { Info: (7) - entering group REJECT {...} Info: (7) attr_filter.access_reject : expand: %{User-Name} -> 0123456789@dsl.test.ie Info: (7) attr_filter.access_reject : Matched entry DEFAULT at line 11 Info: (7) [attr_filter.access_reject] = updated Info: (7) eap : Request didn't contain an EAP-Message, not inserting EAP-Failure Info: (7) [eap] = noop Info: (7) policy remove_reply_message_if_eap { Info: (7) - entering policy remove_reply_message_if_eap {...} Info: (7) ? if (reply:EAP-Message && reply:Reply-Message) Info: (7) ? Evaluating (reply:EAP-Message ) -> FALSE Info: (7) ? Skipping (reply:Reply-Message) Info: (7) ? if (reply:EAP-Message && reply:Reply-Message) -> FALSE Info: (7) else else { Info: (7) - entering else else {...} Info: (7) [noop] = noop Info: (7) - else else returns noop Info: (7) - policy remove_reply_message_if_eap returns noop Info: (7) Finished request 7. Debug: Thread 3 waiting to be assigned a request Debug: Waking up in 0.6 seconds. Info: (7) Sending delayed reject Sending Access-Reject of id 129 to xxx.xxx.xxx.xxx port 1645 Debug: Waking up in 4.9 seconds. Info: (7) Cleaning up request packet ID 129 with timestamp +508 Info: Ready to process requests. ## ## And the startup ## Starting - reading configuration files ... including configuration file /usr/local/etc/raddb/radiusd.conf including configuration file /usr/local/etc/raddb/proxy.conf including configuration file /usr/local/etc/raddb/clients.conf including files in directory /usr/local/etc/raddb/mods-enabled/ including configuration file /usr/local/etc/raddb/mods-enabled/expr including configuration file /usr/local/etc/raddb/mods-enabled/preprocess including configuration file /usr/local/etc/raddb/mods-enabled/expiration including configuration file /usr/local/etc/raddb/mods-enabled/realm including configuration file /usr/local/etc/raddb/mods-enabled/acct_unique including configuration file /usr/local/etc/raddb/mods-enabled/inner-eap including configuration file /usr/local/etc/raddb/mods-enabled/passwd including configuration file /usr/local/etc/raddb/mods-enabled/detail including configuration file /usr/local/etc/raddb/mods-enabled/files including configuration file /usr/local/etc/raddb/mods-enabled/mschap including configuration file /usr/local/etc/raddb/mods-enabled/sql_log including configuration file /usr/local/etc/raddb/mods-enabled/ntlm_auth including configuration file /usr/local/etc/raddb/mods-enabled/utf8 including configuration file /usr/local/etc/raddb/mods-enabled/replicate including configuration file /usr/local/etc/raddb/mods-enabled/logintime including configuration file /usr/local/etc/raddb/mods-enabled/sql including configuration file /usr/local/etc/raddb/sql/mysql/dialup.conf including configuration file /usr/local/etc/raddb/mods-enabled/dynamic_clients including configuration file /usr/local/etc/raddb/mods-enabled/digest including configuration file /usr/local/etc/raddb/mods-enabled/pap including configuration file /usr/local/etc/raddb/mods-enabled/attr_filter including configuration file /usr/local/etc/raddb/mods-enabled/linelog including configuration file /usr/local/etc/raddb/mods-enabled/detail.log including configuration file /usr/local/etc/raddb/mods-enabled/unix including configuration file /usr/local/etc/raddb/mods-enabled/wimax including configuration file /usr/local/etc/raddb/mods-enabled/checkval including configuration file /usr/local/etc/raddb/mods-enabled/sradutmp including configuration file /usr/local/etc/raddb/mods-enabled/soh including configuration file /usr/local/etc/raddb/mods-enabled/echo including configuration file /usr/local/etc/raddb/mods-enabled/exec including configuration file /usr/local/etc/raddb/mods-enabled/eap including configuration file /usr/local/etc/raddb/mods-enabled/always including configuration file /usr/local/etc/raddb/mods-enabled/chap including configuration file /usr/local/etc/raddb/mods-enabled/radutmp including configuration file /usr/local/etc/raddb/mods-enabled/attr_rewrite including configuration file /usr/local/etc/raddb/mods-enabled/counter including configuration file /usr/local/etc/raddb/mods-enabled/cui including configuration file /usr/local/etc/raddb/policy.conf including files in directory /usr/local/etc/raddb/sites-enabled/ including configuration file /usr/local/etc/raddb/sites-enabled/default including configuration file /usr/local/etc/raddb/sites-enabled/tls including configuration file /usr/local/etc/raddb/sites-enabled/inner-tunnel main { security { allow_core_dumps = no } } including dictionary file /usr/local/etc/raddb/dictionary main { name = "radiusd" prefix = "/usr/local" localstatedir = "/usr/local/var" sbindir = "/usr/local/sbin" logdir = "/usr/local/var/log/radius" run_dir = "/usr/local/var/run/radiusd" libdir = "/usr/local/lib" radacctdir = "/usr/local/var/log/radius/radacct" hostname_lookups = no max_request_time = 120 cleanup_delay = 10 max_requests = 2560 pidfile = "/usr/local/var/run/radiusd/radiusd.pid" checkrad = "/usr/local/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = yes auth = yes auth_badpass = yes auth_goodpass = yes } security { max_attributes = 200 reject_delay = 1 status_server = yes } } radiusd: #### Loading Realms and Home Servers #### proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 require_message_authenticator = yes zombie_period = 40 status_check = "status-server" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 coa { irt = 2 mrt = 16 mrc = 5 mrd = 30 } limit { max_connections = 16 max_requests = 0 lifetime = 0 idle_timeout = 0 } } home_server tls { ipaddr = 127.0.0.1 port = 2083 type = "auth" proto = "tcp" secret = "testing123" response_window = 30 max_outstanding = 65536 zombie_period = 40 status_check = "none" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 300 status_check_timeout = 4 } tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 CA_path = "/usr/local/etc/raddb/certs" pem_file_type = yes private_key_file = "/usr/local/etc/raddb/certs/client.pem" certificate_file = "/usr/local/etc/raddb/certs/client.pem" CA_file = "/usr/local/etc/raddb/certs/ca.pem" private_key_password = "whatever" dh_file = "/usr/local/etc/raddb/certs/dh" random_file = "/usr/local/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" ecdh_curve = "prime256v1" } realm test.ie { } realm dsl.test.ie { nostrip } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } home_server_pool tls { type = fail-over home_server = tls } realm tls { auth_pool = tls } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" proto = "*" max_connections = 16 } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating module "exec" from file /usr/local/etc/raddb/mods-enabled/exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating module "expr" from file /usr/local/etc/raddb/mods-enabled/expr Module: Linked to module rlm_expiration Module: Instantiating module "expiration" from file /usr/local/etc/raddb/mods-enabled/expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating module "logintime" from file /usr/local/etc/raddb/mods-enabled/logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server { # from file /usr/local/etc/raddb/radiusd.conf modules { Module: Creating Auth-Type = digest Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating module "pap" from file /usr/local/etc/raddb/mods-enabled/pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating module "chap" from file /usr/local/etc/raddb/mods-enabled/chap Module: Linked to module rlm_mschap Module: Instantiating module "mschap" from file /usr/local/etc/raddb/mods-enabled/mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no passchange { } allow_retry = yes } Module: Linked to module rlm_digest Module: Instantiating module "digest" from file /usr/local/etc/raddb/mods-enabled/digest Module: Linked to module rlm_unix Module: Instantiating module "unix" from file /usr/local/etc/raddb/mods-enabled/unix unix { radwtmp = "/usr/local/var/log/radius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating module "eap" from file /usr/local/etc/raddb/mods-enabled/eap eap { default_eap_type = "ttls" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no max_sessions = 4096 } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } Module: Linked to sub-module rlm_eap_tls Module: Instantiating eap-tls tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 CA_path = "/usr/local/etc/raddb/certs" pem_file_type = yes private_key_file = "/usr/local/etc/raddb/certs/server.pem" certificate_file = "/usr/local/etc/raddb/certs/server.pem" CA_file = "/usr/local/etc/raddb/certs/ca.pem" private_key_password = "whatever" dh_file = "/usr/local/etc/raddb/certs/dh" random_file = "/usr/local/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/usr/local/etc/raddb/certs/bootstrap" ecdh_curve = "prime256v1" cache { enable = no lifetime = 24 max_entries = 255 } verify { } ocsp { enable = no override_cert_url = yes url = "http://127.0.0.1/ocsp/" use_nonce = yes timeout = 0 softfail = yes } } Module: Linked to sub-module rlm_eap_ttls Module: Instantiating eap-ttls ttls { default_eap_type = "md5" copy_request_to_tunnel = yes use_tunneled_reply = yes virtual_server = "inner-tunnel" include_length = yes } Module: Linked to sub-module rlm_eap_peap Module: Instantiating eap-peap peap { default_eap_type = "mschapv2" copy_request_to_tunnel = no use_tunneled_reply = no proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" soh = no } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no send_error = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating module "preprocess" from file /usr/local/etc/raddb/mods-enabled/preprocess preprocess { huntgroups = "/usr/local/etc/raddb/huntgroups" hints = "/usr/local/etc/raddb/hints" with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = no with_alvarion_vsa_hack = no } Module: Linked to module rlm_detail Module: Instantiating module "auth_log" from file /usr/local/etc/raddb/mods-enabled/detail.log detail auth_log { detailfile = "/usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Linked to module rlm_realm Module: Instantiating module "suffix" from file /usr/local/etc/raddb/mods-enabled/realm realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating module "files" from file /usr/local/etc/raddb/mods-enabled/files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } Module: Linked to module rlm_sql Module: Instantiating module "sql" from file /usr/local/etc/raddb/mods-enabled/sql sql { driver = "rlm_sql_mysql" server = "localhost" port = "3306" login = "radius" password = "radius" radius_db = "radius" read_groups = yes sqltrace = no sqltracefile = "/usr/local/var/log/radius/sqltrace.sql" readclients = yes deletestalesessions = yes sql_user_name = "%{%{Stripped-User-Name}:-%{%{User-Name}:-DEFAULT}}" default_user_profile = "" nas_query = "SELECT id, nasname, shortname, type, secret, server FROM nas" authorize_check_query = " SELECT id, username, attribute, value, op FROM radcheck WHERE username = '%{SQL-User-Name}' ORDER BY id" authorize_reply_query = " SELECT id, username, attribute, value, op FROM radreply WHERE username = '%{SQL-User-Name}' ORDER BY id" authorize_group_check_query = " SELECT id, groupname, attribute, Value, op FROM radgroupcheck WHERE groupname = '%{Sql-Group}' ORDER BY id" authorize_group_reply_query = " SELECT id, groupname, attribute, value, op FROM radgroupreply WHERE groupname = '%{Sql-Group}' ORDER BY id" accounting_onoff_query = " UPDATE radacct SET acctstoptime = '%S', acctsessiontime = unix_timestamp('%S') - unix_timestamp(acctstarttime), acctterminatecause = '%{Acct-Terminate-Cause}', acctstopdelay = %{%{Acct-Delay-Time}:-0} WHERE acctstoptime IS NULL AND nasipaddress = '%{NAS-IP-Address}' AND acctstarttime <= '%S'" accounting_update_query = " UPDATE radacct SET framedipaddress = '%{Framed-IP-Address}', acctsessiontime = '%{Acct-Session-Time}', acctinputoctets = '%{%{Acct-Input-Gigawords}:-0}' << 32 | '%{%{Acct-Input-Octets}:-0}', acctoutputoctets = '%{%{Acct-Output-Gigawords}:-0}' << 32 | '%{%{Acct-Output-Octets}:-0}' WHERE acctsessionid = '%{Acct-Session-Id}' AND username = '%{SQL-User-Name}' AND nasipaddress = '%{NAS-IP-Address}'" accounting_update_query_alt = " INSERT INTO radacct (acctsessionid, acctuniqueid, username, realm, nasipaddress, nasportid, nasporttype, acctstarttime, acctsessiontime, acctauthentic, connectinfo_start, acctinputoctets, acctoutputoctets, calledstationid, callingstationid, servicetype, framedprotocol, framedipaddress, acctstartdelay, xascendsessionsvrkey) VALUES ('%{Acct-Session-Id}', '%{Acct-Unique-Session-Id}', '%{SQL-User-Name}', '%{Realm}', '%{NAS-IP-Address}', '%{NAS-Port}', '%{NAS-Port-Type}', DATE_SUB('%S', INTERVAL (%{%{Acct-Session-Time}:-0} + %{%{Acct-Delay-Time}:-0}) SECOND), '%{Acct-Session-Time}', '%{Acct-Authentic}', '', '%{%{Acct-Input-Gigawords}:-0}' << 32 | '%{%{Acct-Input-Octets}:-0}', '%{%{Acct-Output-Gigawords}:-0}' << 32 | '%{%{Acct-Output-Octets}:-0}', '%{Called-Station-Id}', '%{Calling-Station-Id}', '%{Service-Type}', '%{Framed-Protocol}', '%{Framed-IP-Address}', '0', '%{X-Ascend-Session-Svr-Key}')" accounting_start_query = " INSERT INTO radacct (acctsessionid, acctuniqueid, username, realm, nasipaddress, nasportid, nasporttype, acctstarttime, acctstoptime, acctsessiontime, acctauthentic, connectinfo_start, connectinfo_stop, acctinputoctets, acctoutputoctets, calledstationid, callingstationid, acctterminatecause, servicetype, framedprotocol, framedipaddress, acctstartdelay, acctstopdelay, xascendsessionsvrkey) VALUES ('%{Acct-Session-Id}', '%{Acct-Unique-Session-Id}', '%{SQL-User-Name}', '%{Realm}', '%{NAS-IP-Address}', '%{NAS-Port}', '%{NAS-Port-Type}', '%S', NULL, '0', '%{Acct-Authentic}', '%{Connect-Info}', '', '0', '0', '%{Called-Station-Id}', '%{Calling-Station-Id}', '', '%{Service-Type}', '%{Framed-Protocol}', '%{Framed-IP-Address}', '%{%{Acct-Delay-Time}:-0}', '0', '%{X-Ascend-Session-Svr-Key}')" accounting_start_query_alt = " UPDATE radacct SET acctstarttime = '%S', acctstartdelay = '%{%{Acct-Delay-Time}:-0}', connectinfo_start = '%{Connect-Info}' WHERE acctsessionid = '%{Acct-Session-Id}' AND username = '%{SQL-User-Name}' AND nasipaddress = '%{NAS-IP-Address}'" accounting_stop_query = " UPDATE radacct SET acctstoptime = '%S', acctsessiontime = '%{Acct-Session-Time}', acctinputoctets = '%{%{Acct-Input-Gigawords}:-0}' << 32 | '%{%{Acct-Input-Octets}:-0}', acctoutputoctets = '%{%{Acct-Output-Gigawords}:-0}' << 32 | '%{%{Acct-Output-Octets}:-0}', acctterminatecause = '%{Acct-Terminate-Cause}', acctstopdelay = '%{%{Acct-Delay-Time}:-0}', connectinfo_stop = '%{Connect-Info}' WHERE acctsessionid = '%{Acct-Session-Id}' AND username = '%{SQL-User-Name}' AND nasipaddress = '%{NAS-IP-Address}'" accounting_stop_query_alt = " INSERT INTO radacct (acctsessionid, acctuniqueid, username, realm, nasipaddress, nasportid, nasporttype, acctstarttime, acctstoptime, acctsessiontime, acctauthentic, connectinfo_start, connectinfo_stop, acctinputoctets, acctoutputoctets, calledstationid, callingstationid, acctterminatecause, servicetype, framedprotocol, framedipaddress, acctstartdelay, acctstopdelay) VALUES ('%{Acct-Session-Id}', '%{Acct-Unique-Session-Id}', '%{SQL-User-Name}', '%{Realm}', '%{NAS-IP-Address}', '%{NAS-Port}', '%{NAS-Port-Type}', DATE_SUB('%S', INTERVAL (%{%{Acct-Session-Time}:-0} + %{%{Acct-Delay-Time}:-0}) SECOND), '%S', '%{Acct-Session-Time}', '%{Acct-Authentic}', '', '%{Connect-Info}', '%{%{Acct-Input-Gigawords}:-0}' << 32 | '%{%{Acct-Input-Octets}:-0}', '%{%{Acct-Output-Gigawords}:-0}' << 32 | '%{%{Acct-Output-Octets}:-0}', '%{Called-Station-Id}', '%{Calling-Station-Id}', '%{Acct-Terminate-Cause}', '%{Service-Type}', '%{Framed-Protocol}', '%{Framed-IP-Address}', '0', '%{%{Acct-Delay-Time}:-0}')" group_membership_query = " SELECT groupname FROM radusergroup WHERE username = '%{SQL-User-Name}' ORDER BY priority" simul_count_query = "" simul_verify_query = " SELECT radacctid, acctsessionid, username, nasipaddress, nasportid, framedipaddress, callingstationid, framedprotocol FROM radacct WHERE username = '%{SQL-User-Name}' AND acctstoptime IS NULL" postauth_query = " INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( '%{SQL-User-Name}', '%{%{User-Password}:-%{Chap-Password}}', '%{reply:Packet-Type}', '%S')" safe-characters = "@abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789.-_: /" } rlm_sql (sql): Driver rlm_sql_mysql (module rlm_sql_mysql) loaded and linked rlm_sql (sql): Attempting to connect to radius@localhost:3306/radius rlm_sql (sql): Initialising connection pool pool { start = 5 min = 0 max = 100 spare = 3 uses = 0 lifetime = 0 cleanup_delay = 5 idle_timeout = 60 } rlm_sql (sql): Opening additional connection (0) rlm_sql_mysql: Starting connect to MySQL server rlm_sql (sql): Opening additional connection (1) rlm_sql_mysql: Starting connect to MySQL server rlm_sql (sql): Opening additional connection (2) rlm_sql_mysql: Starting connect to MySQL server rlm_sql (sql): Opening additional connection (3) rlm_sql_mysql: Starting connect to MySQL server rlm_sql (sql): Opening additional connection (4) rlm_sql_mysql: Starting connect to MySQL server rlm_sql (sql): Processing generate_sql_clients rlm_sql (sql) in generate_sql_clients: query is SELECT id, nasname, shortname, type, secret, server FROM nas rlm_sql (sql): Reserved connection (4) ... all the NAS are loaded here correctly ... rlm_sql (sql): Released connection (4) Module: Checking preacct {...} for more modules to load Module: Loading virtual module acct_unique Module: Checking accounting {...} for more modules to load Module: Instantiating module "detail" from file /usr/local/etc/raddb/mods-enabled/detail detail { detailfile = "/usr/local/var/log/radius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Linked to module rlm_radutmp Module: Instantiating module "radutmp" from file /usr/local/etc/raddb/mods-enabled/radutmp radutmp { filename = "/usr/local/var/log/radius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Linked to module rlm_attr_filter Module: Instantiating module "attr_filter.accounting_response" from file /usr/local/etc/raddb/mods-enabled/attr_filter attr_filter attr_filter.accounting_response { attrsfile = "/usr/local/etc/raddb/attrs.accounting_response" key = "%{User-Name}" relaxed = no } Module: Checking session {...} for more modules to load Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Instantiating module "reply_log" from file /usr/local/etc/raddb/mods-enabled/detail.log detail reply_log { detailfile = "/usr/local/var/log/radius/radacct/%{Client-IP-Address}/reply-detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Linked to module rlm_wimax Module: Instantiating module "wimax" from file /usr/local/etc/raddb/mods-enabled/wimax wimax { delete_mppe_keys = yes } Module: Loading virtual module remove_reply_message_if_eap Module: Linked to module rlm_always Module: Instantiating module "noop" from file /usr/local/etc/raddb/mods-enabled/always always noop { rcode = "noop" simulcount = 0 mpp = no } Module: Instantiating module "attr_filter.access_reject" from file /usr/local/etc/raddb/mods-enabled/attr_filter attr_filter attr_filter.access_reject { attrsfile = "/usr/local/etc/raddb/attrs.access_reject" key = "%{User-Name}" relaxed = no } Module: Loading virtual module remove_reply_message_if_eap } # modules } # server server inner-tunnel { # from file /usr/local/etc/raddb/sites-enabled/inner-tunnel modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Checking session {...} for more modules to load Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load } # modules } # server thread pool { start_servers = 5 max_servers = 32 min_spare_servers = 3 max_spare_servers = 10 max_requests_per_server = 0 cleanup_delay = 5 max_queue_size = 65536 } Thread spawned new child 1. Total threads in pool: 1 Thread spawned new child 2. Total threads in pool: 2 Thread spawned new child 3. Total threads in pool: 3 Thread spawned new child 4. Total threads in pool: 4 Thread spawned new child 5. Total threads in pool: 5 Thread pool initialized radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 Thread 5 waiting to be assigned a request Thread 4 waiting to be assigned a request Thread 3 waiting to be assigned a request Thread 2 waiting to be assigned a request } listen { type = "acct" ipaddr = * port = 0 Thread 1 waiting to be assigned a request } listen { type = "auth" ipaddr = * port = 2083 proto = "tcp" max_connections = 64 tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 CA_path = "/usr/local/etc/raddb/certs" pem_file_type = yes private_key_file = "/usr/local/etc/raddb/certs/server.pem" certificate_file = "/usr/local/etc/raddb/certs/server.pem" CA_file = "/usr/local/etc/raddb/certs/ca.pem" private_key_password = "whatever" dh_file = "/usr/local/etc/raddb/certs/dh" random_file = "/usr/local/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" require_client_cert = yes ecdh_curve = "prime256v1" cache { enable = no lifetime = 24 max_entries = 255 } verify { } } clients = "radsec" client 127.0.0.1 { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" proto = "tcp" max_connections = 16 } } listen { type = "auth" ipaddr = 127.0.0.1 port = 4000 } listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on authentication proto tcp address * port 2083 (TLS) Listening on authentication address 127.0.0.1 port 4000 Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Opening new proxy address * port 1814 Listening on proxy address * port 1814 Ready to process requests. http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
Krzysztof Grobelak wrote:
I looked at the log output I see what is wrong but dont understand why. The user gets rejected because no password was found. It was not found because the $INCLUDE directive did not include the users.group1 into the users file.
I wouldn't go that far. The "files" module returned "noop". This means that the user wasn't found in the "users" file.
Alan you said that the include directive is ignored if its not being seen or the included file is empty. It's not empty so assuming that the directive is not being seen what would be reason for that??
Are you editing the file that the server is reading?
Module: Linked to module rlm_files Module: Instantiating module "files" from file /usr/local/etc/raddb/mods-enabled/files files { usersfile = "/usr/local/etc/raddb/users"
Check this file. Is it the one you're editing? There's really no magic here. The server reads this file. It either (a) reads all of it, along with "include" lines. Or (b), it gets a parse error, and doesn't read it. Alan DeKok.
Am 22.08.2012 13:48, schrieb Alan DeKok:
Krzysztof Grobelak wrote:
What I expect to happen is that the INCLUDE command will "include" the users.group1 file in to the main users file and that the user will be found.
The behavior of the "users" file is documented. There's no need to say "I expect this to happen". The exact behavior is documented.
What actually happens is that the users file is parsed and the only matched entry is the DEFAULT entry at the bottom of the main users file and the include directive is ignored.
No, that doesn't happen.
If the include directive is ignored, that's because either it's not being seen, or the included file is empty.
Read the debug log to see. It *prints out* the file it's including. It's not hard to see this.
@ Alan I just verified that on a 2.1.10 server and it seems that files, included with the $INCLUDE statement in the users file, are *not* printed out to the debug log. @ Kris Where in /etc/raddb/users did you place the $INCLUDE statement? You didn't put it at the end of the file, did you? ;-) Cheers, Klaus
On 22 Aug 2012, at 17:26, Klaus Klein <k.klein@gmx.de> wrote:
Am 22.08.2012 13:48, schrieb Alan DeKok:
Krzysztof Grobelak wrote:
What I expect to happen is that the INCLUDE command will "include" the users.group1 file in to the main users file and that the user will be found.
The behavior of the "users" file is documented. There's no need to say "I expect this to happen". The exact behavior is documented.
What actually happens is that the users file is parsed and the only matched entry is the DEFAULT entry at the bottom of the main users file and the include directive is ignored.
No, that doesn't happen.
If the include directive is ignored, that's because either it's not being seen, or the included file is empty.
Read the debug log to see. It *prints out* the file it's including. It's not hard to see this.
@ Alan I just verified that on a 2.1.10 server and it seems that files, included with the $INCLUDE statement in the users file, are *not* printed out to the debug log.
Yes, looks that way. https://github.com/alandekok/freeradius-server/blob/master/src/main/files.c#... It'll only print out debug messages if it can't open the file.
On 22 Aug 2012, at 17:42, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
On 22 Aug 2012, at 17:26, Klaus Klein <k.klein@gmx.de> wrote:
Am 22.08.2012 13:48, schrieb Alan DeKok:
Krzysztof Grobelak wrote:
What I expect to happen is that the INCLUDE command will "include" the users.group1 file in to the main users file and that the user will be found.
The behavior of the "users" file is documented. There's no need to say "I expect this to happen". The exact behavior is documented.
What actually happens is that the users file is parsed and the only matched entry is the DEFAULT entry at the bottom of the main users file and the include directive is ignored.
No, that doesn't happen.
If the include directive is ignored, that's because either it's not being seen, or the included file is empty.
Read the debug log to see. It *prints out* the file it's including. It's not hard to see this.
@ Alan I just verified that on a 2.1.10 server and it seems that files, included with the $INCLUDE statement in the users file, are *not* printed out to the debug log.
Yes, looks that way.
https://github.com/alandekok/freeradius-server/blob/master/src/main/files.c#...
It'll only print out debug messages if it can't open the file.
Added extra debug statement. Please build from v2.1.x branch or master. -Arran
Am 23.08.2012 00:54, schrieb Arran Cudbard-Bell:
On 22 Aug 2012, at 17:42, Arran Cudbard-Bell<a.cudbardb@freeradius.org> wrote:
On 22 Aug 2012, at 17:26, Klaus Klein<k.klein@gmx.de> wrote:
@ Alan I just verified that on a 2.1.10 server and it seems that files, included with the $INCLUDE statement in the users file, are *not* printed out to the debug log. Yes, looks that way. https://github.com/alandekok/freeradius-server/blob/master/src/main/files.c#... It'll only print out debug messages if it can't open the file. Added extra debug statement. Please build from v2.1.x branch or master.
Cool !!! Thx, Klaus
Hello and thanks for assistance. I just compiled freeRadius with those debug entries and the radiusd -X now shows: Module: Instantiating module "files" from file /usr/local/etc/raddb/mods-enabled/files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } reading pairlist file /usr/local/etc/raddb/users reading pairlist file /usr/local/etc/raddb/ reading pairlist file /usr/local/etc/raddb/ reading pairlist file /usr/local/etc/raddb/acct_users reading pairlist file /usr/local/etc/raddb/preproxy_users So freeradius definitely not getting a handle on those files that looks to me more like a system issue that a radius. I am running this freeradius on a virtual server OpenSUSE 12.1 using KVM/Qemu. Did anybody came across of issue like that?? Thanks Kris On 22/08/12 23:54, Arran Cudbard-Bell wrote:
On 22 Aug 2012, at 17:42, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
On 22 Aug 2012, at 17:26, Klaus Klein <k.klein@gmx.de> wrote:
Am 22.08.2012 13:48, schrieb Alan DeKok:
Krzysztof Grobelak wrote:
What I expect to happen is that the INCLUDE command will "include" the users.group1 file in to the main users file and that the user will be found. The behavior of the "users" file is documented. There's no need to say "I expect this to happen". The exact behavior is documented.
What actually happens is that the users file is parsed and the only matched entry is the DEFAULT entry at the bottom of the main users file and the include directive is ignored. No, that doesn't happen.
If the include directive is ignored, that's because either it's not being seen, or the included file is empty.
Read the debug log to see. It *prints out* the file it's including. It's not hard to see this. @ Alan I just verified that on a 2.1.10 server and it seems that files, included with the $INCLUDE statement in the users file, are *not* printed out to the debug log. Yes, looks that way.
https://github.com/alandekok/freeradius-server/blob/master/src/main/filesc#L...
It'll only print out debug messages if it can't open the file. Added extra debug statement. Please build from v2.1.x branch or master.
-Arran - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
Krzysztof Grobelak wrote:
I just compiled freeRadius with those debug entries and the radiusd -X now shows: .. reading pairlist file /usr/local/etc/raddb/users reading pairlist file /usr/local/etc/raddb/ reading pairlist file /usr/local/etc/raddb/
Uh, that's wrong. It shouldn't be reading directories.
So freeradius definitely not getting a handle on those files that looks to me more like a system issue that a radius. I am running this freeradius on a virtual server OpenSUSE 12.1 using KVM/Qemu.
Did anybody came across of issue like that??
No idea. Alan DeKok.
On 23 Aug 2012, at 10:47, Alan DeKok <aland@deployingradius.com> wrote:
Krzysztof Grobelak wrote:
I just compiled freeRadius with those debug entries and the radiusd -X now shows: .. reading pairlist file /usr/local/etc/raddb/users reading pairlist file /usr/local/etc/raddb/ reading pairlist file /usr/local/etc/raddb/
Uh, that's wrong. It shouldn't be reading directories.
So freeradius definitely not getting a handle on those files that looks to me more like a system issue that a radius. I am running this freeradius on a virtual server OpenSUSE 12.1 using KVM/Qemu.
Did anybody came across of issue like that??
No idea.
Um just for a sanity check - can OP send me the users file and includes and i'll try it on my system. -Arran
On 23 Aug 2012, at 10:41, "Krzysztof Grobelak" <kgrobelak@airspeed.ie> wrote:
Hello and thanks for assistance.
I just compiled freeRadius with those debug entries and the radiusd -X now shows:
Module: Instantiating module "files" from file /usr/local/etc/raddb/mods-enabled/files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } reading pairlist file /usr/local/etc/raddb/users reading pairlist file /usr/local/etc/raddb/ reading pairlist file /usr/local/etc/raddb/
What are those ^ - That's weird - why is it just the path and not the filename - do you have two include statements?
reading pairlist file /usr/local/etc/raddb/acct_users reading pairlist file /usr/local/etc/raddb/preproxy_users
So freeradius definitely not getting a handle on those files that looks to me more like a system issue that a radius. I am running this freeradius on a virtual server OpenSUSE 12.1 using KVM/Qemu.
Did anybody came across of issue like that??
Thanks Kris
On 22/08/12 23:54, Arran Cudbard-Bell wrote:
On 22 Aug 2012, at 17:42, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
On 22 Aug 2012, at 17:26, Klaus Klein <k.klein@gmx.de> wrote:
Am 22.08.2012 13:48, schrieb Alan DeKok:
Krzysztof Grobelak wrote:
What I expect to happen is that the INCLUDE command will "include" the users.group1 file in to the main users file and that the user will be found. The behavior of the "users" file is documented. There's no need to say "I expect this to happen". The exact behavior is documented.
What actually happens is that the users file is parsed and the only matched entry is the DEFAULT entry at the bottom of the main users file and the include directive is ignored. No, that doesn't happen.
If the include directive is ignored, that's because either it's not being seen, or the included file is empty.
Read the debug log to see. It *prints out* the file it's including. It's not hard to see this. @ Alan I just verified that on a 2.1.10 server and it seems that files, included with the $INCLUDE statement in the users file, are *not* printed out to the debug log. Yes, looks that way.
https://github.com/alandekok/freeradius-server/blob/master/src/main/filesc#L...
It'll only print out debug messages if it can't open the file. Added extra debug statement. Please build from v2.1.x branch or master.
-Arran - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 23/08/12 10:51, Arran Cudbard-Bell wrote:
On 23 Aug 2012, at 10:41, "Krzysztof Grobelak" <kgrobelak@airspeed.ie> wrote:
Hello and thanks for assistance.
I just compiled freeRadius with those debug entries and the radiusd -X now shows:
Module: Instantiating module "files" from file /usr/local/etc/raddb/mods-enabled/files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } reading pairlist file /usr/local/etc/raddb/users reading pairlist file /usr/local/etc/raddb/ reading pairlist file /usr/local/etc/raddb/ What are those ^ - That's weird - why is it just the path and not the filename - do you have two include statements? Yes, it does not look right. Each of those corresponds to an extra $INCLUDE in the main users file.
I recompiled the freeRadius with the extra debug lines on my live server and its printing the filename correctly. Thanks, Kris http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
Hi Alan, freeradius1:/usr/local/etc/raddb # ls -lZ users* -rw-r--r-- 1 root root ? 10859 Aug 23 11:20 users -rw-r--r-- 1 root root ? 11979 Aug 22 13:19 users.group1 -rw-r--r-- 1 root root ? 3241 Aug 23 11:20 users.group2 Kris On 23/08/12 12:18, alan buxey wrote:
Hi,
So freeradius definitely not getting a handle on those files that looks to me more like a system issue that a radius. file permissions?
ls -lZ users*
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
Hi all, I fixed it by putting the absolute path to the users file. $INCLUDE /usr/local/etc/raddb/users.group1 $INCLUDE /usr/local/etc/raddb/users.group2 $INCLUDE /usr/local/etc/raddb/users.group3 like that. I tested this on Ubuntu 12.04 and OpenSUSE 12.1 (64bits) running on virtual server KVM/Qemu and OpenSUSE 12.1 (64bits) on physical server and it only manifests itself on OpenSUSE. Also tried it on OpenSUSE 11.4(32 bits) but no issue there. Thanks all, Kris On 23/08/12 12:45, Krzysztof Grobelak wrote:
Hi Alan,
freeradius1:/usr/local/etc/raddb # ls -lZ users* -rw-r--r-- 1 root root ? 10859 Aug 23 11:20 users -rw-r--r-- 1 root root ? 11979 Aug 22 13:19 users.group1 -rw-r--r-- 1 root root ? 3241 Aug 23 11:20 users.group2
Kris
On 23/08/12 12:18, alan buxey wrote:
Hi,
So freeradius definitely not getting a handle on those files that looks to me more like a system issue that a radius. file permissions?
ls -lZ users*
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
http://www.livelinx.tv/ NEW! See our Ka Uplink Van at IBC in Amsterdam; Stand OE 117, September 7-11, 2012
participants (5)
-
alan buxey -
Alan DeKok -
Arran Cudbard-Bell -
Klaus Klein -
Krzysztof Grobelak