- Freeradius-Users - lists.freeradius.org

Server Scaling
by David Peterson 09 Jan '14

09 Jan '14

I am wondering if anyone has an idea of the amount of hardware I would need to spec out to handle 50,000 EAP authentications per day. Would you recommend a secondary server for accounting? David

3 6

freeradius with ntlm-auth and server2012
by Carsten Czerner 09 Jan '14

09 Jan '14

Hi, I tried to setup a radius server with ntlm_auth but it didn't work. I used this howto for the basic setup: http://wiki.freeradius.org/guide/FreeRADIUS-Active-Directory-Integration-HO… And I made some progress: - The ntlm_auth returned "ok" - The radius_server accepted the pap-auth from the user-file But when I try to enable the ntlm_auth I get these results: +- entering group authorize {...} [ntlm_auth] expand: --username=%{mschap:User-Name} -> --username=peterpan [ntlm_auth] expand: --password=%{User-Password} -> --password=1234567 Exec-Program output: NT_STATUS_OK: Success (0x0) Exec-Program-Wait: plaintext: NT_STATUS_OK: Success (0x0) Exec-Program: returned: 0 ++[ntlm_auth] returns ok ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop ++[digest] returns noop [suffix] No '@' in User-Name = "peterpan", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user Why do I get this error? cat default / inner-tunnel authenticate { # # PAP authentication, when a back-end database listed # in the 'authorize' section supplies a password. The # password can be clear-text, or encrypted. Auth-Type PAP { pap } Auth-Type ntlm_auth { ntlm_auth Regards Carsten -------------- Complete Log root@rad1:~# freeradius -X FreeRADIUS Version 2.1.12, for host x86_64-pc-linux-gnu, built on Dec 16 2012 at 13:28:43 Copyright (C) 1999-2009 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 v2. Starting - reading configuration files ... including configuration file /etc/freeradius/radiusd.conf including configuration file /etc/freeradius/proxy.conf including configuration file /etc/freeradius/clients.conf including files in directory /etc/freeradius/modules/ including configuration file /etc/freeradius/modules/exec including configuration file /etc/freeradius/modules/detail.example.com including configuration file /etc/freeradius/modules/radutmp including configuration file /etc/freeradius/modules/attr_filter including configuration file /etc/freeradius/modules/detail.log including configuration file /etc/freeradius/modules/ldap including configuration file /etc/freeradius/modules/sql_log including configuration file /etc/freeradius/modules/etc_group including configuration file /etc/freeradius/modules/detail including configuration file /etc/freeradius/modules/smsotp including configuration file /etc/freeradius/modules/mschap including configuration file /etc/freeradius/modules/ntlm_auth including configuration file /etc/freeradius/modules/ippool including configuration file /etc/freeradius/modules/mac2vlan including configuration file /etc/freeradius/modules/unix including configuration file /etc/freeradius/modules/digest including configuration file /etc/freeradius/modules/otp including configuration file /etc/freeradius/modules/expiration including configuration file /etc/freeradius/modules/sradutmp including configuration file /etc/freeradius/modules/inner-eap including configuration file /etc/freeradius/modules/perl including configuration file /etc/freeradius/modules/soh including configuration file /etc/freeradius/modules/logintime including configuration file /etc/freeradius/modules/rediswho including configuration file /etc/freeradius/modules/echo including configuration file /etc/freeradius/modules/pap including configuration file /etc/freeradius/modules/always including configuration file /etc/freeradius/modules/pam including configuration file /etc/freeradius/modules/policy including configuration file /etc/freeradius/modules/wimax including configuration file /etc/freeradius/modules/dynamic_clients including configuration file /etc/freeradius/modules/krb5 including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login including configuration file /etc/freeradius/modules/checkval including configuration file /etc/freeradius/modules/expr including configuration file /etc/freeradius/modules/counter including configuration file /etc/freeradius/modules/replicate including configuration file /etc/freeradius/modules/realm including configuration file /etc/freeradius/modules/acct_unique including configuration file /etc/freeradius/modules/attr_rewrite including configuration file /etc/freeradius/modules/redis including configuration file /etc/freeradius/modules/chap including configuration file /etc/freeradius/modules/preprocess including configuration file /etc/freeradius/modules/opendirectory including configuration file /etc/freeradius/modules/mac2ip including configuration file /etc/freeradius/modules/linelog including configuration file /etc/freeradius/modules/cui including configuration file /etc/freeradius/modules/files including configuration file /etc/freeradius/modules/passwd including configuration file /etc/freeradius/modules/smbpasswd including configuration file /etc/freeradius/eap.conf including configuration file /etc/freeradius/policy.conf including files in directory /etc/freeradius/sites-enabled/ including configuration file /etc/freeradius/sites-enabled/inner-tunnel including configuration file /etc/freeradius/sites-enabled/default main { user = "freerad" group = "freerad" allow_core_dumps = no } including dictionary file /etc/freeradius/dictionary main { name = "freeradius" prefix = "/usr" localstatedir = "/var" sbindir = "/usr/sbin" logdir = "/var/log/freeradius" run_dir = "/var/run/freeradius" libdir = "/usr/lib/freeradius" radacctdir = "/var/log/freeradius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/var/run/freeradius/freeradius.pid" checkrad = "/usr/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no 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 } } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } client 193.174.32.73 { require_message_authenticator = no secret = "insecure" shortname = "firewall" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating module "exec" from file /etc/freeradius/modules/exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating module "expr" from file /etc/freeradius/modules/expr Module: Linked to module rlm_expiration Module: Instantiating module "expiration" from file /etc/freeradius/modules/expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating module "logintime" from file /etc/freeradius/modules/logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server { # from file /etc/freeradius/radiusd.conf modules { Module: Creating Auth-Type = NTLM-AUTH Module: Creating Auth-Type = digest Module: Creating Post-Auth-Type = REJECT Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating module "pap" from file /etc/freeradius/modules/pap pap { encryption_scheme = "auto" auto_header = no } Module: Instantiating module "ntlm_auth" from file /etc/freeradius/modules/ntlm_auth exec ntlm_auth { wait = yes program = "/usr/bin/ntlm_auth --request-nt-key --domain=ADINT.DIR --username=%{mschap:User-Name} --password=%{User-Password}" input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_chap Module: Instantiating module "chap" from file /etc/freeradius/modules/chap Module: Linked to module rlm_mschap Module: Instantiating module "mschap" from file /etc/freeradius/modules/mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = yes ntlm_auth = "/usr/bin/ntlm_auth --request-nt-key --username=%{%{Stripped-User-Name}:-%{%{User-Name}:-None}} --challenge=%{%{mschap:Challenge}:-00} --domain=%{mschap:NT-Domain} --nt-response=%{%{mschap:NT-Response}:-00}" allow_retry = yes } Module: Linked to module rlm_digest Module: Instantiating module "digest" from file /etc/freeradius/modules/digest Module: Linked to module rlm_unix Module: Instantiating module "unix" from file /etc/freeradius/modules/unix unix { radwtmp = "/var/log/freeradius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating module "eap" from file /etc/freeradius/eap.conf eap { default_eap_type = "peap" 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 = "/etc/freeradius/certs" pem_file_type = yes private_key_file = "/etc/freeradius/certs/server.key" certificate_file = "/etc/freeradius/certs/server.pem" CA_file = "/etc/freeradius/certs/ca.pem" private_key_password = "whatever" dh_file = "/etc/freeradius/certs/dh" random_file = "/dev/urandom" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/etc/freeradius/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/" } } Module: Linked to sub-module rlm_eap_ttls Module: Instantiating eap-ttls ttls { default_eap_type = "md5" copy_request_to_tunnel = no use_tunneled_reply = no 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 /etc/freeradius/modules/preprocess preprocess { huntgroups = "/etc/freeradius/huntgroups" hints = "/etc/freeradius/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_realm Module: Instantiating module "suffix" from file /etc/freeradius/modules/realm realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating module "files" from file /etc/freeradius/modules/files files { usersfile = "/etc/freeradius/users" acctusersfile = "/etc/freeradius/acct_users" preproxy_usersfile = "/etc/freeradius/preproxy_users" compat = "no" } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating module "acct_unique" from file /etc/freeradius/modules/acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating module "detail" from file /etc/freeradius/modules/detail detail { detailfile = "/var/log/freeradius/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 /etc/freeradius/modules/radutmp radutmp { filename = "/var/log/freeradius/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 /etc/freeradius/modules/attr_filter attr_filter attr_filter.accounting_response { attrsfile = "/etc/freeradius/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 "attr_filter.access_reject" from file /etc/freeradius/modules/attr_filter attr_filter attr_filter.access_reject { attrsfile = "/etc/freeradius/attrs.access_reject" key = "%{User-Name}" relaxed = no } } # modules } # server server inner-tunnel { # from file /etc/freeradius/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 radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 } ... adding new socket proxy address * port 35911 Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1 port 46572, id=207, length=78 User-Name = "peterpan" User-Password = "1234567" NAS-IP-Address = 127.0.1.1 NAS-Port = 1812 Message-Authenticator = 0x20147fc89d9fff841e5fa13785e48b9a # Executing section authorize from file /etc/freeradius/sites-enabled/default +- entering group authorize {...} [ntlm_auth] expand: --username=%{mschap:User-Name} -> --username=peterpan [ntlm_auth] expand: --password=%{User-Password} -> --password=1234567 Exec-Program output: NT_STATUS_OK: Success (0x0) Exec-Program-Wait: plaintext: NT_STATUS_OK: Success (0x0) Exec-Program: returned: 0 ++[ntlm_auth] returns ok ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop ++[digest] returns noop [suffix] No '@' in User-Name = "peterpan", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user Failed to authenticate the user. Login incorrect: [peterpan/1234567] (from client localhost port 1812) Using Post-Auth-Type Reject # Executing group from file /etc/freeradius/sites-enabled/default +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> peterpan attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 0 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 0 Sending Access-Reject of id 207 to 127.0.0.1 port 46572 Waking up in 4.9 seconds. Cleaning up request 0 ID 207 with timestamp +5 Ready to process requests. -- Mit freundlichen Grüßen Dipl. Inform. (FH) Carsten Czerner Medien- und Informationszentrum (MIZ) Leuphana Universität Lüneburg Scharnhorststraße 1, C7.217 21335 Lüneburg Fon 04131.677-1241 Fax 04131.677-1246

4 5

2.1.12: rlm_radutmp errors
by Karsten Honsack 09 Jan '14

09 Jan '14

Hello, this is my first mail to a mailinglist so please be patient. I am running three debian radius-servers using freeradius 2.1.12 with about 40 clients for service and wlan authentication. Everything runs fine but there is one client which always causes errors in the log and i would like to ask if somebody had a similar problem and any suggestions for a solution. The servers make no accounting. I get the following error message in the logs: Error: rlm_radutmp: NAS xxx port 0 unknown packet type 16777216) or Error: rlm_radutmp: NAS xxx port 0 unknown packet type 33554432) The Client Configuration is: client xxxx { ipaddr = xxx.xxx.xxx.xxx secret=xxx nas=other netmask = xx } The Client-Network uses pGina for Windows-Radius-Authentication. Thank you for your help! -- Rheinische Friedrich-Wilhelms-Universität Bonn Hochschulrechenzentrum Karsten Honsack Wegelerstraße 6 53115 Bonn Tel.: +49 (0)228 73-3456

2 2

Re: coa / proxy question
by Richard J Palmer 09 Jan '14

09 Jan '14

OK I now have part one of this done - radacct now holds the LNS IP address thank you. I just want to clarify one small thing if I may ... With the CoA I currently have one CoA server enabled on port 3799 on the radius server. How should I forward the CoA to the LNS ? Do I setup 2 CoA servers either on different ports or IPs within FreeRadius and each send to a different LNS, or Can FreeRadius itself do a SQL query based on the AcctUniqueId and use that to get the IP to forward to ? Or have I again got this totally wrong ? Thanks in advance I do appreciate your help -- Richard Palmer | Director | Merula Limited Company Registered in England and Wales No. 3243995 5 Avro Court, Huntingdon, Cambridgeshire, PE29 6XS Phone 01480 222940 | Support 0845 330 0666 Support Email support(a)merula.net > --- Original message --- > Subject: Re: coa / proxy question > From: Alan DeKok <aland(a)deployingradius.com> > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Date: Monday, 06/01/2014 3:29 PM > > Richard J Palmer wrote: >> >> What I would ideally like to do (simple solution) is send the coa >> request to both LNS routers - one will obviously say 'no match' the >> other will correctly affect the session. With the pool set to failover >> I >> find that second LNS is not sent the coa as the first LNS replied >> (albeit saying no match), load balance works 50/50. > > That's a terrible solution. > >> >> Is there a simple way to configure coa to send the request to both >> here. > > No. Packets go to ONE destination, and ONLY one destination. > >> >> I'm also open to any betrter routes to do this > > Add a column to the accounting table. It should be "LNS IP > Address". > Then, update the accounting queries to store Packet-Src-IP-Address > there. > > For CoA, you just look up the session in the accounting table, and > sent the CoA packet to the LNS IP Address. > > Alan DeKok. > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html

2 1

Question about FreeRadius client programming
by Alexandre Harly 08 Jan '14

08 Jan '14

Hello, I am using the freeRadius client sample to do my own client and it appears that the request sent by this client contains a non crypted password. (I checked with Wireshark). Where can I find the documentation about the way to make the password being crypter ? Did I forgot something ? My source is below. Thanks a lot ! rh = rc_new(); rh = rc_config_init(rh); rc_add_config(rh, "auth_order", "radius", "config", 0); rc_add_config(rh, "login_tries", "4", "config", 0); rc_add_config(rh, "dictionary", "......./dictionary", "config", 0); rc_add_config(rh, "seqfile", "........./radius.seq", "config", 0); rc_add_config(rh, "radius_retries", "3", "config", 0); rc_add_config(rh, "radius_timeout", "5", "config", 0); rc_add_config(rh, "acctserver", "my_ip:my_port:my_secret", "config", 0); rc_read_dictionary(rh, rc_conf_str(rh, "dictionary")); rc_avpair_add(rh, &send, PW_USER_NAME, "my_login", -1, 0); rc_avpair_add(rh, &send, PW_CHAP_PASSWORD, "my_pwd", -1, 0); rc_auth(rh, 0, send, &received, msg);

2 3

Re: restarting? database, radius
by Ryan Milton 07 Jan '14

07 Jan '14

Got it. On 1/7/14, 3:57 PM, "Alan DeKok" <aland(a)deployingradius.com> wrote: >Ryan Milton wrote: >> The error log show the following (I don’t understand it): >> >> /var/db/mysql/serv03XXX.net.err  >> >> 140107 20:20:22 mysqld_safe Starting mysqld daemon with databases from >> /usr/local/data >> ^G/usr/local/libexec/mysqld: Can't find file: './mysql/plugin.frm' >> (errno: 13) > > Ask the MySQL people about MySQL. > > Once you have MySQL working properly, *then* you can look at any >issues with FreeRADIUS. > > Alan DeKok. >- >List info/subscribe/unsubscribe? See >http://www.freeradius.org/list/users.html

1 0

FW: restarting? database, radius
by Ryan Milton 07 Jan '14

07 Jan '14

From: Ryan Milton <rmilton(a)mvsusa.com<mailto:rmilton@mvsusa.com>> Date: Tuesday, January 7, 2014 at 3:16 PM To: "freeradius-users(a)lists.freeradius.org<mailto:freeradius-users@lists.freeradius.org>" <freeradius-users(a)lists.freeradius.org<mailto:freeradius-users@lists.freeradius.org>> Subject: restarting? database, radius Hi, I am using FreeRADIUS 2.1 on a FreeBSD 8.2 In the process of inserting lines into tables on the master server, one server, the one in question wasn’t replicating properly. I attempted to stop radius - /usr/local/etc/rc.d/radiusd stop  and restart MySQL - /usr/local/etc/rc.d/mysql-server restart But that did not work. when I ran a tail command on the radius.log file, I got these errors: Tue Jan 7 20:18:00 2014 : Error: Failed to load clients from SQL. Tue Jan 7 20:18:00 2014 : Info: rlm_sql (sql): Closing sqlsocket 4 Tue Jan 7 20:18:00 2014 : Info: rlm_sql (sql): Closing sqlsocket 3 Tue Jan 7 20:18:00 2014 : Info: rlm_sql (sql): Closing sqlsocket 2 Tue Jan 7 20:18:00 2014 : Info: rlm_sql (sql): Closing sqlsocket 1 Tue Jan 7 20:18:00 2014 : Info: rlm_sql (sql): Closing sqlsocket 0 Tue Jan 7 20:18:00 2014 : Error: /usr/local/etc/raddb/sql.conf[22]: Instantiation failed for module "sql" Tue Jan 7 20:18:00 2014 : Error: /usr/local/etc/raddb/sites-enabled/default[177]: Failed to load module "sql". Tue Jan 7 20:18:00 2014 : Error: /usr/local/etc/raddb/sites-enabled/default[69]: Errors parsing authorize section. Tue Jan 7 20:18:00 2014 : Error: Failed to load virtual server <default> The error log show the following (I don’t understand it): /var/db/mysql/serv03XXX.net.err  140107 20:20:22 mysqld_safe Starting mysqld daemon with databases from /usr/local/data ^G/usr/local/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 140107 20:20:22 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 140107 20:20:22 InnoDB: The InnoDB memory heap is disabled 140107 20:20:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140107 20:20:22 InnoDB: Compressed tables use zlib 1.2.3 140107 20:20:22 InnoDB: Initializing buffer pool, size = 128.0M 140107 20:20:22 InnoDB: Completed initialization of buffer pool 140107 20:20:22 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'create'. InnoDB: Cannot continue operation. 140107 20:20:22 mysqld_safe mysqld from pid file /usr/local/data/serv03.ams5.bganglobalnet.net.pid ended 140107 20:23:33 mysqld_safe Starting mysqld daemon with databases from /usr/local/data ^G/usr/local/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 140107 20:23:33 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 140107 20:23:33 InnoDB: The InnoDB memory heap is disabled 140107 20:23:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140107 20:23:33 InnoDB: Compressed tables use zlib 1.2.3 Now, I’m getting this beloved error when I attempt to go back into the MySQL db: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) I am completely new at this, but I hesitate to do anything drastic to the server since I don’t fully understand it. Thanks in advance for any assistance, Ryan

3 2

RE: Order of loading modules
by stefan.paetow＠diamond.ac.uk 07 Jan '14

07 Jan '14

Compare your two perl modules. The FreeRADIUS configuration might be identical, but the *CONTENTS* of the /product/freeradius-server-2.1.12_0/etc/raddb//modules/perl files are different between the two servers. On the one, the default example.pl is listed as the perl module. On the other, the module to load has been specified as perl_Originale. Read the debug output carefully when you look at the log, and you would notice the difference. It’s subtle, but it’s there. Stefan From: freeradius-users-bounces+stefan.paetow=diamond.ac.uk(a)lists.freeradius.org [mailto:freeradius-users-bounces+stefan.paetow=diamond.ac.uk@lists.freeradius.org] On Behalf Of Francesco Maisano Sent: 07 January 2014 00:13 To: FreeRadius users mailing list Subject: Re: Order of loading modules Sorry Alan, i see my configuration in instantiate section and I do not understand where it is shown the load order of the modules, please explain me. Below my radiusd.conf (same file for each servers) and startup of freeradius in debug mode on server A and on server B and you see the difference in loading modules order. Debug log info: radius_debug_server_A.log --> be careful to line number 46 (load perl module) and 62 (load perl_Originale module) radius_debug_server_B.log --> be careful to line number 45 (load perl_Originale module) and 58 (load perl module) [snipped for brevity] -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

1 0

Order of loading modules
by Francesco Maisano 07 Jan '14

07 Jan '14

Hi all, I need to known the order of loading of freeradius modules because i have two server with same configuration but when i start freeradius on server 1 charge, in order, module x (perl) and y (perl_Original) after, on server 2 viceversa. This info is needed because i have modified the perl module and first, i have saved the original perl with name perl_Original and i have modified the perl with the execution of my perl script. Best regards maframan My servers: Freeradius version 2.1.12 with perl library 5.14.2 on solaris SPARC 10 operating system

4 14

Defects - A reminder
by Arran Cudbard-Bell 07 Jan '14

07 Jan '14

The following can be found bundled with the server in doc/bugs and at https://github.com/FreeRADIUS/freeradius-server/blob/master/doc/bugs. 1.YOU FOUND A BUG Where the server terminates ungracefully due to a bus error, segmentation violation, or other memory error, you should create a new issue in the issue tracker <URL: http://bugs.freeradius.org>, including information from sections 4 and 5. For other issues, you should first discuss them on the users list, to see if anyone can reproduce them. Often there's a simple explanation of why the server behaves as it does, and it's not necessarily a bug in the code, so browse the lists' archives of the last two months, and if you don't see messages about it, ask! If the behavior is correct but confusing, we think that's a bug too, and you should file a bug against our documentation. For more information about the users list, the lists' archives and the faq, please visit http://www.freeradius.org/list/users.html Please make sure to READ and RESPECT the house-rules. You will get much better response and much faster if you do! 2.CORE DUMPS If the server, or one of the accompyaning programs core dumps, then you should rebuild the server as follows: $ ./configure --enable-developer $ make $ make install and then run the program again. You may have to to enable core dumps, via: $ ulimit -c unlimited When it core dumps, do: $ gdb /path/to/executable /path/to/core/file Enable logging in gdb via the following commands: (gdb) set logging file gdb-radiusd.log (gdb) set logging on and follow the instructions in section 4, below. 3. DEBUGGING A LIVE SERVER If you can't get a core dump, or the problem doesn't result in a core dump, you may have to run the server under gdb. To do this, ensure that you have symbols in the binaries (i.e. a non-stripped binary) by re-building the server as described in the previous section. Then, run the server under gdb as follows: $ gdb radiusd Enable logging in gdb via the following commands: (gdb) set logging file gdb-radiusd.log (gdb) set logging on Tell gdb to pass any necessary command-line arguments to the server: (gdb) set args ... Where the "..." are the command-line arguments you normally pass to radiusd. Fo debugging, you probably want to do: (gdb) set args -f Then, do: (gdb) run When something interesting happens, you can hit CTRL-C in the window, and you should be back at the gdb prompt: (gdb) And follow the instructions in section 4, below. 4. OBTAINING USEFUL INFORMATION Once you have a core dump loaded into gdb, or FreeRADIUS running under gdb, you may use the commands below to get useful information about the state of the server. If the server was built with threads, you can do: (gdb) info threads Which will give you information about the threads. If the server isn't threaded, that command-line will print a message saying so. Then, do: (gdb) thread apply all bt full If the server isn't threaded, the "thread apply" section isn't necessary The output should be printed to the screen, and also sent to the gdb-radiusd.log file. You should then submit the information from the log file, along with any server output, the output of radiusd -xv, and information about your operating system to: http://bugs.freeradius.org/ Submitting it to the bug database ensures that the bug report won't get forgotten, and that it will be dealt with in due course. You should provide the issue number in any mail sent to the user's list. 5. VALGRIND On Linux systems, "valgrind" is a useful tool that can catch certain classes of bugs. To use it, run the server via: $ valgrind --tool=memcheck --leak-check=full radiusd -Xm It will print out certain kinds of errors to the screen. There may be a number of errors related to OpenSSL, dlopen(), or libtldl. We cannot do anything about those problems. However, any errors that are inside of the FreeRADIUS source should be brought to our attention. 6. Running with "screen" If the bug is a crash of the server, and it takes a long time for the crash to happen, perform the following steps: * log in as root * open a screen session (http://blogamundo.net/code/screen/) $ screen bash * make sure FreeRADIUS is not running * make sure you have all the debug symbols about, or a debugable version of the server installed * configure screen to log to a file; 'Ctrl-A H' * type 'gdb /path/to/radius' (or /path/to/freeradius on Debian) * at the (gdb) prompt, type 'run -X' * detach from screen 'Ctrl-A D' * when you notice FreeRADIUS has died, reconnect to your screen session $ screen -D -r * at the (gdb) prompt type 'where' or for *lots* of info try 'thread apply all bt full' * tell screen to stop logging, 'Ctrl-A H' * logout from screen -- FreeRADIUS Project, copyright 2014 Arran Cudbard-Bell <a.cudbardb(a)freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

2 1