Bob McCormick [EMAIL PROTECTED] wrote:
If I include both of these lines:
DEFAULTFreeRADIUS-Proxied-To =* 127.0.0.1, Proxy-To-Realm := LOCAL
Hmm... I think that should have been !* instead of =*.
Then the myrealm radius server does receive a request from the proxy,
but issues the
Woohoo!!! I think I finally got it to work!
I put the following in the eap.conf file:
peap {
# The tunneled EAP session needs a default
# EAP type which is separate from the one for
# the non-tunneled
Hmmm.. I must be doing something wrong. With this config in the
users file:
DEFAULT Proxy-To-Realm := adt.com
Fall-Through = Yes
DEFAULT EAP-Type == PEAP, Proxy-To-Realm := LOCAL
Fall-Through = Yes
It *is* sending something to my home radius server, but the home
radius
Sorry, I guess my description was a little vague. I want to handle on
EAP types on the proxy radius server, but send the inner MS-CHAP
request to another radius server.
PEAP is the only one listed in my config right now just because it's
the only one I've been testing with (I'm trying to
I read the post quoted below, and it seemed to indicate that it should
be possible to get freeradius to handle PEAP or TTLS, and proxy the
inner MSCHAP request to another radius server. Has anyone ever got
this to work? I've tried, but I keep getting the following error
message:
WARNING:
Bob McCormick [EMAIL PROTECTED] wrote:
I read the post quoted below, and it seemed to indicate that it should
be possible to get freeradius to handle PEAP or TTLS, and proxy the
inner MSCHAP request to another radius server. Has anyone ever got
this to work? I've tried, but I keep getting
6 matches
Mail list logo