Alan, Stefan
replying to myself:
using 'files' I've managed to make it work. the correct (working)
configuration is:
user_ttls FreeRadius-Proxied-To == "127.0.0.1", User-Password ==
"test_ttls"
Session-Timeout = 3600
user_ttls EAP-Type != EAP-TTLS
hi Alan
hi Stefan
thanks for your help. I think I understand the idea. however my problems
are on the implementation level.
two things are still not clear to me.
1. we use 'sql' and not 'files' (my fault i didn't mention it
previously) and thus I don't see how I can add the line below to m
Hi,
> what you are saying is that I should do something like this:
>
> user_ttls EAP-Type != PEAP
>
> that however only prohibits the usage of PEAP for user_ttls while i
> would like to only enable TTLS for this specific user (which is not
> quite the same).
Yes, however you s
Artur Hecker <[EMAIL PROTECTED]> wrote:
> user_ttls EAP-Type != PEAP
>
> that however only prohibits the usage of PEAP for user_ttls while i
> would like to only enable TTLS for this specific user (which is not
> quite the same).
user_ttls EAP-Type != TTLS, Auth-Type := Reject
See the
hi
[EMAIL PROTECTED] wrote:
we naively try to specify EAP-Type == PEAP for user_peap
and == TTLS for
user_ttls but that breaks both methods (which seems
normal since this
EAP-Type definition is not correct for the internal EAP
method which
however uses the same user name).
Why not almost j
Artur Hecker schrieb:
> we naively try to specify EAP-Type == PEAP for user_peap
> and == TTLS for
> user_ttls but that breaks both methods (which seems
> normal since this
> EAP-Type definition is not correct for the internal EAP
> method which
> however uses the same user name).
Why not almo
hi
we have a Wifi 802.1X network with both TTLS and PEAP users (TTLS/PAP
mostly for non-windows machines, PEAP/MSCHAPv2 for windows machines).
(we also have TLS users, but that's out of scope).
both work like a charm. however, we'd like to prevent PEAP accounts to
log in with TTLS and vice-
7 matches
Mail list logo
