(RADIATOR) Limit authentication method to PEAP

[Hugh Irvine]

Hello Leo -

As I can't find you in our database, could you please tell me the name 
of the organisation that has purchased this copy of Radiator?

Please reply to me directly.

In answer to your question, the example users file contains both the 
anonymous user and the real users, so in your case you should use 
different users files for the inner and the outer requests.

regards

Hugh


On 26 Mar 2004, at 11:17, Leonard Houer wrote:

> Hi all,
>
> Is it possible to limit authentication method to peap only?
> The sample eap_peap.cfg allows clients to connect with mschapv2 without
> peap tunneling.
> Is there a way to prevent this and force peap authentication?
>
> thanks,
>
> Leo
>
> --
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.