eap_sim_db_receive is not called

Alan DeKok aland at deployingradius.com
Sun Sep 18 11:38:04 EDT 2011

Jouni Malinen wrote:
> What exactly are you trying to achieve here? It would likely be easier
> to just run hostapd as an external process for the authentication and
> proxy the queries through FreeRADIUS. Blocking the thread while waiting
> for SIM parameters does not sound like a good solution

  Blocking RADIUS servers is never a good idea.

> and getting the
> re-process-previous-EAP-message mechanism working may require
> considerable amount of design changes within FreeRADIUS.

  It won't happen...

  Allowing the EAP module to wait for an external process *without*
blocking the server would also require major changes.

  Alan DeKok.

More information about the HostAP mailing list