Artur Hecker wrote:
> > > in fact, in my authorize section EAP was the first module from the
> > > beginning on and in the authenticate section it is even the only one.
> >
> > If you're ever going to do System authentication, you'll need the
> > 'unix' module, too.
>
> but if not, i don't need it, right?
>
Yes. You don't need it.
>
> > > the error message after the reponse to the challenge is now:
> > >
> > > rlm_eap: Request found, released from the list
> > > rlm_eap: EAP_TYPE - md5
> > > rlm_eap: processing type md5
> > > rlm_eap_md5: No password configured for this user
> > >
> > > Do I have to configure something like EAP-Password in the user section?
> >
> > No. Hmm... maybe try 'User-Password :=' ???
>
> Tried that one, but no effect, the same behaviour.
>
>
> > Due to historical issues, the treatment of 'User-Password' in the
> > 'users' file is a little odd.
> >
> > Alan DeKok.
>
> My user definition looks like that: (etc/raddb/users)
>
> artur Auth-Type = System, User-Password == "hello"
> Reply-Message = "Hello, %u"
>
Try Auth-Type := EAP and remove eap in the authorize
and check if it works.
> i'm still using radius 0.5 and my sections look like that:
>
> authorize {
> preprocess
> eap
> suffix
> files
> }
>
or try eap as the last one in the above authorize block.
> authenticate {
> eap
> }
>
> any idea where this comes from?
The problem is that the configured User-Password is never picked
into the REQUEST->config_items VALUE_PAIR.
-Raghu
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
