Artur Hecker wrote:
>
> hi
>
> > >Please change it as below
> > >
> > >artur Auth-Type := System, User-Password == "hello"
> > > Reply-Message = "Hello, %u"
> > >
> > >Please note the := before Sytem.
> >
> > I asked to change the operator('='), as it was causing the problem,
> > ie User-Password was never being picked up into the config_items.
>
> You mean that the "System" itself just doesn't matter at all in this
> context, don't you? So I can put in what I want? Is it ignored?
>
Yes. As long as your authorize block contains eap.
ie
authorize {
files,
eap
}
EAP module overwrites any other Auth-Type with EAP,
if present in authorize block.
> I'm currently trying to analyze what's happening with Ethereal, as you
> advised me. On which link would it be better to use Ethereal? On the
> wireless (between user and client) or on the wired? (between client and
> server?)
>
> I'm currently trying between server and client and I see the following
> in the Ethereal:
>
Server & Client.
Which version of Ethereal are you using?
Try the latest one, It can tell you the
EAP type and content in the Radius packets.
> ap -> server: Access Request(1) (id=11)
> server -> ap: Accounting challenge(11) (id=11)
> ap -> server: Access Request(1) (id=12)
> server -> ap: Access Reject(3) (id=12)
>
> then a sequence of ignored requests follows:
> ap -> server: Access Request(1) (id=13)
>
> As you know, the second Request is interpreted as a Notification message
> causing the reject...
>
> Which data would be interesting?
>
RADIUS/EAP data
1. with your old configuration
2. with Auth-Type := EAP
-Raghu
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
