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

Acct-Session-Id
by Arjun Prasad 22 Jun '10

22 Jun '10

Hi, My doubt is regarding the freeradius-client-1.1.6 implementation is sending the Acct-Session-Id(rfc 2866) attribute with accounting request to radius server or not. If yes then how they are generating the session id at run time. Thanks Arjun prasad

1 0

Generating Acct-Session-Id identifier
by JOE 22 Jun '10

22 Jun '10

Hi all! Is possible to set the attribute Acct-Session-ID for a specific user in freeradius?, I have a problem with a Load Balancer that not set this atribute. Regards

2 1

freeradius performance testing with seagull
by Vladimir Romanov 22 Jun '10

22 Jun '10

Hi All! I want test freeradius+mysql accounting interface performance with seagull. My problem - I can't implement valid signature. I always get rad_recv: Accounting-Request packet from host 10.2.170.14 port 65535, id=1, length=48 Received Accounting-Request packet from 10.2.170.14 with invalid signature! (Shared secret is incorrect.) Dropping packet without response. I try next scenario ..... <traffic>  <send channel="trans-ip-v4"> <action>  <inc-counter name="session-counter"> </inc-counter> <inc-counter name="identifier-counter"> </inc-counter> <set-value name="Acct-Session-Id". format="$(session-counter)"></set-value> <set-value name="Identifier". format="$(identifier-counter)"></set-value>  <restore-from-external field="0" entity="Authenticator"></restore-from-external> </action> <Message name="Accounting-Request"> <setfield name="Authenticator" value="0000000000000000"> </setfield> <Attribute name="Acct-Session-Id" value="value_is_replaced"> </Attribute>  <Attribute name="Acct-Status-Type" value="1"> </Attribute> <Attribute name="NAS-Identifier" value="ims.hpintelco.org"> </Attribute> </Message> <action> <store name="ACCT_SES_ID" entity="Acct-Session-Id"></store> <start-timer></start-timer> </action> </send> ..... -- Vladimir Romanov

2 1

LDAP-Availability
by Jens Weibler 22 Jun '10

22 Jun '10

Hi, last night one of our radius servers had a dying network card. I shouldn't be a problem because I've installed several servers and if one server isn't answering the switches are using the fallback servers. But the interface freeradius is using was still up - only the interface with the default gateway (= ldap access) was down. Is there any way I can prevent such a situation in the future (besides using only one interface)? A reply like "I'm temporary not available - please use another radius server" or something ;) -- Jens Weibler

2 1

Users accounting freeradius +LDAP
by Marzieh Raoufnezhad 22 Jun '10

22 Jun '10

Hi, I installed freeradius and configured it with LDAP and installed pptp also in debian lenny. I can login to radius server from windows and I have VPN connection and internet. Now I want to restrict my VPN users' bandwidth and internet charge(for example 4G charge for each user), but I don't know how to do it with freeradius+LDAP. I would be grateful if you can answer me as soon as possible. Regards, Raoufnezhad

1 0

Detail File Reader - Timeout
by Benjamin Marvin 22 Jun '10

22 Jun '10

Howdy, Is the timeout/retransmit timer adjustable for the detail file reader (copy-acct-to-home-server). If not, what is the default retransmit time for the reader? Just to double/triple verify, this is a serial reader (it waits to send a second packet until it has a response from the first) correct? Thanks (yet again)! -Benjamin

2 1

problem with installation of freeradius-server-2.1.9
by Zhouhuai Shen 22 Jun '10

22 Jun '10

Hi, I downloaded the freeradius-server-2.1.9 and tried to install on my Linux box, I did './configure --prefix=/tmp/freeradius', 'make' and then 'make install', a problem appears in the 'make install'. The error messages are as the followings: libtool: install: error: cannot install `rlm_acctlog.la' to a directory not ending in /usr/local/lib gmake[6]: *** [install] Error 1 gmake[6]: Leaving directory `/home/henrys/download/freeRadius/freeradius-server-2.1.9/src/modules/rlm_acctlog' gmake[5]: *** [rlm_acctlog] Error 2 gmake[5]: Leaving directory `/home/henrys/download/freeRadius/freeradius-server-2.1.9/src/modules' gmake[4]: *** [install] Error 2 gmake[4]: Leaving directory `/home/henrys/download/freeRadius/freeradius-server-2.1.9/src/modules' gmake[3]: *** [modules] Error 2 gmake[3]: Leaving directory `/home/henrys/download/freeRadius/freeradius-server-2.1.9/src' gmake[2]: *** [install] Error 2 gmake[2]: Leaving directory `/home/henrys/download/freeRadius/freeradius-server-2.1.9/src' gmake[1]: *** [src] Error 2 gmake[1]: Leaving directory `/home/henrys/download/freeRadius/freeradius-server-2.1.9' make: *** [install] Error 2 I had a libtool installed already on my Linux box under /usr/bin/libtool, which is an old version of the libtool (2.2.6 other than the one defined in freeradius-server-2.1.9 with libtool ver 2.2.8. I still want to keep the old one for other purposes. ) Can someone please point it out to me how I can install the freeradius on my Linux box? Cheers, Henry _________________________________________________________________ Looking for a place to manage all your online stuff? Download the new Windows Live http://download.live.com

3 2

problem migrating to freeradius2 with LDAP/krb5 Authorization/Authentication
by Riccardo Veraldi 21 Jun '10

21 Jun '10

Hello, i moved my old freeradius 1.x server to freeradius 2 I am on CentOS5.5 freeradius2-utils-2.1.7-7.el5 freeradius2-mysql-2.1.7-7.el5 freeradius2-2.1.7-7.el5 freeradius2-postgresql-2.1.7-7.el5 freeradius2-python-2.1.7-7.el5 freeradius2-unixODBC-2.1.7-7.el5 freeradius2-krb5-2.1.7-7.el5 freeradius2-perl-2.1.7-7.el5 freeradius2-ldap-2.1.7-7.el5 What I would like to do is to have the same service with LDAP authorization plus Kerberos V authentication, and users using EAP-TTLS client (SecureW2). But it does not work to me, Kerberos authentication is not even entered by the radius server because of missconfiguration and I am trying to guess where is my error. Basic Cleartext password in users file with EAP authentication works. I am not able to make KErberos authentication work with EAP. I Setup the radius server, I added principal in the kerberos server and I have the proper krb5.keytab file setup here is my configuration, might you check please where I get wrong in my configuration ? Following is my configuration and at the end is the radius log, thank you very much # users DEFAULT Auth-Type := eap DEFAULT Auth-Type := Kerberos Fall-Through = 1 # modules/krb5 krb5 { keytab = /etc/krb5.keytab #service_principal = name_of_principle } # modules/ldap ldap { server = "ldap-m.mydomain.com" basedn = "ou=people,o=myorg o=myorg,c=it" filter = "(uid=%{%{Stripped-User-Name}:-%{User-Name}})" ldap_connections_number = 5 timeout = 4 timelimit = 3 net_timeout = 1 tls { start_tls = no } dictionary_mapping = ${confdir}/ldap.attrmap edir_account_policy_check = no } #sites-avaliable/default authorize { preprocess auth_log chap mschap suffix eap { ok = return } unix files ldap expiration logintime pap } authenticate { Auth-Type PAP { pap } Auth-Type CHAP { chap } Auth-Type MS-CHAP { mschap } Auth-Type Kerberos { krb5 } unix eap Auth-Type eap { eap { handled = 1 } } } preacct { preprocess acct_unique suffix files } accounting { detail unix radutmp attr_filter.accounting_response } session { radutmp } post-auth { exec Post-Auth-Type REJECT { attr_filter.access_reject } } pre-proxy { } post-proxy { eap } #sites-avaliable/inner-tunnel server inner-tunnel { authorize { chap mschap unix suffix update control { Proxy-To-Realm := LOCAL } eap { ok = return } files ldap expiration logintime pap } authenticate { Auth-Type PAP { pap } Auth-Type CHAP { chap } Auth-Type MS-CHAP { mschap } Auth-Type Kerberos { krb5 } unix eap } session { radutmp } post-auth { Post-Auth-Type REJECT { attr_filter.access_reject } } pre-proxy { } post-proxy { eap } radiusd -X rad_recv: Access-Request packet from host 192.168.252.17 port 1645, id=55, length=157 User-Name = "username(a)myrealm.com" Framed-MTU = 1400 Called-Station-Id = "0012.438a.e8f0" Calling-Station-Id = "0022.5f08.a887" Service-Type = Login-User Message-Authenticator = 0xf4d6a67552977fb729b374eba35a1ff4 EAP-Message = 0x0202001b016775697a7a756e746940636e61662e696e666e2e6974 NAS-Port-Type = Wireless-802.11 NAS-Port = 331 NAS-IP-Address = 192.168.252.17 NAS-Identifier = "ap" +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] expand: %t -> Fri Jun 18 11:11:43 2010 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] Looking up realm "myrealm.com" for User-Name = "username(a)myrealm.com" [suffix] Found realm "myrealm.com" [suffix] Adding Stripped-User-Name = "username" [suffix] Adding Realm = "myrealm.com" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 2 length 27 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[unix] returns notfound [files] users: Matched entry DEFAULT at line 6 ++[files] returns ok [ldap] performing user authorization for username [ldap] expand: %{Stripped-User-Name} -> username [ldap] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=username) [ldap] expand: ou=people,o=myorg,o=myorg,c=it -> ou=people,o=myorg,o=myorg,c=it rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: attempting LDAP reconnection rlm_ldap: (re)connect to ldap-m.cr.myrealm.com:389, authentication 0 rlm_ldap: bind as / to ldap-m.cr.myrealm.com:389 rlm_ldap: waiting for bind result ... rlm_ldap: Bind was successful rlm_ldap: performing search in ou=people,o=myorg,o=myorg,c=it, with filter (uid=username) [ldap] looking for check items in directory... [ldap] looking for reply items in directory... WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? [ldap] user username authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 ++[ldap] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 55 to 192.168.252.17 port 1645 EAP-Message = 0x010300061520 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x5753d13e5750c4ac9fc5b5a8b7c8a781 Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.252.17 port 1645, id=56, length=208 User-Name = "username(a)myrealm.com" Framed-MTU = 1400 Called-Station-Id = "0012.438a.e8f0" Calling-Station-Id = "0022.5f08.a887" Service-Type = Login-User Message-Authenticator = 0x98a6abafe23ad54ef0b53c22e50538aa EAP-Message = 0x0203003c158000000032160301002d0100002903010975d1c7f4c77c95b90742f17d51e0e098c8018d2ca1e685239b82b7f1f94398000002000a0100 NAS-Port-Type = Wireless-802.11 NAS-Port = 331 State = 0x5753d13e5750c4ac9fc5b5a8b7c8a781 NAS-IP-Address = 192.168.252.17 NAS-Identifier = "ap" +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] expand: %t -> Fri Jun 18 11:11:43 2010 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] Looking up realm "myrealm.com" for User-Name = "username(a)myrealm.com" [suffix] Found realm "myrealm.com" [suffix] Adding Stripped-User-Name = "username" [suffix] Adding Realm = "myrealm.com" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 3 length 60 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS TLS Length 50 [ttls] Length Included [ttls] eaptls_verify returned 11 [ttls] (other): before/accept initialization [ttls] TLS_accept: before/accept initialization [ttls] <<< TLS 1.0 Handshake [length 002d], ClientHello [ttls] TLS_accept: SSLv3 read client hello A [ttls] >>> TLS 1.0 Handshake [length 002a], ServerHello [ttls] TLS_accept: SSLv3 write server hello A [ttls] >>> TLS 1.0 Handshake [length 0771], Certificate [ttls] TLS_accept: SSLv3 write certificate A [ttls] >>> TLS 1.0 Handshake [length 0004], ServerHelloDone [ttls] TLS_accept: SSLv3 write server done A [ttls] TLS_accept: SSLv3 flush data [ttls] TLS_accept: Need to read more data: SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode [ttls] eaptls_process returned 13 ++[eap] returns handled Sending Access-Challenge of id 56 to 192.168.252.17 port 1645 EAP-Message = 0x0104040015c0000007ae160301002a0200002603014c1b384f09835579da8b5456f480d5c4f5e6adc766d3db6e528ce79ffaf48eed00000a0016030107710b00076d00076a0003ed308203e9308202d1a003020102020243e8300d06092a864886f70d0101050500302e310b3009060355040613024954310d300b060355040a1304494e464e3110300e06035504031307494e464e204341301e170d3130303631313133333433385a170d3131303631313133333433385a3058310b3009060355040613024954310d300b060355040a1304494e464e310d300b060355040b1304486f7374310d300b06035504071304434e4146311c301a0603550403 EAP-Message = 0x13137261646975732e636e61662e696e666e2e697430819f300d06092a864886f70d010101050003818d0030818902818100e52a70b55fcf6cff98debcc333b2250d5bf311550dff5048a3da3436752fcc35fa65da8eeac6ac7661aa05162cfa43a3a9c02b528d01390647ee270d8710bd5a2a91dd0d178afdc7b8720807169ff02b337b4609df026e74b2b67a0c39da43b38b7202bb588f96d28b6ae5da739f19c09579552ef5826cd1868c48bafc29ca870203010001a382016930820165300c0603551d130101ff04023000300e0603551d0f0101ff0404030205a030340603551d25042d302b06082b0601050507030106082b0601050507030206 EAP-Message = 0x0a2b0601040182370a030306096086480186f8420401303d0603551d1f043630343032a030a02e862c687474703a2f2f73656375726974792e66692e696e666e2e69742f43412f494e464e43415f63726c2e64657230250603551d20041e301c300c060a2b06010401d1230a0107300c060a2a864886f74c05020201301d0603551d0e041604143e48fa5b450e5dba99497d2aedda7254d4c70e0030560603551d23044f304d8014d162f3b37772c82efbf2791a6f374e279f13d520a132a430302e310b3009060355040613024954310d300b060355040a1304494e464e3110300e06035504031307494e464e20434182010030320603551d11042b30 EAP-Message = 0x2982137261646975732e636e61662e696e666e2e697481127379736f7040636e61662e696e666e2e6974300d06092a864886f70d0101050500038201010008d0f5e2826b7d1c556096cc4feed46b101a4ec00272fd0d942b554c396c7886e33487362615a313c9dcfdfdb8ab64203ecee766344bf3912a2518e10e2aac98b37ca8c4d4159427c592adda8afc63b25a841583daba3c9922b65784c6bf5810f5581a0e3f4ca7155f323ec784a222ddec9cb96f334699374670f16bee4e7dda4d65796feb99b7cef70801676714813a3dc8575d3803f6bacda7ea4724bf2f441216fcc0b285029a8efcf9aa95d820b88239fe2738e3a283f529b60a656e62 EAP-Message = 0xc960ed2032f034653f28879f Message-Authenticator = 0x00000000000000000000000000000000 State = 0x5753d13e5657c4ac9fc5b5a8b7c8a781 Finished request 1. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.252.17 port 1645, id=57, length=154 User-Name = "username(a)myrealm.com" Framed-MTU = 1400 Called-Station-Id = "0012.438a.e8f0" Calling-Station-Id = "0022.5f08.a887" Service-Type = Login-User Message-Authenticator = 0x908d086ab2287026379e7037b0d5c711 EAP-Message = 0x020400061500 NAS-Port-Type = Wireless-802.11 NAS-Port = 331 State = 0x5753d13e5657c4ac9fc5b5a8b7c8a781 NAS-IP-Address = 192.168.252.17 NAS-Identifier = "ap" +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] expand: %t -> Fri Jun 18 11:11:43 2010 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] Looking up realm "myrealm.com" for User-Name = "username(a)myrealm.com" [suffix] Found realm "myrealm.com" [suffix] Adding Stripped-User-Name = "username" [suffix] Adding Realm = "myrealm.com" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 4 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS [ttls] Received TLS ACK [ttls] ACK handshake fragment handler [ttls] eaptls_verify returned 1 [ttls] eaptls_process returned 13 ++[eap] returns handled Sending Access-Challenge of id 57 to 192.168.252.17 port 1645 EAP-Message = 0x010503c21580000007aef89beeea09cd7cba4cc6815861d1765a5f2cb89b735aa8fbc1bfbdf4d4e8d5001689aab6d4161f788f4e6bd9176dae3836bc5bf626000377308203733082025ba003020102020100300d06092a864886f70d0101050500302e310b3009060355040613024954310d300b060355040a1304494e464e3110300e06035504031307494e464e204341301e170d3036313030333134313634375a170d3136313030333134313634375a302e310b3009060355040613024954310d300b060355040a1304494e464e3110300e06035504031307494e464e20434130820122300d06092a864886f70d01010105000382010f003082010a EAP-Message = 0x0282010100ce958e0e83959d42a9ca2923cab763f90a49ba825e2a4a85e1f6dde8baea7902f476a02296e551f03e32fd3d8caafb1d1ff7e0d2cdc46195034198a6700982dda9a64d7deba973b3df81962c6a57a170265152963cd149a3aac0130870dd28da6bc9848cc89913f262807379448f0aead68ab632ff8c4e1751364e19bbe52ac44ec7324f33a6cee0625d60efaa84af44e47b1b57af7d0d8cae9017d407a0a1b43e860db71d3ca50ac217a78b98f4bfab2616388111bdd5420e0efae0564c730fd75e8bf643d8f88ee88f35cbb9ac8c4ddfba4d7cee9d1df7fafea1f00b4b0a171046de2f8fba06fec7138377929c5b2aa043b80f8205f6fe EAP-Message = 0x3cd46249c20e7c2f0203010001a3819b308198300f0603551d130101ff040530030101ff300e0603551d0f0101ff040403020106301d0603551d0e04160414d162f3b37772c82efbf2791a6f374e279f13d52030560603551d23044f304d8014d162f3b37772c82efbf2791a6f374e279f13d520a132a430302e310b3009060355040613024954310d300b060355040a1304494e464e3110300e06035504031307494e464e204341820100300d06092a864886f70d0101050500038201010078d7d33fb73f72724062012396805ce4b736e0c47f431da822c5206b178edbc89b690348c48640e839b999c92d3021693fa05f978d90377386eb891205b5 EAP-Message = 0x14f183cb621feb3803e13e04b12e7413e2f905334e1bbf14cc5e07f4318195bae40fc544ba0f51a711aeb12c1e1869673ba093fd4d536f75d8e598c8accb9b874f54c268caf671087b7bc244f2270246e66a6b5e7b3a4a3aa0b92a78f4669a94f829d692ec989e3b255f57bd3b995bba92d3a7934ea99442167d628938e9a0d79f82a2c4dec1de7606f63f5bd2f253be1088519d681f37da801d2aa443e64e6f121f3c915d725baef1dfcab57b0590a9a616e1077744ab629061f5908b0e0ab6c7d616030100040e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x5753d13e5556c4ac9fc5b5a8b7c8a781 Finished request 2. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.252.17 port 1645, id=58, length=348 User-Name = "username(a)myrealm.com" Framed-MTU = 1400 Called-Station-Id = "0012.438a.e8f0" Calling-Station-Id = "0022.5f08.a887" Service-Type = Login-User Message-Authenticator = 0xb9b0cb0f79cce7dbac3e6580be35fee8 EAP-Message = 0x020500c81580000000be16030100861000008200805bff51c22c6177f2bb156dc96f1443d0af3f20350edd0b28d8b9e4844b86129d463fde980cabf5fce46c7024645276c3586d28b6ac4581ee187e28a940c0e0475c644cd561d0f22ac52a838e25273d454f11f9614a463646c931f9bac9f87b9af09ca01a7fa78ceea056ba56007a7a41e5853e3283b33bc2aa691cede3ac53bf1403010001011603010028a98916d48662eef747eaca2bb451650dcc22fae50e9dc86965dbb3e82a01f0770c31958f10da6dfd NAS-Port-Type = Wireless-802.11 NAS-Port = 331 State = 0x5753d13e5556c4ac9fc5b5a8b7c8a781 NAS-IP-Address = 192.168.252.17 NAS-Identifier = "ap" +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] expand: %t -> Fri Jun 18 11:11:43 2010 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] Looking up realm "myrealm.com" for User-Name = "username(a)myrealm.com" [suffix] Found realm "myrealm.com" [suffix] Adding Stripped-User-Name = "username" [suffix] Adding Realm = "myrealm.com" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 5 length 200 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS TLS Length 190 [ttls] Length Included [ttls] eaptls_verify returned 11 [ttls] <<< TLS 1.0 Handshake [length 0086], ClientKeyExchange [ttls] TLS_accept: SSLv3 read client key exchange A [ttls] <<< TLS 1.0 ChangeCipherSpec [length 0001] [ttls] <<< TLS 1.0 Handshake [length 0010], Finished [ttls] TLS_accept: SSLv3 read finished A [ttls] >>> TLS 1.0 ChangeCipherSpec [length 0001] [ttls] TLS_accept: SSLv3 write change cipher spec A [ttls] >>> TLS 1.0 Handshake [length 0010], Finished [ttls] TLS_accept: SSLv3 write finished A [ttls] TLS_accept: SSLv3 flush data [ttls] (other): SSL negotiation finished successfully SSL Connection Established [ttls] eaptls_process returned 13 ++[eap] returns handled Sending Access-Challenge of id 58 to 192.168.252.17 port 1645 EAP-Message = 0x0106003d158000000033140301000101160301002843ccdc295b6dbd1d720d5e9087e94f173b3f2cd83798f8012aaca2f7b61d21b38e51a91262b8a64f Message-Authenticator = 0x00000000000000000000000000000000 State = 0x5753d13e5455c4ac9fc5b5a8b7c8a781 Finished request 3. Going to the next request Waking up in 4.7 seconds. rad_recv: Access-Request packet from host 192.168.252.17 port 1645, id=59, length=243 User-Name = "username(a)myrealm.com" Framed-MTU = 1400 Called-Station-Id = "0012.438a.e8f0" Calling-Station-Id = "0022.5f08.a887" Service-Type = Login-User Message-Authenticator = 0x23d67a33d7bfb5afdb680d317b5e5280 EAP-Message = 0x0206005f1580000000551703010050c032907ee2ba0e63bbcc36909c482b61c8d18de52649368384225179d61b86e908bb354bf43d401d75df8bf4e1c07ffc68e07640501742f4a3bf7abe6b99ae0060fc058eade22ce7a088faee0a6a7243 NAS-Port-Type = Wireless-802.11 NAS-Port = 331 State = 0x5753d13e5455c4ac9fc5b5a8b7c8a781 NAS-IP-Address = 192.168.252.17 NAS-Identifier = "ap" +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/192.168.252.17/auth-detail-20100618 [auth_log] expand: %t -> Fri Jun 18 11:11:43 2010 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] Looking up realm "myrealm.com" for User-Name = "username(a)myrealm.com" [suffix] Found realm "myrealm.com" [suffix] Adding Stripped-User-Name = "username" [suffix] Adding Realm = "myrealm.com" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 6 length 95 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS TLS Length 85 [ttls] Length Included [ttls] eaptls_verify returned 11 [ttls] eaptls_process returned 7 [ttls] Session established. Proceeding to decode tunneled attributes. [ttls] Got tunneled request User-Name = "username(a)myrealm.com" User-Password = "mypassword" FreeRADIUS-Proxied-To = 127.0.0.1 [ttls] Sending tunneled request User-Name = "username(a)myrealm.com" User-Password = "mypassword" FreeRADIUS-Proxied-To = 127.0.0.1 server inner-tunnel { +- entering group authorize {...} ++[chap] returns noop ++[mschap] returns noop ++[unix] returns notfound [suffix] Looking up realm "myrealm.com" for User-Name = "username(a)myrealm.com" [suffix] Found realm "myrealm.com" [suffix] Adding Stripped-User-Name = "username" [suffix] Adding Realm = "myrealm.com" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok ++[control] returns ok [eap] No EAP-Message, not doing EAP ++[eap] returns noop [files] users: Matched entry DEFAULT at line 6 ++[files] returns ok [ldap] performing user authorization for username [ldap] expand: %{Stripped-User-Name} -> username [ldap] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=username) [ldap] expand: ou=people,o=myorg,o=myorg,c=it -> ou=people,o=myorg,o=myorg,c=it rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in ou=people,o=myorg,o=myorg,c=it, with filter (uid=username) [ldap] looking for check items in directory... [ldap] looking for reply items in directory... WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? [ldap] user username authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 ++[ldap] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} rlm_eap: EAP-Message not found [eap] Malformed EAP Message ++[eap] returns fail Failed to authenticate the user. } # server inner-tunnel [ttls] Got tunneled reply code 3 [ttls] Got tunneled Access-Reject [eap] Handler failed in EAP/ttls [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> username(a)myrealm.com attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 4 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 4 Sending Access-Reject of id 59 to 192.168.252.17 port 1645 EAP-Message = 0x04060004 Message-Authenticator = 0x00000000000000000000000000000000 Waking up in 3.7 seconds. Cleaning up request 0 ID 55 with timestamp +7 Cleaning up request 1 ID 56 with timestamp +7 Cleaning up request 2 ID 57 with timestamp +7 Waking up in 0.2 seconds. Cleaning up request 3 ID 58 with timestamp +7 Waking up in 1.0 seconds. Cleaning up request 4 ID 59 with timestamp +7 Ready to process requests.

3 5

eduroam PEAP + TTLS
by Jean-Philippe Ghibaudo 21 Jun '10

21 Jun '10

Hi, Before beginning, sorry for my bad English, I'm French. I'm trying to implement PEAP-MSCHAPV2 support in an existing and working configuration with EAP-TTLS + PAP, giving users a full support of eduroam. There are proxy radius maintained by our national "provider", and they test authentication every 15 minutes. When they only test EAP-TTLS authentication, it works, and this is a part of the output of freeradius -X. Login OK: [user/password] (from client proxyradius port 0 cli 02-00-00-00-00-01 via TLS tunnel) +- entering group post-auth {...} [sql] expand: %{User-Name} -> user@realm [sql] sql_set_user escaped user --> 'user@realm' [sql] expand: %{User-Password} -> password [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 ( 'user@realm', 'password', 'Access-Accept', '2010-06-17 18:17:02') [sql] expand: /var/log/freeradius/sqltrace.sql -> /var/log/freeradius/sqltrace.sql rlm_sql (sql) in sql_postauth: query is INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( 'user@realm', 'password', 'Access-Accept', '2010-06-17 18:17:02') rlm_sql (sql): Reserving sql socket id: 4 rlm_sql_mysql: query: INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( 'user@realm', 'password', 'Access-Accept', '2010-06-17 18:17:02') rlm_sql (sql): Released sql socket id: 4 ++[sql] returns ok expand: %{request:User-Name} -> user@realm ++[outer.reply] returns ok } # server inner-tunnel [ttls] Got tunneled reply code 2 User-Name := "user@realm" [ttls] Got tunneled Access-Accept [eap] Freeing handler ++[eap] returns ok Login OK: [anonymous/<via Auth-Type = EAP>] (from client proxyradius port 0 cli 02-00-00-00-00-01) Then, when I specify that our FreeRADIUS server support PEAP-MSCHAPV2, they test PEAP first and never receive an access-accept or access-reject request form only the outer identity, anonymous@realm. So there is the ouput : Login OK: [user/<via Auth-Type = mschap>] (from client proxyradius port 0 cli 02-00-00-00-00-01 via TLS tunnel) +- entering group post-auth {...} [sql] expand: %{User-Name} -> user@realm [sql] sql_set_user escaped user --> 'user@realm' [sql] expand: %{User-Password} -> [sql] ... expanding second conditional [sql] expand: %{Chap-Password} -> [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 ( 'user@realm', '', 'Access-Accept', '2010-06-17 15:32:07') [sql] expand: /var/log/freeradius/sqltrace.sql -> /var/log/freeradius/sqltrace.sql rlm_sql (sql) in sql_postauth: query is INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( 'user@realm', '', 'Access-Accept', '2010-06-17 15:32:07') rlm_sql (sql): Reserving sql socket id: 2 rlm_sql_mysql: query: INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( 'user@realm', '', 'Access-Accept', '2010-06-17 15:32:07') rlm_sql (sql): Released sql socket id: 2 ++[sql] returns ok expand: %{request:User-Name} -> user@realm ++[outer.reply] returns ok } # server inner-tunnel [ttls] Got tunneled reply code 2 User-Name := "user@realm" MS-CHAP2-Success = 0x54533d42374134413830313835384530453531383135373131384643424442444432464133384345413836 [ttls] Got tunneled Access-Accept [ttls] Got MS-CHAP2-Success, tunneling it to the client in a challenge. ++[eap] returns handled Sending Access-Challenge of id 9 to 193.51.182.121 port 35055 User-Name = "user@realm" EAP-Message = 0x010a005f1580000000551703010050f984b434f276e050b0697e427d30ddfe2c0d9cc56a8f5da6ab447bbabae115d8181dfce1b6e52f33fcd2a20d5e26f574b9be69fa946342eafbd7ea350d5782490593a260401dae6b1c71f16f30b3ab38 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcda13382c4ab2647095b27820a4b1850 Finished request 11. Going to the next request Waking up in 4.7 seconds. And then, the proxyradius sends new Access-Request and the outer identity is never accepted. But the user@realm is authenticated... I'm sorry I know you need more informations about my confs and outputs, but I don't want to make this post longer than it is... So, I can post more informations... Thank you for helping me ! J-P. _________________________________________________________________ Installez gratuitement les nouvelles Emoch'ticones ! http://www.ilovemessenger.fr/emoticones/telecharger-emoticones-emochticones…

6 19

PAP Authentication
by simone.trevisan＠telsey.it 21 Jun '10

21 Jun '10

Dear all, I have an ADSL modem (running PPPoE Client) connect to a Cisco PPPoE Server. The Cisco PPPoE Server forward PPPoE request from CPE to the Freeradius 2.1.0. I would like to provide to CPE an IP address based on the pair: Username/password. Authentication used: PAP I see the WARNING message reported by Freeradius, but my tentative to fix them fails. Can you help me Thank you very much. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1) I have added to radiusd.conf the module: # PAP module to authenticate users based on their stored password # # Supports multiple encryption schemes # clear: Clear text # crypt: Unix crypt # md5: MD5 ecnryption # sha1: SHA1 encryption. # DEFAULT: crypt pap { encryption_scheme = clear } 2) I have modify the module pap: pap { auto_header = yes } 3) In users I have added: mr642wg Auth-Type := PAP, User-Password == "mr642wg" Service-Type = Framed-User, User-Name = "mr642wg", User-Password = "mr642wg", Framed-Protocol = PPP, Framed-IP-Address = 192.168.90.161, Framed-IP-Netmask = 255.255.255.248, 4) In clients.conf I have added; client 10.31.0.0/24 { # # secret and password are mapped through the "secrets" file. secret = testing123 shortname = liv1 # # the following three fields are optional, but may be used by # # checkrad.pl for simultaneous usage checks # nastype = livingston # login = !root # password = someadminpas } This is the output from freeradius -X freeradius -X FreeRADIUS Version 2.1.0, for host i486-pc-linux-gnu, built on Nov 14 2008 at 11:57:03 Copyright (C) 1999-2008 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/policy including configuration file /etc/freeradius/modules/passwd including configuration file /etc/freeradius/modules/radutmp including configuration file /etc/freeradius/modules/krb5 including configuration file /etc/freeradius/modules/linelog including configuration file /etc/freeradius/modules/echo including configuration file /etc/freeradius/modules/attr_rewrite including configuration file /etc/freeradius/modules/mschap including configuration file /etc/freeradius/modules/ippool including configuration file /etc/freeradius/modules/digest including configuration file /etc/freeradius/modules/expiration including configuration file /etc/freeradius/modules/sradutmp including configuration file /etc/freeradius/modules/files including configuration file /etc/freeradius/modules/detail.log including configuration file /etc/freeradius/modules/expr including configuration file /etc/freeradius/modules/wimax including configuration file /etc/freeradius/modules/smbpasswd including configuration file /etc/freeradius/modules/mac2vlan including configuration file /etc/freeradius/modules/pap including configuration file /etc/freeradius/modules/logintime including configuration file /etc/freeradius/modules/always including configuration file /etc/freeradius/modules/pam including configuration file /etc/freeradius/modules/inner-eap including configuration file /etc/freeradius/modules/etc_group including configuration file /etc/freeradius/modules/sql_log including configuration file /etc/freeradius/modules/chap including configuration file /etc/freeradius/modules/realm including configuration file /etc/freeradius/modules/exec including configuration file /etc/freeradius/modules/counter including configuration file /etc/freeradius/modules/preprocess including configuration file /etc/freeradius/modules/detail.example.com including configuration file /etc/freeradius/modules/attr_filter including configuration file /etc/freeradius/modules/mac2ip including configuration file /etc/freeradius/modules/unix including configuration file /etc/freeradius/modules/detail including configuration file /etc/freeradius/modules/acct_unique including configuration file /etc/freeradius/modules/checkval including configuration file /etc/freeradius/modules/ldap including configuration file /etc/freeradius/eap.conf including configuration file /etc/freeradius/sql.conf including configuration file /etc/freeradius/sql/mysql/dialup.conf including configuration file /etc/freeradius/sql/mysql/counter.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 including dictionary file /etc/freeradius/dictionary main { prefix = "/usr" localstatedir = "/var" logdir = "/var/log/freeradius" libdir = "/usr/lib/freeradius" radacctdir = "/var/log/freeradius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 allow_core_dumps = no pidfile = "/var/run/radiusd/radiusd.pid" checkrad = "/usr/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = no auth_badpass = no auth_goodpass = no } security { max_attributes = 200 reject_delay = 1 status_server = yes } } client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } client 10.31.0.0/24 { require_message_authenticator = no secret = "testing123" shortname = "liv1" } 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 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 } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } realm serbia.com { authhost = LOCAL accthost = LOCAL } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating expr Module: Linked to module rlm_expiration Module: Instantiating expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating pap pap { encryption_scheme = "clear" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating chap Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/var/log/freeradius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "md5" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no max_sessions = 2048 } 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" } Ignoring EAP-Type/tls because we do not have OpenSSL support. Ignoring EAP-Type/ttls because we do not have OpenSSL support. Ignoring EAP-Type/peap because we do not have OpenSSL support. Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating files files { usersfile = "/etc/freeradius/users" acctusersfile = "/etc/freeradius/acct_users" preproxy_usersfile = "/etc/freeradius/preproxy_users" compat = "no" } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/var/log/freeradius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Linked to module rlm_attr_filter Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/etc/freeradius/attrs.access_reject" key = "%{User-Name}" } } } modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating 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: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating 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 detail detail { detailfile = "/var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Instantiating attr_filter.accounting_response attr_filter attr_filter.accounting_response { attrsfile = "/etc/freeradius/attrs.accounting_response" key = "%{User-Name}" } 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 } radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 10.31.0.107 port 21645, id=26, length=77 Framed-Protocol = PPP User-Name = "mr642wg" User-Password = "mr642wg" NAS-Port-Type = Virtual NAS-Port = 0 Service-Type = Framed-User NAS-IP-Address = 10.31.0.107 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "mr642wg", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[unix] returns notfound WARNING: Found User-Password == "...". WARNING: Are you sure you don't mean Cleartext-Password? WARNING: See "man rlm_pap" for more information. [files] users: Matched entry mr642wg at line 105 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop Found Auth-Type = PAP +- entering group PAP {...} [pap] login attempt with password "mr642wg" [pap] No password configured for the user. Cannot do authentication ++[pap] returns fail Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} expand: %{User-Name} -> mr642wg 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 26 to 10.31.0.107 port 21645 Waking up in 4.9 seconds. Cleaning up request 0 ID 26 with timestamp +121 Ready to process requests. ______________________________________________________________________________ --- NOTICE --- This email and any attachments are confidential and are intended for the addressee only. If you have received this message by mistake, please contact us immediately and then delete the message from your system. You must not copy, distribute, disclose or act upon the contents of this email. Personal and corporate data submitted will be used in a correct, transparent and lawful manner. The data collected will be processed in paper or computerized form for the performance of contractual and lawful obligations as well as for the effective management of business relationship. The data processor is Telsey S.p.A. The data subject may exercise all the rights set forth in art. 7 of Law by Decree 30.06.2003 n. 196 as reported in the following url http://www.telsey.com/privacy.asp. ______________________________________________________________________________

2 1