Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

server with EAP enabled no longer starts #199

Closed
alanbuxey opened this issue Feb 17, 2013 · 4 comments
Closed

server with EAP enabled no longer starts #199

alanbuxey opened this issue Feb 17, 2013 · 4 comments

Comments

@alanbuxey
Copy link
Contributor

hi,

thought to be a transient issue during all the code changes...but still not operating after this weekends big updates.

when server runs, barfs out at rlm_eap module loading time with message like:

Module: Linked to sub-module rlm_eap_tls
Module: Instantiating eap-tls
tls {
tls = "tls-common"
type 5900650 not supported yet
}
rlm_eap: Failed to initialize type tls
/etc/raddb/mods-enabled/eap[17]: Instantiation failed for module "eap"
/etc/raddb/sites-enabled/default[447]: Failed to find "eap" in the "modules" section.
/etc/raddb/sites-enabled/default[447]: Failed to parse "eap" entry.

where type XXXXXXX not support yet line has a different value of XXXXXX each time (so its pointing to wierd places in memory....has there been a cross-over of 2.x code into 3.x ??? anyway, this WAS a 3.x config before a GIT update - so its not a 2.x config in play...

alan

@alandekok
Copy link
Member

Alan Buxey wrote:

when server runs, barfs out at rlm_eap module loading time with message
like:

Module: Linked to sub-module rlm_eap_tls
Module: Instantiating eap-tls
tls {
tls = "tls-common"
type 5900650 not supported yet
}
rlm_eap: Failed to initialize type tls
/etc/raddb/mods-enabled/eap[17]: Instantiation failed for module "eap"
/etc/raddb/sites-enabled/default[447]: Failed to find "eap" in the
"modules" section.
/etc/raddb/sites-enabled/default[447]: Failed to parse "eap" entry.

Use the "boilermake" build system. In fact, I'll go and delete the
old one. It's evil.

That message comes from conffile.c. It means that the config parser
thinks the "tls" entry is not ipaddr, string, integer, etc. The only
way that this can happen is a build error.

The old build system didn't do proper dependency checking. If
something changed in a header file, the modules might not be rebuilt.
The new build system works.

The canonical fix is to re-do "configure". I've made boilermake the
default. That will fix it.

@alanbuxey
Copy link
Contributor Author

interesting..this was with --enable-boilermake

anyway...about to get the latest code...wanna see all the colours! :-)

alan

@alanbuxey
Copy link
Contributor Author

fresh git clone, ./configure with the boilermake. same error. CentOS 5.9 on 32bit Linux.

full debug log doesnt show the tls-common stuff being loaded up

eap {
default_eap_type = "peap"
timer_expire = 60
ignore_unknown_eap_types = yes
cisco_accounting_username_bug = yes
max_sessions = 4096
}
Module: Linked to sub-module rlm_eap_gtc
Module: Instantiating eap-gtc
gtc {
challenge = "Password: "
auth_type = "kerberos"
}
Module: Linked to sub-module rlm_eap_tls
Module: Instantiating eap-tls
tls {
tls = "tls-common"
type 9271658 not supported yet
}
rlm_eap: Failed to initialize type tls
/etc/raddb/mods-enabled/eap[17]: Instantiation failed for module "eap"
/etc/raddb/sites-enabled/default[447]: Failed to find "eap" in the "modules" section.
/etc/raddb/sites-enabled/default[447]: Failed to parse "eap" entry.

(like the RED text BTW! ;-) )

alan

@alanbuxey
Copy link
Contributor Author

looks like it works now.

@arr2036 arr2036 closed this as completed Feb 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants