Thanks for the tips guys. Been doing some more digging and learning a
lot... but maybe I should take a step back here and explain what I am
trying to accomplish
My client Ubiquity Nanostation only supports EAP-TTLS MSCHAPv2.
My NAS, only supports access-requests using PAP/CHAP passwords in
John Gammons wrote:
My client Ubiquity Nanostation only supports EAP-TTLS MSCHAPv2.
My NAS, only supports access-requests using PAP/CHAP passwords in clear-text.
What does that mean?
I am attempting to setup a Radius Proxy that terminates the EAP-TTLS
outer, and takes MSCHAPv2 inner
Sorry, by NAS I was referring to the Home Radius Server (guess my
terminology was incorrect), but I guess that answers the question
anyways.
John
On Thu, Jan 7, 2010 at 12:55 PM, Alan DeKok al...@deployingradius.com wrote:
John Gammons wrote:
My client Ubiquity Nanostation only supports
After doing some more digging, I think I am catching onto this... somewhat.
It sounds like I need to have the Radius Proxy, authenticate the Outer
Identity of the EAP-TTLS session locally, while the Inner Identity is
proxied to the Home Radius server.
I have setup the Outer identity to be
Hi,
After doing some more digging, I think I am catching onto this... somewhat.
It sounds like I need to have the Radius Proxy, authenticate the Outer
Identity of the EAP-TTLS session locally, while the Inner Identity is
proxied to the Home Radius server.
I have setup the Outer identity
John Gammons wrote:
After doing some more digging, I think I am catching onto this... somewhat.
It sounds like I need to have the Radius Proxy, authenticate the Outer
Identity of the EAP-TTLS session locally, while the Inner Identity is
proxied to the Home Radius server.
Yes.
I have
I am attempting to configure freeradius to terminate an 802.1x EAP-TTLS
authentication, but forward/proxy the user/pass to another radius server. I
can get it to standard proxy, and I can get it to function as a standalone
radius server with EAP-TTLS, but can't seem to find any good
7 matches
Mail list logo