> rlm_eap: Loaded and initialized type tls
> rlm_eap: Failed to link EAP-Type/peap: rlm_eap_peap.so: cannot open
> shared object file: No such file or directory
> radiusd.conf[9]: eap: Module instantiation failed.
Hi,
You must compile freeradius with rlm_eap. I dont know how do that in
suse :) Bu
Sorry for my all post :(
I set peap/eap/tls and i start freeradius but when user on laptop with
wifi want to auth. to radius over linksys, in log is:
rad_recv: Access-Request packet from host 192.168.1.245:3072, id=0,
length=167
User-Name = "lpa"
NAS-IP-Address = 192.168.1.245
Oki, i compile freeradius with tls eap, but now i have that problem when
i want start freeradius:
Tue Jan 16 13:49:16 2007 : Debug: Module: Loaded eap
Tue Jan 16 13:49:16 2007 : Debug: eap: default_eap_type = "tls"
Tue Jan 16 13:49:16 2007 : Debug: eap: timer_expire = 60
Tue Jan 16 13:49:16 2007
> Could you post this file ?
I have only:
eap {
default_eap_type = tls
tls {
tls_cacertfile = /etc/freeradius/cert/ca.pem
tls_certfile = /etc/freeradius/cert/radius.crt
tls_keyfile = /etc/freeradius/cert/radius.key
}
}
BR,
Rafal Kamins
Sic :(
I set eap with tls, because when i connect from PC i saw in debug TLS.
Then i set tls in eap, but when i started freeraius (freeradius -XXX -A)
i saw:
Error: rlm_eap: Failed to link EAP-Type/tls: rlm_eap_tls.so: cannot open
shared object file: No such file or directory
Error: radiusd.conf[
Hello,
I change my set and now i have that problem:
rad_recv: Access-Request packet from host 192.168.1.245:3072, id=0,
length=135
User-Name = "rka"
NAS-IP-Address = 192.168.1.245
Called-Station-Id = "001217694588"
Calling-Station-Id = "0014a41e7112"
NAS-Id
>
> Is 'eap' listed in our authorize section. It should be since this is an EAP
> request and Freeradius needs a way to set Auth-Type to EAP to proceed.
>
in authorize section i have:
authorize {
preprocess
eap
ldap
}
in auth section
authentication {
Auth-Type
7 matches
Mail list logo