June 2018 - Freeradius-Users - lists.freeradius.org

password is in Cleartext-Password and NOT in User-Password
by Philemon Jaomalaza 28 Jun '18

28 Jun '18

Hello Dear, I use freeradius 3 and daloradius to manage the user on SQL. When I create manually the username and do a Password-Type in Cleartext-Password, The Acces request match the good password. When I create the users from Daloradius Batch User form, the Paswword-Type is in User-Password, and no option to change it, then the Acces Request doesn't match a good password. It show PAP warning below : ......................... .......................... (3) [sql] = ok (3) [expiration] = noop (3) [logintime] = noop (3) pap: WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! (3) pap: WARNING: !!! Ignoring control:User-Password. Update your !!! (3) pap: WARNING: !!! configuration so that the "known good" clear text !!! (3) pap: WARNING: !!! password is in Cleartext-Password and NOT in !!! (3) pap: WARNING: !!! User-Password. !!! (3) pap: WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! (3) pap: WARNING: No "known good" password found for the user. Not setting Auth-Type (3) pap: WARNING: Authentication will fail unless a "known good" password is available (3) [pap] = noop (3) } # authorize = ok (3) ERROR: No Auth-Type found: rejecting the user via Post-Auth-Type = Reject (3) Failed to authenticate the user (3) Using Post-Auth-Type Reject ............................ .......................... Is this an issue on my freeradius seting ? Can I change the password type in Cleartext-Password somewhere ? How can I do to solve thie issues ? jmlz

2 2

attr_filter/post-proxy - question
by Bornemann, Hans 28 Jun '18

28 Jun '18

Hi, we are using the post-proxy for putting the user in the their vlan. Everything is working fine, if the realm looks like this itmc Tunnel-Private-Group-ID :=5, Fall-Through = Yes # But we want to use itmc.tu-dortmund.de as realm and itmc.tu-dortmund.de Tunnel-Private-Group-ID :=5, Fall-Through = Yes # doesn't work. Regards Hans Bornemann Abteilung Datanet Technische Universität Dortmund ITMC Otto-Hahn-Str. 12 44227 Dortmund Tel.: +49 231-755 2132 hans.bornemann(a)tu-dortmund.de www.itmc.tu-dortmund.de Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.

2 1

authentication request failed for SSH using freeradius server.
by Hailun Tan 28 Jun '18

28 Jun '18

Hi, I figured out why the server failed to respond.. I need to set "require-message-authenticator = no" for that particular client IP address in the client.conf under /etc/freeradius on the server side. However, there are still heaps of other issues after this one was shot down. Now it seems the password for the user cannot be passed to the radius server correctly when ssh was executed. After checking the /var/log/auth.log on the client machine, it has following items (in bold face) which worries me: Jun 25 16:23:15 dev-ldap-server sshd[25675]: pam_radius_auth: Got user name micfox Jun 25 16:23:15 dev-ldap-server sshd[25675]: pam_radius_auth: ignore last_pass, force_prompt set Jun 25 16:23:15 dev-ldap-server sshd[25672]: Postponed keyboard-interactive for invalid user micfox from 127.0.0.1 port 37892 ssh2 [preauth] Jun 25 16:23:19 dev-ldap-server sshd[25675]: pam_radius_auth: Sending RADIUS request code 1 Jun 25 16:23:19 dev-ldap-server sshd[25675]: pam_radius_auth: DEBUG: get_ipaddr(10.10.150.134) returned 0. Jun 25 16:23:20 dev-ldap-server sshd[25675]: pam_radius_auth: Got RADIUS response code 3 Jun 25 16:23:20 dev-ldap-server sshd[25675]: pam_radius_auth: authentication failed Jun 25 16:23:20 dev-ldap-server sshd[25675]: pam_radius_auth: Got user name micfox Jun 25 16:23:20 dev-ldap-server sshd[25675]: pam_radius_auth: ignore last_pass, force_prompt set *Jun 25 16:23:20 dev-ldap-server sshd[25675]: pam_radius_auth: Got password #010#012#015INCOR* Jun 25 16:23:20 dev-ldap-server sshd[25675]: pam_radius_auth: Sending RADIUS request code 1 Jun 25 16:23:20 dev-ldap-server sshd[25675]: pam_radius_auth: DEBUG: get_ipaddr(10.10.150.134) returned 0. Jun 25 16:23:21 dev-ldap-server sshd[25675]: pam_radius_auth: Got RADIUS response code 3 Jun 25 16:23:21 dev-ldap-server sshd[25675]: pam_radius_auth: authentication failed *"#010#012#015INCOR" *is definitely not the password the user "micfox" has *.* I run the freeradius in debug mode on the server side. As expected, the authentication failed due to the incorrect password. Ready to process requests. rad_recv: Access-Request packet from host 10.10.150.136 port 52388, id=151, length=91 User-Name = "micfox" * User-Password = "\010\n\r\177INCOR"* NAS-IP-Address = 10.10.150.136 NAS-Identifier = "sshd" NAS-Port = 26140 NAS-Port-Type = Virtual Service-Type = Authenticate-Only Calling-Station-Id = "10.10.150.136" # Executing section authorize from file /etc/freeradius/sites-enabled/ default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "micfox", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] No EAP-Message, not doing EAP ++[eap] = noop [sql] expand: %{User-Name} -> micfox [sql] sql_set_user escaped user --> 'micfox' rlm_sql (sql): Reserving sql socket id: 14 [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 = 'micfox' ORDER BY id [sql] User found in radcheck table [sql] expand: SELECT id, username, attribute, value, op FROM radreply WHERE username = '%{SQL-User-Name}' ORDER BY id -> SELECT id, username, attribute, value, op FROM radreply WHERE username = 'micfox' ORDER BY id [sql] expand: SELECT groupname FROM radusergroup WHERE username = '%{SQL-User-Name}' ORDER BY priority -> SELECT groupname FROM radusergroup WHERE username = 'micfox' ORDER BY priority [sql] expand: SELECT id, groupname, attribute, Value, op FROM radgroupcheck WHERE groupname = '%{Sql-Group}' ORDER BY id -> SELECT id, groupname, attribute, Value, op FROM radgroupcheck WHERE groupname = 'test' ORDER BY id [sql] User found in group test [sql] expand: SELECT id, groupname, attribute, value, op FROM radgroupreply WHERE groupname = '%{Sql-Group}' ORDER BY id -> SELECT id, groupname, attribute, value, op FROM radgroupreply WHERE groupname = 'test' ORDER BY id rlm_sql (sql): Released sql socket id: 14 ++[sql] = ok ++[expiration] = noop ++[logintime] = noop ++[pap] = updated +} # group authorize = updated Found Auth-Type = PAP # Executing group from file /etc/freeradius/sites-enabled/default +group PAP { *[pap] login attempt with password "? INCOR"*[pap] Using clear text password "micfox001" [pap] Passwords don't match ++[pap] = reject +} # group PAP = reject Failed to authenticate the user. WARNING: Unprintable characters in the password. Double-check the shared secret on the server and the NAS! Using Post-Auth-Type Reject # Executing group from file /etc/freeradius/sites-enabled/default +group REJECT { [sql] expand: %{User-Name} -> micfox [sql] sql_set_user escaped user --> 'micfox' [sql] expand: %{User-Password} -> =5C010=5Cn=5Cr=5C177INCOR [sql] expand: INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( '%{User-Name}', '%{%{User-Password}:-%{Chap-Password}}', '%{reply:Packet-Type}', '%S') -> INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( 'micfox', '=5C010=5Cn=5Cr=5C177INCOR', 'Access-Reject', '2018-06-25 16:45:25') rlm_sql (sql) in sql_postauth: query is INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( 'micfox', '=5C010=5Cn=5Cr=5C177INCOR', 'Access-Reject', '2018-06-25 16:45:25') rlm_sql (sql): Reserving sql socket id: 13 rlm_sql (sql): Released sql socket id: 13 ++[sql] = ok [eap] Request didn't contain an EAP-Message, not inserting EAP-Failure ++[eap] = noop [attr_filter.access_reject] expand: %{User-Name} -> micfox attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] = updated +} # group REJECT = updated Delaying reject of request 8 for 1 seconds *=============* I then check the code in pam_radius_auth.c for the shared library paM_radius_auth.so. I wonder where the password was actually retrieved from the conversation function of PAM session. That is the first question I would like to ask. However, it is not the end of the problems. I now edited the code in pam_radius_auth.c to offer a hard-coded correct password for the user ,micfox (i.e., the correct password is "micfox001"). Then the user authentication passes in both client and server side for this connection. However, the user still cannot open the ssh session. On the client side, the /var/user/auth.log shows the following error: ====================== Jun 25 16:45:29 dev-ldap-server sshd[26137]: pam_radius_auth: Got user name micfox Jun 25 16:45:29 dev-ldap-server sshd[26137]: pam_radius_auth: Sending RADIUS request code 1 Jun 25 16:45:29 dev-ldap-server sshd[26137]: pam_radius_auth: DEBUG: get_ipaddr(10.10.150.134) returned 0. Jun 25 16:45:30 dev-ldap-server sshd[26137]: pam_radius_auth: Got RADIUS response code 3 Jun 25 16:45:30 dev-ldap-server sshd[26137]: pam_radius_auth: authentication failed Jun 25 16:45:30 dev-ldap-server sshd[26137]: pam_radius_auth: Got user name micfox Jun 25 16:45:30 dev-ldap-server sshd[26137]: pam_radius_auth: ignore last_pass, force_prompt set Jun 25 16:45:30 dev-ldap-server sshd[26137]: pam_radius_auth: Got password micfox001 Jun 25 16:45:30 dev-ldap-server sshd[26137]: pam_radius_auth: Sending RADIUS request code 1 Jun 25 16:45:30 dev-ldap-server sshd[26137]: pam_radius_auth: DEBUG: get_ipaddr(10.10.150.134) returned 0. Jun 25 16:45:31 dev-ldap-server sshd[26137]: pam_radius_auth: Got RADIUS response code 2 Jun 25 16:45:31 dev-ldap-server sshd[26137]: pam_radius_auth: authentication succeeded J*un 25 16:45:31 dev-ldap-server sshd[26137]: Failed password for invalid user micfox from 10.10.150.136 port 33330 ssh2* Jun 25 17:09:01 dev-ldap-server CRON[26274]: pam_unix(cron:session): session opened for user root by (uid=0) Jun 25 17:09:03 dev-ldap-server CRON[26274]: pam_unix(cron:session): session closed for user root ================ I am totally lost for that bold-face message. even though the user authentication passes, why is the "Failed password for invalid user" still shows up??? Can ssh actually use pam_radius_auth.so for user authentication?? Please advise how to fix it as I really do not have any clue now... On Mon, Jun 25, 2018 at 2:56 PM, Hailun Tan <dearambermini(a)gmail.com> wrote: > I am trying to perform the user authentication via freeradius server on > the ssh conection. > > I have setup the free radius server according to the wiki pages: > > https://wiki.freeradius.org/guide/Getting-Started > > > In addition, I managed to install the dolaradius to manage the free > radius. I have run the radtest for the servers. > > The configurations for the radius server is: > free radius server IP: 10.10.150.134 > free radius server port: 1812 > master secret: NOJA > user name: micfox > user password: micfox001 > > > On the client machine (client IP: 10.10.150.136), I run the following > command: > > *dev-ldap-server: radtest micfox micfox001 10.10.150.134:1812 > <http://10.10.150.134:1812> 1812 NOJA* > Sending Access-Request of id 5 to 10.10.150.134 port 1812 > User-Name = "micfox" > User-Password = "micfox001" > NAS-IP-Address = 10.10.150.136 > NAS-Port = 1812 > Message-Authenticator = 0x00000000000000000000000000000000 > rad_recv: Access-Accept packet from host 10.10.150.134 port 1812, id=5, > length=38 > Service-Type = Framed-User > Framed-Protocol = PPP > Framed-Compression = Van-Jacobson-TCP-IP > > So it should prove the free radius server is up and running. > > > However, I have configured to use the pam-freeradius-auth.so to hookup > with the PAM modules on the client machine to authenticate the ssh user. it > does not work. I have updated the /etc/pam.d/sshd as follows: > =========== > > > *auth sufficient pam_radius_auth.so debug skip_passwd*# PAM configuration > for the Secure Shell service > > # Standard Un*x authentication. > @include common-auth > > # Disallow non-root logins when /etc/nologin exists. > account required pam_nologin.so > > # Uncomment and edit /etc/security/access.conf if you need to set complex > # access limits that are hard to express in sshd_config. > # account required pam_access.so > > # Standard Un*x authorization. > @include common-account > > # SELinux needs to be the first session rule. This ensures that any > # lingering context has been cleared. Without this it is possible that a > # module could execute code in the wrong domain. > session [success=ok ignore=ignore module_unknown=ignore > default=bad] pam_selinux.so close > > # Set the loginuid process attribute. > session required pam_loginuid.so > > # Create a new session keyring. > session optional pam_keyinit.so force revoke > > # Standard Un*x session setup and teardown. > @include common-session > > # Print the message of the day upon successful login. > # This includes a dynamically generated part from /run/motd.dynamic > # and a static (admin-editable) part from /etc/motd. > session optional pam_motd.so motd=/run/motd.dynamic > session optional pam_motd.so noupdate > > # Print the status of the user's mailbox upon successful login. > session optional pam_mail.so standard noenv # [1] > > # Set up user limits from /etc/security/limits.conf. > session required pam_limits.so > > # Read environment variables from /etc/environment and > # /etc/security/pam_env.conf. > session required pam_env.so # [1] > # In Debian 4.0 (etch), locale-related environment variables were moved to > # /etc/default/locale, so read that as well. > session required pam_env.so user_readenv=1 > envfile=/etc/default/locale > > # SELinux needs to intervene at login time to ensure that the process > starts > # in the proper default security context. Only sessions which are intended > # to run in the user's context should be run after this. > session [success=ok ignore=ignore module_unknown=ignore > default=bad] pam_selinux.so open > > # Standard Un*x password updating. > @include common-password > > > But now when I run the ssh micfox(a)10.10.150.136 (freeradius client's iP). > the /var/log/auth.log has the following error messages: > > > Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: Got user name > micfox > Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: ignore > last_pass, force_prompt set > Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: Sending > RADIUS request code 1 > Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: DEBUG: > get_ipaddr(10.10.150.134) is available. (1812) > Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: DEBUG: > talk_radius(0x86960a0a) is available (1812,port). > Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: DEBUG: > waiting for response from radius server 10.10.150.134 with port 1812 > (master secret: NOJA). > *Jun 25 12:05:54 dev-ldap-server sshd[6441]: pam_radius_auth: RADIUS > server 10.10.150.134 failed to respond* > Jun 25 12:05:54 dev-ldap-server sshd[6441]: pam_radius_auth: All RADIUS > servers failed to respond. > Jun 25 12:05:54 dev-ldap-server sshd[6441]: pam_radius_auth: > authentication failed > Jun 25 12:05:54 dev-ldap-server sshd[6438]: Postponed keyboard-interactive > for invalid user micfox from 127.0.0.1 port 37362 ssh2 [preauth] > > > > The RADIUS server always failed to respond.. > > I have configured the /etc/pam_radius_auth.conf as follows: > > > > # pam_radius_auth configuration file. Copy to: /etc/raddb/server > # > # For proper security, this file SHOULD have permissions 0600, > # that is readable by root, and NO ONE else. If anyone other than > # root can read this file, then they can spoof responses from the server! > # > # There are 3 fields per line in this file. There may be multiple > # lines. Blank lines or lines beginning with '#' are treated as > # comments, and are ignored. The fields are: > # > # server[:port] secret [timeout] > # > # the port name or number is optional. The default port name is > # "radius", and is looked up from /etc/services The timeout field is > # optional. The default timeout is 3 seconds. > # > # If multiple RADIUS server lines exist, they are tried in order. The > # first server to return success or failure causes the module to return > # success or failure. Only if a server fails to response is it skipped, > # and the next server in turn is used. > # > # The timeout field controls how many seconds the module waits before > # deciding that the server has failed to respond. > # > # server[:port] shared_secret timeout (s) > *10.10.150.134:1831 <http://10.10.150.134:1831> NOJA 3* > #other-server other-secret 3 > > # > # having localhost in your radius configuration is a Good Thing. > # > # See the INSTALL file for pam.conf hints. > > > I believed I should have setup everything correctly?? why is the > radius-pam-auth.so not working with the error message, > > * RADIUS server 10.10.150.134 failed to respond??* > I have prolonged the timeout parameter from 3 seconds to 60 seconds but it > did not work. > > If the radius server is not correctly set, it should not even pass the > radtest before. But why there is no response from the radius server for > freeradius-pam-auth.so if the server does work?? what could go wrong from > the configurations on the pam-radius module? > > Please advise >

3 6

How to update user's Session-Time attribute through Coa
by prometeotv＠tiscali.it 27 Jun '18

27 Jun '18

Hi guys I am running freeradius ver 2.2.6.7 on CentOS 6.0. I have configured freeradius with sql_counter module and all is working fine: users are disconnected when they reached the time or traffic assigned. Now my goal is to implement CoA on freeradius in order to update the Time (Session-Timeout) and Traffic (Mikrotik-Xmit-Limit) attribute, every time the NAS server (Mikrotik) sends the interim update packet, : how can I achieve that? I add this inside the accounting section of the file /ETC/SITE-AVAILABLE/DEFAULT #COA update coa { User-Name = "%{User-Name}" Acct-Session-Id = "%{Acct-Session-Id}" NAS-IP-Address = "%{NAS-IP-Address}" Framed-IP-Address = "%{Framed-IP-Address}" Session-Timeout = "%{Session-Timeout}" } update control { Send-CoA-Request = Yes } and this inside CLIENTS.CONF: client 0.0.0.0/0 { secret = xxxxxxx require_message_authenticator = no nastype = other } #COA home_server piazzalaterale-coa { type = coa # # Note that a home server of type "coa" MUST be a real NAS, # with an ipaddr or ipv6addr. It CANNOT point to a virtual # server. # ipaddr = 192.168.0.201 port = 3799 # This secret SHOULD NOT be the same as the shared # secret in a "client" section. secret = xxxxxx # CoA specific parameters. See raddb/proxy.conf for details. coa { irt = 2 mrt = 16 mrc = 5 mrd = 30 } } but when the CoA packet is sent to the NAS the Session-Timeout attribute is set to 0 instead of to the residual credit time of the user. I need that because if two people log-in simultaneosly with the same username, they should share the credit time/traffic instead, without CoA, they will both have the same credit Sorry for my English....I hope to have been clear Best regards Con MyOpen hai Giga, SMS e i minuti che vuoi da 3€ al mese, per sempre. Cambi gratis quando e come vuoi e in più hai 10€ di credito omaggio! SCOPRI DI PIU’ http://tisca.li/MailHPMobile

2 1

best practice for user permissions
by Samuel LEFOL 27 Jun '18

27 Jun '18

Hello, I'm using freeradius 3.0.12 with rlm_ldap authentication. I configured it as suggested in README: authorize { ... ldap if ((ok || updated) && User-Password) { update control { Auth-Type := ldap } } ... } authenticate { ... Auth-Type ldap { ldap } ... } I wonder what is the best practice for user permissions. 1. in users file : DEFAULT Auth-Type := ldap, LDAP-Group == "reseau" cisco-avpair :="shell:priv-lvl=15" DEFAULT Auth-Type := Reject OR 2. in post-auth section if (LDAP-Group == "reseau") { update reply { cisco-avpair :="shell:priv-lvl=15" } } else { reject } Could someone give me an explanation of the best way to go ? Best regards, Sam

3 4

Using rlm_rest for authorization and sqlcounters for session and bandwidth limits
by Rohith Asrk 27 Jun '18

27 Jun '18

Hi everyone, I'm working on a feature for being able to enforce session and bandwidth limits on users using a web interface of django-freeradius. I wish to authenticate the users using the rlm_rest module and use custom defined sqlcounters for putting limits on users. For ex., sqlcounter dailybandwidthcounter { counter_name = Max-Daily-Session-Traffic check_name = Max-Daily-Session-Traffic sql_module_instance = sql key = 'User-Name' reset = daily Reply-Message = "Your daily bandwidth limit has reached" query = "SELECT sum(AcctOutputOctets) + sum(AcctInputOctets) FROM radacct WHERE \ UserName = '%{${key}}' AND \ acctstarttime BETWEEN FROM_UNIXTIME('%%b') AND FROM_UNIXTIME('%%e')" } I'm not sure about configuring the FreeRADIUS configuration for accomplishing this. My authorize section looks like authorize { # ... dailybandwidthcounter rest # ... } I wish to use the concept of radius groups to implement this feature, i.e., add instances of radgroupcheck with attributes like Max-Daily-Session-Traffic so that the dailybandwidth counter checks it and puts the limits. I tried testing it with radclient and radtest but haven't been able to see any results. Am I going the right way? Can anyone help me with the concept of enforcing limits and also configuration? Regards, Rohith ASRK

2 4

Accounting Request
by Muhammed Buvaydani 27 Jun '18

27 Jun '18

I working on freeradius twith fortigate firewall . every things go fine and now I can make authentication and accounting. My problem is when making authentication for any user accounting-request from nas is send to Radius server and the user's info will insert again into radacct table, which will make big wrong in my program This is the Radius - x result when making authentication Sending Access-Accept of id 78 to 10.10.0.103 port 1030 Cisco-AVPair = "shell:priv-lvl=1" Idle-Timeout = 1000 Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Accounting-Request packet from host 10.10.0.103 port 1030, id=79, leng th=122 Acct-Status-Type = Start Acct-Session-Id = "1018bc85" User-Name = "10966417880" NAS-Identifier = "ftg" Framed-IP-Address = 192.168.33.4 Fortinet-Client-IP-Address = 192.168.33.4 Fortinet-Vdom-Name = "root" NAS-IP-Address = 10.10.0.20 Called-Station-Id = "10.10.0.20" Calling-Station-Id = "192.168.33.4" Event-Timestamp = "Jun 27 2018 16:44:33 +03" # Executing section preacct from file /etc/freeradius/sites-enabled/default.save +group preacct { ++[preprocess] = ok [acct_unique] WARNING: Attribute NAS-Port was not found in request, unique ID MA Y be inconsistent [acct_unique] Hashing ',NAS-Identifier = "ftg",NAS-IP-Address = 10.10.0.20,Acct- Session-Id = "1018bc85",User-Name = "10966417880"' [acct_unique] Acct-Unique-Session-ID = "a5d8f840a1843c92". ++[acct_unique] = ok [suffix] No '@' in User-Name = "10966417880", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop +} # group preacct = ok # Executing section accounting from file /etc/freeradius/sites-enabled/default.s ave +group accounting { [detail] expand: %{Packet-Src-IP-Address} -> 10.10.0.103 [detail] expand: /var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:- %{Packet-Src-IPv6-Address}}/detail-%Y%m%d -> /var/log/freeradius/radacct/10.10.0 .103/detail-20180627 [detail] /var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IP v6-Address}}/detail-%Y%m%d expands to /var/log/freeradius/radacct/10.10.0.103/de tail-20180627 [detail] expand: %t -> Wed Jun 27 16:44:33 2018 ++[detail] = ok [sradutmp] expand: /var/log/freeradius/sradutmp -> /var/log/freeradius/srad utmp [sradutmp] expand: %{User-Name} -> 10966417880 rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! ++[sradutmp] = noop [sql] expand: %{User-Name} -> 10966417880 [sql] sql_set_user escaped user --> '10966417880' [sql] expand: %{Acct-Delay-Time} -> [sql] ... expanding second conditional [sql] expand: INSERT INTO radacct (acctsessionid, ac ctuniqueid, username, realm, nasipaddress, naspo rtid, nasporttype, acctstarttime, acctstoptime, acctsessiontime, acctauthentic, connectinfo_start, connectinf o_stop, acctinputoctets, acctoutputoctets, calledstationid, calli ngstationid, acctterminatecause, servicetype, framedprotocol, framedipaddress, acctstartdelay, acctstopdelay, xascendsessi onsvrkey) VALUES ('%{Acct-Session-Id}', '%{Acct-Unique-Ses sion-Id}', '%{SQL-User-Name}', '%{Realm}', '%{NAS-IP-A ddress}', '%{NAS-Port}', '%{NAS-Port-Type}', '%S', NULL, '0', '%{Acct-Authentic}', '%{Connect-Info}', '', '0', '0', '%{Called-Station-Id}', '%{Calling-Station-Id}', '', '%{Ser vice-Type}', '%{Framed-Protocol}', '%{Framed-IP-Address}', rlm_sql (sql): Reserving sql socket id: 27 rlm_sql (sql): Released sql socket id: 27 ++[sql] = ok [attr_filter.accounting_response] expand: %{User-Name} -> 10966417880 attr_filter: Matched entry DEFAULT at line 12 ++[attr_filter.accounting_response] = updated +} # group accounting = updated Sending Accounting-Response of id 79 to 10.10.0.103 port 1030 Finished request 1. Cleaning up request 1 ID 79 with timestamp +41 Going to the next request Waking up in 4.9 seconds. Cleaning up request 0 ID 78 with timestamp +41 Ready to process requests. This mean every user will has tow records in to radacct table how can I stop that .

1 0

(no subject)
by Hailun Tan 27 Jun '18

27 Jun '18

I am trying to perform the user authentication via freeradius server on the ssh conection. I have setup the free radius server according to the wiki pages: https://wiki.freeradius.org/guide/Getting-Started In addition, I managed to install the dolaradius to manage the free radius. I have run the radtest for the servers. The configurations for the radius server is: free radius server IP: 10.10.150.134 free radius server port: 1812 master secret: NOJA user name: micfox user password: micfox001 On the client machine (client IP: 10.10.150.136), I run the following command: *dev-ldap-server: radtest micfox micfox001 10.10.150.134:1812 <http://10.10.150.134:1812> 1812 NOJA* Sending Access-Request of id 5 to 10.10.150.134 port 1812 User-Name = "micfox" User-Password = "micfox001" NAS-IP-Address = 10.10.150.136 NAS-Port = 1812 Message-Authenticator = 0x00000000000000000000000000000000 rad_recv: Access-Accept packet from host 10.10.150.134 port 1812, id=5, length=38 Service-Type = Framed-User Framed-Protocol = PPP Framed-Compression = Van-Jacobson-TCP-IP So it should prove the free radius server is up and running. However, I have configured to use the pam-freeradius-auth.so to hookup with the PAM modules on the client machine to authenticate the ssh user. it does not work. I have updated the /etc/pam.d/sshd as follows: =========== *auth sufficient pam_radius_auth.so debug skip_passwd*# PAM configuration for the Secure Shell service # Standard Un*x authentication. @include common-auth # Disallow non-root logins when /etc/nologin exists. account required pam_nologin.so # Uncomment and edit /etc/security/access.conf if you need to set complex # access limits that are hard to express in sshd_config. # account required pam_access.so # Standard Un*x authorization. @include common-account # SELinux needs to be the first session rule. This ensures that any # lingering context has been cleared. Without this it is possible that a # module could execute code in the wrong domain. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close # Set the loginuid process attribute. session required pam_loginuid.so # Create a new session keyring. session optional pam_keyinit.so force revoke # Standard Un*x session setup and teardown. @include common-session # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. session optional pam_motd.so motd=/run/motd.dynamic session optional pam_motd.so noupdate # Print the status of the user's mailbox upon successful login. session optional pam_mail.so standard noenv # [1] # Set up user limits from /etc/security/limits.conf. session required pam_limits.so # Read environment variables from /etc/environment and # /etc/security/pam_env.conf. session required pam_env.so # [1] # In Debian 4.0 (etch), locale-related environment variables were moved to # /etc/default/locale, so read that as well. session required pam_env.so user_readenv=1 envfile=/etc/default/locale # SELinux needs to intervene at login time to ensure that the process starts # in the proper default security context. Only sessions which are intended # to run in the user's context should be run after this. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open # Standard Un*x password updating. @include common-password But now when I run the ssh micfox(a)10.10.150.136 (freeradius client's iP). the /var/log/auth.log has the following error messages: Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: Got user name micfox Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: ignore last_pass, force_prompt set Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: Sending RADIUS request code 1 Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: DEBUG: get_ipaddr(10.10.150.134) is available. (1812) Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: DEBUG: talk_radius(0x86960a0a) is available (1812,port). Jun 25 12:05:51 dev-ldap-server sshd[6441]: pam_radius_auth: DEBUG: waiting for response from radius server 10.10.150.134 with port 1812 (master secret: NOJA). *Jun 25 12:05:54 dev-ldap-server sshd[6441]: pam_radius_auth: RADIUS server 10.10.150.134 failed to respond* Jun 25 12:05:54 dev-ldap-server sshd[6441]: pam_radius_auth: All RADIUS servers failed to respond. Jun 25 12:05:54 dev-ldap-server sshd[6441]: pam_radius_auth: authentication failed Jun 25 12:05:54 dev-ldap-server sshd[6438]: Postponed keyboard-interactive for invalid user micfox from 127.0.0.1 port 37362 ssh2 [preauth] The RADIUS server always failed to respond.. I have configured the /etc/pam_radius_auth.conf as follows: # pam_radius_auth configuration file. Copy to: /etc/raddb/server # # For proper security, this file SHOULD have permissions 0600, # that is readable by root, and NO ONE else. If anyone other than # root can read this file, then they can spoof responses from the server! # # There are 3 fields per line in this file. There may be multiple # lines. Blank lines or lines beginning with '#' are treated as # comments, and are ignored. The fields are: # # server[:port] secret [timeout] # # the port name or number is optional. The default port name is # "radius", and is looked up from /etc/services The timeout field is # optional. The default timeout is 3 seconds. # # If multiple RADIUS server lines exist, they are tried in order. The # first server to return success or failure causes the module to return # success or failure. Only if a server fails to response is it skipped, # and the next server in turn is used. # # The timeout field controls how many seconds the module waits before # deciding that the server has failed to respond. # # server[:port] shared_secret timeout (s) *10.10.150.134:1831 <http://10.10.150.134:1831> NOJA 3* #other-server other-secret 3 # # having localhost in your radius configuration is a Good Thing. # # See the INSTALL file for pam.conf hints. I believed I should have setup everything correctly?? why is the radius-pam-auth.so not working with the error message, * RADIUS server 10.10.150.134 failed to respond??* I have prolonged the timeout parameter from 3 seconds to 60 seconds but it did not work. If the radius server is not correctly set, it should not even pass the radtest before. But why there is no response from the radius server for freeradius-pam-auth.so if the server does work?? what could go wrong from the configurations on the pam-radius module? Please advise

5 11

accepting all the users
by John Martins 27 Jun '18

27 Jun '18

Hello, I'm new in freeradius, I installed freeeradius 3.016 and mysql, and would like to accept all the users directly. I work with Mikrotik routers. Could anybody give me a clue of how to do it? thanks!! Best Regards

3 5

Bypass Canceled Subscribers
by Guilherme Domingues 26 Jun '18

26 Jun '18

Hello, We've looking for a simple solution to bypass pppoe request from canceled subscribers. It's sounds odd, but some routers/onus from certain clients hits radius all day long, and we're think to access those devices again, by accepting their login(only CHAP) and configure this clients to DHCP networks. In alternative of it, we've seen as soluction blocking at L2, but we're working with different models of NAS and switches and other networks devices. For us is getting complicated for CHAP autentication. Someone have some idea or suggestion ? Best regards, --- "A mente que se abre a uma nova idéia jamais voltará ao seu tamanho original." Albert Einstein

2 1