- Freeradius-Users - lists.freeradius.org

stuck with no errors
by Joe Mom 17 Oct '07

17 Oct '07

K, i'm stuck. Running freeradius 1.1.6 I've got the passwd module working and i can see in the startup.log that its loading the file and settings. the file is in the format username:password the password is an md5 generated password I keep getting a rejected message from my radtests, but I dont see any message in the radius.log as to why. i need to know either, how to get a more verbose log so i can tell what it is i'm doing wrong or simply what is wrong with the statement: passwd pull_export { filename = /home/ftpuser/export.txt format = "*User-Name:Crypt-Password" } -- Regards Joe

3 4

Help(1.1.3): Access-Reject is sent by server for EAP-MD5 challenge response
by Govardhana K N 17 Oct '07

17 Oct '07

Hi, I am trying to send an Access-Request with EAP-Identity response. The Request was successful and Server sent an Access-Challenge in response (MD5 challenge), the response to this challenge is failing (receiving Access-Reject from Server), the Error message was "rlm_eap_md5: User-Password is required for EAP-MD5 authentication". I have the User-Password attribute in Access-Request. Below is the Access-Request packet attributes, -------------------------------------------------------------------------------- User-Name = jrc User-Password = jrc Nas-identifier = jrcnas Nas-Ip-Address = 10.10.10.10 Nas-Port = 20 Nas-Port-Type = 15 CUI = 0 Service-Type = Framed-User Framed-MTU = 1400 Calling-Station-Id = 1:1:1:1:1:1 NSP-Id = nap BS-ID = TestBS EAP-Code = Response EAP-Id = 210 EAP-Type-Identity = "jrc" EAP-MD5-Password = jrc Message-Authenticator = 0x00 -------------------------------------------------------------------------------- am I doing any wrong here? Can Anybody help me how to solve this problem? ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- rad_recv: Access-Request packet from host 127.0.0.1:32825, id=177, length=150 User-Name = "jrc" User-Password = "jrc" NAS-Identifier = "jrcnas" NAS-IP-Address = 10.10.10.10 NAS-Port = 20 NAS-Port-Type = Ethernet CUI = "0" Service-Type = Framed-User Framed-MTU = 1400 Calling-Station-Id = "1:1:1:1:1:1" NSP-ID = "nap" BS-ID = "TestBS" Message-Authenticator = 0x4cc4b9e9f807f7648ddb267ec1365cc6 EAP-Message = 0x02d20008016a7263 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "jrc", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: EAP packet type response id 210 length 8 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 0 users: Matched entry jrc at line 231 modcall[authorize]: module "files" returns ok for request 0 modcall: leaving group authorize (returns updated) for request 0 rad_check_password: Found Auth-Type EAP auth: type "EAP" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 0 rlm_eap: EAP Identity rlm_eap: processing type md5 rlm_eap_md5: Issuing Challenge modcall[authenticate]: module "eap" returns handled for request 0 modcall: leaving group authenticate (returns handled) for request 0 Sending Access-Challenge of id 177 to 127.0.0.1 port 32825 CUI = "TestCUI2" Service-Type = Framed-User Framed-Protocol = PPP Framed-IP-Address = 172.31.128.112 Framed-IP-Netmask = 255.255.255.0 Framed-MTU = 1400 AAA-Session-Id = "MultiSessionId2" MSK = "TestMSK2" HA-IP-MIP4 = 1.2.3.5 DHCPv4-Server = 5.6.7.9 MN-HA-MIP4-KEY = "TestMIPKey2" MN-HA-MIP4-SPI = "TestMIPSPI2" DHCP-RK = "TestDHCPRK2" DHCP-RK-KEY-ID = "TestDHCPRKID2" DHCP-RK_LIFETIME = 30 EAP-Message = 0x01d300160410f492fb48923219d8c9760b271cf4e031 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x467be2cc5938e30e368d1633e8ebd4fd Finished request 0 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... rad_recv: Access-Request packet from host 127.0.0.1:32825, id=178, length=182 User-Name = "jrc" User-Password = "jrc" NAS-Identifier = "jrcnas" NAS-IP-Address = 10.10.10.10 NAS-Port = 20 NAS-Port-Type = Ethernet CUI = "0" Service-Type = Framed-User Framed-MTU = 1400 Calling-Station-Id = "1:1:1:1:1:1" NSP-ID = "nap" BS-ID = "TestBS" Message-Authenticator = 0x7c3e1b2a25d10ce176811099e6ea64a3 State = 0x467be2cc5938e30e368d1633e8ebd4fd EAP-Message = 0x02d300160410d879a36a071bbf8d1111a598184dbe22 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 1 modcall[authorize]: module "preprocess" returns ok for request 1 modcall[authorize]: module "chap" returns noop for request 1 modcall[authorize]: module "mschap" returns noop for request 1 rlm_realm: No '@' in User-Name = "jrc", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 1 rlm_eap: EAP packet type response id 211 length 22 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 1 users: Matched entry jrc at line 231 modcall[authorize]: module "files" returns ok for request 1 modcall: leaving group authorize (returns updated) for request 1 rad_check_password: Found Auth-Type EAP auth: type "EAP" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 1 rlm_eap: Request found, released from the list rlm_eap: EAP/md5 rlm_eap: processing type md5 rlm_eap_md5: User-Password is required for EAP-MD5 authentication rlm_eap: Handler failed in EAP/md5 rlm_eap: Failed in EAP select modcall[authenticate]: module "eap" returns invalid for request 1 modcall: leaving group authenticate (returns invalid) for request 1 auth: Failed to validate the user. Login incorrect: [jrc] (from client localhost port 20 cli 1:1:1:1:1:1) Delaying request 1 for 1 seconds Finished request 1 Going to the next request Waking up in 6 seconds... rad_recv: Access-Request packet from host 127.0.0.1:32825, id=178, length=182 Sending Access-Reject of id 178 to 127.0.0.1 port 32825 EAP-Message = 0x04d30004 Message-Authenticator = 0x00000000000000000000000000000000 --- Walking the entire request list --- Waking up in 3 seconds... ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -- With Regards, Govardhana K N

6 8

problem in integeration with poptop
by hadi golestani 17 Oct '07

17 Oct '07

I've add that line and comment ntlm line but still some error( tnx god it's not the same error) my radtest syntax: radtest root rootpassword localhost.localdomain 1645 testing123 modcall[authorize]: module "files" returns ok for request 4 rlm_pap: WARNING! No "known good" password found for the user. Authentication may fail because of this. modcall[authorize]: module "pap" returns noop for request 4 modcall: leaving group authorize (returns ok) for request 4 rad_check_password: Found Auth-Type System auth: type "System" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 4 rlm_unix: [root]: invalid password i've attached radius.conf and users and output of debug mode for both radtest and vpn client. On 10/16/07, tnt(a)kalik.co.yu <tnt(a)kalik.co.yu> wrote: > > You have obviously done some work on breaking the server configuration. > Put mschap{} section back the way it was (with ntlm_auth line commented > out). You don't need *any* changes to the default configuration if you > are using users file. Put this in users file: > > root Clertext-Password := "rootpassword" > > Radtest will work and so will mschap (VPN). > > Ivan Kalik > Kalik Informatika ISP > > > Dana 16/10/2007, "hadi golestani" < hadi.golestani(a)gmail.com> piše: > > >I've change it to /usr/bin/ntlm_auth ( found from locate ntlm ) > >but still same error. > >What I must add to users file to test my radius from radtest or vpn > client? > > > >sorry for bothering I'm too newbie. > > > >On 10/16/07, tnt(a)kalik.co.yu <tnt(a)kalik.co.yu> wrote: > >> > >> Well path to ntlm_auth obviously isn't /path/to/ntlm_auth. > >> > >> Ivan Kalik > >> Kalik Informatika ISP > >> > >> > >> Dana 16/10/2007, "hadi golestani" <hadi.golestani(a)gmail.com > > pi�e: > >> > >> >hi, > >> >I've installed poptop and freeradius well and both are working, > >> >but when I try to connect from a vpn connection or even radtest some > >> error > >> >occured. > >> >what I need to add to users.conf for a simple radtest connection or a > vpn > >> >client? > >> > > >> >it's the output of debug mode for vpn client, some thing like this has > > >> been > >> >printed for radtest also: > >> > > >> > > >> >rad_recv: Access-Request packet from host 127.0.0.1:32770, id=30, > >> length=132 > >> > > >> > Service-Type = Framed-User > >> > Framed-Protocol = PPP > >> > User-Name = "root" > >> > MS-CHAP-Challenge = 0x4d1a9b1028ef83957754c83ce0f55e01 > >> > MS-CHAP2-Response = > >> > >> > >0x9e000d1394f73d58cc731cd6cf58de7cb74f00000000000000008c6daec89825fb28b90bb60b737fb683a4a80f6252935547 > >> > > >> > NAS-IP-Address = 127.0.0.1 > >> > NAS-Port = 0 > >> > Processing the authorize section of radiusd.conf > >> >modcall: entering group authorize for request 11 > >> > modcall[authorize]: module "preprocess" returns ok for request 11 > >> > modcall[authorize]: module "chap" returns noop for request 11 > >> > rlm_mschap: Found MS-CHAP attributes. Setting 'Auth-Type = mschap' > >> > modcall[authorize]: module "mschap" returns ok for request 11 > >> > rlm_realm: No '@' in User-Name = "root", looking up realm NULL > >> > rlm_realm: No such realm "NULL" > >> > modcall[authorize]: module "suffix" returns noop for request 11 > >> > rlm_eap: No EAP-Message, not doing EAP > >> > modcall[authorize]: module "eap" returns noop for request 11 > >> > users: Matched entry DEFAULT at line 152 > >> > users: Matched entry DEFAULT at line 171 > >> > users: Matched entry DEFAULT at line 183 > >> > modcall[authorize]: module "files" returns ok for request 11 > >> >modcall: leaving group authorize (returns ok) for request 11 > >> > rad_check_password: Found Auth-Type MS-CHAP > >> >auth: type "MS-CHAP" > >> > Processing the authenticate section of radiusd.conf > >> >modcall: entering group MS-CHAP for request 11 > >> > rlm_mschap: No User-Password configured. Cannot create LM-Password. > >> > rlm_mschap: No User-Password configured. Cannot create NT-Password. > >> > rlm_mschap: Told to do MS-CHAPv2 for root with NT-Password > >> >radius_xlat: Running registered xlat function of module mschap for > string > >> >'Challenge' > >> > mschap2: 4d > >> >radius_xlat: Running registered xlat function of module mschap for > string > >> >'NT-Response' > >> >radius_xlat: '/path/to/ntlm_auth --request-nt-key --username=root > >> >--challenge=f1090a99b916ef69 > >> >--nt-response=8c6daec89825fb28b90bb60b737fb683a4a80f6252935547' > >> >Exec-Program: /path/to/ntlm_auth --request-nt-key --username=root > >> >--challenge=f1090a99b916ef69 > >> >--nt-response=8c6daec89825fb28b90bb60b737fb683a4a80f6252935547 > >> >Exec-Program output: Exec-Program: FAILED to execute > /path/to/ntlm_auth: > >> No > >> >such file or directory > >> >Exec-Program-Wait: plaintext: Exec-Program: FAILED to execute > >> >/path/to/ntlm_auth: No such file or directory > >> >Exec-Program: returned: 1 > >> > rlm_mschap: External script failed. > >> > rlm_mschap: FAILED: MS-CHAP2-Response is incorrect > >> > modcall[authenticate]: module "mschap" returns reject for request 11 > >> >modcall: leaving group MS-CHAP (returns reject) for request 11 > >> >auth: Failed to validate the user. > >> >Delaying request 11 for 1 seconds > >> >Finished request 11 > >> >Going to the next request > >> >--- Walking the entire request list --- > >> >Waking up in 1 seconds... > >> >--- Walking the entire request list --- > >> >Waking up in 1 seconds... > >> >--- Walking the entire request list --- > >> >Sending Access-Reject of id 30 to 127.0.0.1 port 32770 > >> >Waking up in 4 seconds... > >> >--- Walking the entire request list --- > >> >Cleaning up request 11 ID 30 with timestamp 47152198 > >> >Nothing to do. Sleeping until we see a request. > >> > > >> > > >> > >> - > >> List info/subscribe/unsubscribe? See > >> http://www.freeradius.org/list/users.html > >> > > > > > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html >

3 4

Re: Problem with LDAP and Groups
by Bryan Evege 17 Oct '07

17 Oct '07

________________________________ Message: 3 Date: Thu, 11 Oct 2007 23:23:45 +0100 From: <tnt(a)kalik.co.yu> Subject: Re: Problem with LDAP and Groups To: "FreeRadius users mailing list" <freeradius-users(a)lists.freeradius.org> Message-ID: <oQaIjLrO.1192141425.2493270.tnt(a)kalik.co.yu> Content-Type: text/plain; charset=ISO-8859-2 Read instructions in huntgroups file. Group devices in huntgroups: cisco NAS-IP-Address == a.b.c.d cisco NAS-IP-Address == a.b.c.e etc. linux NAS-IP-Address == z.y.x.w linux NAS-IP-Address == z.y.x.v etc. Add Huntgroup-Name to the DEFAULT entries: DEFAULT Huntgroup-Name == "cisco", Ldap-Group == "cisco_priv_15", User-Profile := "uid=cisco_priv_15,ou=profiles,ou=radius,dc=csctus,dc=net" You can leave out Auth-Type. These attributes will then be passed only when user logs in from a device in cisco huntgroup. For other entries Ldap group might match but huntgroup will not. Things get complicated if roles and devices overlap and you have two or more entries where both the group and hungroup will match. For instance, you wanted the same user in priv level 1 and 15 groups. You then have to add another level of distincion, like a realm/sufix/prefix. Ivan Kalik Kalik Informatika ISP Dana 11/10/2007, "Bryan Evege" <bryan(a)bevege.com> pi?e: >Message: 6 >> Date: Thu, 11 Oct 2007 21:13:21 +0100 >> From: <tnt(a)kalik.co.yu> >> Subject: Re: Problem with LDAP and Groups >> To: "FreeRadius users mailing list" >> <freeradius-users(a)lists.freeradius.org> >> Message-ID: <bS0cz6Hw.1192133601.8730890.tnt(a)kalik.co.yu> >> Content-Type: text/plain; charset=ISO-8859-2 >> >> >>> If I change the fall through to yes it still matches as many groups as the user is in. How can I tell freeradius which attributes to send back? >>> >> >> If you want to send sets of attributes according to the NAS user is >> trying to log into use huntgroups. >> >> >>> For example, bevege is a member of the following groups, packetshapper, cisco_priv_15, cisco_priv_1, linux. >>> >> >> Your group allocation is wrong. You can't have the same user(name) on >> the same device having priv levels 1 and 15. Pick one. Or have him log >> in as username@1 and username@15 and use realms to allocate correct set >> of attributes. >> >> Ivan Kalik >> Kalik Informatika ISP >> >> >Could you please explain a bit more. From what I understand you cannot >use Huntgroups to lookup what group a user is in. I only uses /etc/group >/etc/password. What I would like to do is this. User bevege logs in from >Cisco router. Have the users file somehow detect that the request has >come from a cisco router (by IP I would guess) then validate that the >user is in the correct group and then pass back the specific attributes >just for the cisco. Same thing for packetshapper etc. > >Thanks, > >Bryan > >- >List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > > Ok, this is driving me insane. I tried the way you suggested but here's the problem. User A is in the packeteer group, user B is in the packeteer_read_only group. Using the Huntgroup and users file below only allows user A (packeteer) to logon. User B doesn't work at all. If I reverse the order of the huntgroup file (packeteer_read_only first) then only user B can logon. This makes sense because which ever one is first in the huntgroups file matches and freeradius doesn't look any further. Isn't there a more detailed way to search the huntgroup? Or maybe I need to do better matching of the ldap group? I really need to get this working ASAP. Just a little background. We have about 10-15 users and about 20 devices of varying types. Some users (network operations) need read only access and some departments (network engineering) need full access to just about everything. Using NAS based huntgroups doesn't seem to work because only one group type can login, ie the first to match. Using just group based lookups doesn't work either unless the user is only a member of only one group, again the first one to match, which defeats the whole purpose of groups. I need to figure out a way to have user A in the packeteer group and user B in packeteer_read_only group and be able to have them both login to multiple devices with the appropriate access defined in LDAP. How on earth are companies with lots of devices and lots of different user access levels doing this? It can't be that hard. Any help would be greatly appreciated, I'm getting pressure to get this going ASAP. Huntgroups file packeteer NAS-IP-Address == 10.17.69.12 packeteer_read_only NAS-IP-Address == 10.17.69.12 Users file 162 DEFAULT Huntgroup-Name == "packeteer",Ldap-Group == Packeteer,User-Profile := "uid=packeteer,ou=profiles,ou=radius,dc=csctus,dc=net", Auth-Type := LDAP 163 Fall-Through = no 165 DEFAULT Huntgroup-Name == "packeteer_read_only",Ldap-Group == packeteer_read_only,User-Profile := "uid=packeteer_read_only,ou=profiles,ou=radius,dc=csctus,dc=net", Auth-Type := LDAP 166 Fall-Through = no

2 1

[Fwd: Re: rlm_perl (threads) performance question]
by Apostolos Pantsiopoulos 17 Oct '07

17 Oct '07

Alan DeKok wrote: > Apostolos Pantsiopoulos wrote: > >> I am using the rlm_perl module for accounting purposes. >> > ... > >> The results I get (after 2-3 k requests) are these : >> >> Mean time for acct start : 0.005 secs >> Mean time for acct stop : 0.01 secs >> >> Since there is a 1:1 ratio of start/stop requests I guess that we can >> say that >> for each request (regardless of its type) I should get a mean of 0.0075 >> secs. >> > > I don't think so. The start/stop requests do different things, so > it's not surprising that they have different mean times. > Yes it is not surprising, indeed. I just used them to find an approximate value for a "request" mean time so that we wouldn't have to distinguish between start and stop. That is not the problem though. My stop script does a lot more then my start, so that's explainable... > >> And this in turn should be giving about 130 req/sec. >> >> But I am not getting this kind of performance. >> I know that there is a handling overhead for each request. I don't know >> the exact >> percentage of this overhead but for simplicity's sake lets be >> pessimistic and >> consider it to be about 30%. >> > > You can measure the performance of the server externally, via a > client. Send the server a request, and wait for a response. Take the > difference, and that's the time required to process a request. > I did that. Actually it was the first thing I did. I got the same result. > Also, the server does a LOT more than just running Perl. You are > measuring the time taken to run your Perl scripts. The time taken to > process a request can be VERY different. > I just benchmarked the "internal" script just to see if the DB is the bottleneck. It is not. EVERY query did not take more than 0.03 secs ( thrice the size of the mean time) > >> Now the performance should be something like 80 req/sec. >> But I am not getting this kind of performance either. >> In fact, as soon as my main radius reaches a number of 50 req/sec my NAS >> starts sending requests to my backup radius. >> > > Likely because the RADIUS server is getting blocked, and not > responding to requests. That's usually because of a slow database. > See above... > >> If every perl clone can complete each request in X secs shouldn't 32 clones >> complete 1/X*32 requests per second? Or something similar to that? >> > > No. They may be competing for resources. The request rate is > affected strongly by requests that take a long time. In contrast, the > mean time per request is strongly affected by a large number of requests > that take a small amount of time. > Yes, I agree that they are competing for resources (and in this case the DB is the only resource, really). But when my server gets choked up shouldn't we expect to see big response times during the benchmark of the perl module? (e.g. running the same queries from an outside program I can get about 200 queries/sec from the DB , when my radiusd reaches the 50 r/s limit the DB idles at 10-24 q/s, so the DB does not seem to be the problem) > i.e. the mean time per request and the request rate are two VERY > different metrics. > > >> The problem does not seem to be the database. I made a simple >> program that uses the exact same code as my radius perl script does and >> I can get >> this kind of performance easily. >> > > There may be other things going on... > > Alan DeKok. > > Is there a way to "monitor" how many threads are actually at work (busy) at a given time? That could be really helpful... -- ------------------------------------------- Apostolos Pantsiopoulos Kinetix Tele.com Support Center email: apant(a)kinetix.gr, support(a)kinetix.gr Tel. & Fax: +30 2310556134 Mobile : +30 6937069097 MSN : apant2(a)hotmail.com WWW: http://www.kinetix.gr/ -------------------------------------------

5 7

Set freeradius attribute value
by yangcuilin 17 Oct '07

17 Oct '07

Hi, all I want to store a value in freeradius, and change it sometimes by radius request. I think there must be some attributes in freeradius which client can change or get its value by request. How can I implement it? Please give me some solutions or advice. Or give me some key points. Thanks very much. Rock

1 0

Re: Using freeradius and 802.1x for dynamic VLAN
by lvizcardof＠unsa.edu.pe 17 Oct '07

17 Oct '07

> you certainly arent checking that the VLAN is 2 - and if it isnt then fail > the authentication. i can understand what you are trying to do...but > do do THAT sort of thing you will need to use checking attributes, > not setting attributes. > > you should find that the port which carlos is attached to is being put onto > VLAN 2 is the config is correct. How do I know if my certificate checking that the vlan is 2 and why the authentication don't fail? What certificate i shoud use, so that valid the: carlos User-Password == "carlos" Service-Type = Framed-User, Tunnel-Type = VLAN, Tunnel-Medium-Type = IEEE-802, Tunnel-Private-Group-Id = 2 and if the user carlos access to the vlan 2, he can access, otherwise he doesn't access. But in my case the user carlos can access to any vlan. for example to vlan 3 or 4. Tell me what certificate I can to use that valid the Tunnel-Type and form it. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

3 3

rlm_passwd pulling file?
by Joe Mom 17 Oct '07

17 Oct '07

looking for some sort of indication that the radius.conf file is working. I've created a section in the radius.conf file under modules as per man rlm_passwd passwd tcovc_group { filename = /home/ftpuser/export.txt format = "*User-Name:LM-Password" delimiter = ":" } but either my hash is not working properly or its not pulling the user:passwords from the file. I checked in the startup.log file after doing a HUP and i dont see any indication that it pulled the data from the file. I also did a reboot of the system to be doubly sure. is there a spot that i can eliminate the possibility of the file not being pulled in or just a muck up my me :) -- Regards Joe

2 1

Freeradius logging w/syslog
by ballgyer＠mac.com 17 Oct '07

17 Oct '07

Hi all, I'm running freeradius 1.0.1 on CentOS 4.4 and I'm trying to get the radius to log to a syslog server. I followed the example "Syslog_HOWTO" but its not working. I was hoping that someone else might know the answer / fix. Thanks in Advance,

2 1

EAP+MD5+SQL trouble
by inl2goal 16 Oct '07

16 Oct '07

Hello, I am trying to configure freeradius with EAP/MD5+SQL support. I already followed all the SQL configuration procedures suggested in the SQL HOW TO, and the steps suggested in the EAP/MD5 HOW TO. However, for some reason when I try to authenticate from the NAS i get the following output in the server rlm_sql (sql): Released sql socket id: 3 modcall[authorize]: module "sql" returns ok for request 5 modcall[authorize]: module "eap" returns noop for request 5 modcall: leaving group authorize (returns ok) for request 5 auth: type Local auth: No User-Password or CHAP-Password attribute in the request auth: Failed to validate the user. Delaying request 5 for 1 seconds Finished request 5 Going to the next request --- Walking the entire request list --- Waking up in 1 seconds... --- Walking the entire request list --- Waking up in 1 seconds... --- Walking the entire request list --- Sending Access-Reject of id 13 to w.x.y.z port 21645 Waking up in 4 seconds... It appears that it finds the user in SQL but then it does not do anything in the EAP module. The log from the NAS says *Jun 1 00:04:25: %RADIUS-4-RADIUS_DEAD: RADIUS server a.b.c.d:16214,16215 is not responding. *Jun 1 00:04:37: %RADIUS-3-ALLDEADSERVER: Group radius: No active radius servers found. Id 12. I don't understand why it says it is dead if the server IS receiving the request. What I find weird is that when I do a radtest from the server it seems to find the user and password and sends an access-accept. I guess this would make sense since there is no EAP involved in this case, but still, I do not understand what is wrong in the rest of the configuration, as i have followed all steps in the HOW TOs. If anyone has an idea on what could be the problem i would appreciate the help. Thank you. Oskar -- View this message in context: http://www.nabble.com/EAP%2BMD5%2BSQL-trouble-tf4571786.html#a13049739 Sent from the FreeRadius - User mailing list archive at Nabble.com.

7 25