- Freeradius-Users - lists.freeradius.org

Post-proxy attribute filtering oddness
by stefan.paetow＠diamond.ac.uk 12 Mar '14

12 Mar '14

Hi, I've got some post-proxy attribute filtering oddness. The servers are both FreeRADIUS 3.0.1. I send an EAP-TTLS/EAP-GTC (or EAP-TTLS/PAP) authentication to my home server (172.23.142.184), which then proxies the request to the UMBRELLAID.ORG realm's server (172.23.142.185). On return, I can see both MS-MPPE-Send-Key and MS-MPPE-Recv-Key in the response, but if I have attr_filter.post-proxy switched on, the MS-MPPE-Send-Key disappears by the beginning of post-auth (so I'm venturing to guess that this triggers a match in the post-proxy attribute filter). When attr_filter.post-proxy is commented out, it is there. The attr_filter/post-proxy file is standard to the distribution with exception of the addition of the following three lines: DEFAULT: User-Name =* ANY, Class =* ANY, Chargeable-User-Identity =* ANY, : : (for clarity, the colons are indicative of the remainder of the DEFAULT entry) I have two logs, one with an Access-Accept with no MS-MPPE-Send-Key (i.e. with filter enabled), one with an Access-Accept with MS-MPPE-Send-Key (filter disabled). The two logs are at https://www.dropbox.com/sh/0j6num17n2tt0mm/sX8GwxgZjR I'm flummoxed! Can someone explain this? Alan D? Alan B? Arran? Anyone? With Regards Stefan -- 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

4 9

Setting PEAP Method and Inner-tunnel virtual server
by Hangi Christian 12 Mar '14

12 Mar '14

Thank you so much for your help. I used the chmod command on the root user to allow the permission and I used the testing user command as a regular user in the debugging mode and it worked. But, I tried to test all the protocols, they are working in the default testing. I tried to set only EAP PEAP-MSCHAPv2 method by commenting out all the others EAP methods except EAP-TLS and EAP-TTLS, and setting default_eap_type = peap. i also changed the password from cleartext into somethin like this ** " testing" User-password = "P@ssw0rd "** But I don't know how to configure the inner-tunnel virtual server inside the sites-enabled in order to allow 802.1x authentication. when i tried to test without configuring the inner-tunnel virtual server i got this . rad_recv: Access-Request packet from host 127.0.0.1 port 55247, id=123, length=77 User-Name = "testing" User-Password = "P@ssw0rd" NAS-IP-Address = 192.168.9.27 NAS-Port = 0 Message-Authenticator = 0x42afe3cc71c80db704cb5b4d6f915c1e server inner-tunnel { # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/inner-tunnel +group authorize { ++[chap] = noop ++[mschap] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop ++update control { ++} # update control = noop [eap] No EAP-Message, not doing EAP ++[eap] = noop 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 testing at line 51 [files] expand: Hello,%{User-Name} -> Hello,testing ++[files] = ok ++[expiration] = noop ++[logintime] = noop ++[pap] = noop +} # group authorize = ok ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel Using Post-Auth-Type REJECT # Executing group from file /usr/local/etc/raddb/sites-enabled/inner-tunnel +group REJECT { [attr_filter.access_reject] expand: %{User-Name} -> testing attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] = updated +} # group REJECT = 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 123 to 127.0.0.1 port 55247 Reply-Message = "Hello,testing" Waking up in 4.9 seconds. Cleaning up request 0 ID 123 with timestamp +16 Ready to process requests. i tried to test the peap method using jradius simulator i got this Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 0 Sending Access-Reject of id 123 to 127.0.0.1 port 55247 Reply-Message = "Hello,testing" Waking up in 4.9 seconds. Cleaning up request 0 ID 123 with timestamp +16 Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1 port 47000, id=2, length=73 User-Name = "testing" NAS-Port = 0 NAS-IP-Address = 127.0.0.1 EAP-Message = 0x0200000c0174657374696e67 Message-Authenticator = 0x3cc3c953e07cc82b12dc94c65102acd1 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 0 length 12 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] = updated ++[unix] = 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 testing at line 51 [files] expand: Hello,%{User-Name} -> Hello,testing ++[files] = ok ++[expiration] = noop ++[logintime] = noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] = noop +} # group authorize = updated Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 2 to 127.0.0.1 port 47000 Reply-Message = "Hello,testing" EAP-Message = 0x010100061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcf4ca028cf4db9debca7c7b78161462f Finished request 1. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 47000, id=3, length=151 User-Name = "testing" NAS-Port = 0 NAS-IP-Address = 127.0.0.1 State = 0xcf4ca028cf4db9debca7c7b78161462f EAP-Message = 0x020100481900160301003d010000390301531ff150fa7d236ea125d229a2f796c081b24c29d4b8fd319c253f294bec4dfd0000120039003800330032001600130035002f000a0100 Message-Authenticator = 0xe3826c6167a24627480ce56fbd6769a0 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 1 length 72 [eap] Continuing tunnel setup. ++[eap] = ok +} # group authorize = ok Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] (other): before/accept initialization [peap] TLS_accept: before/accept initialization [peap] <<< TLS 1.0 Handshake [length 003d], ClientHello [peap] TLS_accept: SSLv3 read client hello A [peap] >>> TLS 1.0 Handshake [length 002a], ServerHello [peap] TLS_accept: SSLv3 write server hello A [peap] >>> TLS 1.0 Handshake [length 08d0], Certificate [peap] TLS_accept: SSLv3 write certificate A [peap] >>> TLS 1.0 Handshake [length 020d], ServerKeyExchange [peap] TLS_accept: SSLv3 write key exchange A [peap] >>> TLS 1.0 Handshake [length 0004], ServerHelloDone [peap] TLS_accept: SSLv3 write server done A [peap] TLS_accept: SSLv3 flush data [peap] TLS_accept: Need to read more data: SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 3 to 127.0.0.1 port 47000 EAP-Message = 0x0102040019c000000b1f160301002a020000260301531ff1501b19bf495e28952a475864897eae5fcc49b9269c4515e0631ef156910000390016030108d00b0008cc0008c90003de308203da308202c2a003020102020101300d06092a864886f70d0101050500308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479 EAP-Message = 0x301e170d3134303232353039343530365a170d3135303232353039343530365a307c310b3009060355040613024652310f300d0603550408130652616469757331153013060355040a130c4578616d706c6520496e632e312330210603550403131a4578616d706c65205365727665722043657274696669636174653120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d30820122300d06092a864886f70d01010105000382010f003082010a0282010100aed3f4e6fa9efadea640eccdba95ba84671a37bd5f8f0526f781d7f52310288efaa32fa4a513a922af4adfe4b160dad05cb685dbbfb809801b7eba53bed1 EAP-Message = 0xb37c222a83b63d94afe8d30f195808535b8ace500284ce9163df58c24b7dc64f2c11817aedc26a45da19a8184ae6c3a357ebf7bbb0bd39cb62f9273fcdaf512343aaca2110b87b2c2115cf7f43299bfd922641a4dd9773e0d6cb904efe06a6a265131a04b08f37d455c557c056e311304cb1a84cf993992b0b01647bd46d591c01f50afc0c11c8093785b9fb90dd102383981dbdec2283e96fe537b589d446df50d8693917fabf154ddc66caa6a3ef01e608f17565eb2520cd41ed765d977e9b3d450203010001a34f304d30130603551d25040c300a06082b0601050507030130360603551d1f042f302d302ba029a0278625687474703a2f2f777777 EAP-Message = 0x2e6578616d706c652e636f6d2f6578616d706c655f63612e63726c300d06092a864886f70d01010505000382010100d7f9a17398b726d5861c69fb1425fc06ec2ced7f2a22b411d42c03275ac249d7236d84bcdf767616edd9c1b15aadbe57aa8c9c9a0350e998066a9407bbd9c7ede47f1020b4115429bc60dec66afc0a1db3def7cd5b2bc8423fc950f7db57a682999127e2abda907ebb7a8b3b040e1296840bce6847fd44e3263d1399b3f85129313e5c4405f287488035e2df63840f2833398d80c68b4c13e328f46af697946722924e1546254ad9d8a4387bbe348d010f147e9c59a4a1258944f07d8351b28b7ed7e7eef81522158fe7ae14aa39 EAP-Message = 0x680bc8b86dc2911707736c66 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcf4ca028ce4eb9debca7c7b78161462f Finished request 2. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 47000, id=4, length=85 User-Name = "testing" NAS-Port = 0 NAS-IP-Address = 127.0.0.1 State = 0xcf4ca028ce4eb9debca7c7b78161462f EAP-Message = 0x020200061900 Message-Authenticator = 0xd8c05c3b9c781d52ed7b93d2d7e5f299 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 2 length 6 [eap] Continuing tunnel setup. ++[eap] = ok +} # group authorize = ok Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 4 to 127.0.0.1 port 47000 EAP-Message = 0x010303fc1940f113789d5fe58467daa0b48d626dcb3d8da9062245d90c64ea654f3981c73a5ca1267f6e525a0004e5308204e1308203c9a003020102020900a9f66bfe117a6d3a300d06092a864886f70d0101050500308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479301e170d3134303232353039343530365a EAP-Message = 0x170d3135303232353039343530365a308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f7269747930820122300d06092a864886f70d01010105000382010f003082010a0282010100e179503ca3da7dcf981aff930f99b8c5a2296ba5072376dc3ad0566b0f09807a284b1ff4cbc0812143ef3a248f2ff2940cc71e1edfaa16 EAP-Message = 0x6091744a8a2cf21a400b59a98250e0097f78c4f7eb5359a896c83856df1239276c4984ed013d5083dfc1f54dbe83082bfca40f48542185e58b53a68c2278b86523dd381d94afc91f584a9471dd84d1582a2c5ae2a59a15c291cfb885c37dedaacd9e0d8582c629cbf7df7a1ae856e776c039d75bdc388105e0e7f881360e1c1deb7c161ef4dd374dc14250813390f4f75cc47c2b675098927890b9d73231ab79cf492ba86b7e4901a29ea1c406a89505622c378939677bd76cf58a49e3fa442ab2093278776958f3370203010001a382013430820130301d0603551d0e0416041432ea5b0d0283f7fe235134d0055fca1822af60a93081c80603551d23 EAP-Message = 0x0481c03081bd801432ea5b0d0283f7fe235134d0055fca1822af60a9a18199a48196308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479820900a9f66bfe117a6d3a300c0603551d13040530030101ff30360603551d1f042f302d302ba029a0278625687474703a2f2f7777772e6578616d706c652e636f6d2f6578 EAP-Message = 0x616d706c655f6361 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcf4ca028cd4fb9debca7c7b78161462f Finished request 3. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 47000, id=5, length=85 User-Name = "testing" NAS-Port = 0 NAS-IP-Address = 127.0.0.1 State = 0xcf4ca028cd4fb9debca7c7b78161462f EAP-Message = 0x020300061900 Message-Authenticator = 0xb79350a495b09dc0b764088a6e733871 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 3 length 6 [eap] Continuing tunnel setup. ++[eap] = ok +} # group authorize = ok Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 5 to 127.0.0.1 port 47000 EAP-Message = 0x0104033919002e63726c300d06092a864886f70d01010505000382010100a4e27f07df6259c73bdf038c528225ab72be8e8447acf759c13159d2e48eb016b6f54c410363392f9d36b4d9a652e871e000e39dd1ae409a5106fa7582ed55601a764fab3bd81e384c3de62d04394a30ab1f0b0820e1eeeb27209c237cf39eb401d76d67756d1dd2129f849a0845e39b159304fe5c62e3950f4d49b6db7b314fc7f244ef19f9efba015dde6d609eaf3556a83b404bb64718b64e7b16d050e103dd715e20691b4a6e31d31ab065bb7a6b8b0f8f27b42726e9c9187f94572613e5c36e433a7b24afffa293930597e486a477c228cc2a9d50f5c916a50f144b3c EAP-Message = 0x7a7a633cb797174fe44470f989dd72a3e9783c745df5cf318e3e84bd246d11d900160301020d0c0002090080a8f0e70aef23c507c30ad6cb681afb5153bfc1417fbe2b4b6ccd4898760c984564b5308bacd50cdcc3ee5e9ddf84cf6047239302a988c35b1c78f6da77b18e079216b679e618fff798faaec47a25ed37480f74dd76d8cbd125384fed51b31efa6ff0feb3e8de9f387c2ee7cc313d2de8ae2e67b01605e9b019720135e9685b5b000102008025814b22830831f6716e74da15ba9866e69b7f29a54fafff0bdeeb38cadbbab1ffb7d1ccc326a9f7b3e5d7c12b446fd44e09c5294b9d2dbaa0273d82358d97297e176d5c8d5ce98fd52aa9a8 EAP-Message = 0x711535a625454a646980373ccb9639d0ebf2b44bc9f0985cfe4c763948d90a838cab0e491f82323dcb1fac770281519ae7a3f4b2010045dc48edf7fdf54171fb368899a00e657c859fcc3fab1f4da00a892dac500c3209280b06420037a1cc2c74333bf826196f3564a008c7e756af5d45b91e619031509ed5afe63bc9d63130f00e462fbe807aee61798a5b3880f83e8e4f6e98779c92e8b8cb18b516b8579e88f2696efd71d0f3498a395025e78c2f00e487aec42affc9dc521b20547e4f6ccf0967b0e145e9ebc8c34b195356a8ed0fca339b11e1a2e8dfc655a72e1db0da0a0df88852bc37307c7ea7eead34495fce92831bece6f74412597d10f3 EAP-Message = 0x75d5d456af23cdd69bc61243b41168d572cabf8768a2780054e9949c1cb9bf222692af5cd4e08a19acba977d1671098c9131876d1b30fefa1816030100040e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcf4ca028cc48b9debca7c7b78161462f Finished request 4. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 47000, id=6, length=315 User-Name = "testing" NAS-Port = 0 NAS-IP-Address = 127.0.0.1 State = 0xcf4ca028cc48b9debca7c7b78161462f EAP-Message = 0x020400ec19001603010086100000820080a77f24ad2050e6bd07cbbef0f616a25dc4d4022a5a8ff6e4f0a4aa13254ed96e6d343ea6c9e92f8905f1889d772e5e85e966b0e0d4c510d1eb9e9105dc8beb84c2f56e9723994de83325df2017edbf1cdd8ec6da78f3403b9dcd3e29a794d5d091d321f9bc435b87a880cff4d730cfd8bd8c7000c0d4cdc452799ad8968dc4541403010001011603010050c491f1ada3008208f04f195129505068ddeb05f6f2b1d9e6bfd8e309f143be46cb9d9668d481f23d7a80c3c99485d2ab8180df3dbf52b8e3af67465835f446620d1f13735fa3f83850591a3947be7655 Message-Authenticator = 0x86eb2811521a1551f40507327ff12743 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 4 length 236 [eap] Continuing tunnel setup. ++[eap] = ok +} # group authorize = ok Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] <<< TLS 1.0 Handshake [length 0086], ClientKeyExchange [peap] TLS_accept: SSLv3 read client key exchange A [peap] <<< TLS 1.0 ChangeCipherSpec [length 0001] [peap] <<< TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 read finished A [peap] >>> TLS 1.0 ChangeCipherSpec [length 0001] [peap] TLS_accept: SSLv3 write change cipher spec A [peap] >>> TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 write finished A [peap] TLS_accept: SSLv3 flush data [peap] (other): SSL negotiation finished successfully SSL Connection Established [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 6 to 127.0.0.1 port 47000 EAP-Message = 0x0105004119001403010001011603010030924cb8cd91029f0767c24ee999838826f05fe99d10722855956dae0ff10e6c4ac9bf0e17151503ba04ccba9b09d0e497 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcf4ca028cb49b9debca7c7b78161462f Finished request 5. Going to the next request Waking up in 4.1 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 47000, id=7, length=85 User-Name = "testing" NAS-Port = 0 NAS-IP-Address = 127.0.0.1 State = 0xcf4ca028cb49b9debca7c7b78161462f EAP-Message = 0x020500061900 Message-Authenticator = 0x6cf39e9e692ebc10078a1dea5845477d # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 5 length 6 [eap] Continuing tunnel setup. ++[eap] = ok +} # group authorize = ok Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake is finished [peap] eaptls_verify returned 3 [peap] eaptls_process returned 3 [peap] EAPTLS_SUCCESS [peap] Session established. Decoding tunneled attributes. [peap] Peap state TUNNEL ESTABLISHED ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 7 to 127.0.0.1 port 47000 EAP-Message = 0x0106002b1900170301002057428dfbc1a703902f590dfce56bae6cd5e6c39efca98488f76badf9b0852fa0 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcf4ca028ca4ab9debca7c7b78161462f Finished request 6. Going to the next request Waking up in 4.1 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 47000, id=8, length=175 User-Name = "testing" NAS-Port = 0 NAS-IP-Address = 127.0.0.1 State = 0xcf4ca028ca4ab9debca7c7b78161462f EAP-Message = 0x0206006019001703010020121d5f70b18873c2ce8adc64ee86316d43cc5c587a65cfede3885092292f45621703010030ae623579fca299bdad152eff69c508636ec69ba9fb2c62f443a75d108dae0e2f80a5cfee6ab81fe8ffe3a8e96fccc18e Message-Authenticator = 0xea19005096c49a314c145dd25e9c8ec2 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 6 length 96 [eap] Continuing tunnel setup. ++[eap] = ok +} # group authorize = ok Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] eaptls_process returned 7 [peap] EAPTLS_OK [peap] Session established. Decoding tunneled attributes. [peap] Peap state WAITING FOR INNER IDENTITY [peap] Identity - testing [peap] Got inner identity 'testing' [peap] Setting default EAP type for tunneled EAP session. [peap] Got tunneled request EAP-Message = 0x0206000c0174657374696e67 server { [peap] Setting User-Name to testing Sending tunneled request EAP-Message = 0x0206000c0174657374696e67 FreeRADIUS-Proxied-To = 127.0.0.1 User-Name = "testing" server inner-tunnel { # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/inner-tunnel +group authorize { ++[chap] = noop ++[mschap] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop ++update control { ++} # update control = noop [eap] EAP packet type response id 6 length 12 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] = updated 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 testing at line 51 [files] expand: Hello,%{User-Name} -> Hello,testing ++[files] = ok ++[expiration] = noop ++[logintime] = noop ++[pap] = noop +} # group authorize = updated Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/inner-tunnel +group authenticate { [eap] EAP Identity [eap] No such EAP type mschapv2 [eap] Failed in EAP select ++[eap] = invalid +} # group authenticate = invalid Failed to authenticate the user. Using Post-Auth-Type REJECT # Executing group from file /usr/local/etc/raddb/sites-enabled/inner-tunnel +group REJECT { [attr_filter.access_reject] expand: %{User-Name} -> testing attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] = updated +} # group REJECT = updated } # server inner-tunnel [peap] Got tunneled reply code 3 Reply-Message = "Hello,testing" EAP-Message = 0x04060004 Message-Authenticator = 0x00000000000000000000000000000000 [peap] Got tunneled reply RADIUS code 3 Reply-Message = "Hello,testing" EAP-Message = 0x04060004 Message-Authenticator = 0x00000000000000000000000000000000 [peap] Tunneled authentication was rejected. [peap] FAILURE ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 8 to 127.0.0.1 port 47000 EAP-Message = 0x0107002b1900170301002057077c5e5c4d4c0e362ffe95fff5a33129b376ed00b69e00c99fffcda1428251 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcf4ca028c94bb9debca7c7b78161462f Finished request 7. Going to the next request Waking up in 4.0 seconds. rad_recv: Access-Request packet from host 127.0.0.1 port 47000, id=9, length=175 User-Name = "testing" NAS-Port = 0 NAS-IP-Address = 127.0.0.1 State = 0xcf4ca028c94bb9debca7c7b78161462f EAP-Message = 0x0207006019001703010020a0530d6df4bf549909743f057be762457c2b6abd38eb6235375f20a27e93fc851703010030fad2db6536da7f64fcc88f8b2a13970065906d4af2accb08c2d89846de9b30519d192e030afa21f131badbc40cbff6da Message-Authenticator = 0xd47ab810fc992cf5a094df676da234a6 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "testing", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 7 length 96 [eap] Continuing tunnel setup. ++[eap] = ok +} # group authorize = ok Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] eaptls_process returned 7 [peap] EAPTLS_OK [peap] Session established. Decoding tunneled attributes. [peap] Peap state send tlv failure [peap] Received EAP-TLV response. [peap] The users session was previously rejected: returning reject (again.) [peap] *** This means you need to read the PREVIOUS messages in the debug output [peap] *** to find out the reason why the user was rejected. [peap] *** Look for "reject" or "fail". Those earlier messages will tell you. [peap] *** what went wrong, and how to fix the problem. [eap] Handler failed in EAP/peap [eap] Failed in EAP select ++[eap] = invalid +} # group authenticate = invalid Failed to authenticate the user. Using Post-Auth-Type REJECT # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group REJECT { [attr_filter.access_reject] expand: %{User-Name} -> testing attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] = updated +} # group REJECT = updated Delaying reject of request 8 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 8 Sending Access-Reject of id 9 to 127.0.0.1 port 47000 EAP-Message = 0x04070004 Message-Authenticator = 0x00000000000000000000000000000000 Waking up in 3.0 seconds. Cleaning up request 1 ID 2 with timestamp +800 Cleaning up request 2 ID 3 with timestamp +800 Cleaning up request 3 ID 4 with timestamp +800 Cleaning up request 4 ID 5 with timestamp +800 Waking up in 0.8 seconds. Cleaning up request 5 ID 6 with timestamp +800 Cleaning up request 6 ID 7 with timestamp +800 Cleaning up request 7 ID 8 with timestamp +800 Waking up in 1.0 seconds. Cleaning up request 8 ID 9 with timestamp +800 Ready to process requests.

3 2

Authentication based on the user groups
by Kitty Chan 11 Mar '14

11 Mar '14

I have setup a Freeradius server to serve as the authentication server for Ruckus Wifi system. The backend directory server is Openldap. I can successfully authenticate users. Now I want to setup two wifi SSID. The "staff" SSID will authenticate to users belonging to the "staff" group in the Openldap directory and the "student" SSID shall authenticate to users belonging to the "student" group. What is the right way to configure this in Freeradius?

3 3

Re: Not trivial configuration of Freeradius as DHCP server
by Vyacheslav Maliev 11 Mar '14

11 Mar '14

Hello! Thanks to all. Configuration example that`s i need, will try it. 2014-03-11 0:46 GMT+04:00 <freeradius-users-request(a)lists.freeradius.org>: > Send Freeradius-Users mailing list submissions to > freeradius-users(a)lists.freeradius.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freeradius.org/mailman/listinfo/freeradius-users > or, via email, send a message with subject or body 'help' to > freeradius-users-request(a)lists.freeradius.org > > You can reach the person managing the list at > freeradius-users-owner(a)lists.freeradius.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Freeradius-Users digest..." > > > Today's Topics: > > 1. Re: Not trivial configuration of Freeradius as DHCP server > (Tony DeMatteis) > 2. Re: Old school: FreeRADIUS and NIS (Alan DeKok) > 3. Re: Old school: FreeRADIUS and NIS (Alan DeKok) > 4. Re: Old school: FreeRADIUS and NIS (A.L.M.Buxey(a)lboro.ac.uk) > 5. RE: Authorise based on Calling Station ID ? > (Darren Ward (darrward)) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 10 Mar 2014 13:07:37 -0700 > From: Tony DeMatteis <tonyd(a)commspeed.net> > To: freeradius-users(a)lists.freeradius.org > Subject: Re: Not trivial configuration of Freeradius as DHCP server > Message-ID: <531E1B89.4040007(a)commspeed.net> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > Hello, > > Took this snippet from what I'm doing which I got from a colleague who > first pulled a working config together. See where you can with this... > > 'dhcp' folder resides in raddb/dhcp and the dhcp-config.txt file is > raddb/sites-available/dhcp > > > > # Main conf - dhcp-config.txt > > server dhcp { > > client any { > ipaddr = 0.0.0.0 > #netmask = 0 > dhcp = yes > } > > listen { > ipaddr = * > port = 67 > type = dhcp > } > > dhcp DHCP-Discover { > update reply { > DHCP-Message-Type = DHCP-Offer > } > > switch "%{DHCP-Gateway-IP-Address}" { > > case 192.168.60.1 { > $INCLUDE dhcp/pool_system1 > } > > case 10.20.0.1 { > $INCLUDE dhcp/pool_system2 > } > > case { > # Do not reply to DHCP requests from subnets > # which we are not authoriative > update reply { > DHCP-Message-Type !* 0 > } > do_not_respond > } > } > > # Global DHCP parameters > $INCLUDE dhcp/global > > dhcp_sqlippool > > if(notfound || noop) { > reject > } > > ok > } > > dhcp DHCP-Request { > update reply { > DHCP-Message-Type = DHCP-Ack > } > > switch "%{DHCP-Gateway-IP-Address}" { > > case 192.168.10.1 { > $INCLUDE dhcp/pool_system1 > } > > case 10.20.0.1 { > $INCLUDE dhcp/pool_system2 > } > > case { > # Do not reply to DHCP requests from subnets > # which we are not authoriative > update reply { > DHCP-Message-Type !* 0 > } > do_not_respond > } > } > > # Global DHCP parameters > $INCLUDE dhcp/global > > dhcp_sqlippool > > if(notfound || noop) { > reject > } > > ok > } > > dhcp DHCP-Inform { > } > > # If there's no named section for the packet type, then the packet > # is processed through this section. > dhcp { > # send a DHCP NAK. > reject > } > } > > # End main conf > > # Global Conf > # ./dhcp/global.conf > update reply { > DHCP-Domain-Name-Server = 8.8.8.8 > DHCP-Domain-Name-Server += 8.8.4.4 > DHCP-Domain-Name = "mydomain.com" > DHCP-DHCP-Server-Identifier = <dhcp-server-ip> > } > > # System 1 devices - Cable Modems > # ./dhcp/pool_system1.conf > if(DHCP-Vendor-Class-Identifier =~ /^docsis[1-2].*$/){ > update control { > Pool-Name := 'system_pool1' > } > } > > # System 2 devices > # ./dhcp/pool_system2.conf > if(DHCP-Vendor-Class-Identifier){ > update reply { > DHCP-Subnet-Mask = 255.255.255.0 > DHCP-Router-Address = 10.20.0.1 > DHCP-Broadcast-Address = 10.20.0.255 > DHCP-IP-Address-Lease-Time = 3600 > } > update control { > Pool-Name := 'system_pool2' > } > } > > > > > On 03/10/2014 12:38 PM, Alan DeKok wrote: > > Vyacheslav Maliev wrote: > >> Hello! I`ve tried to configure my freeradius installation like described > >> here http://wiki.freeradius.org/guide/dhcp-for-static-ip-allocation > >> but it`s very simple case for only one subnet. Now we have two networks > >> which needs to get IP by DHCP server. So is there any possibility to > >> configure DHCP scopes for different networks? Thanks! > > Yes. It's not as easy as with a dedicated DHCP server. You'll need > > to split the packets, so that some use subnet A, and some use subnet B. > > Look at the packets (radiusd -X) to see how they're different. Usually > > there will be a gateway IP address different, or perhaps something else. > > > > It's probably best to use groups to assign the network parameters. > > e.g. use the radgroupcheck and radgroupreply tables. For users in group > > A, assign them options for network A, and users in group B should be > > assigned options in network B. > > > > i.e. separate the *common* configuration into group parameters. Thenm > > each user should have only user-specific parameters. e.g. an IP > > address, and a group membership. > > > > For v3.1, we're looking at maybe coming up with DHCP-specific queries > > for SQL. But getting help from other people would be useful, too. > > > > Alan DeKok. > > > > - > > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > > > >

1 0

RE: Freeradius-Users Digest, Vol 107, Issue 36
by Hangi Christian 11 Mar '14

11 Mar '14

Hi Alan,Thank you for your help. I've already run the radtest command as a regular user using debugging mode and I had this issue : $radclient: dict_init: Couldn't open dictionary "etc/raddb/dictionary" : Permission denied . I want to know how to solve this problem. With regards, Christian. > From: freeradius-users-request(a)lists.freeradius.org > Subject: Freeradius-Users Digest, Vol 107, Issue 36 > To: freeradius-users(a)lists.freeradius.org > Date: Mon, 10 Mar 2014 09:56:18 +0100 > > Send Freeradius-Users mailing list submissions to > freeradius-users(a)lists.freeradius.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freeradius.org/mailman/listinfo/freeradius-users > or, via email, send a message with subject or body 'help' to > freeradius-users-request(a)lists.freeradius.org > > You can reach the person managing the list at > freeradius-users-owner(a)lists.freeradius.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Freeradius-Users digest..." > > > Today's Topics: > > 1. Authentication on the basis of circuit id and not mac address > (Mahima Kumar) > 2. Authorise based on Calling Station ID ? (Darren Ward (darrward)) > 3. Testing an access-request user without the debugging mode > (Hangi Christian) > 4. Re: Testing an access-request user without the debugging mode > (A.L.M.Buxey(a)lboro.ac.uk) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 9 Mar 2014 08:51:51 -0600 > From: Mahima Kumar <mahima(a)ualberta.ca> > To: freeradius-users(a)lists.freeradius.org > Subject: Authentication on the basis of circuit id and not mac address > Message-ID: > <CADOyXPg+1pxy90Dur+Pf6MxmJt3TBUHuo5oyuJvwA_y04uappw(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi , > > I have used an Alcatel router as relay agent which gives the circuit id and > i can see that in the radius debug output, so the client is getting > authenticated on the basis of mac address and is getting the ip address > from the Dhcp server , now i want to authenticate the client based on the > circuit id provided by the relay agent in between, but the radius server > doesn't accept username as circuit id, it only authenticates based on mac > address of the client(i tried changing the users file), so can anyone > please guide me as to what changes i have to make for this to be possible. > > TIA > > > Regards, > Mahima >

2 2

NAS clients ignored...not sure where to go
by Ryan Milton 11 Mar '14

11 Mar '14

3 2

Old school: FreeRADIUS and NIS
by Mark Haney 10 Mar '14

10 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I know it's throwback to the '90s, but my boss wants it done, so I need to do it. I /cannot/ find any documentation on setting up FreeRADIUS with NIS authentication. Does someone have some lying around somewhere? I've googled the Web as well as the Mail Archive and I got precisely two items out of a good 4 hours of searching. 1. I need to set DEFAULT Auth-Type = System 2. The only list post about NIS (from 2002) mentions using rlm_unix....and nothing else. I'm not new to linux, just FreeRADIUS. I'm know it seems silly to set this up using NIS, but we use it in house (for now) and my boss wants it done 'yesterday' and I don't have the time at the moment to migrate everything to LDAP. That's in the works, but he doesn't want to wait for the switch to LDAP before getting this working. Help! - -- Mark Haney Network/Systems Administrator Practichem W: (919) 714-8428 Fedora release 20 (Heisenbug) 3.13.4-200.fc20.x86_64 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTGe2IAAoJEM/YzwEAv6e7ki0H/3l4UG/TBOeNaBPLSmmySgY3 RvnR7G33NzcPTJmwlOQXDnVhUbm0aRo9/ptfw+1ZQBbwxmrfl7j5HaXkoYhyQmxG ZL+uFdRZ26YzTxHq8pGVcvp+XVhHiQcTcKvNspeVEiM1QRgFAT2GBKFiv57etmoz ihKC4+gv699cs3By7474uTYAkWaPVUMeveFnuL81QPMLHE+Z4SDC+i5T2QRDaIz/ AfUWwzZsvJfeInn35Vsx7YLd1JUBoZHNk9l/gC7d7v/HQ7nPEEa2Uv05j7uJXXBW FE9O/Xjryndz4jovy3McR1ldOs+k5vRpxmO+YVebAb/PtMImBp7TVVLQkICsblc= =c6jI -----END PGP SIGNATURE-----

7 20

Not trivial configuration of Freeradius as DHCP server
by Vyacheslav Maliev 10 Mar '14

10 Mar '14

Hello! I`ve tried to configure my freeradius installation like described here http://wiki.freeradius.org/guide/dhcp-for-static-ip-allocation but it`s very simple case for only one subnet. Now we have two networks which needs to get IP by DHCP server. So is there any possibility to configure DHCP scopes for different networks? Thanks!

4 3

update : Re: Authentication on the basis of circuit id and not mac address
by Mahima Kumar 10 Mar '14

10 Mar '14

Hello Alan, Thanks for your reply. To be more specific i can tell you my scenario. client---switch---alcatel(dhcp relay agent)---freeradius and dhcp server The dhcp relay agent is generating a circuit id which i can see in the debug output, it is a hex string beginning from 0x as well as the dhcp agent remote id is visible as a hex string. Now i am putting the username format in the alcatel as mac address and i have no problem in authenticating the client from the radius server on the basis of mac address and dhcp server is giving ip address to the client. But my goal is to authenticate my client on the basis of this circuit id which is being generated by the alcatel dhcp relay agent , and hence provide ip address to the client on from the dhcp server. As i change the username format to circuit-id in the alcatel relay agent, the authentication fails as the debug output in alcatel shows the username format implies circuit-id. I am actually implementing the Alcatel Triple Play ESM scenario(alcatel also has IES and VPLS running on it), but instead of a dslam or any other relay agent i have to use the alcatel router only as the dhcp relay agent. Also i would like to know what changes i have to make in the users file or dhcp-static file or default file or radcheck, so as to do the client authentication based on the cirucit id being generated. (I tried to make a few changes but nothing works for me). Goal is : Authentication of client from radius server on the basis of circuit id and assigning ip address to the client from the dhcp server. Thanks in advance. On Mon, Mar 10, 2014 at 10:23 AM, < freeradius-users-request(a)lists.freeradius.org> wrote: > Send Freeradius-Users mailing list submissions to > freeradius-users(a)lists.freeradius.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freeradius.org/mailman/listinfo/freeradius-users > or, via email, send a message with subject or body 'help' to > freeradius-users-request(a)lists.freeradius.org > > You can reach the person managing the list at > freeradius-users-owner(a)lists.freeradius.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Freeradius-Users digest..." > > > Today's Topics: > > 1. Re: Authorise based on Calling Station ID ? (Alan DeKok) > 2. Re: Authentication on the basis of circuit id and not mac > address (Alan DeKok) > 3. Re: your mail (A.L.M.Buxey(a)lboro.ac.uk) > 4. Re: Old school: FreeRADIUS and NIS (Mark Haney) > 5. Re: Old school: FreeRADIUS and NIS (Alan DeKok) > 6. Re: Old school: FreeRADIUS and NIS (Phil Mayers) > 7. Re: Old school: FreeRADIUS and NIS (Mark Haney) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 10 Mar 2014 08:10:31 -0400 > From: Alan DeKok <aland(a)deployingradius.com> > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Subject: Re: Authorise based on Calling Station ID ? > Message-ID: <531DABB7.50105(a)deployingradius.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Darren Ward (darrward) wrote: > > The mac address was sent by the wifi controller as the > > calling-station-id but the question is how do I match that field against > > the user to authorise them? > > $ man unlang > > It tells you how to do if/then/else checks. > > Perhaps you have a more specific question? > > Alan DeKok. > > > ------------------------------ > > Message: 2 > Date: Mon, 10 Mar 2014 08:33:25 -0400 > From: Alan DeKok <aland(a)deployingradius.com> > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Subject: Re: Authentication on the basis of circuit id and not mac > address > Message-ID: <531DB115.70109(a)deployingradius.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Mahima Kumar wrote: > > I have used an Alcatel router as relay agent which gives the circuit id > > and i can see that in the radius debug output, so the client is getting > > authenticated on the basis of mac address and is getting the ip address > > from the Dhcp server , now i want to authenticate the client based on > > the circuit id provided by the relay agent in between, > > First, does the circuit ID show up in a RADIUS packet? If so, what > attribute is it? > > > but the radius > > server doesn't accept username as circuit id, it only authenticates > > based on mac address of the client(i tried changing the users file), so > > can anyone please guide me as to what changes i have to make for this to > > be possible. > > I'm not sure what you're trying to do, so I don't have a good answer > for you. > > What does debug output say? What do you think it *should* say? > > Alan DeKok. > > > ------------------------------ > > Message: 3 > Date: Mon, 10 Mar 2014 13:54:26 +0000 > From: A.L.M.Buxey(a)lboro.ac.uk > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Subject: Re: your mail > Message-ID: <20140310135426.GC3021(a)lboro.ac.uk> > Content-Type: text/plain; charset=us-ascii > > Hi, > > > I'd like to install on FreeBSD 9.2 > > FreeRadius2 with MySQL > > which bits of http://wiki.freeradius.org/guide/SQL-HOWTO did you > follow, which bits didnt work? > > alan > > > ------------------------------ > > Message: 4 > Date: Mon, 10 Mar 2014 10:03:55 -0400 > From: Mark Haney <mhaney(a)practichem.com> > To: <freeradius-users(a)lists.freeradius.org> > Subject: Re: Old school: FreeRADIUS and NIS > Message-ID: <531DC64B.4010806(a)practichem.com> > Content-Type: text/plain; charset="ISO-8859-1" > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > On 03/07/14 16:00, Alan DeKok wrote: > > >> The only thing I've changed in the config files is to add the > >> DEFAULT Auth-Type = System at the top of the users file. > > > > Which I don't recommend you do. > > > > Anyawyas, debug mode shows: > > > > ++[unix] returns notfound > > > > Which is pretty definitive. > > Okay, what would recommend then? And the ++[unix] returns notfound is > definitive of /what/? > > Since I'm setting up FreeRADIUS on my NIS master, I don't really need > NIS integration, the user accounts are all in /etc/passwd (and > /etc/shadow) so all I need is radiusd to check for local accounts and > authenticate against them. This /should/ simplify things, but > apparently I'm missing something, and something probably relatively > simple. Question is, what? > > > - -- > Mark Haney > Network/Systems Administrator > Practichem > W: (919) 714-8428 > Fedora release 20 (Heisenbug) 3.13.4-200.fc20.x86_64 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJTHcZEAAoJEM/YzwEAv6e7VfIH+gLyCl0i8wJg8yrNRh93PUKG > tuKKRyelWUur6p1Hem/G3LtEBkczbfPw1Mk1mD0McWmrH58lMoFccnFp3KF//QF7 > NNBBrbbtkFLq0gdEUr7vr7ICXDqRKnrSSSh+zjOFZ5DwG4pSjhexqwgRZNw34prg > ddG6qsnVwktztIBuiXI05iWL1yqoTVveiXJCRcoOFMc1cKABt4tYR0y2/7QGmjT2 > DvfvhD3K+pDtO1HLwPOKay9D47AHSsRyvO64d1zfSVokt/7/FLbUuHtoZ9lXK5uH > BjteP//mlE017d848wHF5PzmYXIPQhT3ANQ274TB/Q9wPalhx/7KMd+WN6CvHeA= > =QgVT > -----END PGP SIGNATURE----- > > > > ------------------------------ > > Message: 5 > Date: Mon, 10 Mar 2014 10:21:05 -0400 > From: Alan DeKok <aland(a)deployingradius.com> > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Subject: Re: Old school: FreeRADIUS and NIS > Message-ID: <531DCA51.6070309(a)deployingradius.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Mark Haney wrote: > >> ++[unix] returns notfound > > > >> Which is pretty definitive. > > > > Okay, what would recommend then? And the ++[unix] returns notfound is > > definitive of /what/? > > Uh.... the module looks users up in /etc/passwd. What could > "notfound" possibly mean? > > > Since I'm setting up FreeRADIUS on my NIS master, I don't really need > > NIS integration, the user accounts are all in /etc/passwd (and > > /etc/shadow) so all I need is radiusd to check for local accounts and > > authenticate against them. This /should/ simplify things, but > > apparently I'm missing something, and something probably relatively > > simple. Question is, what? > > The user isn't in /etc/passwd. > > Alan DeKok. > > > ------------------------------ > > Message: 6 > Date: Mon, 10 Mar 2014 14:33:55 +0000 > From: Phil Mayers <p.mayers(a)imperial.ac.uk> > To: freeradius-users(a)lists.freeradius.org > Subject: Re: Old school: FreeRADIUS and NIS > Message-ID: <531DCD53.9080402(a)imperial.ac.uk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 10/03/14 14:03, Mark Haney wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > > > On 03/07/14 16:00, Alan DeKok wrote: > > > >>> The only thing I've changed in the config files is to add the > >>> DEFAULT Auth-Type = System at the top of the users file. > >> > >> Which I don't recommend you do. > >> > >> Anyawyas, debug mode shows: > >> > >> ++[unix] returns notfound > >> > >> Which is pretty definitive. > > > > Okay, what would recommend then? And the ++[unix] returns notfound is > > definitive of /what/? > > rlm_unix has a flow like this: > > r = getpwnam(username) > if not r: > return NOTFOUND > if not r.passwd or len(r.passwd) < 10: > s = getspnam(username) > if not s: > return NOTFOUND > passwd = s.passwd > else: > passwd = r.passwd > > So, either FreeRADIUS is getting no reply to getpwnam() or it's getting > an empty or "x" value for the password hash at that stage, *then* > calling getspnam() and getting no value. > > My NIS is rusty, but IIRC calling the getspnam() routines under NIS > requires you being root? Most likely this is the problem. > > PAM has a suid-root helper for this; FreeRADIUS doesn't. So one possible > alternative would be to use rlm_pam, and let PAM do the work of getting > at the shadow data. > > > ------------------------------ > > Message: 7 > Date: Mon, 10 Mar 2014 12:23:29 -0400 > From: Mark Haney <mhaney(a)practichem.com> > To: <freeradius-users(a)lists.freeradius.org> > Subject: Re: Old school: FreeRADIUS and NIS > Message-ID: <531DE701.5090606(a)practichem.com> > Content-Type: text/plain; charset="ISO-8859-1" > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > On 03/10/14 10:33, Phil Mayers wrote: > > > > > rlm_unix has a flow like this: > > > > r = getpwnam(username) if not r: return NOTFOUND if not r.passwd or > > len(r.passwd) < 10: s = getspnam(username) if not s: return > > NOTFOUND passwd = s.passwd else: passwd = r.passwd > > > > So, either FreeRADIUS is getting no reply to getpwnam() or it's > > getting an empty or "x" value for the password hash at that stage, > > *then* calling getspnam() and getting no value. > > > > My NIS is rusty, but IIRC calling the getspnam() routines under > > NIS requires you being root? Most likely this is the problem. > > Le me re-iterate. Since I've installed FreeRADIUS on my NIS master, I > no longer care so much about dealing with NIS. At this stage, it's > simply a matter of getting FR and rlm_unix to see and access my local > user/pwd sitting in /etc/passwd and /etc/shadow. Surely, setting up > Fr for that is not /that/ complicated. So, forget about NIS. That is > not a problem. > > So, now that I have that out of the way, it seems rlm_unix isn't able > to read /etc/shadow. I'm assuming the getspnam(username) call is > trying to read /etc/shadow? If so, how is the best way to fix this? > I read somewhere that rlm_unix didn't need to copy the password files > into a temp file with radwtmp unless there was a specific reason for > it. What exactly is that all about? > > > - -- > Mark Haney > Network/Systems Administrator > Practichem > W: (919) 714-8428 > Fedora release 20 (Heisenbug) 3.13.4-200.fc20.x86_64 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJTHeb2AAoJEM/YzwEAv6e7EtsH/1DSyXULTwGN2Y4x/lvq/5cj > OYj585upGm0gZlNTEBjDYF1eJQw+S26bIhbogiaaWElBhnNE43K0iXnlJMxC3rwJ > ZRdoT5dQHufyOAFpDrg0GvR4BsnlSUlRzckBDGdFSsEtHHUtH0UU/ajuKo8JgXxZ > 4smQ1dl9dFY9A9xe7AI7MGMI76QAqTIuTREmEwfPVKl9HSsBHAFr64hzxsUc8TcE > 5GEizfXQv3XvTLsYuDCPRF2SxZr5ZpLi3Yuu/GLlC6Vl88qpNHgbPVf5rKw1NVMl > OhYFHSnz+pzgyAKJBg3Np5xoV1cvDYf0wQ3Kv0i1UwP3SF4r9RvdAPNjyyzjZJc= > =mS2E > -----END PGP SIGNATURE----- > > > > ------------------------------ > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > > End of Freeradius-Users Digest, Vol 107, Issue 38 > ************************************************* > > -- Regards, Mahima Kumar 1365962

2 1

None
by krylov＠ukr.net 10 Mar '14

10 Mar '14

Good day. I'd like to install on FreeBSD 9.2 FreeRadius2 with MySQL # radiusd -X ... rad_recv: Access-Request packet from host 1.2.3.4 port 15191, id=95, length=46 User-Name = "krylov" User-Password = "password" # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { rlm_sql (sql): Reserving sql socket id: 4 [sql] expand: -> [sql] Error generating query; rejecting user rlm_sql (sql): Released sql socket id: 4 ++[sql] = fail +} # group authorize = fail Using Post-Auth-Type REJECT WARNING: Unknown value specified for Post-Auth-Type. Cannot perform requested action. 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 95 to 1.2.3.4 port 15191 Waking up in 4.9 seconds. =-=-=-=-=-=-=-=-=-=-=-=-=-=- Radius can't create sql-query Please, help me. May be anybody nows where is examples or howto...

4 3