profrxf
(usa Outra)
Enviado em 30/12/2011 - 19:13h
Estou implementando um servidor de autenticação Freeradius com lista de usuários em uma _base_ mysql.
Sempre que tento logar na rede sem fio, mesmo passando usuário e senha corretos o freeradius informa que está apresentando erro no login, conforme log abaixo.
Alguém já passou por isso?
Alguma sugestão ?
Inseri no mysql o usuário teste com senha teste.
Configurei o AP Dlink DI524 como WPA2(AES) e servidor RADIUS (ip, porta e senha).
Inseri este AP como cliente freeradius e as solicitações de autenticação estão chegando, porém não autentica.
Estou utilizando Debian 6.
Segue o log:
rad_recv: Access-Request packet from host 192.168.254.150 port 65477, id=98, length=159
User-Name = "teste"
NAS-Port-Type = Wireless-802.11
Called-Station-Id = "F0-7D-68-DE-61-36"
Calling-Station-Id = "00-17-C4-D5-BD-0C"
NAS-IP-Address = 192.168.254.150
_frame_d-MTU = 1400
State = 0xd1a6913dd7ae8861f8697a9f708854fd
EAP-Message = 0x020800261900170301001b4a99f77f99a0cd35053469923583b0298457602d93943dd80252ff
Message-Authenticator = 0x66668c3dbffce63e6dde5c47ed540a8f
# Executing section authorize from file /etc/freeradius/sites-enabled/default
+- entering group authorize {...}
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
++[digest] returns noop
[suffix] No '@' in User-Name = "teste", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
[eap] EAP packet type response id 8 length 38
[eap] Continuing tunnel setup.
++[eap] returns ok
Found Auth-Type = EAP
# Executing group from file /etc/freeradius/sites-enabled/default
+- entering 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] returns invalid
Failed to authenticate the user.
Login incorrect: [teste/] (from client ap port 0 cli 00-17-C4-D5-BD-0C)
Using Post-Auth-Type Reject
# Executing group from file /etc/freeradius/sites-enabled/default
+- entering group REJECT {...}
[sql] expand: %{User-Name} -> teste
[sql] sql_set_user escaped user --> 'teste'
[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}}', '%{replyacket-Type}', '%S') -> INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( 'teste', '', 'Access-Reject', '2011-12-30 18:44:58')
rlm_sql (sql) in sql_postauth: query is INSERT INTO radpostauth (username, pass, reply, authdate) VALUES ( 'teste', '', 'Access-Reject', '2011-12-30 18:44:58')
rlm_sql (sql): Reserving sql socket id: 0
rlm_sql (sql): Released sql socket id: 0
++[sql] returns ok
[attr_filter.access_reject] expand: %{User-Name} -> teste
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 19 for 1 seconds
Going to the next request
Waking up in 0.8 seconds.
Sending delayed reject for request 19
Sending Access-Reject of id 98 to 192.168.254.150 port 65477
EAP-Message = 0x04080004
Message-Authenticator = 0x00000000000000000000000000000000
Waking up in 2.9 seconds.
Cleaning up request 12 ID 91 with timestamp +579
Waking up in 0.1 seconds.
Cleaning up request 13 ID 92 with timestamp +579
Waking up in 0.1 seconds.
Cleaning up request 14 ID 93 with timestamp +579
Waking up in 0.1 seconds.
Cleaning up request 15 ID 94 with timestamp +579
Cleaning up request 16 ID 95 with timestamp +579
Waking up in 0.1 seconds.
Cleaning up request 17 ID 96 with timestamp +580
Waking up in 0.2 seconds.
Cleaning up request 18 ID 97 with timestamp +580
Waking up in 1.0 seconds.
Cleaning up request 19 ID 98 with timestamp +580
Ready to process requests.